{"id":85,"date":"2008-06-28T19:41:48","date_gmt":"2008-06-29T02:41:48","guid":{"rendered":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/?p=85"},"modified":"2008-06-28T19:41:48","modified_gmt":"2008-06-29T02:41:48","slug":"ala-2008-merging-print-and-e-serials-workflows-are-e-resources-really-different-from-print","status":"publish","type":"post","link":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/2008\/06\/ala-2008-merging-print-and-e-serials-workflows-are-e-resources-really-different-from-print\/","title":{"rendered":"ALA 2008: Merging Print and E-Serials Workflows &#8211; Are E-Resources Really different from Print"},"content":{"rendered":"<p>This session by Lila Angie Ohler from Maryland&nbsp; &#8211; she says &#8220;Libraries have done themselves a disservice by dealing with e-resources separately&#8221;<\/p>\n<p>Some myths about e-resources:<\/p>\n<ul>\n<li>Why worry &#8211; e-resources just take care of themselves right?<\/li>\n<ul>\n<li>Placing the order and paying the invoice is just hte beginning<\/li>\n<li>E-Resource do not remain &#8216;on the shelf&#8217; &#8211; access can drop or change<\/li>\n<\/ul>\n<li>E-Resource purchase require &#8216;special handling&#8217;<\/li>\n<ul>\n<li>Legacy from when e-resources were new<\/li>\n<li>Libraries built separate processes, and ended up with duplication and inefficient workflows<\/li>\n<li>Getting accurate access and information from vendors very difficult<\/li>\n<li>We ended up with unnecessary gatekeeper structures or special forms which prevent efficient subs management<\/li>\n<\/ul>\n<li>Moving to e-subs means no more print and saves costs<\/li>\n<ul>\n<li>Print has not gone away<\/li>\n<li>Most of the serials market place are still single titles<\/li>\n<li>More to do, not less<\/li>\n<\/ul>\n<li>E-Resources take less time and less staff resources<\/li>\n<ul>\n<li>Admin tasks for e-resources add on to print workflows, not replace them<\/li>\n<li>Many of these activities require input from professional librarians &#8211; meaning more expensive staff<\/li>\n<li>E-Resources staff spend the majority of their time reconciling serial data between different systems &#8211; this is NOT an automated process<\/li>\n<\/ul>\n<li>Only Librarians should manage e-resources<\/li>\n<ul>\n<li>Culture of &#8216;special handling&#8217; creates bottlenecks around specific staff<\/li>\n<li>By not training print serial staff fro new e-resource work, means retaining staff for diminishing work<\/li>\n<li>Junior staff can be more comfortable with online resources and technologies<\/li>\n<\/ul>\n<\/ul>\n<p>What has not changed?<\/p>\n<ul>\n<li>Acquisitions Data<\/li>\n<ul>\n<li>Acquisitiosn order and Purachse is (or should be) Record of authorig for all Library Purcahses<\/li>\n<li>Subs are still subs &#8211; e or p<\/li>\n<li>Title by title details are still the primary management unit &#8211; even if you buy them in packages<\/li>\n<\/ul>\n<li>Subs agents<\/li>\n<ul>\n<li>Vendors do work for you &#8211; e.g. renewals &#8211; still advantages over going with publishers<\/li>\n<li>Vendor reports help reconcile and track format changes, publisher changes, big deal titles lists<\/li>\n<ul>\n<li>This reminds me of a conversation about e-books and the fact that within packages we may get new editions etc. automatically added to the package &#8211; but the publishers are really bad at telling us &#8211; this type of service wasn&#8217;t mentioned by YBP or Coutts in this mornings session about e-books &#8211; they should look at it.<\/li>\n<\/ul>\n<\/ul>\n<\/ul>\n<p>So overall &#8211; what&#8217;s new?<\/p>\n<ul>\n<li>Licnesing<\/li>\n<li>Access Registration<\/li>\n<li>Access Activation Alerts<\/li>\n<li>Troubleshooting Access prolems<\/li>\n<li>Maintain link resolvers<\/li>\n<li>&#8230;<\/li>\n<\/ul>\n<p>Database maintentance<\/p>\n<ul>\n<li>Don&#8217;t try to do this all yourself manually &#8211; follow the 80\/20 rule &#8211; save time for truly unique resources &#8211; you can&#8217;t do everything &#8211; this is a different size of problem to the print world<\/li>\n<li>Link Resolver Knowledge Bases help, but are independent of the catalog and require constant update<\/li>\n<li>Look for other services in the market to help (e.g. PAMS and MARC)<\/li>\n<\/ul>\n<p>Serial Controls and Claims<\/p>\n<ul>\n<li>There are risks of leaving patrons to find the problems<\/li>\n<li>Troubleshooting access problems takes time &#8211; often outside the libraries control<\/li>\n<li>Adapt ILS servials controls for e-journals setting up a once or twice yearly &#8216;pattern&#8217; which generates daily &#8216;claim&#8217; lists<\/li>\n<li>From lists, staff found that 25% of those titles checked were not working properly &#8211; a shocking amount<\/li>\n<li>Note Lila not talking about aggregations here, which change too much to track reliably<\/li>\n<\/ul>\n<p>Serial Acquisitions and Subs Management<\/p>\n<ul>\n<li>Adapt the ILS Acq order to reflect the format purchased and relationship to publisher deals<\/li>\n<li>Lincesing, registration, access, activation, troubleshooting are all part of the subs process<\/li>\n<\/ul>\n<p>Cataloging<\/p>\n<ul>\n<li>Licenses can be catalogued<\/li>\n<li>Use existing ERM tools in new ways<\/li>\n<li>Database to record both full licenses and licensing expresssions<\/li>\n<li>URL through resource target level in SFX pushes &#8216;terms of use&#8217; through to the end user for all titles from that publisher or hosting site<\/li>\n<ul>\n<li>This sounds like a really interesting project &#8211; they are talking about parsing the full-text licenses and extracting terms of use &#8211; would be very interesting to look at.<\/li>\n<\/ul>\n<\/ul>\n<p>What should libraries do?<\/p>\n<ul>\n<li>Stop reinventing the wheel<\/li>\n<li>Keep up to date on market products, new tools from existing vendors and what other libraries are doing<\/li>\n<li>Repurpose data reported from existing information silos and combine it easily in new tools<\/li>\n<li>BUT with any tool selected, plan for change and interoperability &#8211; things change, and tools change with them<\/li>\n<li>Make information and the management process trasnparen, share data files and email lists<\/li>\n<li>Triage troubleshooting, designate a &#8216;Go To&#8217; unit (like TAP mentioned in previous talk), don&#8217;t duplicate your efforts<\/li>\n<li>Provide a single help point for patrons<\/li>\n<\/ul>\n<p>There is no magic system:<\/p>\n<ul>\n<li>Not all ERM tools are the same &#8211; evaluate what your ERM needs are before purchasing or building &#8211; and think about ERM as a set of tools &#8211; you may only need part of the toolset, and this may be cheaper than a all encompassing system<\/li>\n<li>Look at your staff resources in relation to duplication of effort &#8211; beware of systems that increase duplication, rather than making the systems simpler<\/li>\n<li>Beware both of maintaining outdated in-house systems AND the purchase of vaporware &#8211; test drive as much as you can<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>Q: What is the workflow for cataloguing licenses?<\/p>\n<p>A: Research data in licenses. Figure out ways of bringing together data and doing something with them. Standardise language etc.<\/p>\n<p>Q: Would you be willing to share how you do the SFX &#8216;Terms of Use&#8217;<\/p>\n<p>A: Stole this from another library! (although not done at Maryland) &#8211; Washington Research Library Consortium<\/p>\n<p>Q: We have a specialist team. The general &#8216;acq&#8217; team not so familiar with e-vendors etc. What worked for us was a specialist team, but with other staff cycled through to share knowledge.<\/p>\n<p>A: Recommend cross-training as much as you can. Can&#8217;t afford staff who don&#8217;t know the overall process.<\/p>\n<p>Q: There&#8217;s been a lot of talk about communication &#8211; not always good in libraries, are there suggestions for tackling this?<\/p>\n<p>A: Yes &#8211; talk to me after.<\/p>\n<p>&nbsp;<\/p>\n<div class=\"wlWriterSmartContent\" id=\"scid:0767317B-992E-4b12-91E0-4F059A8CECA8:733a7ec5-0bb7-4210-845e-0d7feb2212e5\" style=\"padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px\">Technorati Tags: <a href=\"http:\/\/technorati.com\/tags\/ala2008\" rel=\"tag\">ala2008<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>This session by Lila Angie Ohler from Maryland&nbsp; &#8211; she says &#8220;Libraries have done themselves a disservice by dealing with e-resources separately&#8221; Some myths about e-resources: Why worry &#8211; e-resources just take care of themselves right? Placing the order and paying the invoice is just hte beginning E-Resource do not remain &#8216;on the shelf&#8217; &#8211; [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[9],"class_list":["post-85","post","type-post","status-publish","format-standard","hentry","tag-ala2008"],"_links":{"self":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/85","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/comments?post=85"}],"version-history":[{"count":0,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/85\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/media?parent=85"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/categories?post=85"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/tags?post=85"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}