Linked data and URIs -- #4 Example of an Authority Record URI and more...
Linked data and URIs -- #4 Example of an Authority Record URIHere’s part of a record from the Library of Congress’
catalog for a work by Colin Murphy. Notice that the 100 field has URIs entered
in subfields $0, $1, and $4. We’ll look at the link in the subfield $0 first:  If you paste the link from the $0 into a browser,
you’ll be brought to the authority record for Colin Murphy’s name from the
Library of Congress’ Linked Data Service:
Murphy, Colin (Journalist)
You
might notice that this authority record contains a lot of information not
traditionally found in authority records (such as alternate markup formats).
Some of this information is intended to facilitate linked data applications.
Here’s the authority record for Colin Murphy’s name from the Library of
Congress’ traditional authority file:
LC control no.: no2014111945 LCCN Permalink: https://lccn.loc.gov/no2014111945 (link opens in a new tab) 000 01100cz a2200241n 4500 001 9638516 005 20250804200623.9 008 140822n| azannaabn |n aaa c 010 _ _ $a no2014111945 035 _ _ $a (OCoLC)oca09942879 035 _ _ $a 9638516 040 _ _ $a TNJ $b eng $e rda $c TNJ $d InNd $d DLC 053 0 _ $a PR6113.U7667 100 1 _ $a Murphy, Colin $c (Journalist) 370 _ _ $c Ireland $c Great Britain $2 naf 372 _ _ $a Journalism $2 lcsh 374 _ _ $a Journalists $a Playwrights $a Screenwriters $2 lcdgt 374 _ _ $a Filmmaker 670 _ _ $a Somerville-Large, Peter. The Mount Street Club, 2014: $b title page (Colin Murphy) 670 _ _ $a The Mount Street Club book website, viewed Aug. 22, 2014 $b (Colin Murphy; journalist, film, and documentary maker who writes for politico.ie and various Irish and British papers) $u http://mountstreetclub.com/?page_id=154 670 _ _ $a A day in May, 2022: $b t.p. (Colin Murphy) 670 _ _ $a Amazon author page, Aug. 22, 2023: $b (Colin Murphy is an Irish playwright, screenwriter and journalist) 999 f f $i 522cb403-480c-4675-be7f-40dddc0f88d0 $s f11e8ed5-b846-4d88-85f8-b56e71fc7dc1 In the next post, we’ll look at the “Real World Object” (RWO) record for the journalist Colin Murphy, accessed through the URI in the subfield $1 This is the fourth 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.    
Did that message make it to the list?From the NHAIS Help Desk inbox:
So - I'm wondering, if I send a message to the ILL listserv (nhais-ill@maillist2.nh.gov), is there a way for me, as the sender of the post, to confirm that it actually showed up on the listserv? ...since I don't get a copy of my own message in my own inbox. Sometimes a post is greeted with mossy silence and I don't know if it's because it didn't actually get posted or because no-one has anything to say about it
The default for all e-mail lists maintained by NHAIS Services is for subscribers to receive their own posts to the list but it's possible to change that. You can check the settings for your list subscription by logging into your account and looking under Your [Listname] Subscription Options for "Receive your own posts to the list?" If it's already set to Yes, check your own inbox to see if there's a rule that’s routing your messages elsewhere. But wait...how do you log into your account? Go to the "Listinfo" page and enter your subscribed address and password. What's the "Listinfo" page? It's different for each list: How do you find your password? Near the bottom of the "Listinfo" page, enter your subscribed address next to the Unsubscribe or edit options button, then click the button.  On the next page, find the Password reminder section and click the Remind button to have a password sent to your subscribed address.  No matter what the settings, one way you can confirm that your message was posted is to check that it appears in the list archives. This also involves going to the "Listinfo" page, at the top of which is an About [Listname] section which ends with a link to the archives. Click the link and log in. 
 
SW van route truncated Mon 5/18The SW ILL van route had to be shortened for today [Monday, May 18]. The only libraries receiving ILL deliveries today are:
Linked data and URIs -- #3 Data Provenance Subfields
Data provenance subfields ($0 and $1) provide information about metadata/cataloging data in other subfields within the same MARC field. Codes in parentheses at the beginning of these subfields refer to the category of information given and the subfield within the MARC field to which they apply (if they don’t apply to all of the subfields). The meaning of these codes is given in MARC documentation (Ex. https://www.oclc.org/bibformats/en/controlsubfields.html#subfielddp)) We’ve always provided information about our metadata within catalog records, but these subfields allow us to provide this information in a more structured way than we have in the past. For example, here’s the same note without and with information about the source/ provenance of the cataloging data given in a separate subfield. The code in parentheses tells you that the text in the subfield $7 is a “note on metadata work,” i.e. a note about the cataloging data. In this example, there’s no need to also include an indication of the subfield to which this text applies because there’s only one other subfield in the 520 field: 520__”Everybody has needs. This nonfiction book explores the basic needs of people and how we get our needs met”—Publisher’s website. 520__”Everybody has needs. This nonfiction book explores the basic needs of people and how we get our needs met”$7(dpenmw)Publisher’s website. Here’s an example with the source consulted for the
metadata in the 264 subfield $a given in both textual and URI forms in separate
subfield $7s. The first code in parentheses tells you that the category of
information provided about the metadata is “source consulted” and the second
code tells you that the information applies to the subfield “a” of the 264
field:
264 #1 [Helsinki] : $b Dionysos Films, $c [2019] $7 (dpesc/dpsfa)Dionysos Films website $7 (dpesc/dpsfa)https://www.dionysosfilms.fi/ Subfield $0 vs. Subfield $1 As explained in the last post, subfield $0 carries the “Authority record control number or standard number.” A URI used in $0 will link to a description of the name or label used in the MARC field. The subfield $1 carries a “Real World Object (RWO) URI,” linking to a description of an entity. The descriptions that these two types of URIs link to might look identical at first glance. So, what’s the difference? Remember that the purpose of linked data is to make it easier for computers to find and interpret information. In linked data world, it’s important for computers to be able to distinguish between a name used for an entity and the entity that’s being named. The subfields used for URIs signal this distinction. URIs entered in subfield $0 link to authority records for names or terms used for entities (people, places, corporate bodies, etc.), while Real World Object (RWO) URIs entered in subfield $1 link to descriptions of the entities themselves (the actual people, places, corporate bodies, etc. behind these names or terms). My personal mnemonic device for this is that “0” comes before “1,” and we had authority records in the library world long before records for “real world objects.” For example, a URI in the subfield $0 of a 100 field for the author Charles Dickens would refer to his name, the alphanumeric string that is used to identify him (Dickens, Charles, $d 1812-1870), while a URI entered in a subfield $1 of the 100 field for this author would refer to the human being who wrote “Bleak house” and is identified by this name. Even though they might appear similar at first glance, records linked to by URIs in subfields $0 or $1 may contain different types of data. In the next few posts, we’ll look at an example of three types of links in a catalog record with URIs that link to three different types of descriptions.This is the third 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 SE-B van Thu 5/14The SE-B ILL van route is canceled today [Thursday, May 14] due to illness. The affected libraries are:
"Posted by:" noreply@blogger.com (Mary Russell) |