Property talk:P136
Documentation
creative work's genre or an artist's field of work (P101). Use main subject (P921) to relate creative works to their topic
List of violations of this constraint: Database reports/Constraint violations/P136#Type Q386724, Q17489659, Q11424, Q15416, Q378427, Q5, Q215380, Q18127, Q2088357, Q1141470, Q10648343, Q476300, Q15116915, Q1047299, Q5519943, Q742421, Q16686448, Q11410, Q16334295, Q28640, Q12737077, Q24634210, Q7725634, Q483394, Q868557, Q1364556, Q571, Q1631107, Q55594385, Q4801521, Q1991869, Q223393, Q110912290, Q589183, Q6806507, Q10688145, Q634509, Q20203727, Q7191193, Q667276, Q2936887, Q7523718, Q60550455, Q47433, Q41207, Q855973, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P136#Value type Q483394, Q11921029, Q1406161, Q1792644, Q17155032, Q17955, Q3030248, Q53001749, Q862597, Q1499017, Q223393, Q188451, Q1991869, Q6806507, Q4263830, Q107356781, Q317623, Q56055944, Q64138195, Q108676140, Q128093, Q82753, Q110562117, Q10428845, Q126125231, Q1078597, Q47433, Q37930, Q25679497, Q109551565, Q735, Q3153714, Q104822033, Q41207, Q855973, Q104624828, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P136#Conflicts with P31, SPARQL
if [item A] has this property (genre (P136)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#Contemporary, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P136#Entity types
List of violations of this constraint: Database reports/Constraint violations/P136#Scope, SPARQL
Replacement property:
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: movement (P135)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: fabrication method (P2079)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: educational video game (Q1224999) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: intended public (P2360)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: form of creative work (P7937)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: has use (P366)
Replacement values: stage and screen (Q61340552) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: has characteristic (P1552)
Replacement values: Christmas music (Q1443316) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: form of creative work (P7937)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: form of creative work (P7937)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: game mechanics (P4151)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P136#Conflicts with P31, search, SPARQL
Replacement property:
Replacement values: black-and-white photography (Q3381576) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: output device (P5196)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: instance of (P31)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: form of creative work (P7937)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: has characteristic (P1552)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: ASMR (Q108680155) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: hip hop music (Q11401) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: Dixieland jazz (Q906647) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: big band music (Q105756581) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: form of creative work (P7937)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property:
Replacement values: drama (Q25372) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: form of creative work (P7937)
Replacement values: poetry (Q482) (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Replacement property: occupation (P106)
Replacement values: (Help)
List of violations of this constraint: Database reports/Constraint violations/P136#none of, SPARQL
Value josei (Q503106) will be automatically replaced to value josei (Q503106) and moved to intended public (P2360) property. Testing: TODO list |
Value shōjo (Q242492) will be automatically replaced to value shōjo (Q242492) and moved to intended public (P2360) property. Testing: TODO list |
Value children's anime and manga (Q478804) will be automatically replaced to value children's anime and manga (Q478804) and moved to intended public (P2360) property. Testing: TODO list |
Value shōnen (Q231302) will be automatically replaced to value shōnen (Q231302) and moved to intended public (P2360) property. Testing: TODO list |
Value seinen (Q237338) will be automatically replaced to value seinen (Q237338) and moved to intended public (P2360) property. Testing: TODO list |
Value autonomous sensory meridian response (Q4826866) will be automatically replaced to value ASMR (Q108680155). Testing: TODO list |
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
|
Why only literar? Why nlot mus*ical or film too? JAn Dudík (talk) 12:08, 22 February 2013 (UTC)
- Property added without discussion. I suspect it was taken from en:Template:Infobox writer. en:Template:Infobox film has no genre. --Kolja21 (talk) 19:09, 22 February 2013 (UTC)
- w:cs:Šablona:Infobox film have genre. JAn Dudík (talk) 19:43, 22 February 2013 (UTC)
SupportSo let's change "literary genre" to "genre".--Kolja21 (talk) 20:12, 22 February 2013 (UTC)- Can we use "literary movement" (P135) in a broader sense too? --Kolja21 (talk) 20:14, 22 February 2013 (UTC)
- I don't understand why you want to make this property less specific. It concerns somethings well defined which has nothing to do with music. If you want to have one related to music or movies, why don't you create another one like "musical genre"? --Ayack (talk) 13:42, 23 February 2013 (UTC)
- Can we use "literary movement" (P135) in a broader sense too? --Kolja21 (talk) 20:14, 22 February 2013 (UTC)
- I am not sure, if is the best idea to have
- literary genre
- musical genre
- theatre genre
- film genre
- ...
- In some languages they might have smae name, some genres are common for theatre and literature or film...
- JAn Dudík (talk) 17:35, 23 February 2013 (UTC)
- Now that this property has been created without discussion... I commented at WP:PP earlier today that I see no need to separate genre properties. Do not store excess information in properties, is what I believe. "Literary" or "musical" or "film" adjectives do not add information: you get the information on the type of creative work from other properties of the item. I boldly changed the (English) name to "genre", but I don't mind being reverted. Espeso (talk) 07:06, 24 February 2013 (UTC)
- I´ve changed the german version and moved the property at "Wikidata:List of properties" to "Works". Since it is for Persons too, maybe we should have a different description? "genre of a creative work or person" --Goldzahn (talk) 08:10, 24 February 2013 (UTC) At de it is now something like "genre of a creative work or a genre a person is connected to". Well, my English is limited. --Goldzahn (talk) 11:22, 24 February 2013 (UTC)
- I see. I wasn't thinking of people... hmm... yes definitely amend the description. "Genre of a person" doesn't make complete sense in English at least: could it be "genre of a creative work or creator's oeuvre?" Just a suggestion. There is no getting around it, this property will be used very loosely (it already has been) because "genre" has a very loose definition. If the property is going to exist at all there is no realistic way to limit how it gets used, other than a sourcing policy. Espeso (talk) 08:26, 24 February 2013 (UTC)
I was just clicking through on some genre links on WP, in film infoboxes and they were linked to articles which seemed to be literary genres and not film genres. So, I think this property should be restricted to literature for the time being, otherwise it may get messy. Danrok (talk) 17:18, 24 February 2013 (UTC)
- Thanks for this info. --Kolja21 (talk) 23:19, 24 February 2013 (UTC)
- I don't see your point Danrok. Genre designations are extremely nebulous, and your example doesn't give anything specific--other than to suggest that a film genre can't be a literary genre, or vice versa, which is not true. People can enter poor values whether or not its "genre" or "film genre" and "literary genre". As I said before, all this does is put information in the property name that belongs in property values ("type of creative work"). Espeso (talk) 23:29, 24 February 2013 (UTC)
- The point is that some items will be incorrectly connected with articles which describe something else. I'm not debating the use of the word genre, just pointing out that we risk creating nonsense. Danrok (talk) 20:50, 2 March 2013 (UTC)
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Video game genres
editLots of talks about film vs literature vs music... How about Video game genres? Is this property for that too? --09:35, 25 February 2013 (UTC), Utar (talk)
- I would say yes. see en:List of genres --Goldzahn (talk) 12:43, 25 February 2013 (UTC)
- OK, thanks. I haven't met that article before. --13:02, 25 February 2013 (UTC), Utar (talk)
- However, video games and software are treated as products, and the entity type term is used. But, does it matter? Danrok (talk) 20:47, 2 March 2013 (UTC)
- OK, thanks. I haven't met that article before. --13:02, 25 February 2013 (UTC), Utar (talk)
- I think it might be more useful to have another property for video game genre because these genres describe the way the game works, and not genre in the normal sense. A first-person shooter set in WW2 would be video game genre=first-person shooter, but the genre in a literary sense is war. There again, perhaps both of these can be specified in the same property. Danrok (talk) 23:47, 2 March 2013 (UTC)
- +1. BTW: "War" is not a genre it's a subject. You can write in different genres (satire, tragedy, romance etc.) about war. --Kolja21 (talk) 01:04, 3 March 2013 (UTC)
- Good point. "Video game genre" is a misnomer, even if it is widely used. Danrok (talk) 02:55, 3 March 2013 (UTC)
- A better name: "type of video game"? --Kolja21 (talk) 04:23, 3 March 2013 (UTC)
- Good point. "Video game genre" is a misnomer, even if it is widely used. Danrok (talk) 02:55, 3 March 2013 (UTC)
- +1. BTW: "War" is not a genre it's a subject. You can write in different genres (satire, tragedy, romance etc.) about war. --Kolja21 (talk) 01:04, 3 March 2013 (UTC)
- By "normal" you mean "literary". Its use, even if it is a "misnomer" is also "normal".
- That said, I would say you are incorrect. The reason that "genre" has arisen as a term for video games is that each type of video game genre tells a story in a different fashion (or, as some genres are, completely exclusive stories!). I don't see value adding another property here. --Izno (talk) 14:02, 15 March 2013 (UTC)
It's ok when I read that "War" is not a genre, about video games. But can we use "genre" for telling that a game is a "point and click" genre? There is also "game mode" property (P404) but it seems that for "point and click" it's not the correct property also (you can see history of Q2573145). Is there any other property created for video games? Jeriby (talk) 14:11, 20 July 2013 (UTC)
Valid genres
editWhich is the list of valid genres? Wikidata:List of properties used to list "novel" as a genre, but it's a format just like short story and feature film. How about doing a list of genres (perhaps by populating the corresponding items with the instance of property). --NaBUru38 (talk) 20:39, 27 March 2013 (UTC)
- Yes, instance of genre makes sense, though there is also film genre and literary genre, both now subclasses of genre. At some point, hopefully we'll be able to query for a recursive list of genres. Superm401 - Talk 04:02, 3 April 2013 (UTC)
- here is a simple query for retrieval of all genres. --Jkatzwinkel (talk) 07:02, 11 January 2018 (UTC)
Use for works?
editIt says "in which an artist works". Can we use this for the actual works (books, films, etc.) too? If not, we will have to create a separate property. Superm401 - Talk 03:57, 3 April 2013 (UTC)
- Or: Use for artists? The current constraints define the property to be used on work items. The current descriptions, "genre of a creative work or genre in which an artist works" define it to be used on artist items, too. One of the two has to be changed to resolve the conflict.
Imho it isn't a good idea to use this one property on two completely disjunct classes of items. I propose not to use it on artist items!(seems to work meanwhile) --Marsupium (talk) 10:25, 20 July 2014 (UTC), Marsupium (talk) 10:01, 7 October 2017 (UTC) (PS: If we agree on this we have to remove the statements from artist items and consider another possibility to model the genre an artist has worked in.)- Done Has been solved. --Marsupium (talk) 10:01, 7 October 2017 (UTC)
- @Superm401, Marsupium: I'm confused, where did this land? Q18844224#P136 is giving an error currently. Arlo Barnes (talk) 04:29, 22 June 2020 (UTC)
- @Arlo Barnes: I think the property was intended to be used on instances of humans or works, not classes. If desired profession (Q28640) has to be added as class (P2308) for the subject type constraint (Q21503250). --Marsupium (talk) 21:01, 24 June 2020 (UTC)
- @Superm401, Marsupium: I'm confused, where did this land? Q18844224#P136 is giving an error currently. Arlo Barnes (talk) 04:29, 22 June 2020 (UTC)
- Done Has been solved. --Marsupium (talk) 10:01, 7 October 2017 (UTC)
genre (P136) = film adaptation (Q1257444) or based on (P144) = item ?
editd1g (talk) 15:09, 7 January 2017 (UTC)
- Both? Infovarius (talk) 08:09, 21 March 2017 (UTC)
- Maybe I am misunderstanding, in English I would have said neither. Film adaptation is not a genre. Based on is not a genre either. — billinghurst sDrewth 12:04, 21 March 2017 (UTC)
- Obviously the second part of the question doesn't refer to "genre" at all. If some film is an adaptation, it can use P144. --Infovarius (talk) 19:09, 22 March 2017 (UTC)
- Maybe I am misunderstanding, in English I would have said neither. Film adaptation is not a genre. Based on is not a genre either. — billinghurst sDrewth 12:04, 21 March 2017 (UTC)
P31 vs P136
editI suppose in many cases (films, sculpture) we can use many values (like animation film, statue...) as classes (in P31) so the P136 with the same values would be redundant. Only necessary usecases for P136 I see for people and organisations. Any opinions? --Infovarius (talk) 08:09, 21 March 2017 (UTC)
- I use it for published works, or editions of published works. Published works can have many components. Similarly, genres is transportable across many produced formats. Are you suggesting that we should have horror books, horror short stories, horror movies, horror ... Wouldn't you just have work type and use a genre? — billinghurst sDrewth 12:08, 21 March 2017 (UTC)
- Briefly: I agree with "horror" as a genre. But I don't agree with "animation film" as a genre. And neither "statue". --Infovarius (talk) 19:11, 22 March 2017 (UTC)
- @Infovarius: I agree. They should fall through the value-type constraint (Q21510865) anyway, right? --Marsupium (talk) 09:48, 7 October 2017 (UTC)
- @Infovarius: In cases such as equestrian statue of Elizabeth II (Q58361479) people are still adding P136 + P31=sculpture (Q860861) to items which allready have P31=equestrian statue (Q659396). I also think that's redundant. People may have trouble understanding that one is a subclass of the other though. Is there a way we can make it more clear how subclasses work? --Hjart (talk) 16:17, 18 February 2019 (UTC)
- And as for a statue - ideally this should also be decided by the architecture project, which is not on wikidata yet. And accordingly we should just establish a consensus on just this case somewhere in the discussions. Technically it is now labelled a genre, and hence it is p136. If this branch is going to be subclassed independent (so that types of statues can be placed in genres), then it should be done in a mass way, with a constraint and in the end probably replacing: sculture = genre of sculture with p31 = type of architecture work. Solidest (talk) 16:39, 12 September 2024 (UTC)
- @Infovarius: In cases such as equestrian statue of Elizabeth II (Q58361479) people are still adding P136 + P31=sculpture (Q860861) to items which allready have P31=equestrian statue (Q659396). I also think that's redundant. People may have trouble understanding that one is a subclass of the other though. Is there a way we can make it more clear how subclasses work? --Hjart (talk) 16:17, 18 February 2019 (UTC)
- @Infovarius: I agree. They should fall through the value-type constraint (Q21510865) anyway, right? --Marsupium (talk) 09:48, 7 October 2017 (UTC)
- Briefly: I agree with "horror" as a genre. But I don't agree with "animation film" as a genre. And neither "statue". --Infovarius (talk) 19:11, 22 March 2017 (UTC)
- I agree that these items are not not strictly genres in the classical sense (well maybe except of "silent film", if you mean the cinematic term and not just technical "film without sound" sense). But moving anything you don't think is a genre to p31 is clearly not the way to go. Cluttering p31 leads to even more problems, causing items to get lost both in tools like Mix'n'match and just degrades the quality of queries, complicating simple output (not to mention the inconsistency of such fills). This is why individual projects are developing schemes for populating properties for work types, like the film one. And subsequently also perform clean ups to reduce p31 quantities, like in video game project recently. For that matter, I'd even rather keep using these items in p136 than move them to p31. But it's more complicated with "animated film", since it's been used in p31 for a long time and everyone seems to be used to it. And also I don't really like that such items as animated television film (Q98807719) or animated television short film (Q123995798) are created and used in p31, which also only leads to blurring of the scheme, rather than bringing something useful. And I'm not sure what neat solution should be used here. genre = rules of narrative or aesthetics within the work; form of creative work = mostly describes the structure or format of the work (size or duration). And we're left with a blank spot when we can't use "type of work by the type of production" (like the whole branch animated film by fabrication method (Q124026596) or black-and-white cinema (Q10282327)), for lack of others. It even seems to me that genre (P136) is still the most favoured option we have. The other alternative is has characteristic (P1552) or ideally a new property, which is difficult to imagine at this point. Solidest (talk) 16:25, 12 September 2024 (UTC)
Need fix to constraints to stop this being directly applied to people
editHi. Can someone skilled in the art of constraints please look to modify the constraints here. At the moment, I am seeing this constraint being directly applied to a person, rather than as a qualifier to the field of work or occupation that they are undertaking. A person not be able to be labelled as "genre -> opera". Thanks. — billinghurst sDrewth 23:11, 7 November 2017 (UTC)
- From a technical point of view, you'd just need to remove "Q5" from the type constraint.
--- Jura 06:49, 8 November 2017 (UTC) - A good first step might also be to change the description so that it doesn't promote applying this property to people. Also, see #Use for works?, above. Currently, 85,950 of the 611,374 uses of this property are on items for humans. --Yair rand (talk) 14:29, 23 November 2017 (UTC)
- Support these changes. - PKM (talk) 21:56, 25 November 2017 (UTC)
- I'd also suggest adding an example with "person" <field of work> "genre". Perhaps fix Arthur C. Clarke (Q47087)? Happy to do that when we're ready. - PKM (talk) 22:01, 25 November 2017 (UTC)
Music festivals
editWhy can't music (or other art) festivals have a genre? Are, say, folk or rock or baroque or, for all I care, tintinnabuli music festivals totally unheard of? --Ehitaja (talk) 21:03, 17 October 2018 (UTC)
Bands and musical groups
editI'm noticing a lot of items about choirs and bands have the "genre" property - indicating the style of music they are known for (e.g. U2 (Q396) lists rock music (Q11399) as their "genre". The item for Prince (Q7542) has no fewer than 10 "genre" statements. However, this is a constraint violation as the property is only supposed to be used for artistic works - not the artists themselves. What should be done? Should this property allow artistic acts (e.g. bands) to have a "genre", or is there a different property that could be used, to indicate the kind of music that this artist performs? Wittylama (talk) 10:51, 26 October 2018 (UTC)
- Wittylama: I agree that it seems weird to apply genre to people and groups directly — to me, it would make the most sense as a qualifier for occupation, in the case of humans. For bands, I'm less clear on what makes the most sense. I note that User:Premeditated has now added human and band to the constraints, which matches how it's being used pretty widely.--Ragesoss (talk) 18:00, 16 November 2018 (UTC)
- @Ragesoss, Wittylama: I understand your frustration, but I haven't found any standard way of handling this, other then putting genre directly to human which are used almost everywhere. I have made a test site with a suggestion on how we should organize genre under field of work (P101). Example. - Premeditated (talk) 11:23, 1 December 2018 (UTC)
Art style
editIf both art movement (Q968159) and musical style (Q11921029) are valid values for this property, can we add art style (Q1792644) as well? We have no other property to indicate "art style". - PKM (talk) 21:13, 9 July 2019 (UTC)
- Adding as there are no objections here or at Wikidata talk:WikiProject Visual arts. - PKM (talk) 21:16, 17 July 2019 (UTC)
False-positive contemporary constraint
editHi,
I've got this false-positive violation of the contemporary constraint:
- because of and
What is the best way to solve this?
My understanding is: end time (P582) is a bit strange on genre items (French baroque music (Q3328590) and Colossal Baroque (Q5149108) also have a end time (P582), all three added by Spinster). that said, I understand the idea: it's the point where this genre stop being "productive". Maybe there is a better property for this? And an artist can still play a genre even if it is no more "productive". So maybe the "contemporary" constraint is wrong, it's doesn't need to be at the same time, only not before the creation of the genre.
Pinging top 5 users of genre (P136): @Ghuron, Danrok, Jura1, Thierry Caro, Simon Villeneuve: (ref)
Cdlt, VIGNERON (talk) 15:51, 11 September 2019 (UTC)
- Like you, I think that the "contemporary" constraint is possibly wrong here. Like you said, just keep the "before the creation of the genre" part.
I also understand the "productive" idea, but I'm not sure that P582 is a good property to express that. Mais malheureusement, j'ai rien d'autre à proposer. Simon Villeneuve (talk) 19:04, 11 September 2019 (UTC)
- Maybe it's better to ping users who actually added this genre. I have no recollection of doing so. --- Jura 05:46, 12 September 2019 (UTC)
- Also seeing this. It should just be "before the creation of the genre". --A3nm (talk) 15:54, 27 April 2020 (UTC)
part of classes
editCan you helpo me with Q79382428 - there is blinking off de_problem:
- Eigenschaftseinschränkung „Wertetyp“Hilfe Diskussion
- Werte der Aussagen Genre sollten Instanzen von einer der folgenden Klassen sein (oder von einer ihrer Unterklassen), aber Sage hat sie derzeit nicht:
- Genre
- Musikstil
- Sujet
- Kunstströmung
- Kunststil
- Software-Typ
- Kritik
Thank you, Conny (talk) 08:13, 22 December 2019 (UTC).
art movement (Q968159) is obviously an issue and leads to confusion with movement (P135) which is the appropriate property for those items. There were massive edits on genre (P136) with art movement (Q968159) items in duplicate with movement (P135). This has a significant and negative impact. So art movement (Q968159) has been removed from the class (P2308) of value-type constraint (Q21510865). --Shonagon (talk) 17:00, 12 October 2020 (UTC)
How many values should be listed for genre?
editThere was a recent content dispute between UWashPrincipalCataloger and MovieFex. When a genre value gets added, should superclasses of the newly added genre be removed or kept? If some should be kept, what standards should be used?
Notified participants of WikiProject Movies ChristianKl ❪✉❫ 02:59, 16 December 2020 (UTC)
- I'd say, It should be kept if it has a source. You could set the more precise value to preferred -- Shisma (talk) 08:21, 16 December 2020 (UTC)
- as a bonus we could quality the statement with reason for preferred rank (P7452) ⭢ most precise value (Q71536040) --Shisma (talk) 09:00, 16 December 2020 (UTC)
- This solution only works when there is choice between just two genre values. Consider a transgender romantic comedy. There are three specific genres for this: transgender films, romance films, and comedy films. If the item had both transgender film and LGBT-related film as well as romance film and comedy film, how would you be able to mark transgender film as preferred over LGBT-related film, the superclass? Would you mark transgender film, romance film, and comedy film as preferred? If you only had transgender film and LGBT-related film recorded, then marking one as preferred is clear. But once you have more than two, it becomes unclear what is preferred over others. UWashPrincipalCataloger (talk) 16:13, 17 December 2020 (UTC)
- In your example all values should be preferred except for LGBT-related because it is a superclass. whats the problem with multiple preferred values? --Shisma (talk) 18:34, 17 December 2020 (UTC)
- Given that Wikidata includes multiple references, it's likely to happen that we have superclasses and subclasses. Also, some references might just focus on one aspect of a work and not necessarily attempt to cover and describe a work in all its facets. --- Jura 18:46, 17 December 2020 (UTC)
Removed format constraint
editI removed the format constraint that was recently put on this. A format constraint can only be used to restrict a text type value, not the label of a link type value in some language. - Andre Engels (talk) 19:07, 3 May 2023 (UTC)
- I reverted back to the version before the odd edits by user:Duckmather. Multichill (talk) 10:45, 7 May 2023 (UTC)
- @Andre Engels, Multichill: I added the website title extract pattern regexes merely because there was a suggestion constraint that anything with a URL match pattern statement should also have a website title extract pattern qualifier. (I added the format constraint statement for the same reason.) Duckmather (talk) 22:15, 7 May 2023 (UTC); amended 22:19, 7 May 2023 (UTC)
Podcasts without genre
editIt seems to me that part of find a podcast (listed in wikidata) that you like is knowing the genre
This is a link to the wikidata query servive that'll list those that do not have a genre (but do have an apple podcast id as a potential source of genre)