1. MARC Tags to BIBFRAME Vocabulary: a new view of metadata Sally McCallum Library of Congress smcc@loc.gov ALA - January 2014

2. Outline Introduction A bit of the BIBFRAME vocabulary –Cataloging resource categories –Titles –Relationships Thanks and URL

3. BIBFRAME is about metadata Metadata for libraries has two aspects –Rules for recording it were: AACR2 and its predecessors are (going forward): RDA –Rules for structuring and encoding it for exchange basically MARC process started to replace MARC with a more internet compatible framework: BIBFRAME and RDF

4. Grouping and identifying In MARC exchange environment we identified data elements with “content designation” –tags to group and identify –subfields to identify –serialized with ISO 2709 and later with XML In BIBFRAME we use W3C’s RDF conventions –classes to group and identify (names have initial capitals) –properties to identify and relate (names have initial lower case) –serialized in several ways – most human readable called “turtle” The list of classes, properties, and their attributes are the BIBFRAME (BF) vocabulary

5. Data values (ranges) –Value type specifications in MARC range from codes to URI, but mostly text –Value types (ranges) in BIBFRAME RDF statements: domain -- property -- range Each property has a designated range of value types In the BF vocabulary we allow data to be: –Strings or literals (i.e., words) Work – title – Webster’s collegiate dictionary Instance – extent – 1045 pages –URIs Unspecified – language – id.loc.gov/vocabulary/languages/eng –Classes Unspecified – language – Language Language – languageOfPart – english Language – languageSource – ISO 639-2

6. BIBFRAME - Primary classes BF has 4 primary classes –Work Includes RDA’s works and expressions Includes MARC uniform title authority information and subjects from MARC bibliographic –Instance Includes RDA’s manifestations Approximately MARC bibliographic descriptions –Authority Includes MARC names and subjects (but not titles which are BIBFRAME Works) Other types to be explored, e.g., classification, publisher info –Annotations Includes RDA’s items

7. A taste of the BIBFRAME vocabulary …

8. Cataloging resource categories BF Work resource types (subclasses) ~MARC LDR/06 Text, Cartography, Audio, NotatedMusic, NotatedMovement, Dataset, StillImage, MovingImage, ThreeDimensionalObject, Multimedia, MixedMaterial –High level to enable –Profiles for input or validation –Database configuration –Display options –Multiple possible for a cataloging resource BF Instance communication and mode (subclasses) ~MARC 007/00, 008/23, LDR/07 Print, Manuscript, Archival, Tactile, Electronic Monograph, MultipartMonograph, Serial, Integrating, Collection

9. Cataloging resource categories Properties for special category lists ~MARC 336-8 contentCateory (property) mediaCategory (property) carrierCategory (property) –These accommodate the RDA lists, but other lists from other communities could be used –How? contentCategory --- URI to a Dublin Core list element Or contentCategory --- Category (class) –Category – categorySource – schema.org –Category – categoryValue --

10. Titles Key elements that take multiple forms instanceTitle (property) ~MARC 245 Parse into properties: titleValue, subtitle, partNumber, partName workTitle (property) ~MARC 240 & name/title authority Parse into same properties as instanceTitle -- plus titleAttribute for additions for uniqueness RDA-based properties for cataloging resource characteristics ~MARC 377-384 –formDesignation, treatySignator, legalDate, musicNumber, musicKey, musicVersion, musicMedium, originPlace, originDate Can we exploit this additional information for the end user?

11. Titles Special types of titles Need options because of variations in cataloging rules and resource types –Simple title (property) -- no type available or needed, e.g., Dublin Core title –titleStatement (property) – to accommodate transcription needs of ISBD –abbreviatedTitle (property) ~MARC 210 –keyTitle (property) ~MARC 222 –titleVariations (property) ~MARC 246 and Authority 4XX

12. Other description property groups in the vocabulary category view –Instance description –Identifiers –Notes –Subjects –Classification –Agents (creators, contributors, etc.) –…

13. Title to title relationships Two fundamental targets for BIBFRAME –Describe a cataloging resource –Link it to other cataloging resources Over 300 relationships in RDA, around 30 in MARC Two ways to link –Use general relationship properties –Use specific relationship properties

14. Title to title relationships General relationship properties –If relationship type unknown ~many MARC 7XX relatedResource – URI pointing to the BF Work –Don’t know URI? relatedResource – Related (class) nameOrTitle – –Want to give a special type of relationship? relatedResource – Related (class) nameOrTitle – relationship -- –Other general relationships Work-to-Work, Work-to-Instance, Work-to-expression,...

15. Title to title relationships Specific relationship properties –Around 40 specific relationships have been included in the BF vocabulary as properties –specific – largely the relationship groups from RDA hasEquivalent, hasDescription, hasPart, accompaniedBy, precedes, succeeds, hasDerivative (plus reciprocals) –very specific – sub-relationships to the specific ones ~MARC 76X-78X + a few notes supplementTo (accompaniedBy); translation (isDerivativeOf), reproduction (hasEquivalent), etc. Handling specificity of relationships needs to be explored.

16. Thanks! Now, check out the vocabulary for yourself –www.loc.gov/bibframe is the main home for the initiative and you can go to the vocabulary from there.www.loc.gov/bibframe –Go to the Category view and explore but read the description and terminology/convention “papers” first. (Note, the site, which is across 2 locations, is being reorganized but the new vocabulary views and supporting documents are in place.)