Feature Request/Idea: Make dataverses metadata configurable

[DS-INRAE]

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 :

1. making affiliation multiple (maybe this could be done with the current system without the effort of externalizing the dataverses metadata)
2. editing the dataverseType list https://github.com/IQSS/dataverse/blob/6ca1c9d873218cb1e28f8443e7e242912ae09c8f/src/main/java/edu/harvard/iq/dataverse/Dataverse.java#L75-L77

Any open or closed issues related to this feature request?

None that I found, surprisingly.

[jggautier]

This might be a solution for the closed issue at https://github.com/IQSS/dataverse/issues/3681. These Dataverse collection categories are "hard coded" and when Dataverse installations don't need all of them or need new ones, changing and maintaining those changes might be made easier. The Datavese Metrics page lets us see what new categories have already been added.

[pdurbin]

@jggautier yes, it would be. Good memory. 😄

@DS-INRA is this something you'd want to create a pull request for (though it would be a lot of work).

For the record, people have (often) asked for similar flexibility at the file level.

[DS-INRAE]

Hello and thanks for the notes. It's not something we'll be able to contribute on in the short or medium term sadly

[pdurbin]

There's additional discussion in Zulip. Thanks, @DS-INRA, for reminding us about this issue!