MODS to BIBFRAME
These MODS 3.7 to BIBFRAME 2.0 mappings and corresponding XSLTs were created by the MODS Editorial Committee to benefit institutions that want to reuse MODS records in a BIBFRAME environment, either by converting existing MODS/XML records or by using creation tools that can output them in the BIBFRAME OWL ontology. In the mappings each MODS element, subelement, and attribute was considered, however, each one was not be mapped to BIBFRAME. The mapping spreadsheets consist of twenty tabs; each tab corresponds to a top-level MODS element. These conversion specifications are drafts. Given the complexity of the task, there may be areas of improvement or inaccuracies. Please feel free to share comments and suggestions with the MODS Editorial Committee by sending a message to either the public MODS list ([email protected]) or to MODS EC Chair, Melanie Wacker, [email protected].
MODS 3.7 to BIBFRAME 2.0 Conversion (2023 Version)
MODS 3.7 to BIBFRAME 2.0 Mapping 
DRAFT FOR COMMUNITY REVIEW & FEEDBACK
MODS 3.7 to BIBFRAME 2.0 XSLT 2.0 DRAFT FOR COMMUNITY REVIEW & FEEDBACK
This 2023 version is a slightly improved and updated revision of the 2021 version (see below). It includes some fixes to bugs discovered in the 2021 version. It does not include any elements introduced in MODS 3.8. It has not been updated to the most current BIBFRAME version nor has it been aligned with the most up-to-date MARC to BIBFRAME conversion. A new, more complete, revision is expected in 2024.
MODS 3.7 to BIBFRAME 2.0 Conversion (2021 Version)
MODS 3.7 to BIBFRAME 2.0 Mapping
MODS 3.7 to BIBFRAME 2.0 XSLT 2.0
The mapping and XSLT above were created by members of the MODS Editorial Committee. The mapping will benefit institutions that want to reuse MODS records in a BIBFRAME environment, either by converting existing MODS/XML records or using creation tools that can output them in the BIBFRAME OWL ontology. The specifications are written from the perspective of MODS. Each MODS element, subelement, and attribute has been considered, though not every single element, subelement, or attribute could be mapped. The spreadsheet consists of several tabs, one for each top-level MODS element.
The BIBFRAME conversion for elements, subelements, and attributes is shown using Turtle syntax. A shorthand was used to accommodate the BIBFRAME mapping in the spreadsheet format. The BIBFRAME core class to which the properties apply are given as follows:_inst = bf:Instance
_w = bf:Work
_I = bf:Item
Other conventions used include:
<URI> = insert a URI
## = inherits the information from the rows above
There are some cases where vocabularies from http://id.loc.gov are appropriate and indicated. This hasn’t been done in a comprehensive way, and other relevant vocabularies could be used. Any suggestions for enhancing the specifications with additional vocabularies are encouraged.
The Turtle serialization shown in the mapping was used because it is the most human readable and can be accommodated in a spreadsheet. Turtle lends itself to the illusion that blank nodes are being specified, but the presence of intermediate classes is not the same as using blank nodes. The BIBFRAME and MODS Editorial Committee take no position on the use of blank nodes.
Questions and comments:
Contact Us (
April 19, 2024
)
Legal | External Link Disclaimer