1 / 16

ONIX for Serials: how it can map to the MARC 21 Holdings Format

ONIX for Serials: how it can map to the MARC 21 Holdings Format. Prepared by Linda Miller and Rebecca Guenther, Library of Congress Presented by Rebecca Guenther ALA Midwinter 2009, Denver. What is the purpose of SOH?.

gladys
Download Presentation

ONIX for Serials: how it can map to the MARC 21 Holdings Format

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. ONIX for Serials: how it can map to the MARC 21 Holdings Format Prepared by Linda Miller and Rebecca Guenther, Library of Congress Presented by Rebecca Guenther ALA Midwinter 2009, Denver

  2. What is the purpose of SOH? • A family [group] of XML messages containing information about holdings of online serial resources • Can be transmitted from a vendor or content provider to a receiving library’s OPAC, link resolver,or electronic resource management system • ERM system interprets and imports the information • Serves the purpose of “electronic check-in” • Minimizes manual intervention in updating holdings

  3. How can ONIX SOH Version 1.1 be useful to libraries? • By expressing complete enumeration and chronology in a communication format that could be understood in MARC21 based systems. • By providing a sufficient level of enumeration and chronology detail to be useful to patrons with known item searches that wish to match citation information in hand to the library’s electronic holdings. • By supplying an unambiguous expression of holdings that can be parsed by machine and used for link resolution. • By providing a means to express and update holdings statements in such a way that reduces the workload in libraries since ONIX SOH can automatically update/replace serials holdings statements that appear in the library’s OPAC and/or in their electronic resource management system (ERMS).

  4. Components of SOH • Header • Holdings List • Online Package For descriptions of the ONIX for serials formats, consult: http://www.editeur.org/onixserials/

  5. Coverage in SOH version 1.1 • The ONIX for Serials Coverage Statement is an XML structure that can carry either simple or complex statements of holdings of serials resources that can be included inside ONIX for Serials SOH messages.

  6. Diagram of the ONIX coverage composite. Today’s focus is on the Fixed Coverage part of the ONIX Serials Coverage Statement. The diagram above, borrowed from the “Online Serials Coverage Statement, version 0.9 User Guide” can be found at: http://www.editeur.org/onixserials/userguides/ONIX_Serials_Coverage_0.9.htm\

  7. TheAstrophysical Journal: Starting Enumeration and Chronology Level 1 Enumeration Level 2 Level 3 Chronology

  8. The Astrophysical Journal: Ending Enumeration and Chronology Level 1 Enumeration Level 2 Level 3 Chronology

  9. ONIX to MARC: Enumeration <Level1> <Unit>Volume</Unit> {MARC 853$a} <UnitAbbr> <UnitAbbrType>02</UnitAbbrType> 02 indicates AACR2 <Abbreviation>v.</Abbreviation> </UnitAbbr> <Number>220</Number> {MARC 863 $a} <Level1> Focusing on this detail from the SOH enumeration, ONIX can convey the full caption name, Volume, at the first level, but also allows the sender to specify an abbreviation for the caption in addition to the abbreviation code denoting its source. As with MARC21, the caption is in a field that is separate from the value of the enumeration.

  10. ONIX to MARC: Chronology ONIX SOH chronology, however, follows a specified journal issue date scheme. One that has been adopted by other ONIX formats. 00 for YYYMMDD 07 for YYYYMMYYYYMM 01 for YYYYMM 08 for YYYYWWYYYYWW 02 for YYYYWW 09 for YYYYQYYYYQ 03 for YYYYQ 10 for YYYYSYYYYS 04 for YYYYS 11 for YYYYYYYY 05 for YYYY 12 for Text String 06 for YYYYMMDDYYYYMMDD where DD=day, MM=month, Q=Quarter, S=season, WW=Week, YYYY=year

  11. The ONIX data scheme can be interpreted into MARC-like structures because it follows a known set of fixed formats. <Nominal Date> <Calendar>00</Calendar> “00” = Gregorian calendar <Date Format>00</DateFormat> Form YYYYMMDD where YYYY maps to MARC 853$i, MM to MARC 853 $j, DD to MARC 853 $k <Date>19780301</Date> <Nominal Date> Using the ONIX date format from this example, “00”, you can observe that: 1978 = MARC 863 $i 03 = MARC 863 $j 01=MARC 863 $k in representing the starting date of the sequence,

  12. Prediction is missing from ONIX SOH…perhaps If our software systems are importing updated holdings statements periodically, will our e-holdings require the predictive elements?

  13. Researchers tracking down citations like the one offered below require the most complete holdings descriptions to match their citations to the material that Library patrons can access:

  14. Library of Congress Voyager OPAC The user can discover that we have issue No. 4 from our inkprint holdings description.

  15. Library of Congress ERMS OPAC . Since the user’s citation lacked the month, April, the user can not tell if our electronic holdings contain the desired content.

  16. Comparison of inkprint holdings displays from Voyager OPAC and Electronic hodlings displays from the III ERMS OPAC HOLDINGS Display for Inkprint version HOLDINGS Display based on data supplied by publication access management services.

More Related