02-24-2025, 07:50 PM
Reggoboy's request is IMHO too specific to justify such huge changes.
BUT: it would absolutely make sense to implement meta data for groups. They should be flexibly usable for users' individual needs, similar to custom and custom2, additionally with configurable names.
I can organise my workflow for many gigs with various line-ups without problems. Reggoboy could use the meta data of setlists to store whatever he thinks to need.
My personal use cases for meta data for groups would be:
I use albums for fakebooks. If albums had meta data I would configure them to store e.g. author, publisher, year, ISBN ...
European copyright depends on the year of death of all authors. If composers had meta data I would use them to store the date of death and a different display name and sort name.
BUT: it would absolutely make sense to implement meta data for groups. They should be flexibly usable for users' individual needs, similar to custom and custom2, additionally with configurable names.
I can organise my workflow for many gigs with various line-ups without problems. Reggoboy could use the meta data of setlists to store whatever he thinks to need.
My personal use cases for meta data for groups would be:
I use albums for fakebooks. If albums had meta data I would configure them to store e.g. author, publisher, year, ISBN ...
European copyright depends on the year of death of all authors. If composers had meta data I would use them to store the date of death and a different display name and sort name.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de