The universal database hierarchy for music databases is:
Artist->Album-> Song.
Rose uses:
Artist → song and Album → song.
Please consider switching to the standard hierarchy for music databases.
StandardModel
The universal database hierarchy for music databases is:
Artist->Album-> Song.
Rose uses:
Artist → song and Album → song.
Please consider switching to the standard hierarchy for music databases.
StandardModel
It is?
I did not know that there is such a global valid standard for music data base.
In any case, Rose has a lot of work to do to make using a music DB worthwhile and ease of use.
And while you’re at it:
Please, please add listing by Album Artist as well as just artist. JPLAY for iOS added this within days of it being requested
Also add the ability to sort albums within an artist by release date rather than just alphabetically.
Ben,
“Global” it may not be. I used the word “standard” to mean what arrangement is used by the biggest music listing players and is the easiest to use.
As your question implies, there is no authoritative or regulatory body that sets music database nesting hierarchies. The way Rose does it, although illogical, is not invalid.
I’m just in favor of the most logical, easiest to search and use database nesting hierarchy.
StandardModel
@StaandardModel Apologies for jumping on your thread like that. It’s just very frustrating that simple and logical suggestions for improvement, which arguably should have been in there from day 1, appear to not get anywhere.