Wikidata:Property proposal/MusicBrainz release ID

MusicBrainz release ID

Originally proposed at Wikidata:Property proposal/Authority control

   Done: MusicBrainz release ID (P5813) (Talk and documentation)

Description	identifier for a release in the MusicBrainz open music encyclopedia (edition)
Data type	External identifier
Domain	version, edition or translation (Q3331189)
Example 1	Between the Buttons (Q56055356) → d05b1707-2885-4261-b0f0-4a8a23513523
Example 2	Nuggets: Original Artyfacts from the First Psychedelic Era, 1965–1968 (Q54641059) → 4f970f09-69ed-47bd-85e6-daf19347f17a
Example 3	Nuggets: Original Artyfacts from the First Psychedelic Era, 1965–1968 (Q54641193) → 7beb47e7-f54b-46a3-a570-7fe932f0e350
Example 4	Eastside (Q55977453) → 48915aaf-a245-4f92-acef-b9d3610d07d2 (item also has MusicBrainz release group ID (P436), since there is only one edition)
Formatter URL	https://musicbrainz.org/release/$1
See also	MusicBrainz release group ID (P436), MusicBrainz artist ID (P434), MusicBrainz work ID (P435), MusicBrainz instrument ID (P1330), MusicBrainz series ID (P1407), MusicBrainz label ID (P966), MusicBrainz area ID (P982)

https://www.wikidata.org/wiki/Property

Motivation

Doesn't exist yet; would be helpful for albums released in multiple editions (e.g. standard/deluxe, or different tracks in different countries). Unfortunately using this would require a lot of extra items for very similar releases (e.g. mono/stereo), but it would be necessary for tracklist (P658) to be used correctly. Jc86035 (talk) 19:31, 11 August 2018 (UTC)

Discussion

•  Support David (talk) 09:17, 12 August 2018 (UTC)
•  Comment couldn't this be a parent property for all other MB ones? It seems that value are unique across all the properties with have.
  --- Jura 20:24, 12 August 2018 (UTC)

  @Jura1: The formatter URLs would break. Also, for release groups with only one release it would make sense to add both identifiers to the item which represents the release (since as far as I'm aware Wikidata uses version, edition or translation (Q3331189) only to distinguish works with multiple versions). Jc86035 (talk) 10:47, 13 August 2018 (UTC)

  I'm sure a solution can be could for the formatter url. Somehow these MB properties got out of the hand.
  --- Jura 05:51, 16 August 2018 (UTC)

• wholehearted  Support by analogy with all other MusicBrainz properties. Mahir256 (talk) 18:19, 13 August 2018 (UTC)
•  Support Smallison (talk) 15:55, 14 August 2018 (UTC)
•  Oppose as proposed. See above.
  --- Jura 05:51, 16 August 2018 (UTC)

  @Jura1: If you want to have one unified MusicBrainz property then propose the other MusicBrainz properties for deletion first. I don't think there's a limit on the number of properties that can exist, and different MusicBrainz IDs might have different constraints (e.g. an item might be allowed to have a recording ID as well as a work ID, but not a recording ID as well as a release group ID). Jc86035 (talk) 06:54, 16 August 2018 (UTC)

  We can make this a parent property for anything that doesn't have a dedicated one yet. No need to delete the others first. As I understand it, there is just one MB identifier: the same value doesn't re-occur across properties.
  --- Jura 07:44, 16 August 2018 (UTC)

•  Support Regards, ZI Jony ^(Talk) 14:26, 27 August 2018 (UTC)

@ديفيد عادل وهبة خليل 2, ZI Jony, Smallison, Jc86035, Mahir256, Jura1:  Done: MusicBrainz release ID (P5813). − Pintoch (talk) 09:59, 7 September 2018 (UTC)