Hide objects in sub-dataverses (dataverses that are children of children)

[RightInTwo]

As a user, I would like to browse a dataverse installation hierarchically, so that only direct children (dataverses and datasets that belong to THIS dataverse, not to children of THIS dataverse) are displayed.

Motivation: This would help new users to understand and find their way around the hierarchy of dataverses.

(Sorry if this has been discussed already, it's kind of hard to find something about it because of the ambiguous search terms....)

[pdurbin]

@RightInTwo I don't think this has been discussed but I'm reminded of screenshots in #182 (and somewhat conversations like #5131).

[RightInTwo]

I'm a bit surprised that this never came up. Would it be hard to implement a switch to include/exclude sub-dataverses?

...or something like "Include sub-dataverses"

[mheppler]

@RightInTwo it was definitely a design decision to display children and grand/sub children together, in an attempt to make it easier to determine "what is in this". That said, I would be curious to know more about the use case you present, and if anyone else in the community has similar needs and expectations.

My take on your proposed "Sub-Dataverses" facet filter would be to suggest what @pdurbin already hinted at when referencing #5131, that a "Hierarchical" option under the Sort btn could also be a potential solution. Listing direct child first, and so on down the tree.

For the record, hierarchical views of datasets was added in 4.13 (#5572), and I just wanted to reference that work here, as there are a lot of similarities in these two features.

[RightInTwo]

@RightInTwo it was definitely a design decision to display children and grand/sub children together, in an attempt to make it easier to determine "what is in this". That said, I would be curious to know more about the use case you present, and if anyone else in the community has similar needs and expectations.

Well, it confused multiple colleagues of mine. When they add a dataverse to another, they do that to get a better overview, which they don't achieve by nesting dataverses, as everything is still displayed on the higher layer.

My take on your proposed "Sub-Dataverses" facet filter would be to suggest what @pdurbin already hinted at when referencing #5131, that a "Hierarchical" option under the Sort btn could also be a potential solution. Listing direct child first, and so on down the tree.

This would not fulfill my use case, where I want to make the structure of our dataverses easy to understand for newbies. I'd much prefer filtering over sorting.

[pdurbin]

As a user, I would like to browse a dataverse installation hierarchically, so that only direct children (dataverses and datasets that belong to THIS dataverse, not to children of THIS dataverse) are displayed.

It's funny, that's how the "contents" endpoint of the native API works. It only shows direct children. And it show both collections and datasets.

Motivation: This would help new users to understand and find their way around the hierarchy of dataverses.

Yes, we heard this often. #2155 starts with "Reconsider Featured Dataverses so they could also be used to show the hierarchy of the dataverse." (We'd called these "collections" these days).

@RightInTwo are you still interested in this?

[RightInTwo]

Since I am not working with Research Data currently, I'm not pursuing this. Feel free to reopen this issue if need arises.

[pdurbin]

Thanks, @RightInTwo . Hopefully we'll create another dataset together in the IQSS kitchen someday!

[RightInTwo]

Agreed, @pdurbin! I'll definitely plan a stop if I'm near. That dataset needs some solid follow-up replication anyways! ... and maybe even a larger focus group with an extended universe :D Best wishes to everyone