Hierarchy, Tree View, and Permissions

<p>We've been working on a big new feature set: improved handling of different levels of hierarchy and permissions in the admin site. The first release, pushed out a day or two ago, provides a couple of important enhancements over the existing method, first explained by Eric in <a href="http://libraryh3lp.blogspot.com/2008/05/hierarchy.html">May of last year</a>.<br /><br />To rundown the changes:<br /><br /><span style="font-weight: bold;">Tree View</span>, found in the users/queues area, gives the admin a graphical display of their system's hierarchy. Admins can see what users own what queues, and they can assign users as owners of queues. Drag and drop works, too. You can switch back to the default display by clicking Flat View.<br /><br /><span style="font-weight: bold;">Has Admin Rights</span> is a checkbox that will appear when a user is selected. Ticking that checkbox will give the selected user admin rights at the same permissions level as his or her "boss" one level up in the hierarchy.<br /><br />Why would you want to do this? Let's say you work at a large university, with several libraries. You have a top-level account called <span style="font-style: italic;">big-admin</span><span style="font-weight: bold;"> </span>registered with LibraryH3lp. <span style="font-style: italic;">Big-admin</span> can create users to act as admins of their own individual libraries at the university: <span style="font-style: italic;">main-library-admin</span>, <span style="font-style: italic;">law-library-admin</span>, <span style="font-style: italic;">health-library-admin</span>, etc... <span style="font-style: italic;">Big-admin</span> can create and assign queues to those mini-admins using Tree View, or the lower-level admins can create their own queues independently.<br /><br />When <span style="font-style: italic;">law-library-admin</span> logs into the admin site, they will only see queues that they themselves own, and they can create their own users to assign to their queues. They may also wish to share the task of running the chat system in the Law Library by assigning admin rights to one of their own users. This will grant that user the same permissions that they themselves have.<br /><br />This is also a good way to build a collaborative service spanning multiple institutions. If you have existing top-level admin sites that you'd like to put together, let us know, and we can do that manually.<br /><br />All of this can cascade through as many levels as you wish. As has always been the case, <span style="font-weight: bold;">ALL</span> operators <span style="font-weight: bold;">anywhere </span>in the hierarchy can transfer chats and IMs on queues to any other queue or operator within the same administrative domain (starting from the top-most level).<br /><br /><span style="font-weight: bold;">Things still to come: </span><br /><ul><li>Read-only access to reports and transcripts for ALL users on the queues to which they are assigned.</li><li>Write access to the transcripts/Monitor Activity area for "mini-admins" granted rights with the "has admin rights" function.<br /></li><li>Way for top-level admins to connect with other top-level admins in order to merge admin domains with no intervention from us.<br /></li></ul></p>

We've been working on a big new feature set: improved handling of different levels of hierarchy and permissions in the admin site. The ...

SMS Gateway Released

<p>We've just completed our first SMS gateway (with some help from Ron DuPlain at <a href="http://espresso-labs.com/">Espresso Labs</a>). We've been thinking about and working on this for <a href="http://libraryh3lp.blogspot.com/2008/11/sms-texting-services.html">awhile now</a>. The main thing we wanted in our gateway was the ability for patrons to text their library at a real phone number, as opposed to using a shortcode technique such as the AIM hack.<br /><br />We have been able to achieve this goal by working with Google's Android phone (T-Mobile G1). Since it has an open architecture and allows applications to run in the background, Eric has been able to write an application that is installed directly on the phone. The application intercepts SMS messages sent to the phone and redirects them to a LibraryH3lp queue, where they are then delivered just like other IMs on the system.<br /><br />We like a few things about this:<br /><ol><li>Patrons text a phone number and don't need to remember any shortcode tricks.</li><li>Libraries are fully responsible for their phone and texting package, which means...</li><li>LibraryH3lp fees do not need to increase one bit. This is just another gateway.</li><li>The phone's mobile number can be redirected to another line, such as a reference desk line, for voice communications, in case someone tries to call it rather than text it.</li><li>If you staff your service with our web client, you get a <a href="http://libraryh3lp.blogspot.com/2009/03/countdown.html">character countdown</a> when replying to texts, which is helpful in reducing the number of messages sent. (A long message will be broken down and sent as multiple SMS messages.)<br /></li></ol>Of course, libraries will need to secure the phone and make sure it doesn't run out of power.<br /><br />We believe the application works well, but this is our beta release. Currently, text messages sent when a gateway's queue is offline will not be delivered; these offline messages will get delivered soon, after a bit more work. The application is available for free in the Android Market now.<br /><br /><div style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyvRtkazLqHSmY0nKM9jf66vMuGs6J9V08OOtTce7Ed8XlJpKpUbJDvaDYM2gtaX6RBLeT6MpE_UT00xRMPB-3aiVy2wy-v-itqQ_OfmDmDw3RTPddwbpEWBwEdOv97GjqkgGHAtcLpCU/s1600-h/sms-gateway.jpg" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5313568756704404946" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgyvRtkazLqHSmY0nKM9jf66vMuGs6J9V08OOtTce7Ed8XlJpKpUbJDvaDYM2gtaX6RBLeT6MpE_UT00xRMPB-3aiVy2wy-v-itqQ_OfmDmDw3RTPddwbpEWBwEdOv97GjqkgGHAtcLpCU/s320/sms-gateway.jpg" style="cursor: pointer; width: 320px; height: 230px;" /></a><br /></div><br /><br />To setup an SMS gateway, start by installing the LibraryH3lp application on your G1. Go to the menu, click Settings, and give it a password (which can be anything). Then, go to the LibraryH3lp admin web site to define the gateway. This step is just like setting up any other gateway, just choose "sms", enter your ten-digit phone number as the username, and give it the same password you gave the phone. Finally, go back to your phone and click the "Start" button, and you're ready to start texting.<br /><br />Source code freely available on <a href="http://github.com/esessoms">Eric's Github</a>. The code will work with any Jabber server; it is not LibraryH3lp-specific.</p>

