[API Request] New fields "releaseStatus" and "media" for Albums

[GioF71]

Type of change

API extension

Proposal description

For the endpoints which return Album, it would be nice to have extra fields for releaseStatus and media.
I have shortly discussed the topic with @epoupon here.

Both fields can be retrieved from tags that are generally filled by popular tag editors like e.g. MusicBrainz Picard.
Considering that releaseType is already available through the subsonic api, this addition would add good information which might be made available to clients.

Of course if this is approved I will create a pull request with the proposed changes.

Backward compatibility impact

There should be no backward compatibility impact as there is no change to existing fields.

Backward compatibility

• No backward compatibility impact.

API details

The change should extend to all the endpoint which return Albums.
Simply two more fields with releaseStatus and media should be added in order to carry the additional detail about the album.

Security impacts

No response

Potential issues

No response

Alternative solutions

No response

[Tolriq]

Can you confirm the tags used for that ?

[GioF71]

I'm not sure I understand the question, maybe this image might clarify:

Or, maybe you'd prefer the output of metaflac or a similar tool?

[GioF71]

Using metaflac with "--show-all-tags", the tags are:

MEDIA=CD
RELEASESTATUS=official

Hope this helps!

[Tolriq]

Yes the actual tags, seems they are different https://docs.mp3tag.de/mapping/#musicbrainz_albumstatus and probably https://docs.mp3tag.de/mapping/#mediatype ?

It's important to really know what we are talking about and the related tags, to not add some custom tags that won't match real users data.

[GioF71]

Hello, maybe @epoupon can give a better and more detailed answer, but yes, I suppose that the information that should be displayed as "media" and "releasestatus" might come from different tags, and maybe the same file might contain multiple, so a list of tag names to consider, in order or priority, might be helpful.

[epoupon]

Let's focus on Media. Also adding picard reference for it: https://picard-docs.musicbrainz.org/en/appendices/tag_mapping.html#id14 -> mapped to TMED/etc.

This tag is tied to each media (disc) that is in the release.
For example: https://musicbrainz.org/release/9c67551e-3b09-30c0-b68a-c0ee2cbff6d2 -> Here we have a CD and an enhanced CD. Picard will write a different media tag for each disc.
So we should set the info at the disc level. Maybe we could somewhat "recycle" the OS DiscTitle object for that? And also put a cover for that disc...

[Tolriq]

Ok so Picard media is media type for the rest of the world as usual ...

And yes seems DiscTitle was a really bad name after all :(
Not sure if we should introduce a new better type, or extend the existing despiste the naming issue.

[GioF71]

Hello @epoupon and @Tolriq, again as with previous changes to the api, would it beneficial if I split this request in two, one for each field?

[GioF71]

Let's focus on Media. Also adding picard reference for it: https://picard-docs.musicbrainz.org/en/appendices/tag_mapping.html#id14 -> mapped to TMED/etc.

This tag is tied to each media (disc) that is in the release. For example: https://musicbrainz.org/release/9c67551e-3b09-30c0-b68a-c0ee2cbff6d2 -> Here we have a CD and an enhanced CD.

Hello, what kind of data should be available at the album level, in that specific case? Maybe, if we agree that media returns an array, both the values?