|Field Name:||Relation is the default. However, custom-tailored field names (Related Work, Required Software, etc.) may be appropriate for an individual collection.|
|Repeatable:||No (although there could be multiple Relation fields with each field serving a separate purpose, using one or more Refinements listed below)|
|Search:||Yes (determined by needs of each project and the type of information entered into each field)|
|Dublin Core (DC) Mapping:||dc.relation|
|MARC Mapping:||787 [0 ] $n|
|CONTENTdm Data Type:||Text|
|Dublin Core Definition:||A related resource. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.|
|UA Definition:||A resource that is somehow connected or related to, or its use of, the resource being described. This definition may be expanded as local practice develops over time.|
Use this field to record such information as related titles, different versions of the resource, names of software needed to use the resource, etc. Use the general “dc.relation” only when none of the more specific refinements listed below are appropriate.
When recording relationship statements, include information sufficient for a user to identify, locate, or cite the related resource. Refer to other fields such as Title, Description, Original Publisher, etc., for instructions about entering data.
It is possible that the resource being described might be related to one or more resources in a variety of ways. In such cases, a separate Relation element along with a clarifying element name (and appropriate refinement) should be used to record each type of relationship (e.g., “Required Software,” “Is Referenced By,” etc.).
If multiple values are appropriate for a single relationship type (e.g., more than one software package is needed to use the resource), enter them in the same field, separated by a semicolon space.
Note that with the exception of “Is Part Of,” “Is Referenced By,” and “Requires,” it is anticipated that the use of these refinements for UA collections would likely be rare. Default field labels are listed, but these may be customized.
Example of dc.relation.requires
(special software is needed to open/play the digital resource)
Example of dc.relation.isReferencedBy
(paired with the custom field name of “Child Number” in the Ozark Folk Song collection)
Example of dc.relation.isPartOf
(link from a Traveler issue excerpt in the Special Collections Gallery to the collection The Arkansas Traveler Newspapers)
Example of dc.relation
(used in the collection Annual Report (Arkansas Agricultural Experiment Station) to link to the same item that is also part of Bulletin (Arkansas Agricultural Experiment Station) (A link to the collection would be dc.relation.isPartOf)