The Library of Congress is making available for public use the following BIBFRAME 2.0 components. They are the result of work the Library is carrying out for a new Pilot for the input of BIBFRAME 2.0 data. To create the environment for that Pilot, the Library is converting the whole Library of Congress bibliographic file to BIBFRAME (model and vocabulary). This means developing BIBFRAME Work and Instance descriptions from the MARC Bibliographic records, bringing together and linking Work and Instance descriptions, and integrating them with Work descriptions converted from title and name/title MARC Authority records. This development has resulted in the following BIBFRAME 2.0 components and tools that we now share with the community for others to carry out development and investigations of the linked data environment using the BIBFRAME 2.0 Vocabulary.
BIBFRAME 2.0 Vocabulary Update
In the MARC to BIBFRAME conversion specifications it was occasionally necessary to make extensions or adjustments to the BIBFRAME 2.0 Vocabulary to accommodate data in MARC and there were also suggestions from users that needed to be accommodated. These additions, changes, or deletions are noted in the new Vocabulary that is now available http://www.loc.gov/bibframe/docs/. The previous version of the Vocabulary is archived at https://github.com/lcnetdev/bibframe-ontology .
In addition, several other elements were identified and made into a Library of Congress extension of BIBFRAME until they could be tested to see if they were needed. They are in the namespace bflc: and are viewable at http://id.loc.gov/ontologies/bflc.html and accessible at http://id.loc.gov/ontologies/bflc.rdf . An additional 20 very local properties needed in the Pilot merge and match operations for the current and ongoing conversions as MARC records flow into the Library's BIBFRAME system are also in the bflc: namespace.
MARC to BIBFRAME 2.0 Specifications
The Specifications are written by the Library's Network Development and MARC Standards Office from the perspective of MARC so that each element in MARC would at least be considered, even if not converted. The Specifications are Excel files accompanied by a few explanatory Specifications in Word.
If there is little of no use of an element in the Library of Congress records the Specifications usually say "nac" (no attempt to convert) in the conversion column. Some elements in a MARC record are not relevant outside the MARC environment so they are simply marked "ignore".
A shorthand is used for the specification of the conversion from MARC to BIBFRAME RDF. The shorthand uses W for Work, I for Instance, but Item for Item. The Specifications use the vocabularies that are in id.loc.gov in a number of cases, especially for names, subjects, genre, and 007 and 008 data.
The Specifications also use properties with strings for data that will serve as keys to be used when trying to match and merge data to conform to the BIBFRAME Work and Instance models and to identify labels and RWOs in the MADS name and subject files. These local elements (mentioned above as bflc: namespace properties) are included in the conversion of names and titles. The Library of Congress will be using these elements through multiple conversions until we are satisfied with the file conversion. These "helper" local elements will be eliminated from the RDF when the merge and match is complete unless we see a need to keep certain ones for data that will continue to come into our BIBFRAME environment from MARC.
Note that these Specifications will be changed as needed as we develop the system for the BIBFRAME 2.0 Pilot. Revisions to specifications will be marked and the file name and the title on the document will indicate a revision (e.g., R1, R2, R3, …).
MARC to BIBFRAME Conversion Programs
The Programs for converting the MARC data to BIBFRAME were written for the Library of Congress by Index Data. They are written in XSLT and are available for download on the Library of Congress Github site at https://github.com/lcnetdev/marc2bibframe2 . The Library is currently working with these conversions in development of the Pilot project and we expect that they will be adjusted as work progresses.
A description of the conversion Programs and their use with Index Data's Metaproxy and YAZ tools are found in a ReadMe file at the site.
BIBFRAME 2.0 Tools
A conversion tool will also available shortly to enable viewing converted BIBFRAME descriptions. The Library of Congress uses Index Data's Metaproxy tool with its Voyager OPAC system to enable searching using Z39.50 or SRU, and the search results may be obtained in MARC, MODS, and soon BF2.0. Other tools will be announced as they become available.