Feature: Allow depositors to self-publish submission after approval

[zoidy]

Is there an existing issue for this?

• I have searched the existing issues

Description

If a depositor wishes to keep a dataset unpublished after it's been reviewed, they need to contact us to actually get it published. This adds friction to the process of publication.

To reduce the friction, the depositor could be allowed to self-publish their own data at any time, after it has been reviewed and if the record hasn't been changed in any way since approval.

Suggested Implementation

This functionality would require both LD-Cool-P and a simple web app. The process could look something like this.

Overview

1. Depositor submits a dataset like normal and wishes to keep it unpublished until the associated article is accepted.
2. It undergoes the normal review process.
3. Upon completion of the review and after the dataset is Approved (all info has been provided by depositor), the depositor is sent an email with a magic link.
4. The magic link allows them to publish their own dataset at any time, assuming no changes have been made to the submission by anyone

Magic link

1. Obtained by LD-Cool-P by interacting with a simple web app that sets up the magic link
2. The magic link contains a code that will publish the associated dataset via the Figshare API.
3. The magic link will open a web page that allows the depositor to publish their dataset

Web app front-end

1. A static web page will accept a magic link and display a button and and any appropriate warnings that publishing is final
2. Upon clicking the button, the dataset will be published or an error will be returned if it cannot be published (e.g., the dataset has been changed and therefore requires review, updates to readme etc. or it has already been published, or if the link has been manually disabled by staff)

Web app serverless back-end

1. A function accepts information via GET or POST parameters and generates an entry in a backend file store or db (see e.g. the link shortener for a straightforward way to do this with an S3-compatible storage). The entry, which is associated with a unique code, contains information that allows for publication via the API. The magic link contains the code.
2. Another function accepts the code, performs a lookup in the file store or db and publishes the associated dataset, returning appropriate messages or errors to the caller.
3. The functions should have a way to override the check of whether a dataset has been modified to allow administrators to make changes to the data but still allow depositors to self-publish. This could be done by a timestamped flag in the data associated with the code that would need to be set/modified by administrators.
4. Fighshare API secrets are stored securely within the serverless environment