June 4, 2026

Linked data and URIs -- #6 Example of a Relator URI

The 100 field for the author in our example bib record also contains a third URI in a subfield $4.

Graphical user interface, text, application, email

AI-generated content may be incorrect.

As stated in an earlier post, URIs may now be used in subfield $4 to link to records that provide information about the relationship/relator codes that catalogers have been using for a while in this subfield.

The URI in the second subfield $4 of this example:

$4 http://id.loc.gov/vocabulary/relators/aut

links to the record below from the Library of Congress’ Linked Data Service (https://id.loc.gov/) which describes the relator, “author” (represented by the code “aut” in the first subfield $4):

author

URIs in subfield $0 might also point to records describing other types of controlled terms used in cataloging. For example, the URI for content type from the Library of Congress’ Linked Data Service (https://id.loc.gov/vocabulary/contentTypes/sti.html) would be entered in the subfield $0 of a 336 field:

336 field from MARC record:

336    $a text $b txt $2 rdacontent $0 http://id.loc.gov/vocabulary/contentTypes/txt

Record linked to by URI in the subfield $0 describing the controlled term “text”:

text

In the next and final post of this series, you’ll find a list of resources that you can use to learn more about linked data and URIs in MARC records.

This is the sixth in a series of seven weekly blog posts written by Zahra Gordon, the NHSL Cataloger, which will explain “Linked Data,” an emerging topic in the library field, and how it relates to “Uniform Resource Identifiers (URIs),” which are appearing in subfields of MARC records with increasing frequency.

No comments:

Post a Comment

Comments on this blog are welcome, but they are moderated. Signed comments that we feel make a positive contribution to the discussion will be posted.