I am splitting off a topic about Paul Whiteman and related groups here. I invite @tillywilly to take the microphone and lead a discussion.
This subject has been popping up in an edit discussion, a related forum thread Classical or not classical: edge case, another forum thread Hiding artist into credits to force them into discographies, and maybe more.
@tillywilly, what end goal are you trying to achieve? Is it to have a single MusicBrainz web page with a complete discography of every Release Paul Whiteman performed for, regardless of whether the release artwork credited him individually or as part of a group? Is it to record the historical facts about the various group names, and whether they were distinct groups or just wording for the sake of branding? And in what way is what you currently get from MusicBrainz falling short?
I suspect the discussion will eventually focus on a few questions:
- What are the historical facts about Paul Whiteman and these groups?
- What do Release artworks say about these facts, and which facts do the artworks not mention?
- How should the above be turned into data in the MusicBrainz database?
- How should the MusicBrainz web app display the data in the database?
My first contribution: an important way to represent this kind of data in the MusicBrainz database (#3) is by means of Relationships. It is better to use those than to hide misplaced factual data in Track Artist fields and the like.
Relationships are underused for Paul Whiteman, it seems to me. For instance, Paul Whiteman artist/b8d920 is not related to the Paul Whiteman Concert Orchestra artist/4d4582 as a Founding Eponymous Member. He is so related to the Paul Whiteman & His Ambassador Orchestra artist/03ade0. Adding Relationships to capture the facts about Paul Whiteman seems to be a good next step.