Jennifer Losalio LIS 694 Dr. Asako 9/27/2015
Metadata Application Profile: Determining element set
● The name of the collection of your choice
For this assignment, I’ve chosen Scenario 1: University Photographs Collection.
● A set of metadata elements for the collection
The following are elements adapted from the Metadata Object Description Schema (MODS) that I’ve selected to describe resources in my collection at the item‐level.
Shared Record Elements (Content‐Related)
❖ Photograph Title (MODS= <titleInfo>)
❖ Photographer (MODS = <name><namePart><namePart><date>,
<namePart><family>, <namePart><given> & <role> = creator)
❖ Subject of Photograph
➢ (MODS = <subject><name>) [for photos of people and meetings/conferences]
➢ (MODS = <subject><topic>) [for photos of buildings, events, and historic moments]
➢ (MODS = <subject><temporal>) [for photos taken during a specific time frame]
➢ (MODS = <subject><occupation>) [for photos of occupational information related to content of photograph]
❖ Location of Photograph (MODS = <originInfo><place>)
❖ Date of Photograph (MODS = <originInfo><dateCreated>
Analog Object‐Record Elements (Carrier‐related)
❖ Photograph Medium (MODS = <physicalDescription><form> = print or slide or negative)
❖ Photograph Collection (MODS = <relatedItem> = host>)
❖ Photograph Repository (MODS = <location><physicalLocation>)
❖ Photograph Size (MODS = <physicalDescription><extent>)
❖ Photograph Copyright (MODS = <originInfo><copyrightDate>)
❖ Photograph ID Number (MODS = <identifier>)
❖ User Access Information (MODS = <accessCondition>)
❖ Resource also available in ____ form (MODS =
<relatedItem><location><url>) [Optional field only if other forms/mediums exist for the same resource]
Digital Object‐Record Element (Carrier‐related)
❖ Form (MODS = <physicalDescription><form> = electronic)
❖ Digital Origin Information (MODS = <physicalDescription><digitalOrigin>)
❖ Digital Collection (MODS = <relatedItem> = host)
❖ Link to Digital Image (MODS = <location><url>)
❖ Digital Image Publisher (MODS = <originInfo><publisher>)
❖ Date Digitized (MODS = <originInfo><dateCreated>)
❖ Digital Image Copyright (MODS = <originInfo><copyrightDate>)
❖ Digital File Format (MODS = <physicalDescription><internetMediaType)
❖ Digital File Number (MODS = <identifier>)
❖ User Access Information (MODS = <accessCondition>)
❖ Resource also available in ____ form (MODS =
<relatedItem><location><url>) [Optional field only if other forms/mediums exist for the same resource]
As suggested in the assignment description, in selecting the aforementioned
elements, I considered the following factors: the nature and characteristics of the resources, envisioned users, and functional requirements for browsing, searching, and limiting.
Because I wanted to include descriptive elements according to metadata best
practices, I referenced the readings from Module 3: Describing Resources for Access.
One best practice mentioned in the Miller readings is the concept of mapping local elements to shared elements. The author claims that good metadata often results when metadata designers and creators take both local and shared resource discovery purposes into account. (2011, Chapter 2, p. 40). When considering an underlying schema to map my local elements to, I jumped at the idea of utilizing MODS as the schema to model my locally‐created elements after because of the benefits
mentioned in Asako’s Module 4 presentation, namely: its capability for richer description than Dublin Core and its use of language‐based tags.
Before settling on MODS as my guiding metadata schema, I referenced Riley’s (2010) poster visualization of metadata standards to ensure that the type of resources in my collection would match up with MODS. Satisfied with MODS semi‐strong connection with the Visual Resources domain (a domain whose description fits the type of my resources), I felt comfortable using it as a model for my local elements.
Another best practice of metadata creation mentioned in the Miller readings is the One‐to‐One Principle (2011, Chapter 2, p. 41). In Module 3’s forum assignment in which we had to comment on metadata records, I got confused by a record that contained mixed elements describing analog and digital carriers of the content. Not wanting to put users of my collection through the same confusion, I’ve opted to maintain the One‐to‐One Principle. Because I’ve assumed that users of the University Photographs Collection may still have access to the analog objects of their digitized copies, I made sure to distinguish record elements by content and carrier information.
Essentially, as described by Miller (2011, Chapter 2, p.43), I’ve adopted the method of creating distinct records for analog and digital manifestations of the same work with full content information.
Brief Definition & Rationale of Use for the Selected Elements
The following information (Brief Definition & Rationale) about the elements is based on/cited from the MODS User Guidelines (ver. 3) by the Library of Congress, as well as other class content.
Shared Record Elements
(Content‐Related) Brief Definition Rationale
Photograph Title (MODS=
<titleInfo>)
A word, phrase, character, or group of characters, normally appearing in a
resource, that names it or the work contained in it.
I included this element because the MODS
guidelines describes it as an “extremely important access point for digital library resources”, as well as an important deciding factor for end users when it comes to investigating a resource further.
Photographer (MODS = <name>
→ <namePart><date>,
<namePart><family>,
<namePart><given> & <role> = creator)
The name of a person, organization, or event (conference, meeting, etc.) associated in some way with the resource.
I included this element because I want users to be able to discover the name of the photographer responsible for creating the photograph, and I want
my users to be able to search for other photographs in the
collection created by the same photographer. Along with subelements for name information
(<namePart><date> &
<namePart><family> &
<namePart><given>)I’ve also included the <role>
subelement with a
“creator” value so that if a photograph is associated with other names, the record will show the photographer’s name as the main entry for the record.
Subject of Photograph (MODS = <subject><topic>) [for photos of buildings, events, and historic moments]
(MODS = <subject><temporal>) [for photos taken during a specific time frame]
(MODS = <subject>
<occupation>) [for photos of occupational information related to content of photograph]
(MODS =<subject><name>) [for photos of people and meetings/conferences]
A term or phrase representing the primary topic(s) on which a work is focused.
As a library catalog user and someone who helps people navigate library catalogers, users are always wanting to begin their search with the
“aboutness” of something, as described in Asako’s Module 3 PowerPoint lecture. Subject terms are popular with users to begin searches and discover other materials that share those same subject(s), and so I think it’s critical to include this kind of
element. I’ve also included appropriate subelement information that will allow users to search for
resources on specific people, buildings, time frames, historic events, and occupations as subject
terms relevant to the
content of the photograph.
Location of Photograph (MODS
= <originInfo> <place>)
Name of a place associated with the issuing, publication, release, distribution, manufacture,
production, or origin of a resource.
I want users to be able to discover where a
photograph was taken.
Date of Photograph (MODS =
<originInfo> <dateCreated>
The date of creation of the resource.
I want users to be able to discover when a
photograph was taken.
Analog Object‐Record Elements (Carrier‐related)
Brief Definition Rationale
Photograph Medium (MODS =
<physicalDescription> <form>
= print or slide or negative)
A designation of a particular physical presentation of a resource, including the physical form or
medium for a material for a resource.
Because there may be multiple manifestations of a work (i.e.: an analog version and a digital version), I want to
minimize user confusion by making a clear statement about what kind of
form/medium the resource is in within the record that they are observing.
Photograph Collection (MODS =
<relatedItem> = host)
A value to describe a host or parent resource or a collection in which an item belongs.
I want users to be able to discover a whole collection of other items that the resource record they are observing is a part of.
Photograph Repository (MODS
= <location>
<physicalLocation>)
The institution or repository that holds the resource or where it is available.
Assuming that users have access to the analog photographs from which their digital copies are derived, I want users to be able to discover the
physical location of the resource.
Photograph Size (MODS =
<physicalDescription>
<extent>)
A statement of the number and specific material of the units of the resource that express physical extent.
Depending on what use users may have in mind for an analog photograph, I think it’s helpful to know the extent (in this case, size) of it. Also, because my user audience ranges from an academic one to a general one, I want to make sure I include as much possibly useful information as possible.
Photograph Copyright (MODS =
<originInfo> →
<copyrightDate>)
A date in which a resource is
copyrighted.
I want users to know: 1) that a copyright for the image exists; and 2) when the image was
copyrighted.
Photograph ID Number (MODS
= <identifier>)
Contains a unique standard number or code that distinctively identifies a resource.
In Asako’s Module 4 presentation, she
described DC elements, one of which was
dc:identifier. This element makes an “unambiguous reference” to the
resource. MODS equivalent element is the <identifier>
element, and it serves the same purpose. Again, in order to avoid confusing users with what resource the record is describing exactly, I think the
inclusion of an <identifier>
value would help ensure
resource discovery accuracy.
User Access Information (MODS
= <accessCondition>)
Information about restrictions imposed on access to a resource.
For our Module 4 assignment, we were required to observe
metadata collections. One such collection cited by Monica included restricted images, and I thought it would be helpful if the user could be able to filter their searches based on access information. I included this element because I want that capability for my collection’s users.
Resource also available in ____ form (MODS =
<relatedItem><location>
<url>) [Optional field only if other forms/mediums exist for the same resource]
Information that identifies other resources related to the one being
described.
In Miller’s Chapter 2 example of realizing the One‐to‐One Principle with two distinct records, she also describes the value of linking these records:
specifically, the linking provides the user an easy connection to a record about the same resource in a different form/medium.
It’s yet another element to promote user‐friendly discoverability.
Digital Object‐Record Element (Carrier‐related)
Brief Description Rationale
Photograph Medium (MODS =
<physicalDescription> <form>
= electronic)
A designation of a particular physical presentation of a resource, including the physical form or
medium for a material for a resource.
Because there may be multiple manifestations of a work (i.e.: an analog version and a digital version), I want to
minimize user confusion by making a clear statement about what kind of
form/medium the resource is in within the record that they are observing.
Digital Origin Information (MODS = <physicalDescription>
<digitalOrigin>)
The method by which a resource achieved digital form.
This element helps to build the user’s awareness of other related resources. In this instance that the digital object is a copy of an analog object, there are appropriate values to describe this. There is also a subelement that lets users know that the digital object was born digital.
Digital Collection (MODS =
<relatedItem> = host)
A value to describe a host or parent resource or a collection in which an item belongs.
I want users to be able to discover a whole collection of other items that the resource record they are observing is a part of.
Link to Digital Image (MODS =
<location><url>)
Contains the Uniform Resource Location of the resource.
This element shares the same discoverability rationale as the
Photograph Repository element: I want these records to ultimately and successfully provide access to the resource being described.
Digital Image Publisher (MODS
= <originInfo><publisher>)
The name of the entity that published, printed, distributed, released, issued, or produced the resource.
I want to make sure that users have a clear
understanding of the party responsible for creating the digital image of a resource.
Date Digitized (MODS =
<originInfo><dateCreated>)
The date of creation of the resource.
I want users to know when the digital image was created.
Digital Image Copyright (MODS
= <originInfo> →
<copyrightDate>)
A date in which a resource is
copyrighted.
I want users to know: 1) that a copyright for the image exists; and 2) when the image was
copyrighted.
Digital File Format (MODS =
<physicalDescription>
<internetMediaType)
An identification of the electronic format type, or the data
representation of the resource.
Having used digital images in the past for projects, I know how important file format information can be to the user. For this
reason, I included an element that specifies this information.
Digital File Number (MODS =
<identifier>)
Contains a unique standard number or code that distinctively identifies a resource.
This element shares the same rationale as the Photograph ID Number element: in order to avoid confusing users with what resource the record is describing exactly, I think the inclusion of an
<identifier> value would help ensure resource discovery accuracy User Access Information (MODS
= <accessCondition>)
Information about restrictions imposed on access to a resource.
For our Module 4 assignment, we were required to observe
metadata collections. One such collection cited by Monica included restricted images, and I thought it would be helpful if the user could be able to filter their searches based on access information. I included this element because I want that capability for my collection’s users.
Resource also available in ____ form (MODS =
Information that identifies other
In Miller’s Chapter 2 example of realizing the
<relatedItem><location><url>) [Optional field only if other forms/mediums exist for the same resource]
resources related to the one being
described.
One‐to‐One Principle with two distinct records, she also describes the value of linking these records:
specifically, the linking provides the user an easy connection to a record about the same resource in a different form/medium.
It’s yet another element to promote user‐friendly discoverability.
References
Library of Congress. MODS User Guidelines (Version 3). Retrieved September 27, 2015 from http://www.loc.gov/standards/mods/userguide/
Miller, S. J. (2011). Introduction to resource description and Dublin Core. In Metadata for digital collections: A how‐to‐do‐it manual. (pp. 25‐48). New York:
Neal‐Schuman. Retrieved September 27, 2015 from
https://laulima.hawaii.edu/access/lessonbuilder/item/60872/group/MAN.1190 .201613/Module%203:%20Describing%20Resources%20for%20Access/miller_ch2.p df
Riley, J. (2010). Seeing standards: A visualization of the metadata universe. Retrieved September 27, 2015 from
http://www.dlib.indiana.edu/~jenlrile/metadatamap/
