Overview of the Feature Request
Allow collection managers to configure the set of curation labels for their collection from the edit collection form.
What kind of user is the feature intended for?
Dataverse collection administrators
Any brand new behavior do you want to add to Dataverse?
If AllowedCurationLabels is enabled with at least one set of curation labels, then add a section in the edit collection form to configure the collection's allowed set of collection labels curationLabelSet.
Choices should be :
Inherit from ROOT (default) (for reverting after another selection curl -H "X-Dataverse-key: $API_TOKEN" -X DELETE http://$SERVER/api/admin/dataverse/$dataverse-alias/curationLabelSet)
Selecting a set from the installation (equivalent to curl -H "X-Dataverse-key: $API_TOKEN" -X PUT http://$SERVER/api/admin/dataverse/$dataverse-alias/curationLabelSet?name=$curationLabelSetName), field disabled when "Inherit from ROOT" is ticked
Selecting none of the allowed sets, therefore disabling the feature for the collection ( curl -H "X-Dataverse-key: $API_TOKEN" -X PUT http://$SERVER/api/admin/dataverse/$dataverse-alias/curationLabelSet?name=DISABLED
The labels should be internationalized if the installation supports multiple languages.
Example of mockups
Inherit from root
Selecting a set
Notes: I did put wrongly a multiple selector.
The "too long example" is intentional to remember to address it when implementing.
Any open or closed issues related to this feature request?
None seen
Are you thinking about creating a pull request for this feature?
Not planned, we won't start contributing to the SPA before 2025.
Overview of the Feature Request Allow collection managers to configure the set of curation labels for their collection from the edit collection form.
What kind of user is the feature intended for? Dataverse collection administrators
Any brand new behavior do you want to add to Dataverse? If AllowedCurationLabels is enabled with at least one set of curation labels, then add a section in the edit collection form to configure the collection's allowed set of collection labels
curationLabelSet. Choices should be :curl -H "X-Dataverse-key: $API_TOKEN" -X DELETE http://$SERVER/api/admin/dataverse/$dataverse-alias/curationLabelSet)curl -H "X-Dataverse-key: $API_TOKEN" -X PUT http://$SERVER/api/admin/dataverse/$dataverse-alias/curationLabelSet?name=$curationLabelSetName), field disabled when "Inherit from ROOT" is tickedcurl -H "X-Dataverse-key: $API_TOKEN" -X PUT http://$SERVER/api/admin/dataverse/$dataverse-alias/curationLabelSet?name=DISABLEDThe labels should be internationalized if the installation supports multiple languages.
Example of mockups
Any open or closed issues related to this feature request? None seen
Are you thinking about creating a pull request for this feature?
Not planned, we won't start contributing to the SPA before 2025.
https://guides.dataverse.org/en/latest/admin/dataverses-datasets.html#configure-a-dataverse-collection-to-allow-use-of-a-given-curation-label-set