Linked data and URIs -- #7 Resources

Even if your library isn’t currently using linked data, it’s helpful to be aware of these practices, especially with the increasing presence of URIs in cataloging data. The posts shared here over the past 6 weeks have only presented some introductory material on linked data and URIs in MARC records.

Here are some links to more information on these topics if you want to dive deeper:

• World Wide Web Consortium (WC3) wiki on linked data:
  https://www.w3.org/wiki/LinkedData
• Library of Congress Linked Data Service: https://id.loc.gov/
• Program for Cooperative Cataloging (PCC) URI FAQs
  https://www.loc.gov/aba/pcc/bibframe/TaskGroups/URI%20FAQs.pdf
• PCC Task Force on Linked Data Best Practices Final Report:
  https://www.loc.gov/aba/pcc/taskgroup/linked-data-best-practices-final-report.pdf
• PCC Guide to Formulating and Obtaining URIs:
  https://www.loc.gov/aba/pcc/taskgroup/linked-data-best-practices-final-report.pdf

 

This is the final post in a series 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.

Van route changes this week

We are still juggling ILL driver shortages and van maintenance schedules, so!
Today’s SW route and tomorrow’s SW-A route have been combined, modified, and shortened into one Friday [June 12] route. 

The libraries on these routes who WILL RECEIVE deliveries tomorrow (Friday) are as follows:

New London  
Newport  
Washington  
Charlestown  
Keene  
Marlborough  
Dublin  
Mont Vernon  
Weare

Thank you,
Jennifer M. Finch (she/her)
Reference Librarian and State Data Coordinator
New Hampshire State Library

More Request Manager modifications Tue 6/9 10pm

The NHAIS ILL System will be offline briefly tonight (Tuesday, June 9) starting at 10 o'clock. This will allow installation of software updates that include further enhancements to the Request Manager screen based on feedback following changes made two months ago.

With this update, you'll see a larger font size on the Request Manager page and the red dots will go away, with the same "unreviewed notes" icon you see elsewhere in the program replacing the dots.

Users will now see a search box to the left of the display tabs. This will allow you to narrow the statuses displayed to those that include, for example, "patron" or "pending" in the status name.

Clicking on the Borrower heading near the top of the Request Manager screen will take you to the Borrower Requests list and clicking on the Lender heading will take you to the Lender Requests page. This saves a step if you're looking for a request but don't find it in the expected status. When that happened in the past, you needed to go to Staff Dashboard > ILL Admin > Borrower [or Lender] Requests to look for a title and see its status. You can still do that but now you have the option of going straight to Borrower Requests or Lender Requests from the Request Manager.

There are other changes you'll see only if you use the All tab when viewing the Request Manager page (but remember that the Active tab shows you what you really need to see). Statuses with a count of zero will no longer display as grayed out. Also, in the last two months statuses that are not used in the NHAIS ILL System (like ILL Review and Passed to Local System) have been included in the All display. These inactive statuses will no longer be seen.

SW-A van route truncated Fri 6/5

Sorry for the delayed announcement. The SW-A van route is shortened/modified today [Friday, June 5]. The libraries who ARE receiving deliveries today are:

Charlestown
Keene
Marlborough
Dublin
Mont Vernon
New Boston

Thank you for your patience and understanding.

Be well,
Jennifer M. Finch (she/her)
Reference Librarian and State Data Coordinator
New Hampshire State Library

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.

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

• A person, family, or organization responsible for creating a work that is primarily textual in content, regardless of media type (e.g., printed text, spoken word, electronic text, tactile text) or genre (e.g., poems, novels, screenplays, blogs). Use also for persons, etc., creating a new work by paraphrasing, rewriting, or adapting works by another creator such that the modification has substantially changed the nature and content of the original or changed the medium of expression.
• URI(s)
• http://id.loc.gov/vocabulary/relators/aut
• Codes
• aut
• Variants
• joint author
• Narrower Terms
• author in quotations or text abstracts
• author of afterword, colophon, etc.
• author of dialog
• librettist
• lyricist
• screenwriter
• SubProperty Of
• http://purl.org/dc/elements/1.1/contributor 
• Editorial Notes
• changed MARC def
• History Notes
• MARC bib: 1XX/7XX/8XX $4
• Instance Of
• MADS/RDF Authority
• SKOS Concept 
• OWL ObjectProperty 
• BF Role
• Scheme Membership(s)
• List of Relator Terms
• Collection Membership(s)
• Collection of Past and Present Relators Entries
• Relators - BIBFRAME Collection
• Relators - RDA Collection
• Relators - RDA Work Collection
• Relators - RDA Creator Collection
• Change Notes
• 2021-08-02: new
• 2022-11-29: modified
• Alternate Formats
• RDF/XML (MADS and SKOS)
• N-Triples (MADS and SKOS)
• JSON (MADS/RDF and SKOS/RDF)
• MADS - RDF/XML
• MADS - N-Triples
• MADS/RDF - JSON
• SKOS - RDF/XML
• SKOS - N-Triples
• SKOS - JSON

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

• URI(s)
• http://id.loc.gov/vocabulary/contentTypes/txt
• Codes
• txt
• History Notes
• MARC bib: Leader/06: a or t
• Instance Of
• MADS/RDF Authority
• SKOS Concept 
• OWL Class 
• bibframe Category 
• Scheme Membership(s)
• Content Types
• Collection Membership(s)
• Content Types Collection
• Change Notes
• 2021-08-13: new
• Alternate Formats
• RDF/XML (MADS and SKOS)
• N-Triples (MADS and SKOS)
• JSON (MADS/RDF and SKOS/RDF)
• MADS - RDF/XML
• MADS - N-Triples
• MADS/RDF - JSON
• SKOS - RDF/XML
• SKOS - N-Triples
• SKOS - JSON

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.