the DOI is shown on the landing page, because the PID exists in the database
the DOI widget in the frontend has to be grayed out if the access is set to restricted
is it really necessary to gray it out? it complicates the code. it has to be done independent of DOI but for all other pids too, to be generic in that way. The problem is, that the DOI could be already there (entry in pidstore_pid), in the InvenioRDM instance, because the record is set to restricted in the end of the drafting process. there would be a lot of work to do to make that consistent.
ATTENTION:
to make it clear for the user, a message should be added to the landing page too. this has to be done on invenio-app-rdm
NOTE:
with this solution it is easy to change from restricted to public and mint the DOI with this step. No further implementation or work from the user would be necessary
UI:
after grace period of a public record ended, the restriction button is disabled + the popup message
this PR will close https://github.com/inveniosoftware/product-rdm/issues/178
still open Problem:
the DOI is shown on the landing page, because the PID exists in the databasethe DOI widget in the frontend has to be grayed out if the access is set to restrictedATTENTION:
NOTE:
restrictedtopublicand mint the DOI with this step. No further implementation or work from the user would be necessaryUI: after grace period of a public record ended, the restriction button is disabled + the popup message