DataONE PIRI Service


The DataONE PIRI (Persistent Internationalized Resource Identifier) Service provides canonical and resolveable IRIs (Internationalalized Resource Identifier) for top-level DataONE resources (e.g., datasets, people) in both web and linked open data contexts. The problem this solves is that DataONE resources can be resolved at a variety of URLs which contain application-, deployment-, and API (Application Programming Interface)-version-specific details. An IRI space that is agnostic to these details allows resources to be identified and resolved in a stable fashion.

Take, for example, the following IRI, which can be used to resolve the location of the Object with the PID (Persistent Identifier) 'mydataset':

Under the PIRI Service, the above resource has the following PIRI:

This is an improvement because the first IRI leaks application-, deployment-, and API-version-specific information into the IRI. All of which may change as some point in the future. With the DataONE PIRI Service (and the IRI space it defines), applications become free to be addressed at different DNS (Domain Name Service) names and APIs are free to change and/or have their versions incremented. All while references to resources within the network remain resolveable.


The DataONE PIRI Service defines an IRI space with the following pattern:{type}/{id}

Where {type} is one of:

  • datasets

  • people (not implemented)

And {id} is an appropriate identifier for resource such as a PID or SID (Series Identifier) for the ‘datasets’ type. Note that all identifiers should be escaped according to RFC3986. See Identifiers in DataONE for more information.


Requests to URLs (Universal Resource Locator) within the PIRI service’s IRI space are redirected with an HTTP 302 status to a corresponding URL within the DataONE search portal. Future changes to this service may include providing content-negotation and returning information about resources or the resources themselves directly from the PIRI service.

Only URLs under are supported and are redirected to by configuration on the web server running at