We're One Year Old Today!

<p>Today marks LibraryH3lp's first birthday, as measured from the <a href="http://libraryh3lp.blogspot.com/2008/01/call-for-testers.html">start of this blog</a>, which announced our intentions with the system and asked for testers. It's been a fantastic, if busy year, and a number of exciting things have come to pass. Besides adding lots of features mentioned elsewhere in the blog, there are a few other things worth mentioning.<br /><ul><li>Self-sufficiency. When we started, we knew we didn't want to have advertisements or data mining in order to generate revenue to pay for hosting; there was no grant source, venture capital, or investor other than Eric's small business. That left us with the idea of a <a href="http://code.google.com/p/libraryh3lp/wiki/Free_or_Fee_Full_Disclosure">nominal subscription fee</a>, since we could not afford to fund LibraryH3lp out of pocket indefinitely. A number of our busiest libraries have already stepped up and contributed with their subscription (thank you!). At this point, the system's current hosting fees are covered. Now, programming time is still mostly donated, with a very exciting exception in the form of...</li></ul><ul><li>Support from the state of North Carolina towards development of features needed by larger collaborative services. That's right, NC is funding some actual feature development (i.e., programming time), which is <span style="font-weight: bold;">very </span>much appreciated. So far, the main thing to show for this is the <a href="https://libraryh3lp.com/webchat">librarians' webchat client</a>. More reports, tag-for-followup, profile pages, and access-control lists are among funded features still to come. North Carolina, our home state, has always been good to us. After all, it was the freedom to experiment with, and the <a href="http://journal.code4lib.org/articles/107">technical challenges involved in</a>, chat and IM services at Duke University, North Carolina State University, and UNC-Chapel Hill that led to the development of LibraryH3lp in the first place.<br /></li></ul><ul><li>It's just working. Knock on wood, the system has been pleasantly stable and generally operates at very low load. We've had less than five minutes of downtime in the last three months. LibraryH3lp was engineered from the ground up for scalability and stability, and this has paid off.</li></ul><ul><li>Our first corporate partnership. <a href="http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fwww.altarama.com%2Frefchatter.htm&ei=bhx1SeG6LKKBtwf2uYzlCA&usg=AFQjCNEocShRlZhrcL1tAPLi-3zwCF7qMA&sig2=pqpbdqqo06yECEVudDLsmQ">Altarama's RefChatter</a> product remains available for those who require professional support, setup, and training. Options are good.</li></ul>But perhaps the most exciting thing for us has been witnessing the rate of adoption and the subsequent high use the system is receiving. At the peak of the Fall academic semester last October and November, there were about 600 chats and IMs on queues and probably about the same number in direct chats each day. We love to see that the system is getting put to good use.<br /><br />One small request: if you're using LibraryH3lp, please consider listing your library in the <a href="http://www.libsuccess.org/index.php?title=Online_Reference#Libraries_Using_libraryh3lp_for_Embedded_Chat">Library Success Wiki</a>. We occasionally are asked for a list of users, and because of our views on privacy, we don't share this information, but we love being able to point folks who ask to a user-generated list.<br /><br />Thank you for your support, and we look forward to this year!</p>

Today marks LibraryH3lp's first birthday, as measured from the start of this blog , which announced our intentions with the system and a...