When a consumer uploads a brand new doc, they must assign that doc to a sure class and subcategory. Our present resolution makes use of two dropdowns for this.
So presently the workflow appears like this:
- Consumer selects class
- Choices for subcategory are loaded into second dropdown, relying on the choice for the primary dropdown
- Consumer selects subcategory
Nonetheless, there’s one main limitation to this resolution: The consumer can’t scan all the chances at a look. Which means that if they’ve sure subcategory in thoughts, however do not know the corresponding class of their desired subcategory, they might want to click on by means of all classes in a trial-and-error method with a purpose to discover the wanted subcategory.
Since subcategories are lazily loaded when a class has been chosen, there’s additionally no chance to look by means of all subcategories.
One other stumbling block on the subject of looking out is, that there might be equally named subcategories inside completely different classes.
The alternate options
I’ve learn by means of related questions right here on UXSE and the one viable different appears to be a tree view. I do not assume there’s something flawed with tree views normally. Nonetheless, classes and subcategories are created and maintained by admins and thus, not restricted in quantity (notice: prospects’ admins, not ours. So each buyer may need their very own distinctive set of classes). So we’re coping with 1..n classes, which every incorporates 1..m subcategories. Due to this fact, the tree view may get fairly massive, making it very cumbersome to learn and use.
The identical is true for a singular dropdown with each classes and (indented) subcategories.
- Precisely one class and one subcategory can and have to be chosen.
- The hierarchy is proscribed in depth as described. There are not any sub-subcategories.
- Classes are distinctive.
- Subcategories are distinctive inside their class, however not globally (There might be an equally named subcategory in one other class).
- No constraints to variety of classes and variety of subcategories.
Making it simpler and extra handy for the consumer to pick class and subcategory. Particularly if the consumer is uncertain in regards to the wanted (sub-)class, it might be very useful to get an summary of what is obtainable.
Is there one thing I’m lacking? There have to be a intelligent method to do that. Or is our present resolution already probably the most possible choice? Any enter is drastically appreciated!