Showing posts sorted by relevance for query subfield n. Sort by date Show all posts
Showing posts sorted by relevance for query subfield n. Sort by date Show all posts

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.

Posted by Mary Russell at 2:00 PM

Labels: ,

December 24, 2024

007 - Physical Description Fixed Field (Part 1)

The 007 tag is used to code data related to the physical characteristics of a work being cataloged. The data in this tag may refer to the work in its entirety, to parts of the work (including accompanying material), or to applicable additional physical characteristics.  

Elements in field 007 are identified based on their position and according to the category of material defined by the first position (00) in the field. There are lots of possible categories of materials and BF&S includes a chart that shows the various code options and the meanings of the positions in the tag based on those codes. The categories of material for which 007 coding is defined are map, electronic resource, globe, tactile material (something that is intended to be read by touch), projected graphic, microform, nonprojected graphic, motion picture, kit, notated music, remote-sensing image, sound recording, text, and videorecording.

Software will often display the 007 tag will with subfield delimiters to make the information easier for people to read. However, the actual tag is coded by position, not with subfields. Both indicators are undefined for the 007 tag.

I'm going to describe one fairly simple category of material, a globe, to give you an idea of how this tag works.

A globe is defined in BF&S as "the model of a celestial body, usually the Earth or another celestial sphere depicted on the surface of a sphere." 

  • An 007 tag describing a globe begins with "d" (labeled as subfield a)

  • The next position (subfield b) contains a one-character code for the specific material designation (a celestial globe, for example, is "a")

  • Next (subfield d) is a code for one-color ("a") or multicolor ("c") -- subfield c is skipped over, I don't know why

  • Next (subfield e) is a code for the physical material the globe is made of (paper, wood, metal, plaster, etc.)

  • The final position (subfield f) contains a code indicating if the globe is a facsimile ("f"), or other kind of reproduction

Some examples:

 A globe of the Earth's moon, in multiple colors, made of metal, that is not a reproduction of any kind:

007    ǂa d ǂb e ǂd c ǂe d ǂf n    

A terrestrial globe, in a single color, made of plastic, which is not a reproduction:

007    ǂa d ǂb c ǂd c ǂe i ǂf n  

It is common to see 007 tags in records for kits where there are a variety of included items of different types and the 007 tag contains details about specific pieces of the kit. Books that are accompanied by a computer disk (these were common when I started cataloging) also use these tags.

Enjoy the holiday tomorrow and we will wrap up this series next week with another, more complex, 007 example.

 

Posted by Mary Russell at 4:58 AM

Labels: , ,

May 28, 2026

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

Graphical user interface, text, application, email AI-generated content may be incorrect.

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)

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.

Posted by Mary Russell at 2:00 PM

Labels: ,

Subscribe to: Posts (Atom)