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

Support Hierarchical Controlled Vocabularies #434

Open
eaquigley opened this issue Jul 9, 2014 · 7 comments
Open

Support Hierarchical Controlled Vocabularies #434

eaquigley opened this issue Jul 9, 2014 · 7 comments
Labels
Feature: Metadata Type: Feature a feature request User Role: Depositor Creates datasets, uploads data, etc.

Comments

@eaquigley
Copy link
Contributor

eaquigley commented Jul 9, 2014


Author Name: Eleni Castro (@posixeleni)
Original Redmine Issue: 3849, https://redmine.hmdc.harvard.edu/issues/3849
Original Date: 2014-04-12
Original Assignee: Gustavo Durand


We will need to be able to support lists of hierarchical controlled vocabularies. We currently only support flat lists. This will be important for biomedical metadata and for GSD metadata block.

For example:

  • Semester (Fall 2013)
    ** Course Name (only list of courses for Fall 2013)
    ** Faculty Name (only list of faculty for Fall 2013)
@eaquigley eaquigley added this to the In Review milestone Jul 9, 2014
@bencomp
Copy link
Contributor

bencomp commented Mar 11, 2015

This sounds like the vocabulary has several facets; three fields could be used for this case. I don't think faculty teaching in Fall 2013 is conceptually different from faculty teaching in other semesters?

However, controlled vocabularies, especially subject vocabularies or geographical coverage vocabularies, are rarely flat lists. Having identifiers for terms in a vocabulary can help structure them (see #947). But (althought I'm not assigned) I'm not sure what kind of support is envisioned here.

@bencomp
Copy link
Contributor

bencomp commented Mar 11, 2015

Giving it another thought: one way of support for hierarchical controlled vocabularies is including all dataverses and datasets that have been assigned vocabulary term 1.X when in a facet only term 1 is selected (and 1.X is a narrower term than 1).

@posixeleni
Copy link
Contributor

@bencomp you're right the example above wasnt a good one. A better example is the NCBI Taxonomy for Organisms used in Life Sciences studies: http://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?name=Eubacteria

image

@pdurbin
Copy link
Member

pdurbin commented Oct 15, 2016

This is something @bmckinney at least mentioned last week so I added the SBGrid label.

@mheppler mheppler added this to the 4.7 - Dashboard milestone Oct 18, 2016
@mheppler
Copy link
Contributor

With the potential to require this feature in association with a custom Harvard Dataverse homepage (#2003), I have added the 4.7 milestone label.

@djbrooke djbrooke added the ready label Jan 20, 2017
@djbrooke djbrooke removed the ready label Jan 25, 2017
@djbrooke djbrooke removed this from the 4.7 - Dashboard and Dataverse Homepage milestone Jan 30, 2017
@djbrooke djbrooke added ready and removed SBGrid labels Jan 30, 2017
@pdurbin
Copy link
Member

pdurbin commented Feb 2, 2017

There is discussion about the subject field in #1815 that should be reviewed. These issues seem quite similar to me.

@pdurbin
Copy link
Member

pdurbin commented Oct 6, 2022

This will be important for biomedical metadata

Related:

These days we support external vocabularies but I'm not sure if any are hierarchical (I've only played with ORCID and ROR): https://guides.dataverse.org/en/latest/admin/metadatacustomization.html#using-external-vocabulary-services

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Metadata Type: Feature a feature request User Role: Depositor Creates datasets, uploads data, etc.
Projects
None yet
Development

No branches or pull requests

9 participants