Skip to content.
|Networking government in New Zealand.
 

Section J: The Relation Element

Purpose of this section

This section contains the rules for creating metadata records using the Relation element (number 10).

J.1. Rules for the Relation Element

J.1.1. Name

Relation

J.1.2. Definition

Identification of other resources or services that are related to this current resource, and a description of the type of relationship.

J.1.3. Purpose

The relation element should be used where there are significant related resources which the searcher could also find useful.

J.1.4. Obligation

Optional

J.1.5. Element refinements 

The Portal will use the Relation element to link the documents which support a service - for example, instructions and forms.

Similarly, it will use this element to cluster services provided by a particular agency.

The best general approach is to use the name of the service concerned as the value of the Relation element. The service name should be chosen from the controlled list of those services (or agencies) described in NZGLS itself.

The following table shows how various types of relationships would work under this approach.

If this element is used, the type of relationship must be specified by choosing a value from one side of any of the pairs in the following list:

isPartOf/hasPart

One resource is a physical or logical part of another. Used to describe the relationship between a service and relevant documents (e.g. web pages and forms)

isVersionOf/hasVersion

One resource is an historical state or edition of another resource by the same creator.

isFormatOf/hasFormat

One resource has been derived from another by a reproduction or reformatting technique which is not fundamentally an interpretation but intended to be a representation.

references/isReferencedBy

One resource cites, acknowledges, disputes or otherwise refers to another resource.

isBasedOn/isBasisFor

One resource is a performance, production, derivation, translation, adaptation or interpretation of another resource.

isRequiredBy/requires

One resource requires another resource for its functioning, delivery, or content and cannot be used without the related resource being present. For services, includes pre-requisite information, service or activity necessary for accessing the service.

isReplacedBy/replaces

One resource supplants, displaces, or supercedes another resource.

J.1.6. Encoding schemes

Examples:

URI - Uniform Resource Identifier

ISBN - International Standard Book Number

ISSN - International Standard Serial Number

J.1.7. Default value

None

J.1.8. Scope and interpretation

Use this element to describe significant relationships from the searcher's point of view - not all relationships.

If the Relation element is used, then an element refinement must also be used to express the type of relationship. Note that each of the seven relationship types is two sided, but the chosen value must be one side of a pair only - otherwise it won't make sense.

When the other related resource has been described, give its full proper name or use a formal identifier.

It is a good idea to use this element when the information about another resource is useful for discovering or understanding the current resource. It is also a good way to link resources which contain similar or related information.

J.1.9. How to use this element when describing a service

The Relation element can be used to identify information necessary for using a service. It can also be used to link to another service which is related to the current service, and supports linking or integration of a number of services.

This element will be of most use where the relationship between services is not obvious, and will not be identified by the search tool. Functionally related and subject-related services should be picked up by search tools.

J.1.10. The role of Relation in the Portal

The Portal uses this element to relate documents to services, through the isPartOf element refinement. If you do not establish this relationship, then documents will not be discoverable in a service-based search. For example, the document whose title is 'Student Loan Application Form' will appear in the Portal as part of the 'Student Loan Scheme' service only if the document has the Relation element identifying that the document isPartOf 'Student Loan Scheme'.

Displayed on metadata full record screen.

J.1.11. Examples

references Ministry of Education strategic plan [URI] http://www.minedu.govt.nz/web/document/document_page.cfm?id=3522

references Ministry of Education annual report [URI] http://www.minedu.govt.nz/web/document/document_page.cfm?id=5188

references Ministry of Education departmental forecast report [URI] http://www.minedu.govt.nz/web/document/document_page.cfm?id=4756

isBasisFor [URI] http://www.winz.govt.nz/student/maori_alt.html

isPartOf [URI] http://student.winz.govt.nz/apply.html

(requires) Please note that you will be asked for your IRD number, bank account number, Student ID and study details. You may wish to read through the form to make sure you have the appropriate information at hand before you start filling in the form

hasPart [URI] http://www.winz.govt.nz/student/maori_alt.html

hasPart [URI] http://www.winz.govt.nz/student/index.html

hasPart Student Services on 0800 88 99 00

J.2. How the Portal Uses the Relation Element

Relationship

Portal Use

How

Document -> Agency

To display the agency(ies) that relate to a discovered document - in search results.

All element values which have an encoding scheme of NZGLS-AN represent an agency name, regardless of the element they are contained in.

The link to an agency metadata record is done through a search: where Title=agency name and Type.Category='agency'.

Note: To link directly to an agency's web site (home page) from a document, if there is one, might be possible but might not be easy. A two step process might be best.

Document -> Service

To display the service(s) that relate to a discovered document - in search results

All element values which have an encoding scheme of NZGLS-SN represent a service name, regardless of the element they are contained in.

The link to a service metadata record is done through a search: where Title= service name (from current metadata record) and Type.Category='service'.

Note: To link directly to the service page on the web, if there is one, would be possible but more complicated. A two step process might be best.

Document -> Document

To display other documents that relate to a discovered document - in search results.

This is handled by the current NZGLS Relation element, which would normally contain the URIs of related documents. This is basic AGLS and DC functionality.

Clicking on the URI would take the user directly to the related document, if it was a web address.

Note: Related documents would not necessarily have NZGLS metadata, but if they did and if the Portal wanted to link to it, this would be done with a search: where identifier=URI (from current metadata record).

Service -> Agency

To indicate the agency(ies) that provide a service - in a listing of services or in search results.

Exactly the same as for Document -> Agency above. According to NZGLS, the primary agency will be identified in the Creator element

Service -> Service

To indicate relationships between services - in a listing of services or in search results

Exactly the same as for Document -> Service above.

Service -> Document

This is one of the main search mechanisms in the Portal whereby, once a service is chosen, a search returns all related documents.

The search would include the following criteria: where Relation=service name and Category.Type='document'.

Note: More specificity could be gained by adding 'and encoding scheme=NZGLS-SN' but this is probably not necessary

Agency -> Agency

To indicate relationships between agencies - in an agency listing or in search results.

Exactly the same as for Document -> Agency above

Agency -> Service

To provide a list of services, by agency.

A search is required to identify the service records, with the following criteria: where any element=agency name and encodig scheme='NZGLS-AN' and Type.Category='service'.

Note: More specificity could be gained by limiting the search to the Creator element of the service record.

Agency -> Document

Possibly - to display all the documents relevant to an agency

A search is required to identify documents, with the following criteria: where any element=agency name and encoding scheme = 'NZGLS-AN' and Type.Category='document'.

J.2.1. Hierarchical lists

For the Portal to provide hierarchical representation of agencies or services, metadata records will need to be related to each other with Relation.isPartOf/hasPart pairings. This would still be achievable if only one side of the relationship was maintained, but it could lead to greater programming complexity.

Lower-level to higher-level relationship: where Relation.hasPart-agency/service name and Type.Category-'agency'/service'.

Higher-level to lower-level relationship: where Relation.isPartOf=agency/service name and Type.Category='agency'/'service'.


[ Previous | Next ]