Splitting out Release Comments

featurerequest
comments
release-comments
Tags: #<Tag:0x00007f23c506b040> #<Tag:0x00007f23c506ae60> #<Tag:0x00007f23c506ab90>

#1

OK, you can probably file this one away under S for “Some yahoo’s getting ideas above her station in life again and suggesting big changes to someone else’s perfectly working and beloved system”…

It looks to me like Release Comments are serving two different purposes, and might benefit from being split up into two different fields, e.g. Disambiguation and Release Subtitle.

One of these uses seems to be to disambiguate things for people adding and editing Releases, so they make sure they’re working on the right one. “Made in Germany by Warner Manufacturing Europe” and “reissue, 28 tracks. “Whoops Now” on separate track 28” would fall into this category. They help contributing users to make sure they’re editing the right Release, but you don’t want them showing up in the metadata that gets saved with the music files in your library. They’re also not explicitly named in the packaging.

Another use seems to be to disambiguate releases within people’s actual music libraries (completionist type people, at least). They’re not just of interest to people editing the metadata, but also useful to people using that data to sort their library out. “30th anniversary edition” and “CD1” would fall into this category. You can have CD 1 and CD 2 of a pair of singles, and you can have an original album and also its deluxe edition, and these keep them separate in your music player. If not a fully fledged subtitle, they’re at least a main selling point. They are usually explicitly named in the packaging.

Although this is still somewhat simplistic: Weezer’s album colours seem like fully fledged subtitles, essential to include when loading the tracks into a music player in order to keep the albums separate, even if they’re unofficial.

Does this seem like a feature worth requesting? Or am I missing something about how Release Comments are used?

Cheers!


#2

I second the motion, super-duper great idea! I add a lot of older recordings and Spanish recordings, where the style of the song is often printed on the label and where it’s not an editors opinion or “disambiguation”. Examples are “Fox-Trot”, “Bolero”, “Alegrias”, etc.

A̶r̶e̶ ̶y̶o̶u̶ ̶c̶o̶m̶f̶o̶r̶t̶a̶b̶l̶e̶ ̶a̶d̶d̶i̶n̶g̶ ̶a̶ ̶t̶i̶c̶k̶e̶t̶ ̶t̶o̶ ̶t̶h̶e̶ ̶d̶e̶v̶e̶l̶o̶p̶m̶e̶n̶t̶ ̶b̶o̶a̶r̶d̶?̶ (Never mind, see you are a programmer. Add a ticket and you have my vote!)


#3

The first four Peter Gabriel albums are a similar case to Weezer. In both those cases, the “subtitle” seems like it’s a property of the release group rather than the release.

Interesting that there’s a guideline for Extra Title Information at the track level but not at the release/RG level.


#4

Thanks for your input! It sounds like this might touch upon several semi-related things then…

  1. Perhaps Songs should be allowed to have optional Subtitles, judging by the above (although I’m not familiar enough myself to say).

  2. Release Groups have a single Disambiguation which works well (e.g. “Weezer (blue album)”), as Release Groups encompass all versions, so that single level of disambiguation is enough. So they’re fine already…

  3. …but Releases themselves could probably do with two different types of disambiguation, the regular Disambiguation (editor’s disambiguation) and the Subtitle (library’s disambiguation).

I think I was overlooking the existence of Release Group Disambiguation, so my fear about coloured albums and the like being too complex was unfounded after all. Phew, that actually makes things simpler then.


#5

Feature request added, cheers!


#6

Release comments actually are disambiguation comments, that is, they should serve the first purpose.

Subtitles should be appended to the field title, separated by a colon (:), according to the official style guideline (until MusicBrainz eventually supports sub-titles as a separate field).

Release comments that do not serve at least the purpose of distinguishing between releases should be removed or moved to the appropriate field or else to the annotation.


#7

I agree with this, but it would be better to call the new field “Edition” rather than “Subtitle”.


#8

This feels wrong to me in the case of unofficial subtitles (such as the Weezer and Peter Gabriel examples). “Peter Gabriel: Melt” is not the title of an album. But maybe those are rare enough cases to be treated as exceptions. Maybe users just have to use the cover art to tell them apart in their players (or else write a clever Picard script to name them uniquely).


#9

Well, those are literally disambiguation comments - they only exist to tell which of the albums of the same name this is. Those can definitely stay there, and calling them subtitles seems strange to me in the first place :slight_smile:


#10

Understood, but to ZoeB’s original point, they potentially serve a purpose for end users of the data, not just for editors.


#11

In this case, they should be put in both disambiguation and annotation: