This is long-winded, I know, but hang with me, I’m trying to brainstorm.
So, here’s my situation (for those who might be unfamiliar):
One of my responsibilities at work is to maintain the catalog for a large public library consortium. It’s a pretty big catalog – 83 scopes, most of which have custom layouts so that each individual library can have its own interface and branding.
Not only that, but we have two servers for our catalogs – so we’re really maintaining two OPACs. One is for Staff, and can be accessed from within one of our member libraries only. This gives us a chance to present more search options, more detail, staff-specific incoming RSS feeds, links to staff resources, and a few staff-only functions. The public accesses a different catalog running on another server, so we can present them with something more suited to their needs.
Maintaining this is a huge job, but I think we do a pretty good job of keeping it going. However, I have had a challenge come up lately that I was trying to use a little creative problem solving to address.
Communication can be a challenge in any organization, and no more so than when there is a problem. I would like to find some new ways to use the Catalog as a way to communicate with staff in our libraries as well as patrons when there is a system issue they should be aware of. For many of our users, patrons and staff alike, the catalog is the main interface they interact with each day, and rather than trying to send them to other places to get information that they need about issues, I’d love to use the Catalog to put in right in their faces, so to speak.
But how do I do that in a reasonably sustainable way when I’m talking about such a huge entity as our two giant catalogs?
One brainstorm I had a while ago is this. (And I want to know what folks think.)
In a nutshell, I have set up two twitter accounts that I can feed into the OPAC display.
For our Staff Catalog, I created the account PALSstatus, and I embedded the most recent “tweet” so it displays at the bottom of the staff interface on every page of our catalog. (See the image below)

The idea is to keep this updated reasonably often with the most current status of the entire ILS, posting things that the staff would need to know about, such as “We are currently experiencing technical difficulties on the Public Catalog” or “The Circulation module is currently down. All transactions must be performed offline until further notice.” Stuff that would keep people in the loop in a real-time way, especially some of the front-line staff who sometimes feel left out of our information dissemination methods. More detailed information would be available through our ListServ or our Website, but at least folks working the desk would have some idea that it’s not just them.
Since it’s a twitter-based message, staff who wanted to could also follow PALSstatus for updates, and even get the updates texted to them, if they’re a department head or someone who really wants to be constantly informed of major problems. Not only is it easy to instantly update, we could use it to link staff to some of the online information we have available to them, and going back through the older “tweets” would give us an automatic log of what communication went out. So I see a lot of possible benefits to using this method to communicate with the staff in our libraries.
For the public, I set up a second twitter account, SuffolkLib, but thought I could handle it a little differently.
This time, I embedded the tweet so that it shows up at the top of the display on each page of the catalog. (This one currently is set up on our public catalog just for the full county scope- but I want to think about adding it in to all of the individual library scopes if we decide to go with this.)
(See image below.)

This one would only have a message if there was currently a problem. I have already used this once to announce to our patrons that the catalog was going to be down for maintenance on a certain evening. I “tweeted” a message that said “
When I typed that into Twitter, it appeared at the top of every page in the County Catalog. When the maintenance was over, I went to twitter and deleted the “tweet”. The message disappeared from the catalog. Simple as that.
However, I do have a few reservations about really launching this throughout our whole catalog and jumping right in to this. For one, I am concerned about impacting the performance of our catalog by using more things that must constantly refer to outside sites. We already do this for some other stuff, and I just don’t want to bog things down too much.
Another concern I have is something that seems to be coming up more and more with out libraries. I won’t go into the issue too much here (I think another post is in order!), but many of our libraries have their public catalog terminals locked down like Fort Knox, and are very hesitant to allow content from outside sites to come into the catalog. I guess the worst thing that this might cause is the few dedicated OPAC terminals in the libraries would not show the messages we publish this way. Staff (in most cases) and the public accessing the catalog from outside the building (most of them!) would see the messages.
I really need to play with this a bit more on our staging catalogs (oh, yeah, we have those, too!), and take some time to assess performance impact. But while I do some hard thinking about this, does anyone have any input they’d like to share? Is this just a dumb idea? Do you have other solutions for similar problems that you use in your libraries? Other concerns I haven’t mentioned? Other suggestions? I’d love to hear from people!
Tags:
catalog,
twitter