Property talk:P434
Latest comment: 5 years ago by Jura1 in topic Same value in other MusicBrainz properties
Documentation
MusicBrainz artist ID
identifier for an artist in the MusicBrainz open music encyclopedia
identifier for an artist in the MusicBrainz open music encyclopedia
[create Create a translatable help page (preferably in English) for this property to be included here]
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Scope, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Single value, SPARQL
Format “
List of violations of this constraint: Database reports/Constraint violations/P434#Format, hourly updated report, SPARQL[0-9a-f]{8}-[0-9a-f]{4}-[4][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}”: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P434#Item P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P434#Item P31, search, SPARQL
Type “human (Q5), group of humans (Q16334295), fictional character (Q95074), group of fictional characters (Q14514600), musical ensemble (Q2088357), brand (Q431289), special purpose artist (Q59755569), recording alias (Q87189273), human whose existence is disputed (Q21070568), podcast (Q24634210), VTuber (Q55155641)”: item must contain property “instance of (P31)” with classes “human (Q5), group of humans (Q16334295), fictional character (Q95074), group of fictional characters (Q14514600), musical ensemble (Q2088357), brand (Q431289), special purpose artist (Q59755569), recording alias (Q87189273), human whose existence is disputed (Q21070568), podcast (Q24634210), VTuber (Q55155641)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Type Q5, Q16334295, Q95074, Q14514600, Q2088357, Q431289, Q59755569, Q87189273, Q21070568, Q24634210, Q55155641, SPARQL
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836), Wikimedia list article (Q13406463)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P31, hourly updated report, SPARQL Conflicts with “MusicBrainz release group ID (P436)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P436, search, SPARQL
Conflicts with “MusicBrainz work ID (P435)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P435, search, SPARQL
Conflicts with “MusicBrainz label ID (P966)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Team Shanghai Alice (Q1377647)List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P966, search, SPARQL
Conflicts with “MusicBrainz area ID (P982)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P982, search, SPARQL
Conflicts with “MusicBrainz place ID (P1004)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Hessischer Rundfunk (Q23565)List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P1004, search, SPARQL
Conflicts with “MusicBrainz instrument ID (P1330)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P1330, hourly updated report, search, SPARQL Conflicts with “MusicBrainz series ID (P1407)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P1407, search, SPARQL
Conflicts with “MusicBrainz recording ID (P4404)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#Conflicts with P4404, search, SPARQL
Qualifiers “subject named as (P1810), identifier shared with (P4070), reason for preferred rank (P7452), reason for deprecated rank (P2241), applies to name of subject (P5168), alternative name (P4970)”: this property should be used only with the listed qualifiers. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P434#allowed qualifiers, SPARQL
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||
Regexp for Constraint:Format
editA regular expression is needed for {{Constraint:Format}}. The page about the MusicBrainz Identitier should help. Allen4names (talk) 03:08, 5 May 2013 (UTC)
- Please leave at least the 36 character check until you figured it out (I removed the <!-- --> you added).-- Docu at 06:32, 5 May 2013 (UTC)
- The extended regular expression '
[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}' should work but I don't know what pattern type Ivan is using for the bot. You can either try it to see if it work or if you understand Russian (I don't) you can leave Ivan a message. Allen4names (talk) 14:34, 5 May 2013 (UTC)
- The extended regular expression '
- I avoided {} in regex, as I'm not sure if it works (in display, it looks odd).
- You could either try it with Property:P370 or repeat the elements. -- Docu at 14:40, 5 May 2013 (UTC)
- I have done a bold edit. Please wait for Wikidata:Database reports/Constraint violations/P434 to be updated to see if this needs to be reverted. Allen4names (talk) 22:20, 5 May 2013 (UTC)
Disambiguation pages
editIs this really meant to be added to the disambiguation pages also, like here: Q14155774? --Stryn (talk) 08:20, 22 July 2013 (UTC)
- Looks like musicbrainz.org's bug. User:Mineo can know more (his bot added the claim). — Ivan A. Krestinin (talk) 17:23, 22 July 2013 (UTC)
- Adding it to disambiguation pages is not intentional and most likely a mistake in the data on MusicBrainz itself - I've stopped the cronjob and will look into preventing (and probably getting a log of) those wrong links in the next few days --Mineo (talk) 21:23, 22 July 2013 (UTC)
- I've updated the bot to not do this anymore - if it still happens or you find it doing something else that doesn't seem right, please let me know --Mineo (talk) 20:14, 26 July 2013 (UTC)
Authority Control on english Wikipedia
editPlease note that in order for the MBID to be displayed on the english Wikipedia (using the Authority Control template) needs certain values in occupation (P106) (singer and others) or instance of (P31) (musical group (Q215380)). See the Authority Control Documentation for Details.
Navigation template
editThere are already six MusicBrainz properties. We need something like a Template:Music properties (see Category:Navigation templates):
Fake artists / Placeholder entries
editI noticed that (many?) producers or labels also have an artist id: For the publisher of video games Capcom (Q14428) we have MusicBrainz label ID (P966) as label/602632fb-a937-4473-a160-316ad38f9e19 but additionally P434 as artist/602632fb-a937-4473-a160-316ad38f9e19 which states:
Capcom is not an artist, but rather a Japanese video game company. This artist should not be deleted as it, like all other companies, serves as a placeholder until the correct artist(s) can be listed for an album.
For wikidata the question is now whether we should allow these reference-kind of listings or keep to try artists, organizations &c. strictly separate. -- Gymel (talk) 09:09, 7 February 2015 (UTC)
- Additionally, there are explicit "do not use" entries like Ministry of Sound:
YOU SHOULD NEVER SEE THIS BECAUSE YOU SHOULD NEVER BE ENTERING A RELEASE HERE Ministry of Sound is NOT an Artist. Entries should be entered as a "Various Artists" or "Various Artists" under the mix artist.
- And on the other hand, there are (mostly hip-hop) "collectives" like Disturbing tha Peace (Q1151996) or Underground Resistance (Q1753317) which are also music labels (as I understand, sometimes the label is an offspring of the band, in other cases labels produce releases where all of the label's artists collaborate).
- In a compeletely different vein, we do not have a clear distinction between artists and their "projects" on one hand and resulting albums on the other hand: God Help the Girl (Q3109657) might be an album by Belle and Sebastian (Q691568). However it is also true that "God Help the Girl" is a "project" by Stuart Murdoch (Q2746295), Belle and Sebastian (Q691568)'s lead artist, yielding into several recordings, a film and the album named "God Help the Girl", albeit under collaboration of (featuring) Belle and Sebastian (Q691568).
- Or: Is Tim Timebomb (Q7804396) an album by Tim Armstrong (Q503710) or a project / fictitious artist controlled by Tim Armstrong (Q503710)? This has implications as to the album's name (Tim Timebomb vs. Tim Timebomb's RockNRoll Theatre or just RockNRoll Theatre) but also to statements like which make sense only in the context of Tim Armstrong, not of Tim Timebomb.
- In all these constellations MusicBrainz does not really care about complications, the same name appears in different categories with different identifier, an approach Wikidata probably not always will be able to follow since the articles backing the items here usually deal with more aspects than just one "identity". -- Gymel (talk) 17:08, 15 February 2015 (UTC)
Items with multiple MBIDs
editThere are Wikidata items which are representation of multiple MusicBrainz Artist objects. For example in MusicBrainz there is an Artist object for a musician as a person and another Artist object for the musician's single-person project (or pseudonym). In Wikidata both the person and the project are currently represented by a single item. Example:
MusicBrainz: Tomáš Dvořák — person, some works released with this name, Floex — project, different works released with this name
Wikidata: Q3073803 — label: Floex, alias: Tomáš Dvořák — as a single item
The Wikidata item (which was merged[1]) contains both MBIDs. Unfortunately currently it is not possible to identify the MBIDs directly from the Wikidata item properties. I think one of the following should be done:
- IMHO correct: Split the item again into the two items (Floex and Tomáš Dvořák). Unfortunately there is only a single Wikipedia article for both the items. Could a single Wikipedia article have multiple Wikidata items? How to prevent a repeated merge in Wikidata?
- IMHO problematic approach: Add a qualifier to each Property:P434 (MusicBrainz artist ID and other affected properties like VIAF identifier) value specifying which of the multiple names of the item the value relates to. Is there a qualifier for this already? Property:P742 (pseudonym) fits somewhat but does not seem to be suitable for the primary name of the item (Tomáš Dvořák in our example).
There are many items with more than one Artist MBID: [2] What is the correct approach in Wikidata? --Pabouk (talk) 16:51, 4 March 2015 (UTC)
- We have many cases "one article - many items". For example: Yukina sisters (Q15270274), Olga Yukina (Q4534275), Tatiana Yukina (Q4534279). Better description prevents repeatable merges sometimes. Crosslinks like author (P50), notable work (P800) are help too. Wikidata:Do not merge can help maybe.
{{Constraint:Conflicts with}}is useful sometimes (see Property talk:P21 for example). — Ivan A. Krestinin (talk) 20:57, 4 March 2015 (UTC)
- i think both the item should be split or we should live one item that has two mbids--Shisma (talk) 08:22, 5 March 2015 (UTC)
- I think at the root of the problem is a missing item (or item tree?) for "musical project" to use in P31: We only have the "side project" side project (Q2707384) which probably is intended as much narrower in scope:
- In some genres (Techno if it still exists?, some rap subgenres) almost everything is not directly attributed to the artist but to on of his "projects"
- In at least one article about a jazz musician (? sorry, I don't recall the details) was his "main musical project" mentioned
- even for proper bands sometimes one album or even a series of albums ist considered a "project" (of that band)
- With a proper P31 the potential "project items" could be linked to the proper person item via a (one) property yet to determined (founder, responsible party, pseudonym of, ...) I'm not convinced that we really have to introduce a new one.
- Unfortunately this might also have implications for properties like "previous in series" for albums: With respect to the band the predecessor might exist, with respect to the "project" it is the first one of the "series"... -- Gymel (talk) 09:06, 5 March 2015 (UTC)
Single value constraint exceptions
editI've added a generated list of exceptions for the single value constraint. These are all the cases where MusicBrainz has separate entries for a legal name and a performance name which are linked together and both have the same Wikidata link. Wikipedia normally has one article for a person which talks about all of the names they use (see above), so these are cases where exceptions would currently be expected.
The SQL query I used against the MusicBrainz database to make the list is:
select array_to_string(array_agg(distinct regexp_replace(url0.url, E'http://www.wikidata.org/wiki/Q([0-9]+)', E'{{Q|\\1}}')), ', ') from l_artist_artist laa join link l on l.id=laa.link join link_type lt on lt.id=l.link_type join l_artist_url lau0 on lau0.entity0=laa.entity0 join l_artist_url lau1 on lau1.entity0=laa.entity1 join url url0 on url0.id=lau0.entity1 join url url1 on url1.id=lau1.entity1 where lt.name = 'is person' and url0.url ~ 'wikidata.org' and url0.url=url1.url;
MBID redirects
editAccording to MusicBrainz docs: ”An entity can have more than one MBID. When an entity is merged into another, its MBIDs redirect to the other entity.” We should only link to the actual MBID, not the redirects, correct? I was thinking of cleaning up Wikidata:Database reports/Constraint violations/P434, but want to be sure before moving further. For example Tupac Shakur (Q6107) had a total of five MBIDs, out of which three were redirects. (You can tell by clicking the artist title or one of the tabs, all redirect to 382f1005-e9ab-4684-afd4-0bdae4ee37f2.) –Kooma (talk) 09:58, 29 December 2016 (UTC)
MusicBrainz LOD?
edit
WikiProject Music has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Notified participants of WikiProject Authority control WikiProject Cultural heritage has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
In 2015 Laboramus added "URI used in RDF" as "http://musicbrainz.org/$1/artist" (see this revision). Unfortunately this doesn't resolve, eg:
- https://musicbrainz.org/artist/44b16e44-da77-4580-b851-0d765904573e: web page for Rachmaninov, is ok
- https://musicbrainz.org/44b16e44-da77-4580-b851-0d765904573e/artist: claimed RDF for Rachmaninov, doesn't resolve
Does anyone know the correct MusicBrainz LOD/RDF URL patterns? --Vladimir Alexiev (talk) 08:28, 23 June 2017 (UTC)
There is https://wiki.musicbrainz.org/LinkedBrainz but it's very old (2011), says "experimental", and the SPARQL endpoint https://wiki.musicbrainz.org/LinkedBrainz is down --Vladimir Alexiev (talk) 08:43, 23 June 2017 (UTC)
Same value in other MusicBrainz properties
editThere are currently some on Wikidata:Database reports/uuid. ------ Jura 08:41, 9 November 2019 (UTC)