Date on shipping labels

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.

Linked data and URIs— #5 Example of a Real World Object URI

Our example record from last week also includes a URI entered in a subfield $1

When you searched on the URI in the subfield $0, you were brought to an authority record for the name “Colin Murphy.” When you search on the URI found in the subfield $1, on the other hand, you’re brought to a description of the person behind this name:

 

Murphy, Colin (Journalist)

• URI(s)
• http://id.loc.gov/rwo/agents/no2014111945
• Is Identified By Authority
• http://id.loc.gov/authorities/names/no2014111945

o   Associated Locale: Ireland

Field Of Activity

• Field Of Activity: Journalism
• Occupation
• Occupation: Journalists
• Occupation: Playwrights
• Occupation: Screenwriters
• Occupation: Filmmaker
• Instance Of
• MADS/RDF RWO
• BF Person
• FOAF Person 
• 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

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)

• URI(s)
• http://id.loc.gov/authorities/names/no2014111945
• Identifies LC/NAF RWO
• http://id.loc.gov/rwo/agents/no2014111945

Murphy, Colin (Journalist)

• URI(s)
• http://id.loc.gov/rwo/agents/no2014111945
• Is Identified By Authority
• http://id.loc.gov/authorities/names/no2014111945

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.