dataverse icon indicating copy to clipboard operation
dataverse copied to clipboard

Add settings to make Tree View as a default option

Open lubitchv opened this issue 2 years ago • 2 comments

Overview of the Feature Request Some of our users upload many files in one dataset. To navigate around so many files there is a file hierarchy (tree view). But table view is a default and it confuses some of the users who do not realize that there is a tree view option. We would like to see a setting in a specific dataverse that can trigger default tree view for datasets in this dataverse.

What kind of user is the feature intended for? (Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin) Dataverse UI users who can see the TreeView and dataverse Admin users who can setup such an option for a specific dataverse.

lubitchv avatar Aug 04 '22 14:08 lubitchv

@lubitchv thanks, this issue is related:

  • #6730

pdurbin avatar Aug 04 '22 21:08 pdurbin

Related:

  • #8694

eunices avatar Aug 23 '22 04:08 eunices

Hello, my team and I are also interested in this, has anyone made any progress?

arnaumevi avatar Jan 11 '23 10:01 arnaumevi

I'm not aware of any but FWIW: https://github.com/IQSS/dataverse/pull/9204 supports a group-by-folder functionality in the main table which might help. It will hopefully be part of the next release.

qqmyers avatar Jan 11 '23 13:01 qqmyers

I'm afraid #9204 doesn't solve the issue. For larger datasets, a view which displays the hierarchical file structure is really indispensable.

kobbejager avatar Aug 29 '23 08:08 kobbejager

2024/01/22

  • As per conversation during prioritization meeting, there is a desire for a data owner to be able to set the view at the dataset level (e.g., for datasets that do not belong to a collection) and at the collection level. This current issue doesn't cover the first case.
    • Question: Is there a user need or desire for visual consistency across all datasets/collections
  • Recommendations. Propose the following to @siacus:
    • Split functionality into API and UI components
      • Implement functionality in the API for collections
      • Assess the functionality (in partnership with members of the Dataverse usability community) to inform decision about whether/when to implement API for datasets
        • Implement functionality in the API for datasets
      • Post-SPA Beta, implement a switch in the UI
      • Decide how and when to activate feature in the Harvard Dataverse UI
        • Note that this will require further conversations with other stakeholders. Conversations are anticipated to require Tree View as the default for HDV

Note: This discussion touches on UX/UI topics and a more detailed strategy for addressing these issues should be considered.

Next steps:

  • Prioritize issue
  • @siacus and @jggautier will review issue
  • Conversation with @siacus , @jggautier , @scolapasta , @sbarbosadataverse and @cmbz about scheduling implementation and/or additional Community engagement.

cmbz avatar Jan 22 '24 19:01 cmbz

2024/03/14

  • Some folks will reach out to other interested stakeholders to see if they would be willing to implement the feature.
  • Otherwise we will wait to implement this feature in the SPA.

cmbz avatar Mar 13 '24 17:03 cmbz

2024/03/13 Closing because unfortunately this project will not move forward

cmbz avatar Mar 13 '24 17:03 cmbz

To follow development of the tree view in the new frontend:

  • https://github.com/IQSS/dataverse-frontend/issues/117

pdurbin avatar Mar 14 '24 00:03 pdurbin