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

Featured Dataverses: Review this functionality #2155

Closed
eaquigley opened this issue May 12, 2015 · 9 comments
Closed

Featured Dataverses: Review this functionality #2155

eaquigley opened this issue May 12, 2015 · 9 comments
Labels
Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... Type: Suggestion an idea User Role: Curator Curates and reviews datasets, manages permissions UX & UI: Design This issue needs input on the design of the UI and from the product owner

Comments

@eaquigley
Copy link
Contributor

Reconsider Featured Dataverses so they could also be used to show the hierarchy of the dataverse.

cc @mcrosas

@eaquigley eaquigley self-assigned this May 12, 2015
@eaquigley eaquigley added this to the In Review milestone May 12, 2015
@sbarbosadataverse
Copy link

@eaquigley Hi Liz, just wondering where we are with this feature? It seems to be coming up as I create collections etc....

@mercecrosas
Copy link
Member

Also, from @sbarbosadataverse and PSI consider how to we display a large number of featured dataverses - perhaps use a solution different than a carroussel.

@mheppler mheppler added the Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... label Jan 28, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@pdurbin pdurbin added User Role: Curator Curates and reviews datasets, manages permissions and removed zTriaged labels Jun 30, 2017
@CCMumma
Copy link

CCMumma commented Nov 8, 2017

From TAMU, institutional user of the Texas Data Repository: "Although the organization of a dataverse with datasets and sub-dataverses may be hierarchical, we lack a way to create a view that represents this beyond the possibility of displaying “featured dataverses” near the top of a page. By this I mean that a given dataverse will show all sub-dataverses and datasets contained within as a list. I’ve had researchers ask why there isn’t a way to reflect the organization they try to impose through collections."

@sbarbosadataverse
Copy link

sbarbosadataverse commented Nov 8, 2017 via email

@jggautier
Copy link
Contributor

Reviving this general issue to record here (before I forget) that a Dataverse collection's "Featured" carousel can contain only its direct children collections (so not its grandchildren collections or great-grandchildren, etc.) and this might also be reconsidered.

For example, being able to display on Bob Dataverse collection's "Featured" carousel any collection within Bob Dataverse collection, even if it's a grand child or great grand child, is something the Harvard Dataverse Repository staff wonder would be beneficial. The staff are re-organizing sub-collections with a particular large collection on the Harvard Dataverse Repository and the re-organizing will mean that some sub-collections that were in the parent collection's "Featured" carousel will be removed from the carousel because they'll no longer be direct children of the parent collection.

@pdurbin
Copy link
Member

pdurbin commented Oct 6, 2022

Although the organization of a dataverse with datasets and sub-dataverses may be hierarchical, we lack a way to create a view that represents this

@CCMumma there's some code at https://github.com/IQSS/miniverse/tree/master/dv_apps/metrics/templates/metrics/viz-tree and a comment at #5603 (comment) that explains where this viz of collections (but not datasets) below came from. Not sure if this helps. Please feel to create a fresh issue. I hear you. People want to see the tree, they want to know how collections are organized.

54040476-79bdf180-4193-11e9-9769-fc4a143512ae

@DS-INRAE
Copy link
Member

Chould this get the label "UX & UI: Design" so the discussion of this feature doesn't get forgotten when porting on the SPA ? 😀

@pdurbin pdurbin added the UX & UI: Design This issue needs input on the design of the UI and from the product owner label Jul 3, 2024
@DS-INRAE DS-INRAE moved this to 🔍 Interest in Recherche Data Gouv Jul 10, 2024
@DS-INRAE
Copy link
Member

Another suggestion to take into account in the rework, being able to sort the featured collections:

@cmbz
Copy link

cmbz commented Aug 20, 2024

To focus on the most important features and bugs, we are closing issues created before 2020 (version 5.0) that are not new feature requests with the label 'Type: Feature'.

If you created this issue and you feel the team should revisit this decision, please reopen the issue and leave a comment.

@cmbz cmbz closed this as completed Aug 20, 2024
@github-project-automation github-project-automation bot moved this from 🔍 Interest to Done in Recherche Data Gouv Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... Type: Suggestion an idea User Role: Curator Curates and reviews datasets, manages permissions UX & UI: Design This issue needs input on the design of the UI and from the product owner
Projects
Status: Done
Development

No branches or pull requests

10 participants