Just a quick note to our Metadata Discussion Group blog readers to let you know that we might be quiet right now but we are still discussing metadata!
Jennifer and I are both still involved in the MODS and RDF Descriptive Metadata Subgroup within the Hydra community. We’ll likely have additional decisions from that group regarding mapping MODS to RDF and some demo tools to share this fall.
If you have a metadata topic you are interested in discussing, please suggest a topic and if you’re not on our email list make sure you’re on that so you stay updated.
Thank you for your attention and please continue enjoying your summer!
[UPDATE: This meeting IS happening and is now scheduled for Tuesday, April 5 from 9-10am in Wells Library 043. Apologies for missing the meeting where this was originally scheduled but this thing is BACK ON! And don’t forget to check out Jennifer’s post discussing More about MODS (and XML) to learn more about MODS and its uses before we meet.]
It’s been a while since the Metadata Discussion Group last met but Jennifer and I think we have something that could benefit from a few more metadata-aware eyes at IU. If that’s you, or if you’re interested in topics like transforming metadata or linked library data, read on!
There is an ongoing effort in the Hydra community to figure out strategies to deal with descriptive metadata in RDF for use in Fedora 4 (the digital object repository that we hope to upgrade to here at IUB Libraries). The MODS and RDF Descriptive Metadata Subgroup, lead by Steven Anderson from the Boston Public Library, is working on how to handle MODS XML as RDF that will create a usable, if unofficial, metadata application profile to bring MODS into Fedora 4 as RDF properties.
So far this work has involved going through MODS element by element using examples from various institutions and asking the question “If [you] had to move that [MODS element] to RDF in Fedora 4 today, what would [you] chose to do with it?” (see the work for Abstract as an example). The MODS elements examined so far include name, title, typeOfResource, genre, originInfo, physicalDescription, abstract, language, and current work is happening on tableOfContents.
Join us on Tuesday, April 5 from 9-10am in Wells Library 043 to learn about this effort and Indiana University Libraries’ participation. We’ll share contributed examples and discuss how the MDG might help this effort along for IU and the Hydra community.
Since the time was blocked off on everyone’s calendars (and since we hadn’t met in a while), group members participated in a round robin. Below is a summary of the updates. Errors and misunderstandings on my part may be corrected in the comments below and I’ll do my best to update the post.
Andrea Morrison reported seeing more and more ORCiD identifiers in Library of Congress Name Authority File (NAF) records
Browse Functionality in Progress for IUCAT
Rachael Cohen reported on the progress to implement browse for IUCAT
Working from code developed by Cornell (they also use Blacklight for their discovery layer)
Development team will start with author browse, then tackle Kinsey subject headings, then Library of Congress Subject Headings (LCSH)
Spencer Anspach clarified how browse will work:
Authorized access points in bibliographical records will be hyperlinked
Browse results will display all access points (authorized and unauthorized) that appear in bibliographic records–all results will have a number next to it, denoting how many times that access point is used in the bibliographic records database; some access points will have an icon next to them, which will denote that the access point is the authorized version (NAF, etc.)
Clicking on the icon will take a user to the authority record for that authorized access point (MARC 670 fields will NOT display to users)
Clicking on any of the access points will conduct a search on that access point
Concerns: batch loaded records from vendors (we won’t mention names) do not have authority control; one vendor in particular never includes dates (MARC subfield d) in authorized access points–this will certainly have an adverse impact on browse!
Shelf ready materials often do not have authority control–those errors are picked up in post-cataloging, by the Database Management team
At the Metadata Discussion Group meeting on March 8 April 5, 2016, we will talk about some of the challenges of mapping a descriptive metadata structure standard (in this case, MODS) from a XML-based expression to one that is RDF-based. This post will explain what MODS is and what it’s used for.
MODS: the ‘Who, What, and When’
The Metadata Object Description Schema (MODS) was published in 2002 by the Library of Congress’ Network Development and MARC Standards Office. The standard is maintained by an editorial committee comprised of library metadata practitioners from North America and Europe.
MODS is a “bibliographic element set” that may be used to describe information resources. MODS consists of 108 elements and subelements (there are 20 top-level or “parent” elements). At this point, I’ll urge you to go read the brief overview of MODS on the Library of Congress’ Standards website.
Go ahead. I’ll wait.
You read that bit about MODS being more or less based on MARC21, right? In the example below, I’ve described a sheet map using MODS elements and MARC tags.
DATA (formulated according to AACR2, if that sort of thing matters to you)
MARC TAG (and mapped MARC data value, when applicable)
Campbell County, Wyoming
Campbell County Chamber of Commerce (Wyo.)
Campbell County Chamber of Commerce
1 map ; 33 x 15 cm
Table 1. Data expressed in MODS elements and MARC tags.
There’s a full mapping of MARC21 tags to MODS elements available, if you’re really curious. This example demonstrates that, although there are a few divergences, MARC21 was built to map almost directly into a MODS element.
MODS encodes descriptive metadata, or information about resources (title, creator, etc.). MODS and MARC21 are examples of data structure standards. Elements or tags are meant to serve as containers for data. Structure standards do not give any directions about how to formulate data—those directions come from data content standards (AACR2, RDA, DACS, etc.). The main purpose for structure standards (Dublin Core, EAD, and TEI are other examples of metadata structure standards) is to encode data so that it can be manipulated by machines. Elements separate discreet information for use in search and browse indices. Data structure standard elements often convey the meaning of the data. The MODS:title element only contains the word or words that are used to refer to a resource. MODS:title will never serve as a container for the resource’s size.
MODS: the ‘Where, Why, and How’
MODS was built “for library applications.” MODS has been chiefly implemented to support discovery of digital library collections. At IUB Libraries, MODS is the metadata standard of choice for the digital objects that are ingested into our digital collections repository, Fedora.
MODS elements are expressed in XML. XML is a metalanguage, which means that XML is an alphabet, of sorts, for expressing other languages. The figure below illustrates the XML syntax (the “alphabet”) by which XML expresses another language. A fake language with a bogus element named “greeting” is encoded in Figure 1.
HTML (the language responsible for displaying this webpage to you right now), EAD, and TEI are also expressed using XML.
From the beginning, MODS was designed to be expressed as an XML schema. Schemata are the sets of rules for how languages work: which elements are valid and what their semantic meanings are, which elements nest within others, whether or not an element can be modified by attributes (e.g., the MODS:titleInfo might have an attribute called “type”), and whether there is a controlled list of values for a given attribute (e.g., the MODS:titleInfo “type” attribute is limited to the values “abbreviated, “translated,” “alternative,” “uniform”).
MODS records are created in a number of ways. You could open up an XML editor and start creating a MODS/XML record. If you want to really get to the know the MODS standard, that wouldn’t be a bad idea. However, if you wish to create metadata for a half a million photographs, editing raw XML won’t be terribly efficient. At IU, we have a few different methods for creating MODS records for digital objects. My favorite is the Image Collections Online cataloging tool. Use of the tool is restricted but I’ve included a screenshot below.
Once a collection manager decides which metadata elements are desired and has consulted with the metadata specialist for digital collections (our own Julie Hardesty), those elements will display in a web form. Data may then be entered without needing to know XML or MODS. In Figure 1, you’ll see a box in the lower right-hand corner “Transform metadata to…” Clicking on that link that says “mods” allows me to download the data that I input into the web form as MOD/XML. You may view the full record for this photograph below.
That’s the 5 cent tour of MODS, as it’s expressed in XML. Questions? Leave a comment below!
A message went out to the Program for Cooperative Cataloging (PCC) listserv announcing the appointment of the PCC Task Group on URIs in MARC. The Task Force was formed to “help fulfill our strategic objective to optimize library data for the web” (email from Kate Harcourt to PCCLIST, 8 September 2015).
The group’s charge is available online (.docx). In brief, the group’s objective is to find ways to “transition from string-based descriptive and authority data.”
Those working in an OCLC environment may have already seen URIs in MARC. In order to transition to linked library data, the German National Library (DNB), regularly adds the MARC subfield 0 to access points in MARC bibliographic records. Below is a screenshot of OCLC record 827841368.
The information in subfield 0 contains a code identifying the authority file in parentheses, immediately followed by the authority record control number for the vocabulary term. DE-588 refers to the German National Library’s Integrated Authority File–Gemeinsame Normdatei (GND), which is available as linked data.
Subjects and names selected from authority files are the first obvious identifiers that might be included in bibliographic records; however, those aren’t the only terms selected from controlled vocabularies. Task Force charge #4 addresses “other” entities and relationships expressed in bibliographic records that would be better treated as identifiers. For instance, all RDA Relationship Designators (Appendices I, J, K, M, and eventually L) are terms that might be referenced with URIs, as all RDA element and vocabulary terms are available in the Library of Congress Linked Data Service and/or the Open Metadata Registry. The URI for “Sequel to“, as it might appear in a subfield i of a 7XX field, would become a machine-actionable link between the 1st book in a series and a 2nd book in a series. So much more of our RDA data (e.g., RDA carrier types or RDA media types) could be referenced by URIs.
Quoting again from the charge: “Providing URIs in MARC records will greatly facilitate the reuse of MARC data as linked data and opens the way for catalogers to work with entity registries and controlled vocabularies from the larger metadata community.”