Wikidata:Property proposal/MusicBrainz genre ID

From Wikidata
Jump to navigation Jump to search

MusicBrainz genre ID

[edit]

Originally proposed at Wikidata:Property proposal/Authority control

Descriptionidentifier for a genre on the MusicBrainz open music encyclopedia
Representsmusic genre (Q188451)
Data typeExternal identifier
Domainmusic genre (Q188451)
Allowed values[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}
Examplenerdcore (Q1754592)9c8ba153-740e-4b88-b7ff-31d004944c95
Format and edit filter validationThe same as other MusicBrainz, if present
Sourcehttps://musicbrainz.org/
Formatter URLhttps://musicbrainz.org/genre/$1

Motivation

[edit]

Similarly to other MusicBrainz related entities like Property:P434, Property:P1330 and Property:P435 we now also have genres!
Musical genre is a new entity type, it's fairly bare-bones right now, but it's actively being worked on by User:Reosarevok . CatQuest, The Endavouring Cat (talk) 10:20, 20 March 2020 (UTC)[reply]

Discussion

[edit]

 Support I'm of course a bit biased, but I agree! :) (and it would be consistent with us having the other MusicBrainz identifiers as properties). --Reosarevok (talk) 10:00, 23 March 2020 (UTC)[reply]

 Support Any move to better handle genres is a welcome one in my book! Moebeus (talk) 16:34, 23 March 2020 (UTC)[reply]

 Support Also biased, but yes, if WD has properties for other MBIDs, then I don’t see why it wouldn’t have Genre MBIDs too. —Freso (talk) 18:34, 23 March 2020 (UTC)[reply]

 Support Glad to see how far MusicBrainz' genre tagging system has come. Do you have any examples with multiple associated tags so we can see what that looks like? —Ringbang (talk) 01:51, 30 March 2020 (UTC)[reply]

WikiProject Music has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. @CatCat, Reosarevok, Moebeus, Freso, Ringbang: ✓ Done at MusicBrainz genre ID (P8052) --SilentSpike (talk) 13:18, 3 April 2020 (UTC)[reply]

 SupportDaniele.Brundu (talk) 18:54, 3 April 2020 (UTC)[reply]