Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request/Idea: Make dataverses metadata configurable #9420

Open
DS-INRAE opened this issue Mar 2, 2023 · 4 comments
Open

Feature Request/Idea: Make dataverses metadata configurable #9420

DS-INRAE opened this issue Mar 2, 2023 · 4 comments
Labels
Feature: Metadata Type: Suggestion an idea User Role: Curator Curates and reviews datasets, manages permissions

Comments

@DS-INRAE
Copy link
Member

DS-INRAE commented Mar 2, 2023

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
    public enum DataverseType {
    RESEARCHERS, RESEARCH_PROJECTS, JOURNALS, ORGANIZATIONS_INSTITUTIONS, TEACHING_COURSES, UNCATEGORIZED, LABORATORY, RESEARCH_GROUP, DEPARTMENT
    };

Any open or closed issues related to this feature request?

None that I found, surprisingly.

@jggautier
Copy link
Contributor

This might be a solution for the closed issue at #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
Copy link
Member

pdurbin commented Mar 2, 2023

@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
Copy link
Member Author

DS-INRAE commented Mar 2, 2023

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 pdurbin added Type: Suggestion an idea Feature: Metadata User Role: Curator Curates and reviews datasets, manages permissions labels Oct 9, 2023
@DS-INRAE DS-INRAE moved this to 🔍 Interest in Recherche Data Gouv Jul 10, 2024
@pdurbin
Copy link
Member

pdurbin commented Jul 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Metadata Type: Suggestion an idea User Role: Curator Curates and reviews datasets, manages permissions
Projects
Status: 🔍 Interest
Development

No branches or pull requests

3 participants