Property talk:P58

From Wikidata
Jump to navigation Jump to search

Documentation

screenwriter
person(s) who wrote the script for subject item
Descriptionauthor(s) of the screenplay or script for this work - screenwriter (Q28389)
Representsscreenwriter (Q28389), film screenwriter (Q69423232)
Data typeItem
Domain
According to this template: work (Q386724)
According to statements in the property:
work (Q386724)
When possible, data should only be stored as statements
Allowed valuesPersons that have occupation (P106) = screenwriter (Q28389) (note: this should be moved to the property statements)
ExampleTitanic (Q44578)James Cameron (Q42574)
The Witness (Q472007)Péter Bacsó (Q367265)
Asterix the Gaul (Q618719)René Goscinny (Q192214)
Tracking: sameno label (Q42533392)
Tracking: usageCategory:Pages using Wikidata property P58 (Q23908978)
See alsofilm script (P3816), adapted by (P5202)
Lists
Proposal discussion[not applicable Proposal discussion]
Current uses
Total225,412distinct valuesratio
Main statement224,92999.8% of uses61,1213.7
Qualifier4700.2% of uses
Reference13<0.1% of uses
Search for values
[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/P58#Entity types
Property “sex or gender (P21)” declared by target items of “screenwriter (P58): If [item A] has this property with value [item B], [item B] is required to have property “sex or gender (P21)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: no label (Q109772286)
List of violations of this constraint: Database reports/Constraint violations/P58#Target required claim P21, SPARQL, SPARQL (by value)
Type “work (Q386724): item must contain property “instance of (P31)” with classes “work (Q386724)” 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/P58#Type Q386724, SPARQL
Conflicts with “instance of (P31): musical work/composition (Q105543609): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P58#Conflicts with P31, hourly updated report, search, SPARQL
Scope is as main value (Q54828448): 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/P58#Scope, SPARQL
Property “occupation (P106)” declared by target items of “screenwriter (P58): If [item A] has this property with value [item B], [item B] is required to have property “occupation (P106)”. (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/P58#Target required claim P106, SPARQL, SPARQL (by value)
Property “instance of (P31): human (Q5), collective pseudonym (Q16017119), duo (Q10648343), sibling duo (Q14073567)” declared by target items of “screenwriter (P58): If [item A] has this property with value [item B], [item B] is required to have property “instance of (P31): human (Q5), collective pseudonym (Q16017119), duo (Q10648343), sibling duo (Q14073567)”. (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/P58#Target required claim P31, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Qualifiers and qualifier values

[edit]
SELECT ?qual ?qualLabel ?pq_obj ?pq_objLabel ?count 
WHERE 
{
  {
    SELECT ?qual ?pq_obj (COUNT(DISTINCT ?item) AS ?count) WHERE {
         hint:Query hint:optimizer "None" .
         ?item p:P58 ?statement .
         ?statement ?pq_qual ?pq_obj .
         ?qual wikibase:qualifier ?pq_qual .
         FILTER( ?pq_qual NOT IN (  pq:P1545 , pq:P580 , pq:P582 ) )
         FILTER( ?pq_obj NOT IN (  "Guido Nolitta" ) )
    }  GROUP BY ?qual ?pq_obj
  } .

  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
ORDER BY DESC(?count) ASC(?qualLabel)

Try it!

Above of a query to view some of the current qualifiers and their values. It could use some cleanup. I was looking for a good way to specify "story by" and "teleplay by". --- Jura 08:35, 25 November 2018 (UTC)[reply]

Default English label

[edit]

As this property isn’t only used for films and tv, shouldn’t “Scriptwriter” (or another) be the default label in English? “Screenwriter” being one special case that can be first in “also known as”. On comics entities for instances, the appearance of a “Screenwriter” is very weird. Nclm (talk) 12:37, 13 February 2024 (UTC)[reply]

There's also an ongoing discussion in the VG project to change the label to "scenarist", see Wikidata talk:WikiProject Video games#author (P50) vs screenwriter (P58). Because due to the current name, enwiki has linked the value of "writer" in VG infobox with author (P50) instead of this property, and this is rather incorrect in many cases. I think I prefer the "scenarist" variant, but wouldn't mind the "scriptwriter" option either. Solidest (talk) 14:12, 29 March 2024 (UTC)[reply]
Thanks for raising this Nclm. I would personally go for scenarist (it’s already the French label for exmaple) as it sounds to me the closest to the intent of the property. Jean-Fred (talk) 16:19, 29 March 2024 (UTC)[reply]