Besides the difficulty of managing ejournals and ebooks compared to print versions. Why is eresource management, keeping a accurate knowledge base etc is so hard?
|
|
Assuming one doesn't have a vendor ERM product, one must maintain or handle:
That's a lot. And I probably missed some things! |
|||||||||||
|
|
The main thing I find, aside from dsalo's list, is that you are working with virtual items rather than physical, which means your workflow must change to include more documentation of where you are in the process. If you subscribe to a print journal and it doesn't arrive when you expect it to, your ILS usually notifies you that it's late, and then you can do something about it. Not so with an ejournal. Usually it's your ILL or public services departments that notify you when you don't have access, unless you dedicate staff to checking every title on a regular basis. |
|||
|
|
|
One other thing that is different than handling physical items is that the various packages and aggregators present a moving target of titles and coverages. This is a part of daslo's #3 above. If you receive and checkin a journal issue, it stays on the shelf (or checked out) until you bind it or weed it. If you add holdings for "The Journal of Irreproducible Results" from a package or aggregator, then next year the package changes, that journal disappears. This is why large or serials-intensive libraries often use a third party service to track these changes and populate their knowledgebases and/or catalog holdings. Examples are Serials Solutions, Ex Libris SFX Knowledge Base, Worldcat knowledge base. These services allow librarians to say "We have package X" and lets the service keep track of what's actually in that package. |
|||
|
|