-
Notifications
You must be signed in to change notification settings - Fork 495
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
Add settings to make Tree View as a default option #8892
Comments
@lubitchv thanks, this issue is related: |
Hello, my team and I are also interested in this, has anyone made any progress? |
I'm not aware of any but FWIW: #9204 supports a group-by-folder functionality in the main table which might help. It will hopefully be part of the next release. |
I'm afraid #9204 doesn't solve the issue. For larger datasets, a view which displays the hierarchical file structure is really indispensable. |
2024/01/22
Note: This discussion touches on UX/UI topics and a more detailed strategy for addressing these issues should be considered. Next steps:
|
2024/03/14
|
2024/03/13 |
To follow development of the tree view in the new frontend: |
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.
The text was updated successfully, but these errors were encountered: