Users struggle to find tree view for dataset files

[PaulBoon]

When we upgraded from 4.10.1 to 4.18.1 some users where eager to see the directory structure (tree view) of the dataset files, but could not at first find it.

I propose to make the two view 'options' more related to each other and the files 'view' by using a 'tab view' instead of two separate buttons. Furthermore I propose to use icons on the buttons to make them more prominent and a bit more intuitive.

[TaniaSchlatter]

Hi @PaulBoon. I can see that the button to toggle List and Tree view is hard to find. The dataset page is busy. We need to balance a wide number of possible user scenarios and installation situations. To achieve this, each UI element has a role to play. Elements are part of groups based on function and context. Tabs change the information shown for a dataset. Search/filter/sort features change the display of information on the files tab. "Tree view" plays a role more like search and filter features than the role of tabs. We need to balance the visual emphasis of elements overall, which means that some are less noticeable than others.

I understand that rationale is not necessarily useful for users stuck in a particular situation. Hopefully this grouping will be more clear in the redesign. Mockups of the updated dataset page

[PaulBoon]

Hi @TaniaSchlatter, I think that usability testing would be helpful to improve the interface.
Also the datasets you then test with should not only have just a handful of files in a single folder, but instead have much more files that are obviously categorised in a folder structure.
As an alternative you should also consider to always show a tree view to the left of the file listing.

[TaniaSchlatter]

@PaulBoon we did usability testing a little over a year ago before implementation. Responses were quite positive. We made some refinements, based on what we learned, and launched. There is always room for improvement. We are planning more usability testing, and will keep this feedback in mind.

[PaulBoon]

I just had to edit a screenshot from the mockup to explain what I think is better.

[LauraHuisintveld]

I am not sure if this deserves a separate issue, but one of our users suggested to show the tree view (instead of table view) as default for datasets with a lot of files. He mentioned an example of a dataset with 1129 files.
There are of course also datasets with a lot of files without a folder structure at all.

[rlzijdeman]

Hi, I'd like to +1 @LauraHuisintveld 's the suggestion to have tree view as the default. Our users fail to find the label as well. Moreover, if there is no structure, tree view doesn't hurt anyone, while vice versa it sort of does.

Though I can't rely on user feedback, I instinctively side with @LauraHuisintveld's proposal. A compromise could also be: let users choose whether their dataset's files will appear in table or tree view on a dataset basis (e.g. the same user might think that, for dataset A, which has few files, table view is fine, but for dataset B, which has 50+ files, it is best to have tree view toggled by default, though users can still revert to table view if that's their preference).

[TaniaSchlatter]

A compromise is a good solution. There are use cases that support showing file detail and functionality from the table view. The vast majority of datasets in Harvard Dataverse have fewer than 20 files. There is also strong desire here to make file-level features more visible as opposed to less, which would be the case if tree view were the default.

[pdurbin]

Related:

• Feature Request/Idea: making the tree view on dataset page bookmarkable #8694
• Add settings to make Tree View as a default option #8892