We've just completed our first SMS gateway (with some help from Ron DuPlain at Espresso Labs ). We've been thinking about and worki...

Countdown!

<p>There are a few unique challenges associated with trying to integrate a texting (SMS) service into an IM/chat reference workflow. Two of them are:<br /><ol><li>Attempting to keep responses relatively short. SMS tops out at 160 7-bit characters or 140 8-bit characters.<br /></li><li>Training librarians to notice when they have an SMS patron in the first place.</li></ol>Messages in excess of the character limits will be automatically split up into multiple messages, so going over the limit is not the end of the world, but SMS conversations flow more nicely if the librarian has an awareness of the limitations.<br /><br />Eric just added a nifty feature to the webchat client to help out with patrons sending messages from cell phones.<br /><br /><div style="text-align: center;"><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiWUhmoic8p0V5fx1Mtvphrhgo3q2ApiPkZtAevKzZtym54IRx9mTvFmj200sw_5tVyUV9uRUYJe8rcVbrrGW4A6rY9_f6JkW4myaK6qx3t5MXaxm7HUGwgOHlJHDtJ60WALFSaZyTc6Zg/s1600-h/sms-character-countdown.png" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5308740486977204450" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiWUhmoic8p0V5fx1Mtvphrhgo3q2ApiPkZtAevKzZtym54IRx9mTvFmj200sw_5tVyUV9uRUYJe8rcVbrrGW4A6rY9_f6JkW4myaK6qx3t5MXaxm7HUGwgOHlJHDtJ60WALFSaZyTc6Zg/s320/sms-character-countdown.png" style="cursor: pointer; width: 320px; height: 259px;" /></a><br /></div><br />When the librarian begins composing a message, a character countdown starting at 140 begins displaying in the top right corner of the window. You can also see from the normal routing information displayed in the top left corner that the patron is on a phone and contacted the pamq queue. If this wasn't a goofy test chat, you could have seen that they contacted your special reference queue, or your SMS queue, or whatever you've setup.<br /><br />[edited to add: The webchat client automatically detects phone numbers and applies the countdown display only then. It will not display with routine chats and IMs.]<br /><br />We're working on a new kind of SMS gateway, one that will let a patron text a phone number rather than using a short code like with the AIM hack. More news on that as it happens...</p>

There are a few unique challenges associated with trying to integrate a texting (SMS) service into an IM/chat reference workflow. Two of th...

Meebo.com: new suitable jabber client

