Your SlideShare is downloading. ×

Lossless MARC Mapping


Published on

Presentation for the LITA/ALCTS MARC Transition Interest Group, ALA Midwinter, Seattle, January 2013. Abstract: Many of those who seek to map or crosswalk data from MARC to other schemas believe that …

Presentation for the LITA/ALCTS MARC Transition Interest Group, ALA Midwinter, Seattle, January 2013. Abstract: Many of those who seek to map or crosswalk data from MARC to other schemas believe that the elderly MARCXML is the only option. However, another option exists, in a more modern package: These
'level zero' elements allow MARC21 data to be represented without loss in RDF; subsequently, semantic mappings can be used to interoperate the data with other linked data based on Dublin Core, ISBD, RDA, etc. This resource is open to use by anyone, and will be available in the mapping service beingbuilt by the Open Metadata Registry (

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Lossless MARC Mapping ALA Midwinter Seattle 2013 MARC Formats Transition IG Diane Hillmann
  • 2. Is MARC Dead?•  The communication format is very dead (based on standards no longer updated)•  The semantics are not dead o  They represent the distillation of decades of descriptive experience o  As we move into a more machine-assisted world, our old concerns about the size of our legacy can be addressed o  Taking the legacy records with us should be based on solutions developed using open and transparent strategies
  • 3. ‘Lossy’ vs. ‘Lossless’ MARC Mapping•  ‘Lossy’ means that some information gets lost in transition o  Loss can also occur intentionally, e.g. when pre- selection of preferred elements is made•  Current mapping strategies are based on o  One-time, inflexible, programmatic methods that effectively hide the process from consumers §  This practice makes it difficult for community members to effectively respond to decisions made behind the curtain or to contribute to better maps
  • 4. A Better Strategy•  The decision to set up the MARC21rdf data was to provide the possibility of transparent mapping by data providers at many levels•  This strategy is based on mapping all of MARC – not a selection o  Filtering accomplished by data consumers, who know best what they need o  Meeting the potential for widespread use of data mapped from MARC depends on putting data out without assuming we know what other people need
  • 5. Libraries as Data Publishers•  Data from library ‘publishers’ should look like an American supermarket—lots of choices, with decisions made by consumers o  Right now we seem to be operating as Soviet bakeries (“we don’t care what you want, we know what you need”) §  This stifles innovation and continues to treat libraries as passive consumers §  This is not what open linked data is supposed to be doing for us
  • 6. A Resource, WorldCat
  • 7. A Resource, MARC21
  • 8. marc21rdf.info
  • 9. marc21rdf.info 260 (Publication, Distribution, etc. (Imprint) )ind1: # (Not applicable or No information provided or Earliest available publisher)ind2: # (no caption)sub: a (Place of publication, distribution, etc.)Definition:Place of publication and any additions to the name ofa place, including an address...
  • 10. Search for Place of Publication (1)
  • 11. Search for Place of Publication (2)
  • 12. RDA Place of Publication (Manifestation)
  • 13. RDA Place of Publication
  • 14. FRBRer Place of Publication
  • 15. ISBD has Place of Publication...
  • 16. How Does this Strategy Fit?•  Mapping as a service o  Maps continually updated o  Openly available o  Easily distributable•  Publishing & Consuming systems o  Need to work in tandem to enhance and improve data o  The methods to do this are not new, but are not well understood in traditional libraries (to some extent because of their continuing emphasis on ‘records’)
  • 17. RDF map of “audience” attributeM21 Level 0
  • 18. Let the machine to do the workISBD My Resource has note on use or audience “juvenile”Dublin Core My Resource (has) audience “juvenile” My Creative work (has) audience “juvenile”RDA My Work (has) Intended audience “juvenile”MARC 21 My Resource (has) Target audience “juvenile”Level 0 My Resource (has) Target audience of Music “juvenile”M 21 triple ex:Resource - m21:M008MU22 - m21t:commonaud#j
  • 19. The Place of Publication
  • 20. Questions?Diane HillmannMetadata.Maven@gmail.comMetadata Management Associates