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: extend list of collection categories with "Division" #11160

Open
poikilotherm opened this issue Jan 16, 2025 · 1 comment
Open
Assignees
Labels
Feature: Controlled Vocabulary Includes both Internal and external controlled vocabularies Feature: Metadata Size: 0.5 A percentage of a sprint. 0.35 hours Type: Feature a feature request

Comments

@poikilotherm
Copy link
Contributor

poikilotherm commented Jan 16, 2025

Overview of the Feature Request

We would like to extend the list of possible options for categories of Dataverse collections with the term "division".

What kind of user is the feature intended for?
API User, Curator, Depositor, Guest

What inspired the request?
Our board of directors recently decided that we want to unify the naming how we call our internal organizational units. They came up with the term "institute division" and are asking all services to adapt this term.

What existing behavior do you want changed?
Currently there is a hard coded enum list, which is also used for indexing/searching (thus changing the term is not just a matter of a UI change).

image

Any brand new behavior do you want to add to Dataverse?
We would like to extend the existing list with the term "Division" (see screenshot below) to better comply with our internal wording guidelines.

image

As this is a very general term it is probably applicable to many other installations as well. See also https://differencess.com/department-vs-division-whats-the-difference/ and many other places why "department" may not be the right term for everybody. (Some context: what we colloquially call "institutes" at FZJ usually is a large group of people, often divided into groups or even departments, depending on the size of an "institute" - which may range from 10 to a 1000 people. Which is why calling it a "division" makes a lot more sense... As it's not an independent "organization or institution", we refrain from using that one.)

Thus to satisfy our immediate need it would be great if we can include the term short-term (pun intended) before tackling the long-term solution of making all the terms configurable.

Any open or closed issues related to this feature request?
There is #9420 which is about removing the limitation of the list being hard coded. Something similar was done before with File Categories, see #8478. @philippconzett asked for inclusion of another term back in #3681 .

Are you thinking about creating a pull request for this feature?
Yes sure, we would be glad to add a PR for this. I expect it to be very small and very un-disruptive, as it is only about extending the list.

@poikilotherm poikilotherm added Type: Feature a feature request Feature: Metadata Feature: Controlled Vocabulary Includes both Internal and external controlled vocabularies labels Jan 16, 2025
@poikilotherm poikilotherm self-assigned this Jan 16, 2025
@poikilotherm poikilotherm added the Size: 3 A percentage of a sprint. 2.1 hours. label Jan 16, 2025
@pdurbin
Copy link
Member

pdurbin commented Jan 16, 2025

I don't think adding "division" is controversial at all. IQSS is part of the Division of Social Science: https://socialscience.fas.harvard.edu

@poikilotherm please feel free to create a pull request if you like. Thanks.

@poikilotherm poikilotherm added Size: 0.5 A percentage of a sprint. 0.35 hours and removed Size: 3 A percentage of a sprint. 2.1 hours. labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Controlled Vocabulary Includes both Internal and external controlled vocabularies Feature: Metadata Size: 0.5 A percentage of a sprint. 0.35 hours Type: Feature a feature request
Projects
Status: Important
Status: No status
Development

No branches or pull requests

2 participants