<p>We don't usually update the blog when we change the <a href="http://code.google.com/p/libraryh3lp/wiki/SuitableJabberClients">documentation</a>, but this one is very exciting! It's now safe to monitor LibraryH3lp queues using the meebo.com website as the librarians' client. <br /><br />What happened? Did we pay them money? Negotiate with them in some way? Nope. All that has changed is that Meebo now more fully complies with <a href="http://www.xmpp.org/extensions/xep-0085.html">XEP-0085</a>, the Jabber standard that describes sending chat state notifications. In plain English, this means that Meebo's server will notify the LibraryH3lp server when librarians do things like close windows and sign out. The result is that patrons who begin a chat with Librarian A will not get lost in the ether if they go silent during a chat, and in the meantime, Librarian A signs off and Librarian B signs on. <br /><br />Now, Meebo.com won't have LibraryH3lp's special features like transfer, send file, and e-mail transcript integrated right into each chat window like our <a href="http://libraryh3lp.com/webchat">native librarians' webchat client</a> does. To do those extra things from Meebo, you'll have to follow the "chat management" link that starts each chat and sign into the LibraryH3lp server directly. You may also have other concerns with Meebo (ads, privacy), but it will work from a technical point of view. <br /><br />To sign in, simply use the Jabber login, with the lightbulb icon. The format for the login is <span style="font-weight: bold;">username@libraryh3lp.com</span>. Be sure to officially sign off, rather than just closing its browser window to end a shift, and you're good to go. It works with the Meebo Firefox plugin as well as the website.<br /><br />Hooray!</p>

We don't usually update the blog when we change the documentation , but this one is very exciting! It's now safe to monitor Library...

Growing Pains

<p>As many of you know, LibraryH3lp crashed last night. It was up again within minutes of our discovering it was down, but it's been so stable that this was quite a surprise. Eric has been investigating the cause, and it appears that the system is simply experiencing growing pains. This is normal, and it has happened before with different parts of the system. As LibraryH3lp gets busier, we find various limitations in different components and need to rework code in order to achieve greater levels of efficiency and scalability. <br /><br />The thing is, we expected to hit our next such phase this fall, with coding to prepare for it taking place over the summer. As it is, Eric needs to stop working on new features for now and instead work intensively over the next couple of weeks getting the system in shape for this next level of use. We will do our best to keep service disruptions to a minimum (and hopefully non-existent!).</p>

As many of you know, LibraryH3lp crashed last night. It was up again within minutes of our discovering it was down, but it's been so st...

New Reports Features

