Feature request: Export all Persistent URI's from the resolver

[netsensei]

Problem

A related data publisher wants to import objects with data & representation URL's which reference resources created by our organisation (website). We don't want their persistent URL's to directly resolve to the website resources.

Instead, their resolver should point to URI's generated by our resolver.

To be able to do this, we need to be able to export a list of relevant persistent URI's generated by our resolver.

Request

The resolver does not have the possible to export lists of persistent URI's. I would like to have a button which allows me to:

• Export a CSV list of all the persistent URI's in the system
• Each record has these columns
  • PID
  • entity type
  • persistent URI
  • enabled
  • notes
  • reference
  • order

[netsensei]

Additional remark:

A data publisher should keep the resolver instance and the collection management system (CMS) in sync.

This means that persistent URI's registered in the CMS should also be generated & active in the resolver.

Best practice, however, suggests that the state of the resolver is not "leading". Deciding which objects get persistent URI's does not happen on the level of the resolver. This is done in the CMS. A typical workflow would look like this:

1. Decided which objects should get published persistent URI's
2. Create the URI's in the collection management system for each object
3. Export the relevant set of object identifiers as a list
4. Create an import file via Open Refine based on this list
5. Make a mapping between data/representation URL's and the object identifiers
6. Import the file in the resolver.

Exporting a CSV list of persistent URI's from the resolver has benefits though:

1. Reconciliation between persistent URI's in the CMS vs. Resolver > fix errors on CMS level, etc.
2. Automated check if persistent URI's are active/working via 3rd party batch tools.

This feature request warrants some discussion.