Eg2010 calvin-serials


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Eg2010 calvin-serials

  1. 1. Managing Serials with Evergreen A Case Study of Hekman Library at Calvin College
  2. 2. Why Serials Management? <ul><li>High volume of throughput </li></ul><ul><li>Large number of repetitive tasks </li></ul><ul><li>Fine-grained details of great importance </li></ul>
  3. 3. Challenges of Serials Management <ul><li>Take advantage of general predictability and repeatability </li></ul><ul><li>Allow for very frequent exceptions </li></ul><ul><li>Accommodate wide variety of management practices </li></ul><ul><li>Manage metadata level holdings, physical level copies, and business level information </li></ul>
  4. 4. Evergreen Serials Model Metadata Physical Business
  5. 5. Metadata – Basics of MFHD <ul><li>M ARC F ormat for H oldings D ata </li></ul><ul><li>Often pronounced as “muff-head” </li></ul><ul><li>Standard, often computable way to share volume, part, and copy information </li></ul><ul><li>Incorporates publication patterns as part of the standard </li></ul>
  6. 6. MFHD Example <ul><li>Field 853 </li></ul><ul><ul><li>Caption and Pattern statement </li></ul></ul><ul><ul><li>Often one per record </li></ul></ul><ul><li>Field 863 </li></ul><ul><ul><li>Enumeration and Chronology statement </li></ul></ul><ul><ul><li>Often many per record </li></ul></ul><ul><li>Other paired fields – 854/864, 855/865 </li></ul><ul><li>Field 866 – Textual (i.e. non-standardized) Holdings </li></ul>
  7. 7. Metadata Management <ul><li>Goal – Internalize and automate the MFHD record editing so that the serials worker can concentrate on the physical item workflow </li></ul><ul><li>Benefits </li></ul><ul><ul><li>Greater accuracy </li></ul></ul><ul><ul><li>Easier integration </li></ul></ul>
  8. 8. Evergreen Serials Model Metadata Physical Business
  9. 9. Physical – The Issuance Table <ul><li>Primary workspace and data source for serials </li></ul><ul><li>Every serial ‘piece’ will have it’s own entry </li></ul><ul><li>Critical fields include </li></ul><ul><ul><li>Date Expected </li></ul></ul><ul><ul><li>Date Received </li></ul></ul><ul><ul><li>Series Label Information </li></ul></ul><ul><ul><li>Claimed? </li></ul></ul><ul><ul><li>Shelving Unit </li></ul></ul>
  10. 10. Physical – The Shelving Unit <ul><li>Shelving Units are generic containers of one or more issuances </li></ul><ul><li>May be used to represent a single issue, a volume of issues, an entire shelf of volumes, etc. </li></ul><ul><li>The entire unit is represented by a single call number </li></ul><ul><li>Therefore, each copy represents an entire unit </li></ul>
  11. 11. Shelving Unit – Use Cases <ul><li>Library does not circulate serials </li></ul><ul><ul><li>Free to have any number of Units </li></ul></ul><ul><ul><li>Simplest case – single unit for entire run, single call number </li></ul></ul><ul><li>Library circulates current issues only </li></ul><ul><ul><li>One Unit per current issue (may have multiple copies) – use ‘Auto per Issue’ feature </li></ul></ul><ul><ul><li>At least one unit for any bound volumes </li></ul></ul><ul><li>Library circulates bound volumes </li></ul><ul><ul><li>One Unit per bound volume – use ‘Auto per Volume’ feature </li></ul></ul><ul><ul><li>May also have Unit per unbound issue </li></ul></ul>
  12. 12. Business – Not Included <ul><li>While some of the structures are in place, links to the acquisition structure will be a future development task </li></ul>
  13. 13. Standard Workflow <ul><li>Create MFHD record, including prediction pattern statement </li></ul><ul><li>Generate one or more issuances based on pattern in MFHD </li></ul><ul><li>Receive issuances </li></ul><ul><ul><li>automatically generates/edits enumeration and chronology statements in MFHD </li></ul></ul><ul><ul><li>creates call number and copy records as needed </li></ul></ul><ul><li>Return to step 2 </li></ul>
  14. 14. Primary Serials Interface - Preview
  15. 15. Workflow Exceptions <ul><li>Types of problems </li></ul><ul><ul><li>Claims </li></ul></ul><ul><ul><li>Prediction pattern exceptions (issue cancelled, extra issue, date changed, etc.) </li></ul></ul><ul><ul><li>Manual Shelving Unit, call number, and copy management </li></ul></ul><ul><li>Will be handled as needed by separate interfaces </li></ul>
  16. 16. More Information <ul><li>Credits </li></ul><ul><ul><li>Dan Wells, Library Programmer Analyst </li></ul></ul><ul><ul><li>Steven Putt, Electronic Services Librarian </li></ul></ul><ul><li>For the latest version of this presentation, please visit </li></ul>