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

Data resources should have a hierarchy #72

Open
beckvalle opened this issue Jul 14, 2024 · 1 comment
Open

Data resources should have a hierarchy #72

beckvalle opened this issue Jul 14, 2024 · 1 comment
Labels
design improvement Improvements of frontend design

Comments

@beckvalle
Copy link

Is your feature request related to a problem? Please describe.
I would like to upload a Natural Earth dataset. Natural Earth provides many sub datasets.

Describe the solution you'd like
There should be an upper level page per provider that contains subpages for individual datasets. For example Natural Earth main dataset page with links to all pages for individual datasets. Otherwise there can be many competing links that are not well tied tied together. I think the related resource link is not strong enough to be sufficient for something like this. Similarly - should be a top level frame for US Census data, with subpages for individual datasets.

@erickzli erickzli added the design improvement Improvements of frontend design label Jul 17, 2024
@beckvalle
Copy link
Author

Additional thoughts:
Some knowledge elements on the I-GUIDE platform are strongly connected and should be able to be searched for as a unit, along with metadata about the collection as a whole. Having linked tags is a weak relation that does not allow for additional organization and curation needed for a stronger connected group of elements.

Add a "collection" knowledge element that is a container for providing additional information about a group of other knowledge elements. In the main page for this elements, sub-elements should be able to be listed in specific orders along with additional information about each element.

For example, all resources relating to one of the summer schools should be part of a collection for the summer school. There should be a top level container element for all summer schools, and then a container element for each summer school.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design improvement Improvements of frontend design
Projects
None yet
Development

No branches or pull requests

2 participants