1 / 0

SkyRiver vs OCLC

SkyRiver vs OCLC. In a cooperative environment, can there be ownership?. How did MSU get involved?. High level talks in Summer 2009 Saw prototype in early July 2009. The fun began . Announced to staff on August 17, 2009 Installed on August 18, 2009 Left OCLC cataloging on November 1, 2009

rusk
Download Presentation

SkyRiver vs OCLC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SkyRivervs OCLC

    In a cooperative environment, can there be ownership?
  2. How did MSU get involved? High level talks in Summer 2009 Saw prototype in early July 2009
  3. The fun began Announced to staff on August 17, 2009 Installed on August 18, 2009 Left OCLC cataloging on November 1, 2009 Total of 75 days to make the move No time to understand the implications – we simply reacted!
  4. What did we learn? Our questions were never about the system (SkyRiver worked) Our issues were all about our policies and procedures We quickly realized how much the cataloging world was “OCLC centered” Everyone uses OCLC numbers for match points OCLC dominates cataloging conversations
  5. Typical question What is ‘original’ cataloging? When you can find records everywhere when is it still ‘original’? In OCLC, if it isn’t in WorldCat it is new and original. However, what about Biblios? Other national catalogs?
  6. Typical question #2 What is a standard in OCLC and what is the actual standard? Began to question all codes and reasons for them. Was it an OCLC requirementfor their purposes, or something established by national standards? Example: 7XX fields
  7. Example 7761 |t Journal of psychology |x 0022-3980 |w (DLC) 38003075 |w (OCoLC)1782317
  8. 776 - Additional Physical Form Entry $o - Other item identifier (R)$r - Report number (R)$s - Uniform title (NR)$t - Title (NR)$u - Standard Technical Report Number (NR)$w - Record control number (R)$x - International Standard Serial Number (NR)$y - CODEN designation (NR)$z - International Standard Book Number (R)$4 - Relationship code (R)$6 - Linkage (NR)
  9. cunundrum of single record source vs. open record source What inhibits/hems us in? What keeps us from sharing, enhancing? Vendor requirements Holdings
  10. The holdings issues MSU no longer adding holdings to WorldCat because cost prohibitive Result? Two overlapping but unique databases! Is there any way to keep them in synch? Do we want/need to keep them in synch?
  11. Implications for Being OCLC centric OCLC numbers used for everything Google HathiTrust OCLC standards are the defacto standards OCLC sits on PCC – has influence
  12. Cooperating on a micro level MSU shares catalog with two other libraries Library of Michigan MSU College of Law They still use OCLC so we have OCLC numbers in some of our records. MSU is also a part of MelCAT
  13. Final thoughts Very liberating With liberation comes responsibility With responsibility comes standards
  14. Final thoughts MSU catalogers are not rogue We still follow PCC standards even though we are not CONSER participants We have worked with SkyRiver to establish policies that will benefit all and position them to participate in cataloging discussions Now a part of NACO again as of November 1, 2010
  15. Thinking out loud We need to think more broadly about cataloging implications. And, we need to think about how our catalog relates to catalogs outside our catalog! If indeed we will move beyond MARC, then we need to position the data in such a way that it can be easily moved. Therefore, we need standards.
  16. More information? Nancy W. Fleck Associate Director for Technical Services and Systems Michigan State University Libraries fleckn@msu.edu
More Related