<p>In the admin interface, you'll find the <span style="font-weight: bold;">View Reports</span> tab has been improved. You can pick one, some, or all queues and get a chart and a CSV file of activity for any date range. There are also some handy controls for all reports:<br /><ol><li><span style="font-style: italic;">Ignore system messages</span>. System messages typically come from your gateways. They might say things like, "two unread messages" if the Gmail account for your Google Talk gateway has unread mail, or they might alert you that your AIM account was been signed in from another location.<br /></li><li><span style="font-style: italic;">Ignore not answered</span>. These are primarily cases where your patrons return to say "thanks" or "bye" after the librarian has closed their own window. Of course, they may also represent chats that truly were not answered because the patron left before a librarian answered (hopefully there aren't a lot of these on your queues).</li><li><span style="font-style: italic;">Minimum chat duration</span>. Use this to set the minimum threshold for how long a chat must last in order for it to register in your report. It defaults to 10 seconds. This lets you weed out, for example, chats where your patron returned with a "thanks" message and your librarian quickly fired off a "you're welcome" in return.</li></ol>In the case of the first two options, you probably don't want to count those as chats in your reports. <br /><br />In the case of the third, it may not be possible set the perfect threshold, but being able to set a minimum duration is quite helpful. In less-busy services, you can weed through your transcripts in the Monitor Activity tab and delete records of chats you don't want to count. Then you can run your reports on everything that is left, but this may become less practical with busier services.<br /><br />Here is an example of a chart; we're using the Google Charts API, so you can create a permalink. This chart shows traffic by month and by protocol for most of UNC-Chapel Hill's queues for May 2008 through today:<br /><br /><a href="http://chart.apis.google.com/chart?chs=600x400&chd=e:GRKbK8W-rdwkxuZqmBaf,DEGJGBE7KLLpNYGhGBFH,AIAQAMAMAUAkAcAMAYAI,AAAAAIAMAQAIAYAYAEAQ,AEAIAAAgAAAIAEAYAMAQ,AAAAAAAIAAAEAAAAAAAA&chco=000000,FF0000,00FF00,0000FF,00FFFF,FF00FF&chdl=web%7Caim%7Cyahoo%7Cgtalk%7Cmsn%7Cjabber&chxl=0:%7C0%7C20%7C40%7C60%7C80%7C100%7C120%7C140%7C160%7C180%7C200%7C220%7C240%7C260%7C280%7C300%7C320%7C340%7C360%7C380%7C400%7C420%7C440%7C460%7C480%7C500%7C520%7C540%7C560%7C580%7C600%7C620%7C640%7C660%7C680%7C700%7C720%7C740%7C760%7C780%7C800%7C820%7C840%7C860%7C880%7C900%7C920%7C940%7C960%7C980%7C1000%7C1:%7C5%2f08%7C6%2f08%7C7%2f08%7C8%2f08%7C9%2f08%7C10%2f08%7C11%2f08%7C12%2f08%7C1%2f09%7C2%2f09&chxt=y,x&cht=bvs" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" src="http://chart.apis.google.com/chart?chs=600x400&chd=e:GRKbK8W-rdwkxuZqmBaf,DEGJGBE7KLLpNYGhGBFH,AIAQAMAMAUAkAcAMAYAI,AAAAAIAMAQAIAYAYAEAQ,AEAIAAAgAAAIAEAYAMAQ,AAAAAAAIAAAEAAAAAAAA&chco=000000,FF0000,00FF00,0000FF,00FFFF,FF00FF&chdl=web%7Caim%7Cyahoo%7Cgtalk%7Cmsn%7Cjabber&chxl=0:%7C0%7C20%7C40%7C60%7C80%7C100%7C120%7C140%7C160%7C180%7C200%7C220%7C240%7C260%7C280%7C300%7C320%7C340%7C360%7C380%7C400%7C420%7C440%7C460%7C480%7C500%7C520%7C540%7C560%7C580%7C600%7C620%7C640%7C660%7C680%7C700%7C720%7C740%7C760%7C780%7C800%7C820%7C840%7C860%7C880%7C900%7C920%7C940%7C960%7C980%7C1000%7C1:%7C5%2f08%7C6%2f08%7C7%2f08%7C8%2f08%7C9%2f08%7C10%2f08%7C11%2f08%7C12%2f08%7C1%2f09%7C2%2f09&chxt=y,x&cht=bvs" style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer; width: 600px; height: 400px;" /></a><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />I can also download a CSV to bring the numbers into Excel; in the Reports interface, there is also a visualization tool kind of like a tag cloud, but without the tags:<br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxlhQKBMHm9UD1-isEPS0up7AID9GS-WPS-d7rJDn4RzZFfbMq0bdG5s3CzvPSGTPpL3h1aeHYJFZ8e15DqaWrDEmwwhI_zmI2F9ts3qhj7oQRsaPw-fX_3lPEOXKzCxfMgKPqKTljJnQ/s1600-h/csv.png" onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}"><img alt="" border="0" id="BLOGGER_PHOTO_ID_5303142412222450498" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjxlhQKBMHm9UD1-isEPS0up7AID9GS-WPS-d7rJDn4RzZFfbMq0bdG5s3CzvPSGTPpL3h1aeHYJFZ8e15DqaWrDEmwwhI_zmI2F9ts3qhj7oQRsaPw-fX_3lPEOXKzCxfMgKPqKTljJnQ/s320/csv.png" style="cursor: pointer; width: 320px; height: 178px;" /></a><br /><br />Remember: Besides this View Reports tab, you can also use the <span style="font-weight: bold;">Monitor Activity tab</span> to review transcripts, download transcripts in bulk, download a CSV file of all activity, delete system messages, delete transcripts, delete entire call histories. Use the <span style="font-style: italic;">Calendar Page</span> link to perform these actions over select queues and date ranges.<br /><br /><span style="font-weight: bold;">Note</span>: the information in Reports will normally be up to 24 hours old because of database caching. The information in Monitor Activity is accurate up-to-the-second.<br /><br />Have fun!</p>

In the admin interface, you'll find the View Reports tab has been improved. You can pick one, some, or all queues and get a chart and ...

Hardening the Gateways

<p>This weekend, we installed a big enhancement to the gateway system. All of the protocols besides Google Talk have been on libpurple. Before today, we ran one instance of libpurple for all of the non-gtalk protocols (AIM, Yahoo!, MSN, ICQ), and that was fine until fairly recently.<br /><br />With hundreds of gateways active on LibraryH3lp nowadays, libpurple performance was taking a hit. So, Eric had broken the libpurple protocols apart so that now, each protocol has its very own instance of libpurple. This should mean a number of good things:<br /><ol><li>Performance should improve now that no single libpurple instance is running so many gateways.</li><li>When a protocol change at the source (like MSN) means that a gateway needs programming work, we can just go ahead and work on it right away without worrying about disrupting the other gateways.</li><li>When a gateway is having some problem, we can restart it independently from the others. Restarts aren't a big deal, but they do cause accounts to briefly flicker offline and online again.</li></ol>Our libpurple gateway system has been open-sourced for a good while now, and this latest release has been updated at <a href="http://github.com/esessoms/purplegw/">Eric's github</a>. <br /><br />Happy Valentine's Day!</p>

This weekend, we installed a big enhancement to the gateway system. All of the protocols besides Google Talk have been on libpurple. Befor...