Posts tagged with 'Processes'

Technologies for Assisting with e-Resource workflow (Notes from Workflow Roundtable, Part II)

ewinter March 25th, 2008

At the Workflow Roundtable, the group also discussed the ways in which they were using a variety of tools and technologies to assist with workflow-related issues.

Some of them were:

  • A blog to track resource problems and experiences (to keep track for personal use, in case the same problem comes up again)
  • Scanning/digitizing license agreements and keeping them on a shared drive so that they can be retrieved and emailed to library employees as needed.
  • ERMs: Obviously, this is a major tool many libraries are working on using for many things; some mentioend using existing problem-tracking fields or creating customized fields for this purpose, so that library employees can see when resources are experiencing problems.
  • Adapted ILS modules to deal with e-resources in lieu of an ERM, e.g., eTracker (Deberah England from Wright State Univ. presented on this during ER&L 2008)
  • An internal listserv with a searchable archives feature for those who work with e-resources to share info.
  • A wiki for communication between collection development and acquisitiosn regarding e-resource subscriptions (new purchases, renewals, changes, etc. We are doing this at Georgia Tech…a presentation I gave at ALA 2007 in part on this topic is available at http://r2consulting.org/ppnts/GTWikisEtc.ppt)

Tags: , , , , , , ,

Mapping Library Work to ERAMS Processes

ewinter March 21st, 2007

Serial Solutions’ ERAMS concept seems able to encapsulate most of the types of work currently done in libraries:

  • Determining what goes into the knowledgebase (kb) = collection development. This seems to map to Collect and Control.
  • Making sure things are added to the kb accurately in a timely way = acquisitions + cataloging. This seems to map to Correct.
  • Presenting kb contents in a meaningful way to users = system/web/user interface design and development + information literacy and reference services (help the user interpret and use what s/he finds) + document delivery services (provide users with specific units of content). This seems to map to Connect.
  • Ensuring that kb contents represent a good use of library budgets and are acquired smoothly = administration + collection development + acquisitions. This seems to map to Control.

Other thoughts?
Disagreements?

Tags: