Mappings

PBCore and MARC

This documentation below provides recommendations for converting from the PBCore metadata standard to the MARC 21 Format for Bibliographic Data. Since MARC has more fields than PBCore, there may be multiple recommendations for the same PBCore element, depending on context and desired level of detail. The documentation includes recommendations for both simple and complex mappings. MARC 21 fields are listed by field number with specific subfields if applicable.

This mapping includes all PBCore elements, but does not include all possible attributes to those elements. Attribute mappings are included when attributes are required within PBCore, or when mapping an attribute would allow for a more specific mapping within MARC.

These documents do not provide recommendations for converting from MARC 21 to PBCore, although it may in some cases be used as a guideline for such work.

Download the Excel spreadsheet mapping and the associated documentation.

MARC 21 is supported by the Library of Congress; this mapping refers to the 1999 edition, Update No. 27.

PBCore XML-RDF (EBUCore/Dublin Core/DC Terms/SKOS)

The chart below provides a simple example mapping for converting from the PBCore metadata standard to existing RDF predicates, using primarily terms from the EBUCore ontology as well as Dublin Core and SKOS.

This mapping includes all PBCore elements, with the exception of Extension elements (the infinitely extensible structure of RDF makes Extension attributes redundant.) Because of the structure of RDF, the mapping does not include attributes or Type sub-elements except when the use of these would allow for mapping to a more specific predicate (i.e. AssetDate @dateType=”broadcast” = ebucore:dateBroadcast, pbcoreRelation with relationType=Has Derivative = ebucore:derivedTo.)

Because RDF is not hierarchical, we recommend that Assets, Instantiations, and Essence Tracks each exist as separate RDF objects. Links between Assets and Instantiations can be expressed using dc:hasFormat and dc:isFormatOf; links between Instantiations and EssenceTracks can be expressed using ebucore:hasTrack and ebucore:isTrackOf.

Download a simple mapping.

Any RDF implementation will vary based on the specific needs of the institution and the use case. EBUCore also encourages uses to define their own subclasses and subproperties as required for their specific business needs. To demonstrate the decision-making required around indexing, presentation, and local properties, we have also included an example of the full data modeling worksheet used to determine properties and behavior for the American Archive of Public Broadcasting’s PBCore-based metadata management system.

EBUCore is supported by the European Broadcasting Union; this mapping refers to version 1.9 of the EBUCore Ontology. The development of the EBUCore ontology is a joint effort of the EBUCore and PBCore communities, with several properties that have been added specifically to facilitate PBCore mapping. For more information about EBUCore, visit the homepage of the EBUCore metadata standard.

Credits

Thanks to the following people for their work on the PBCore and MARC mapping: Danielle Calle, Rebecca Fraimow, Rebecca Guenther, Annie Schweikert, and Sigridur R. Sigurthorsdottir.

Thanks to the following people for their work on the PBCore XML/RDF mapping: Glenn Clatworthy, Jean-Pierre Evain, Tessa Fallon, Rebecca Fraimow, Peggy Griesinger, Julie Hardesty, Sadie Roosa, Kara Van Malssen and the members of the PBCore and EBUCore communities who contributed to EBUCore 1.9