When a PIDs service contract at SURF ends and is not renewed, there are four options in handling the PIDs hosted at SURF: maintain, tombstone, redirect or delete.
Option A: Maintain PIDs
| What is it? | Existing PIDs (or a subsection of existing PIDs) will continue to be available for the next 10 years. New PIDs cannot be minted. If an existing PID becomes irrelevant over the 10 years, you commit to tombstoning it (see option B). |
|---|
| Why do it? | Your PIDs have been shared in the public sphere and/or have internal value and can be maintained going forward. |
|---|
| Your obligations | Continue to maintain and update the existing PIDs and their metadata. Tombstone PIDs should they become irrelevant (see option B). |
|---|
| Our obligations | Host the existing PIDs for 10 years. |
|---|
Steps:
- Ask to maintain the existing PIDs in the service portal.
- Use the API to modify PIDs as needed going forward.
- Attempting to create a new PID will return an error.
Option B: Tombstone PIDs
| What is it? | All PIDs will be redirected to thew PIDs cannot be minted. Existing PIDs cannot be deleted. |
|---|
| Why do it? | The objects the PIDs point to no longer exist or must be retracted from the public sphere, but you wish to provide transparency and |
|---|
| Your obligations | Source a tombstone metadata schema and fill it out for each object. Update the existing PIDs with the new metadata data and metadata schema. |
|---|
| Our obligations | Host the existing tombstoned PIDs for 10 years. |
|---|
Steps
- Ask to maintain the existing PIDs in the service portal.
- Create a tombstone metadata schema based on the best practices for your objects and domain.
- Update existing PIDs with tombstone metadata.
Option C: Redirect PIDs
| What is it? | All PIDs will be redirected to a new PID (e.g. handle, DOI, ARK). New PIDs cannot be minted. Existing PIDs cannot be deleted. |
|---|
| Why do it? | Prevents link rot while allowing you to manage your entire collection with a new PID solution. |
|---|
| Your obligations | Update the existing PIDs with the new PID for each object. |
|---|
| Our obligations | Host the redirecting PIDs for 10 years. |
|---|
Steps
- Ask to maintain the existing PIDs in the service portal.
- Replace all the existing PIDs metadata with the corresponding new PID (e.g. "http://dx.doi.org/10.3389/fgene.2013.00289") in the URL "index 1" field.
Option D: Delete PIDs
| What is it? | All PIDs will be deleted. |
|---|
| Why do it? | The PIDs were never shared with the public sphere and have no value internally. |
|---|
| Your obligations | None. |
|---|
| Our obligations | Delete all information about your PIDs from our system. |
|---|
Steps
- Ask to delete the existing PIDs in the service portal.
If you have any questions or would like to discuss your migration plan, please do not hesitate to reach out through our service portal.