QDR/6886 external status labels #7967
Conversation
Conflicts: src/main/java/propertyFiles/Bundle.properties
Conflicts: src/main/java/propertyFiles/Bundle.properties
Conflicts: src/main/java/edu/harvard/iq/dataverse/settings/SettingsServiceBean.java src/main/java/propertyFiles/Bundle.properties
Conflicts: src/main/webapp/dataset.xhtml
QDR/6886-external_status_labels Conflicts: src/main/java/edu/harvard/iq/dataverse/settings/SettingsServiceBean.java
|
@philippconzett /all - this PR is now a working capability that allows an admin to set a defined list of states/statuses a draft dataset can be in (via an :AllowedCurationLabels setting) that can be set/removed via a UI menu (under publish data, showing only for those who can publish) or API. The only affect is to set a label that shows on the dataset/file page and dataverse/search listings and is searchable by field (e.g. entering externalstatus:* in the search box). Changes to status result in a notification and email. Any status is removed upon publication. The intent is to allow integration with an externally defined curation process that defines states that a draft dataset can be in. (A dataset can't have more than one status (although embargoed also adds a label that is independent of this), published dataset versions can't have a status). (This PR doesn't include any push mechanism to alert an external process that a draft dataset is ready to process, but one could configure a pre-publication workflow that would trigger an external app that could then use the API to report updates as curation steps are done. For now, QDR's main use case will be curators manually changing the state via the UI.) The images below give the basic idea (examples from QDR - label color is different and they include unrelated QDR customizations such as the use of 'Data Project' instead of 'Dataset').
If this looks generally useful and consistent with the larger directions for curation support, I can add documentation, etc. to finalize this PR. Otherwise, feel free to reject/close. |
|
Should be all set - the only remaining test fail was in an unrelated one reading http://schema.datacite.org/meta/kernel-4.1/metadata.xsd which must have been down. |
…QualitativeDataRepository/dataverse.git into QDR/6886-external_status_labels
What this PR does / why we need it: Adds a mechanism to set/display an additional status label on draft datasets to aid in coordinating with an external curation workflow mechanism
Which issue(s) this PR closes:
Closes #
Special notes for your reviewer: Relates to #6886 but doesn't cover all aspects. Created for QDR - will be discussed/reviewed/potentially modified/tested there before inclusion in QDR's version. This draft PR is to make it easier for community exploration.
Suggestions on how to test this: Call the API to set/delete the label (suggested values such as 'Queued', 'In Process', etc. - up to 32 chars, alphanumeric and spaces allowed), verify that the label is displayed and that any existing label is removed when the version is published.
Does this PR introduce a user interface change? If mockups are available, please link/include them here: see comment below
Is there a release notes update needed for this change?:
Additional documentation: tbd