4 ms·
> GZR, also known as g//z/r on their first album, geezer on their second, and GZR on their third. I would be impressed if they had changed the band name from a
by euroderf 3y ago
> GZR, also known as g//z/r on their first album, geezer on their second, and GZR on their third.
I would be impressed if they had changed the band name from album to album BUT all three albums had the same identical album name.
- kdwikzncba 3y agoAll of these "band is changing name" edge cases are solved by separating giving entities ids internal to the dataset. Not even sure it's called an edge case at this stage.
- morelisp 3y agoWow if only we had an album_grouping_key or musicbrainz_albumid or something we could have solved this 20 years ago. "Horrible."
- tremon 3y agoI "solved" this years ago by (ab)using the artistsort key for this. Regardless of how the artist name is spelled, their tracks are listed sequentially. But my player uses a flat list, not an hierarchical structure.
- jwells89 3y agoAssuming a music library use case, one could address it with UI alone (making the the method of grouping under the hood an implementation detail) with “merge artist” and “merge album” functions surfaced in places like the context menu that appears when right-clicking an artist/album.
- obscenitido 3y agobonus points if it does this without altering the metadata in the original tracks.
- numpad0 3y agoYou just have to have a binary ID and maybe "pronunciation" fields too, for each song/album/artist entities in the database schema, that are on UI sanitized/normalized by searches and loose matches. It's not worth dealing with regularization and mapping rules between ASCII and whatever artists insist on using, like slightly different style of T used only in Western East Antarctic. It'll be just a String whatever. That way each files may keep whatever emojis used specifically for any specific distribution channels without troubles.