Feature Request/Idea: Make dataverses metadata configurable #9420
Labels
Feature: Metadata
Type: Suggestion
an idea
User Role: Curator
Curates and reviews datasets, manages permissions
Overview of the Feature Request
Make dataverse collections metadata configurable.
What kind of user is the feature intended for?
Instance administrators for the configuration and dataverse collections creators/administrators for the end-use.
What inspired the request?
Dataverse for research units or project with multiple affiliations and the will to specify other dataverse types.
What existing behavior do you want changed? / Any brand new behavior do you want to add to Dataverse?
Allow to change the metadata of a Dataverse via an external configuration file in a similar manner to the tsvs for the datasets metadata.
With the main objectives being :
affiliation
multiple (maybe this could be done with the current system without the effort of externalizing the dataverses metadata)dataverse/src/main/java/edu/harvard/iq/dataverse/Dataverse.java
Lines 75 to 77 in 6ca1c9d
Any open or closed issues related to this feature request?
None that I found, surprisingly.
The text was updated successfully, but these errors were encountered: