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
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
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.
The SE-B van route is cancelled today [Thursday, June 4] due to illness. Affected libraries are as follows:
Auburn
Windham
Pelham
Salem
Derry
Londonderry
Hudson
Nashua
Milford
Amherst
Merrimack
Bedford
Manchester
Thank you for your understanding.
Best,
Jennifer M. Finch (she/her)
Reference Librarian and State Data Coordinator
New Hampshire State Library
From the NHAIS Help Desk mailbox:
Would it be possible to have the “Date:” on the printout reflect the actual day it will go out on the van? I change the shipping date in the request and try to remember to leave a note in the lending library request box, but the shipping date always reflects the current date, not the actual date of the van pick up.
While most of what you see on the shipping labels is drawn from the request record (what you see on the Borrower's or Lender's Full Record Display pages), the date isn't. It's not the Request Date, Due Date, Date Shipped, Need by Date, Date Received, Date Returned, Date Checked In, or Respond by Date--all of which can appear in the request record depending on the request’s status. The date you see on shipping labels simply reflects the day the Format to Print button was used to display and (presumably) print the labels. Changing that to Date Shipped is not an option but you're welcome to write whatever else you want on shipping labels.
Our example record from last week also includes a URI entered in a subfield $1
Murphy, Colin (Journalist)
o Associated Locale: Ireland
Field Of Activity
Some of the fields found in this record are the same as those found in his authority record (such as “Occupation”). However, notice that the “Sources” listed in the authority record from the last post (which appear in 670 fields in the traditional authority record) don’t appear. The sources consulted by a cataloger to establish the authorized form of Colin Murphy’s name are important information to include in an authority record describing his name, but not in the “Real World Object” (RWO) record describing the person behind the name.
One other thing to note about these two types of records is that they have fields with links that refer to each other. The authority record has an “Identifies RWO” field with a URI pointing to the “real world object” record for the person Colin Murphy, and the “real world object” record has an “Is Identified By Authority” field with a URI pointing to the authority record for his name:
Murphy, Colin (Journalist)
Murphy, Colin (Journalist)
In the next post, we’ll look at the third type of URI in the example bib record, a link to a record for a “Relationship” term located in a subfield $4.
This is the fifth 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.
