In the RDA Registry relationships between real world entities are described by linking registry objects together using different kinds of relations. Relationships between activities, collections, parties and services are used to provide navigational links and contextual information. These relations create a rich mesh of information about Australia's research data and the parties, activities and services that support it. The four classes of registry objects can be related to each other.
RelatedObject has a number of child elements that describe the related resource:
A Relation Type is required. Preferably specify a type from the Relation Type vocabulary. Local types may also be used, for example if a data source has described different relationships according to an established schema. Ad hoc local values should be avoided.
Available Relation Types differ according to the classes of registry object being linked; detailed descriptions of relevant relations are provided on the collection, service, activity and party pages. If the generic relation 'hasAssocationWith' is used, include a description of the details or nature of the association.
Expand the links below to view available Types:
All relations are displayed as hyperlinks and can be used to navigate to other information within Research Data Australia.
Labels for relationships are simplified for display in Research Data Australia:
If two or more collections are related to each other with a relationship type of 'hasPart' or 'isPartOf' (nested collections: see XML encoding example below), they will graphically display as a hierarchy in Research Data Australia similar to the following:
Contributors should consider how important a relation is to discovery, and not create relations that will not improve access. In particular, although the RDA Registry allows parties to be related, this should be used only to improve discovery. A relation between a person (researcher) and a group (funding organisation) may add value, while hierarchical relations between organisational parts may not.
Registry objects can be linked to a related collection, party, activity or service in one of two ways:
As Research Data Australia is primarily a collections registry, it is preferred that a RegistryObject be created to describe collections. However, consider whether you need to create a RegistryObject for parties. Research Data Australia treats parties linked via RelatedObject or RelatedInfo in the same way (the indexing and display of names are equivalent). The simplest (and most sustainable) way to link parties to collections, activities and services is by using RelatedInfo with a globally unique persistent identifier (preferably an ORCID or NLA Party identifier).
Whichever option is chosen, contributors are strongly encouraged to provide a globally unique identifier such as a DOI, ORCID or PURL in their records. Identifiers support a linked data approach that enables relationships between resources to be identified and displayed in Research Data Australia regardless of the source of the record.
It is possible to create multiple relations for a single object. For example, a party may be related to a collection as both manager and owner. Multiple relations for a single object should be provided in a single instance of the RelatedObject element. See the XML encoding examples below for details.
See Relationships between registry objects for information on how the RDA Registry can automatically create relationships between objects, and bi-directional links between related objects.
<relatedObject> <key>hdl:102.100.100/999999</key> <relation type="isOwnerOf"/> </relatedObject>
<relatedObject> <key>http://nla.gov.au/nla.party-549576</key> <relation type="isOwnedBy"/> </relatedObject>
<relatedObject> <key>http://nla.gov.au/nla.party-549576</key> <relation type="isManagedBy"/> <relation type="isOwnedBy"/> </relatedObject>
<relatedObject> <key>Collection26</key> <relation type="isPartOf"/> </relatedObject> <relatedObject> <key>Collection28</key> <relation type="isPartOf"/> </relatedObject> <relatedObject> <key>Collection29</key> <relation type="hasPart"/> </relatedObject>