Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

To be read together with the the RAiD Service Schedule (User Agreement)

1 Purpose

This statement describes the core policies underpinning the ARDC RAiD Service

2 Background

The Australian Research Data Commons (ARDC) is a publicly funded national research infrastructure capability that collaborates with a range of partners to establish underpinning infrastructure that enables Australian researchers to gain research advantage through data. Persistent identifiers (PIDs) are a core component of this national infrastructure and key to world class, global research infrastructure. ARDC’s commitment to PIDs and our strategy in offering PID services are outlined in the ARDC Persistent Identifiers Policy .


As part of its PID strategy, ARDC provides the RAiD Service to registered users (“service points”) to allow them to create (“mint”) identifiers for research projects as part of national infrastructure to support excellent and impactful research in Australia.

3 Policies

3.1 Service functionality

The Research Activity iDentifier (RAiD) is a persistent identifier for research projects and supports data management across all phases of research by placing the research activity (or project) at the centre of research workflows, creating a chain of provenance, improving discovery and access, and ensuring that output is attributable and reportable. It also supports the F.A.I.R Principles for research. 


  • Additional use cases for broadening the scope of RAiD are welcome. These need to be discussed with and approved by ARDC prior to implementation. 

3.3 Service access

Clients are required to register with ARDC [insert link to user agreement] before access to the RAiD service is granted. Once registered with ARDC, clients will be set up as a RAiD Service Point and can access the RAiD API and web dashboard to register and manage RAiDs and metadata either programmatically or by using the manual interface. 

3.4 Service style

The ARDC RAiD Service encourages users of the service to maintain information in their own systems about the project and the digital objects recorded in the RAiD metadata. We also encourage the integration of RAiD minting into automated workflows to enable comprehensive coverage of projects.  For both these reasons, use of the API interface is encouraged.

3.5 RAiD structure

The structure of the RAiD will be in accordance with RAiD ISO Certification (pending). It consists of a Handle minted through the ARDC Handle service and metadata stored on a Cloud service. 


ARDC assumes no responsibility for the currency of information of RAiDs minted using the ARDC RAiD service. It is the responsibility of the client who minted a RAiD to ensure it is kept up to date and integrated with the systems that hold the most current information.

3.7 Service availability and support

ARDC will provide service availability and support for users of the ARDC RAiD service. Although ARDC aims to ensure maximum availability of the RAiD service, planned and unexpected outages will occur. Notice of all planned outages will be distributed via email prior to the event. Users of the service should ensure that software being integrated with this service is designed to cope with occasional service unavailability and that contact details provided to ARDC are kept up to date.