Aim of this ticket
This ticket collects the needed modifications of Edmond which are directly related to the introduction of the curation process.
M1: Add new field "CurationLevel"
That field informs the reader of a dataset about the curation level. While a DataSubmitter may use that field to propose a curation level, the decision about the level is done by the DataReviewer (i.e. a Curator).
Following possible values are currently planned, further options may be added in future:
- NA (empty) for already existing dataset versions
- "PreliminaryReview"
- "BasicReview"
- "EnhancedReview"
Implementation:
- Select field with 3 values
- not required
- Position: Last on page
Context help for that field:
Curation level of the dataset. See help page Data_Usage for more information.
M2: Button "Submit for review" to "Submit"
Currently, the DataSubmitter pushes a button "Submit for review" to start the review process. The caption of this button shall be changed to "Submit".
M3: Deactivate Deaccession
So far, a DataSubmitter can deaccession a dataset theirself. This shall be forbidden in future, also for already existing datasets. It might already be enough to remove curator rights, but ideally only a superuser should be allowed to deaccession.
Also to check in that context: Once a dataset is deaccessioned, can it be made public again? Use case: Problematic dataset where decision about whether to finally deaccession or not needs time.
M4: Remove curator role for existing datasets
While a DataSubmitter will have no curation rights per default for a new dataset, they still have curator rights for their already existing dataset. In order to prevent the uncurated change for such existing datasets, the curator rights have to be removed from all existing datasets.
Aim of this ticket
This ticket collects the needed modifications of Edmond which are directly related to the introduction of the curation process.
M1: Add new field "CurationLevel"
That field informs the reader of a dataset about the curation level. While a DataSubmitter may use that field to propose a curation level, the decision about the level is done by the DataReviewer (i.e. a Curator).
Following possible values are currently planned, further options may be added in future:
Implementation:
Context help for that field:
M2: Button "Submit for review" to "Submit"
Currently, the DataSubmitter pushes a button "Submit for review" to start the review process. The caption of this button shall be changed to "Submit".
M3: Deactivate Deaccession
So far, a DataSubmitter can deaccession a dataset theirself. This shall be forbidden in future, also for already existing datasets. It might already be enough to remove curator rights, but ideally only a superuser should be allowed to deaccession.
Also to check in that context: Once a dataset is deaccessioned, can it be made public again? Use case: Problematic dataset where decision about whether to finally deaccession or not needs time.
M4: Remove curator role for existing datasets
While a DataSubmitter will have no curation rights per default for a new dataset, they still have curator rights for their already existing dataset. In order to prevent the uncurated change for such existing datasets, the curator rights have to be removed from all existing datasets.