Background

In agreeing to the proposal to allow additional resource types to be described using RIF-CS, the RIF-CS Advisory Board (RAB) asked that ANDS provide greater clarity around the use of all collection types and provide examples.  

The first five in the list of eight types below are existing collection types.  The first four types (‘catalogueOrIndex’, ‘collection’, ‘registry’, ‘repository’), and their definitions are taken directly from the IS0 2146 standard.  These types and definitions remain unchanged to ensure compliance with the standard.  

The ‘dataset’ type and definition were introduced to support business requirements for the ANDS Registry.  To ensure consistency and continuity, this type and definition, also remain unchanged.  

The final three collection types listed below have been recently approved by the RAB to support the business requirements of ANDS and other users of RIF-CS.  They will be implemented with version 0.1.7 of the schema.

Explanatory text and examples have been provided for all collection types, noting that exemplar records in RDA do not yet exist for all types, in particular, the three newly approved types.  The information provided here is intended to assist providers to answer the question “which collection type should I choose?”

Collection types and definitions

Definitions with explanatory text and examples


This type should be used to describe the content of one or more repositories or collective works usually associated with an institution or subject discipline. A catalogue or index may be local, regional, national or international. Usually it will consist solely of resource descriptions but it may also contain full-text indexes to the digital content that it describes.  
An example of this type is:

Catalogues and indexes may themselves be described in a registry.


This type should be used to describe a collection of objects, grouped according to a shared criteria, which are stored and managed as a collective group.  This may be a collection of similar object types with a common theme such as a collection of music audio files.  See for example in Research Data Australia:

It may also be a collection of different object types brought together around a particular topic, subject or project. See for example in Research Data Australia:

It should be noted that where the appropriate collection types exist, a provider may also, or instead, choose to describe components of a collection separately.  For example, where a collection is comprised of a dataset and software, separate descriptions would enable each component of the collection (ie the dataset and the software) to be individually discoverable and citable.  These separate descriptions should be connected via the relatedObject element to facilitate discovery of all related components.


This type should be used to describe a collection that consists solely of resource descriptions or metadata records. These records may describe catalogues, indexes, repositories or collections.

Examples include:


This type should be used to describe a collection of digital or physical research objects sharing a managed storage location.  A repository is usually associated with an institution or subject discipline.

An example of this type in Research Data Australia is:

Other resources that could be described as collection type=’repository’ include:

Repositories may store and provide access to other collection types such as datasets, source code, collections and publications.


This type should be used to describe structured data that is an input to, or output of research.  This may include scientific observations, remote sensing data, survey transcripts and photographs.  

Examples of this type in Research Data Australia include:


This type should be used to describe software that supports research, including models and workflows.  Use this type to publish and make discoverable software that may be downloaded, compiled, executed and instantiated.  The aim is to enable such software to be reused and cited by others.   Its scope may range from a single source file to an entire code base of multiple files.  

 

Do not confuse with:

The ‘Edgar’ web application run out of James Cook University can provide an example of this distinction.

This Service record in RDA describes the Edgar service that can be used to generate environmental suitability maps for Australian bird species under various climate change scenarios.

With the introduction of collection type=’sourceCode’, a collection record of type=’sourceCode’ could also be published in RDA to describe the code underpinning the Edgar service and provide access to the code in GitHub via the location element.  See sample encoding below.

  

software_example.png


This type should be used to describe a research asset that is comprised of terms used in a particular context. Use this type to publish and make discoverable classification schemes such as controlled vocabularies, authority lists, ontologies and thesauri that may be reused by others.   Examples include:


It is not intended that collection type=”publication” be implemented in the ANDS Registry.  It has been added to the list of types to support business requirements of other systems that use RIF-CS.  In the ANDS Registry, providers should continue to use relatedInfo type=”publication” to describe a publication related to a collection.

Those organisations intending to implement type=”publication”, may wish to consider whether sub-types such as ‘journal article’, or ‘conference paper’ are required.  These should be implemented in accordance with a controlled list of terms such as the Confederation of Open Access Repositories (COAR) Resource Type Vocabulary