TheoryOfOperation

From libraryh3lp

To use Pidgin4Lib, a library will need to allocate one well-known buddy name per protocol to be made available to the public. This is the dispatch ID. By way of example, we'll use refdesk on AOL and MSN.

The library will also need to allocate zero-or-more additional internal buddy names on any available protocol. For example, refstaff1 and refstaff2. These are operator IDs. The operator IDs do not need to be replicated by protocol, they only have to use known protocols. In this example, refstaff1 could be on AOL and refstaff2 on MSN. The account refstaff3 on Yahoo could not be used (in this example) because the dispatcher is not on Yahoo. See SetupConfiguration for more details.

One PC running the Pidgin4Lib plugin will need to be setup and logged in using the dispatch ID.

When a patron sends an IM to refdesk, the dispatcher will automatically forward that IM to each operator. In the example, chat windows will open simultaneously for refdesk, refstaff1, and refstaff2. It does not matter that the chat started on AOL, refstaff2 on MSN will still see it (and conversely).

At this point all three users will have an opportunity to respond to the chat. The first user to start typing "wins" the chat and will be connected to the patron. The chat windows on the other machines will close. This is all transparent to the patron who will see only a chat session with refdesk even if he or she is in fact working with refstaff2.

The session will be logged by the dispatcher so that record keeping is centralized.