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: Customize the list of default file categories #8461

Closed
abujeda opened this issue Mar 4, 2022 · 6 comments · Fixed by #8478
Closed

Feature Request/Idea: Customize the list of default file categories #8461

abujeda opened this issue Mar 4, 2022 · 6 comments · Fixed by #8478
Labels
HDC Harvard Data Commons HDC: 2 Harvard Data Commons Obj. 2
Milestone

Comments

@abujeda
Copy link
Contributor

abujeda commented Mar 4, 2022

Overview of the Feature Request
At the moment, the default list of file categories is hardcoded to "Documentation", "Data" and "Code". This is then used as the default set of values for the file tags UI.

Allow this values to be loaded from a configuration file so that sysadmins can customize the list.

What kind of user is the feature intended for?
Configuration of the values for sysadmin
The use of file tags for all users

What inspired the request?
As part of the Harvard Data Commons project there is a requirement to add Workflow as a file tag that will appear in the UI for all users.

What existing behavior do you want changed?
How these default values are configured in the Dataverse system.

Any brand new behavior do you want to add to Dataverse?
No

Any related open or closed issues to this feature request?
No AFAIK

@abujeda
Copy link
Contributor Author

abujeda commented Mar 4, 2022

This feature is a requirement for the Havard Data Commons project, Objective 2.

We are working on a possible solution and will discuss the approach within this issue.

@qqmyers
Copy link
Member

qqmyers commented Mar 4, 2022

These are not currently Dataset categories, only file categories. At the dataset level, there are citation metadatablock entries for subject (controlled list) and kindofdata (open) that already categorize the data. Is the intent here to make another dataset-level metadata item?

@abujeda
Copy link
Contributor Author

abujeda commented Mar 4, 2022

Sorry, I called them Dataset categories as the Dataset object is responsible to generate them.

The intent is to update the default set of file categories.
Will update the description to reflect that these are file categories as mentioned above.

@abujeda
Copy link
Contributor Author

abujeda commented Mar 8, 2022

Had a discussion with @qqmyers about this issue and he suggested the use of the Settings feature.
We could store a :FileCategories setting to override the default set of file category values.

@abujeda
Copy link
Contributor Author

abujeda commented Mar 8, 2022

Created a branch to start sharing a proposal implementation:
https://github.com/adaybujeda/dataverse/commits/8461-datafilecategory-configuration

@abujeda
Copy link
Contributor Author

abujeda commented Mar 10, 2022

PR created to start a discussion with the Dataverse team:
#8478

@abujeda abujeda changed the title Feature Request/Idea: Customize the list of default Dataset categories Feature Request/Idea: Customize the list of default file categories Mar 16, 2022
landreev added a commit to abujeda/dataverse that referenced this issue Mar 18, 2022
(Please add to or edit as you see fit; IQSS#8461)
abujeda added a commit to abujeda/dataverse that referenced this issue Mar 18, 2022
abujeda pushed a commit to abujeda/dataverse that referenced this issue Mar 21, 2022
(Please add to or edit as you see fit; IQSS#8461)
abujeda added a commit to abujeda/dataverse that referenced this issue Mar 21, 2022
@pdurbin pdurbin added this to the 5.11 milestone Mar 29, 2022
@scolapasta scolapasta added HDC Harvard Data Commons HDC: 2 Harvard Data Commons Obj. 2 labels Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HDC Harvard Data Commons HDC: 2 Harvard Data Commons Obj. 2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants