Feature Request: Support the COAR Notify Request Review and Announce Review patterns

Overview of the Feature Request

We'd like to expand COAR Notify support to allow depositors to request a review of their dataset from a review service, and to be notified when a review is published.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

Depositor

What inspired the request?

SciELO Data are looking to allow depositors to request reviews from the PREreview community, in the same way as SciELO Preprint does already using the COAR Notify protocol. We (PREreview) would like to expand on this, to allow us to notify SciELO Data when a review has been published (with or without a request), so they can notify the depositor (we already have this arrangement with other preprint servers).

What existing behavior do you want changed?

n/a

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

• A Dataverse instance can be configured to allow for COAR Notify review requests to be sent to 1 or more review services.
  • People depositing datasets (or have already done so) can choose to send a request to any of these services.
• A Dataverse instance can be configured to receive COAR Notify review announcements from review services.
  • Depositors can choose to be notified when a review announcement is received.
  • Links to (and details of) these reviews can be displayed on the dataset.

Any open or closed issues related to this feature request?

Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?

PREreview has no experience with Dataverse, so we can't contribute code. We are available for support as needed.

The COAR Notify project has indicated they may be able to help fund development.

Start by reading Dataverse's existing COAR Notify support, then study the linked COAR Notify request-review and announce-review specifications. Map configuration, depositor actions, outgoing requests, incoming announcements, notifications, and dataset review links; done means both workflows can be configured and exercised end to end.