Feature Request: Enable file PIDs at Dataverse Collection Level

[sbarbosadataverse]

The Harvard Dataverse Model for supporting file-level DOIs will support collection level instead of production-wide file-level PIDs.
This requires the ability to enable file-level PIDs at the collection level. Eventually, we may discuss enabling at dataset level, if needed.
-->

Overview of the Feature Request

What kind of user is the feature intended for?
SUPERUSER/INSTALLATION ADMIN

What inspired the request?
THE COST OF PROVIDING FILE LEVEL PIDs FOR GENERALIST, OPEN REPOSITORIES

What existing behavior do you want changed?
MANAGED FILE LEVEL PIDs distribution

Any brand new behavior do you want to add to Dataverse?

Any related open or closed issues to this feature request?
NO

@scolapasta

[scolapasta]

Some notes:

We'll want to introduce this as a setting per dataverse collection, and model it after other such settings (metadablocks, facets, etc) in that a child dataverse would inherit the setting from its parent unless it chooses to override it.

For now this will be superuser only, so we can set via API (optionally, we could include a rudimentary UI way, though further design would be warranted if we opened it up to dataverse collection admins).

Additionally, we'll want to modify the current installation wide setting from just true / false to also allow for this option (so likely, off, on, and "set all collection level" - though we may not need "on" and just off and "set all collection level" - something to discuss when we start working on this).

We'll also need an API (or move the current admin only API) to register for existing datasets (for when a superuser turns this on in a dataverse collection with existing datasets).

[j-n-c]

PID settings have been discussed recently:

• https://groups.google.com/g/dataverse-community/c/hFZRMXJ_-CE
• https://docs.google.com/document/d/1H8XTmrQd6TIILCZ--YMrZGEicmcgJGpwc5c0vC9JTJw/
• https://docs.google.com/document/d/1P1txmW0MUWm35AQPTDoh5Kl1X0m7HOZvXwXjX5wZAps

This feature was in fact suggested by @qqmyers in session 2 of the community call held on the 20th Sep 2022

Adding to @scolapasta comment, perhaps the file PID configuratin could be set only on desired collections (passed as a parameter to the API or set through the GUI). On other Collections, the system wide default would be used.

Please consider adding this feature on a future release of the Datavese Software.

[mreekie]

Sizing:

What is needed is to assign XX to a specific collection

• all datasets automatically get a persistent identifier.
• Files - persistent identifier is option.
• Persistent-data identifiers for files is currently disabled in production.
• It's a global switch.

Sonia would like this to be turned on/off on a per-collection basis.
This feelis like it could be one sprint: Size 80

[landreev]

BTW, @poikilotherm 's #9462 is already adding a per-collection (and inheritable) setting that's related to PID behavior. For versions PIDs. Can be used as a model for this setting.