- they could be transferred;
- files could be shared between librarians and patrons;
- the patron's IP address and referring URL displayed to librarians in the webchat client;
- queues could have profile pages viewable via the webchat client; and
- transcripts could be stored in the admin site, with statistical reports also available.
This often led admins designing chat services to create a queue for each of their librarians, with exactly one librarian assigned to each queue. This way, chats targeted to those librarians would have all the extra flexibility associated with queues.
This practice has become especially prevalent in service rollover models, where chats are routed to a subject expert, if available, but will fall over to a general reference service if the expert is not available. With their very own queue, the subject expert could transfer their patron to another librarian or to another queue as needed.
That workaround was fine, but it created extra work for the local admin, and it increased the overall confusion level.
Today, we rolled out a series of fundamental behind-the-scenes changes that blur the line between individuals and queues where widget chats are concerned. Now, widget chats for individuals:
- can be transferred;
- will display patron's IP and referring URL in the webchat client; and
- allow file sharing between patrons and librarians.
There is still more work to do to further integrate this change into the admin site. Profile pages, transcript storage and statistics for individual widgets will become available in a later update.
A very important point: this change is only for chats using widgets. Direct IMs between librarians via the buddy list remain and will continue to remain private. They cannot be logged or transferred. Individuals should be buddied as email@example.com.
We'll be updating the docs to reflect this change. In the meantime, the preferred syntax for creating widgets for individuals AND queues is:
The old widget syntax for individuals (http://firstname.lastname@example.org) will continue to work.
We know it can be confusing for our existing users when we change fundamental concepts, but LibraryH3lp continues to be an evolving system undergoing improvements. This change should make life easier overall, especially for new users. We do not think that the change will break any existing code, and we hope that most librarians will welcome the new functionality.