Since we’ve just started with this project, I’m assuming there will be multiple posts on the topic. Well, that and the fact that I’m just a wee bit excited to be part of the group working on this. UCO will be the first library in Oklahoma to implement these ExLibris products (as far as we know — please let me know if otherwise), and it’s the first time I’ve gotten to be in on a largish technology implementation. It’s not like libraries get new ILSs every day, so I figure this is as close as I’ll get to something of that magnitude, at least for the foreseeable future.

Essentially, MetaLib is a federated search engine for electronic resources — a layer on top of SFX, which is our link resolver and A-Z list — while Primo takes the information from MetaLib and adds our catalog into the mix. I’m still fuzzy on specifics, and honestly will probably remain so until I have the opportunity to get in a play with these things from both the admin and the user ends.

But before we can get to that point I’ve got to contact all our e-resource vendors with the new IP address (since ExLibris is hosting MetaLib for us). Luckily, I had it poined out to me today that I can start with the vendors for the 50 test cases, which makes my immediate schedule somewhat less frightening as there’s some vendor overlap in the test resources (EBSCO, Proquest, CSA).

In addition to this, I’m going through a spreadsheet of MetaLib’s knowledge base, matching up our resources. One of our IT folks started the project, but everyone seems to like to use different names and/or naming conventions, so it has to be checked by hand. On the plus side, I’m going to have the names of our e-resources much more firmly implanted in my brain by the time it’s done.

Speaking of which, break’s over.