|
XML Element Name
|
naa:RelationType
|
|
Definition
|
A category of relationship between records, at the
same or different levels of aggregation, or between records and other
information resources.
|
|
Purpose
|
This element documents the nature of the
relationships between the two or more items. It provides contextual
information about records by documenting other items with which they have
logical associations or historical relationships.
|
|
Obligation
|
Conditional (must be present in all M42 RELATION elements).
|
|
Repeatable
|
Yes
|
|
NAA Metadata
|
Yes
|
|
Assigned Values
|
Value Name
|
Definition
|
|
|
Contains/
Contained in
|
Denotes participation in a level of aggregation.
Denotes a record or resource that makes up part
of a defined whole.
Records may be contained in folders; folders (and
hence records) are contained in a series.
It shall not be possible to use this value to relate
an item of a particular security classification to a file of a lower security
classification.
|
|
|
Next/Previous
|
Denotes that the record is the next or previous part
of a sequence – e.g. the next or previous part of file 99/131.
|
|
|
Replaces/
Replaced by
|
Denotes that the content of the record replaces/is
replaced by (supersedes/is superseded by) the content of another record.
|
|
|
Refers to
|
Denotes that the record refers (e.g. through textual
references, URIs or bibliographic information) to other resources.
|
|
|
See also
|
Denotes that another record should be consulted for
more or related information.
|
|
|
Derived from (source)
|
Denotes another record or resource from which the record
is derived.
|
|
|
[other]
|
Other agency-defined value
|
|
Default Value
|
Should be able to be agency-defined and set, based
on agency requirements.
|
|
Attributes
|
Attribute Name/Type
|
Definition
|
|
|
vers:schemeCDATA
|
(Optional) A reference to the scheme that controls
the values of this element. Would normally only be present if there is a
published scheme that can be referred to by a viewer.
|
|
Comments
|
Multiple
use of this element within the one relationship is NOT RECOMMENDED. For
example, RELATION must not contain two Relation Type values like ‘Contains’
and ‘Next’. If a record has multiple relationships they must be documented as
separate instances of M42
RELATION even if the relation refers to the same record.
Other types of relations may be added as an Assigned
Value by agencies to meet their own requirements for defining relationships
between records, and records and other information resources.
|
