Add Hierarchical Categories to More Metadata Fields
š Summary
Allow hierarchical, collapsible values in additional metadata fields using the same structure currently supported by Genres.
ā Problem
Genres can be organized using values such as:
Role-Playing / Action RPG
This creates a parent category with a collapsible subcategory. Other fields, including Series and custom fields, currently appear as flat lists even when users need several related values.
Large collections can therefore produce long and difficult-to-navigate filter lists.
š” Proposal
Extend hierarchical value support to other compatible metadata fields, particularly:
Series
Custom fields
Play Mode
Other multi-value fields displayed in the sidebar
Users could enter values such as:
Final Fantasy / Main SeriesCollection / Fan TranslationsMultiplayer / Cooperative
LaunchBox would display these as collapsible parent and child entries throughout applicable filters.
š§© Use Cases
Organize a large franchise into main games, spin-offs, and remakes
Create structured custom categories for hacks, translations, or collections
Group related values without filling the sidebar with separate entries
Browse large libraries using more meaningful hierarchies
š¦ Benefits
Improves navigation in large collections
Makes custom fields significantly more flexible
Provides consistent organization across metadata fields
Reduces clutter in sidebar filter lists
ā ļø Considerations
Hierarchies should only apply to fields where nested values make sense
Existing values containing slashes must continue to work correctly
Editing, filtering, and bulk editing should recognize the same hierarchy
Parent selections should optionally include items assigned to their child values

Log in to comment and vote
Comments1
Sep 21
PinnedHi there!
Thanks so much for submitting this request and for taking the time to explain your use case ā that context is always super helpful.
Iāve gone ahead and fleshed out the main idea using the info you provided, and Iām opening it up to the community for further discussion and feedback. Please let me know if this fleshed-out version doesnāt match your original intended request.
Feel free to let me know if you have any extra thoughts, examples, or edge cases you think might be relevant!
Cheers,
The LaunchBox team