Hey LS566 Folks – I really want some feedback on my guidelines!! Here it goes.
Label: Relation
Element Description: A reference to a related resource. This is an identifier of a second resource and its relation to the present resource. This element permits links between related resources and resource descriptions to be indicated i.e a link between one record item and another, between various aggregations of records, or a link between a record and another information resource. Recommended best practice is to identify the resource by means of a string or number conforming to a formal identification system although it can also be a title. Relation is used to describe things such as: the collection in which the object belongs, a different version of the object, something the object is based on, etc.
Required: Yes
Repeatable: Yes
Guidelines for the creation of content:
- Use separate Relation elements to enter multiple relations.
- For the sake of interoperability and when applicable select the appropriate refinement from the Dublin Core list of qualifiers found below.
- Include sufficient information in the Relation element to enable users to identify, cite, or link to a related resource. Record the URL to the collection home page.
- Is Version Of
- Has Version
- Is Replaced By
- Replaces
- Is Required By
- Requires
- Is Part Of
- Has Part
- Is Referenced By
- References
- Is Format Of
- Has Format
- Conforms to
Examples:
IsPartOf: University of Alabama Archival Football Photograph Collection (link item to a larger collection title)
IsFormatOf: Item no. 21, 33b-765, UA Football Photograph Collection, Paul W. Bryant Museum (links digital item such as an image to an original 35mm photo housed in a particular location)
IsPartOf: Collection finding aid located at [URL] (links resource to a finding aid of a larger collection)
IsPartOf: April–14–00 Alabama vs. ? Game (links resource to a specific game of which it is a part)
Notes: Be careful not to confuse the Relation element with Source or Format element.