1 / 45

The eXtensible Catalog (XC): Transitioning to a Post-MARC Environment

The eXtensible Catalog (XC): Transitioning to a Post-MARC Environment. Jennifer Bowen, University of Rochester Cornell University May 8, 2012, Ithaca, NY. Agenda. What is eXtensible Catalog (XC) Software? XC’s potential role in the transition from MARC to a non-MARC environment

xenon
Download Presentation

The eXtensible Catalog (XC): Transitioning to a Post-MARC Environment

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. TheeXtensible Catalog (XC): Transitioning to a Post-MARC Environment Jennifer Bowen, University of Rochester Cornell University May 8, 2012, Ithaca, NY

  2. Agenda What is eXtensible Catalog (XC) Software? XC’s potential role in the transition from MARC to a non-MARC environment Lessons learned from XC to inform RDA implementation and a new bibliographic framework XC’s potential for producing linked data

  3. What is XC software? eXtensible Catalog (XC) is open source, user-centered, next generation software for libraries. XC provides a discovery system and a set of tools for libraries to manage metadata and build applications.

  4. XC Software – end to end OAI Toolkit NCIP Toolkit MST Toolkit Drupal Toolkit User Interface - Search - Browse ILS Connectivity Synchronize data with XC ILS Connectivity - Circ. status - Account info Metadata Services - Cleanup - Format Convert Voyager “Driver” Voyager “Driver” Metadata Digital Repository Voyager ILS Live Circ. Data User Interface

  5. XC software – just the metadata OAI Toolkit NCIP Toolkit MST Toolkit Drupal Toolkit Insert your Application with OAI-PMH Harvester here! User Interface - Search - Browse ILS Connectivity Synchronize data with XC ILS Connectivity - Circ. status - Account info Metadata Services - Cleanup - Format Convert Voyager “Driver” Voyager “Driver” Metadata Digital Repository Voyager ILS Live Circ. Data User Interface

  6. Why Build XC? Empower libraries to have control over their discovery environment Put results of user research into practice Everything in XC user interface is customizable Create a new platform for metadata manipulation that uses FRBR, RDA

  7. XC User Research: A few findings

  8. XC User Research Partners: Cornell University Ohio State University University of Rochester Yale University Studying scholars at the UR…

  9. User Research Findings Users have preferred material and format types, depending upon their projects “I want the printed book. Well, I read online but, what have I accomplished if I print out the pages? Printer ink is incredibly expensive, it’s a horrible pain to do all that. I want the book.” “I’m very happy because I know it’s online […] I try to do everything electronically now.”

  10. User Research Findings Users have preferred material and format types, depending upon their projects “I’ve done a fair amount of scanning with microfilm and then using the document delivery service to have them scan microfilm and it never works very well for me and what seems to be fine on the computers [in the library] doesn’t work well when I get [to my office]. So I avoid microfilm when I can.”

  11. User Research Findings: XC Approach Users have preferred material and format types, depending upon their projects • Show online materials only • Exclude microforms • Enable facet for format 12

  12. User Research Findings Users want to choose between versions of a resource, see relationships between resources “Yesterday I was teaching Robinson Crusoe and usually I’ll have the newest edition…” “At the present moment I am completing an edition of selected narratives from the 1883 edition of Fox’s Book of Martyrs …”

  13. User Research Findings: XC Approach Users want to choose between versions of a resource, see relationships between resources XC approach: • Base underlying XC Schema metadata on linked FRBR Group 1 entity records: works, expressions, manifestations, etc. • Develop metadata processing services to aggregate/group FRBR entities in the XC User Interface (forthcoming) 15

  14. “View XC Schema”

  15. “Uplinks” between FRBR levels

  16. XC Schema record originated as this MARC record in our ILS

  17. “FRBRized” MARC records • Parse MARCXML records into linked FRBR-based XC Schema records • MARC Holdings records produce XC Holdings records • Uplinks created XC Work Work Expressed XC Expression MARCXML Bibliographic Expression Manifested XC Manifestation OO4 “Uplink” Manifestation Held MARCXML Holdings XC Holdings

  18. XC software – just the metadata OAI Toolkit MST Toolkit NCIP Toolkit FRBRized option Drupal Toolkit Insert your Application with OAI-PMH Harvester here! User Interface - Search - Browse ILS Connectivity Synchronize data with XC ILS Connectivity - Circ. status - Account info Metadata Services - Cleanup - Format Convert Voyager “Driver” Voyager “Driver” Metadata Digital Repository DC Voyager ILS MARC Live Circ. Data User Interface

  19. What are the implications of XC’s FRBR capabilities?

  20. Facilitating RDA Implementation XC transforms MARC data into a FRBR-informed “transitional” XML schema The “XC Schema,” uses a subset of RDA elements and roles alongside Dublin Core, some XC data elements More RDA elements can be added to the schema in the future

  21. “View XC Schema”

  22. By March 2013… By the time that RDA is implemented, Using XC Software, libraries will be able to use RDA in MARC and RDA in a non-MARC environment at the same time.

  23. RDA in Multiple Environments at Once Use RDA in MARC via existing ILS Set up XC alongside a MARC-based ILS. XC harvests a copy of the ILS metadata, converts it to the FRBRized XC Schema that uses some RDA elements and roles. This enables risk-free experimentation of RDA outside of the constraints of MARC, but without disturbing current workflows

  24. What have we learned from “FRBRizing” MARC in a live system? (some really ugly slides!)

  25. MARC to XC Schema Transformation XC Work MARCXML Bibliographic XC Expression XC Manifestation Parses MARCXML records into linked FRBR-based records Maps MARCXML data elements to elements in the XC Schema.

  26. Converting MARC 21 Problematic areas: • Some MARC fields/subfields are difficult to map to appropriate FRBR entities • Tracking relationships between FRBR entity records: How many relationships can we support with XC software?

  27. Managing Relationships XC Work MARCXML Bibliographic XC Expression XC Manifestation

  28. Managing Relationships XC Work MARCXML Bibliographic XC Expression XC Manifestation

  29. Issue 1: Managing Multiple Relationships MARC bibliographic records can refer to multiple FRBR entities of the same type (analytics that represent multiple works/expressions, e.g. tracks on a CD) XC Work XC Work MARCXML Bibliographic XC Expression XC Expression XC Manifestation

  30. Issue 2: Beyond FRBR Group 1 Entities MARC “Alternate Graphic Representation” (880 fields) can contain data that belong in records for Group 2 and Group 3 entities Contributor: 700 1 ‡6 880-08 ‡a Vasil’ev, Maksim. 880 1 ‡6 700-08 ‡a Васильев, Максим. Subject: 600 10 ‡6 880-06 ‡a Putin, Vladimir Vladimirovich, ‡d 1952- 880 10 ‡6 600-06 ‡a Путин, Владимир Владимирович, ‡d 1952-

  31. If we were to parse this 880 data correctly: • Contributor • Contributor in Cyrillic characters • Contributor in Roman characters • Subject • Subject in Cyrillic characters • Subject in Roman characters XC Work MARCXML Bibliographic XC Expression Alternative script of name from 880 Alternative script of subject from 880 XC Manifestation

  32. Issue 3: Related Group 1 Entities Language attribute for a related expression 041 1 ‡a eng ‡h ita 100 0 ‡a Dante Alighieri, ‡d 1265-1321. 240 10 ‡a Divina commedia. ‡l English 245 14 ‡a The divine comedy / ‡c Dante ; a new verse translation by C.H. Sisson. 500 ‡a Translation of: Divina commedia.

  33. If we were to parse 041 ‡h data… • Contributor • Contributor in Cyrillic characters • Contributor in Roman characters • Subject • Subject in Cyrillic characters • Subject in Roman characters XC Work Original language from 041‡h MARCXML Bibliographic XC Expression Alternative script of name from 880 Alternative script of subject from 880 Based on (Expression) XC Manifestation

  34. Managing Relationships Between Entities • Contributor • Contributor in Cyrillic characters • Contributor in Roman characters • Subject • Subject in Cyrillic characters • Subject in Roman characters Original language from 041 $h Alternative script of name from 880 Alternative script of subject from 880 Based on (Expression) XC Work MARCXML Bibliographic XC Expression XC Manifestation

  35. What we are learning from XC Maintaining links between separate FRBR entity records in a production environment may not be scalable if we continue to manipulate records. XC Work • new records • changed records • deleted records • changed relationships XC Expression XC Manifestation

  36. What XC has taught us about FRBR… The GOOD news: MARC data is very rich, and contains data about MANY relationships described in FRBR and related data models There are hundreds of RDA Relationships between FRBR entitles!

  37. What XC has taught us about FRBR… The GOOD news: MARC data is very rich, and contains data about MANY relationships described in FRBR and related data models The BAD news: managing all of these relationships in a record-based system is probably not feasible Conclusion (more good news): Linked Data may make a fuller implementation of FRBR much more attainable!

  38. Questions?

  39. XC MST Demo www.extensiblecatalog.org/software/mst/demo

More Related