METADATA CROSSWALK LAYNE AINGELL LI 883 XI – INTRODUCTION TO METADATA PROFESSOR MELISSA MESSINA SPRING 2014 MARC FIELD 037$b - Source of Acquisition DUBLIN CORE TERM Source DATA VALUE IMPLEMENATION NOTES 040$c - Cataloging Source ProQuest. 789 E. Eisenhower Parkway, Ann Arbor, MI 48108-3218 Cu-RivES 040$d - Cataloging Source CStRLIN; WaOLN 040$e - Cataloging Source dcrb Data Value: LC Descriptive Cataloging of Rare Materials Data Value: LC MARC Code List for Organizations Data Value: LC Z39.50 100$d - Main Entry – Personal Name Contributor Dates associated with a name. Data Value: MARC 21 Format for Bibliographic Data Field List 100$e - Main Entry – Personal Name Contributor. Aut Shakespeare, William, 1564-1616 Data Value: LC Name Authority DC Element Qualifier: MARC Relator Code 240 - Uniform Title Title Hamlet. Data Value: LC Title Authority 245$h - Title Statement Title.Alternative 246 - Varying Form of Title 260$a - Publication, Distribution, etc. 260$b - Publication, Distribution, etc. Title.Alternative Publisher The tragicall historie of Hamlet Prince of Denmarke by William Shake-speare. As it hath beene diuerse times acted by his Highnesse seruants in the cittie of London: as also in the two vniuersities of Cambridge and Oxford, and elsewhere [electronic resource]. Hamlet; Tragedy of Hamlet Prince of Denmarke. At London. Publisher Printed [by Valentine Simmes] for N[icholas] L[ing] and Iohn Trundell. METADATA CROSSWALK LAYNE AINGELL LI 883 XI – INTRODUCTION TO METADATA PROFESSOR MELISSA MESSINA SPRING 2014 260$c Publication, Distribution, etc. Date.Created c1603. 260$c Publication, Distribution, etc. Date.Copyrighted c1603. 300$a - Physical Description 500$a - General Note 500$a - General Note 500$a - General Note 500$a - General Note Format.extent Description Description Description Description 500$a - General Note 500$a - General Note 510 - Citation/References 533$a - Reproduction Note 533$b - Reproduction Note 533$d - Reproduction Note 533$f - Reproduction Note 533$n - Reproduction Note 655$e - Index Terms 830 -Series Added Entry 856$u - Electronic Location and Access Description Description Relation.IsReferencedby 856$u - Electronic Location and Access Identifier 66 pp. Mostly in verse. Printer's and Ling's names from STC. Signatures: [A]² (-A1) B-I⁴. Running title reads: The tragedy of Hamlet Prince of Denmarke. Reproduction of the original in the British Library. Title page lacking. STC (2nd ed.)/c22275; Greg, I, 197(a). Electronic reproduction. Ann Arbor, Mich. 1999 Early English books online. Digital version of Early English books, 1475-1640; 904:10 Electronic books. Early English books online. http://proxy.mul.missouri.edu:2048/login?url=http://gat eway.proquest.com/openurl?ctx_ver=Z39.882003&res_id= xri:eebo&rft_val_fmt=&rft_id=xri:eebo:image:11497 http://ezproxy.mnl.umkc.edu/login?url=http://gateway.p roquest.com/openurl?ctx_ver=Z39.882003&res_id=xri:eeb o&rft_val_fmt=&rft_id=xri:eebo:image:11497 Coverage.Temporal Date.Created Type.image Relation.IsPartOf Identifier Because “c” preceded the date, it is implied that creation date and copyright date are the same. Because “c” preceded the date, it is implied that creation date and copyright date are the same. DCMI DCMI URI: Accessed through MU gateway. URI: Accessed through UMKC Law Online gateway. METADATA CROSSWALK LAYNE AINGELL LI 883 XI – INTRODUCTION TO METADATA PROFESSOR MELISSA MESSINA SPRING 2014 Creating a Metadata Crosswalk Table I started this assignment, much like I did for the Dublin Core assignment, by creating a table with the MARC field in the first column. I omitted the leader and control codes (first 24 character positions) per the assignment’s instructions. In assigning the first column, I used the MARC 21 Format for Bibliographic Data Field List to determine the main entry fields and subfields. I then compared these to the MARC to Dublin Core Crosswalk, and entered those in the second column. Although it is counterintuitive to the assignment, I chose not to combine fields. Instead I entered each as a separate line item in order to illustrate the granularity of MARC. Particularly, the MARC fields of 260, 500 and 533 could be combined, but separating them allowed me to explore the subfields and how they are expressed in Dublin Core. This gave me a visual example and greater clarity on how the mapping works. This could also supplement the data lost in mapping to Dublin Core. As I became more familiar with the MARC 21 Format for Bibliographic Data Field List, I was able to understand the subfields and how they compared to Dublin Core. I also referred to the MARC Reference Materials, Part XI for the breakdown of a sample MARC record and what each entry meant. I found the MARC 21 Format for Bibliographic Data Field List to be the most helpful resource, because it gave a detailed explanation of the fields and their methodology. I was able to see the descriptions of the subfields and how they related to Dublin Core. Once I made sense of this, the categories fell into place. Keeping the line item format helped me to distinguish the categories and see their differences and similarities, and gain a greater understanding of MARC. Bibliography MARC to Dublin Core Crosswalk, (2008). Retrieved from http://www.loc.gov/marc/marc2dc.html#qualif MARC 21 Format for Bibliographic Data Field List, (2013). Retrieved from http://www.loc.gov/marc/bibliographic/ecbdlist.html MARC 21 Reference Materials, Part XI, (2009). Retrieved from http://www.loc.gov/marc/umb/um11to12.html
© Copyright 2025 ExpyDoc
