Configurability to arrange the categories to be multilevel (tree) for Search

As I solution architect I would like to arrange persistently all my categories in my landing “Search page”, in a multilevel (tree) format, with minimal 2 levels, so the “Search page” is not convoluted/big and users still have access to all their categories with minimal clicks. 

As of today, I see that the only categories that allow multiple levels are the ones that were “inherited” from the old resource types, such as asset, files, time series, activity. Everything else added in the data model will be available view bullets.

For PBF we have several data models within the same project, what causes the search page to be very extensive and not user friendly. As a workaround, we created a solution data model and configured a new location to expose a simplified “search page”, but for that we are omitting several of the categories that users would like to see. So if the user wants to access data that is not in this simplified view he/she needs to select the “full” location that has all the data, what is a bad user experience in terms of multiple clicks.. on the other hand if we keep everything exposed it is very hard to find a category and the search page gets convoluted. In the work around we implemented, user can still change location go from the “full” location to the “simplified” location, but it requires multiple clicks, what is not desirable. A better solution would be to allow multilevel configuration for categories (parent/child relationship), so we could groups categories that are related to each other. Also the data would be more organized and friendly from the user point of view. 

Note: The following it is just and example to show the desirable outcome for a “look & feel” in terms of arranging data, please ignore the “material” reference, once it is not relevant.

- Material

  - Material Group

  - Material Type

  - Material Status