Property talk:P9102

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

CineFanRo person ID
identifier for a person on the cinefan.ro site

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “human (Q5)”: item must contain property “instance of (P31)” with classes “human (Q5)” or their subclasses (defined using subclass of (P279)). (Help)

List of violations of this constraint: Database reports/Constraint violations/P9102#Type Q5, hourly updated report, 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/P9102#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/P9102#Single value, SPARQL

Format “[1-9]\d{0,5}(-[a-z]+)*”: 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/P9102#Format, SPARQL

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P9102#Scope, hourly updated report, SPARQL

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/P9102#Entity types

Item “occupation (P106): actor (Q33999), film actor (Q10800557), television actor (Q10798782), director (Q3455803), art director (Q706364), film director (Q2526255), film or television director (Q6102247), film screenwriter (Q69423232), film editor (Q7042855), film producer (Q3282637), filmmaker (Q1414443), cinematographer (Q222344), costume designer (Q1323191), production designer (Q2962070), stage actor (Q2259451)”: Items with this property should also have “occupation (P106): actor (Q33999), film actor (Q10800557), television actor (Q10798782), director (Q3455803), art director (Q706364), film director (Q2526255), film or television director (Q6102247), film screenwriter (Q69423232), film editor (Q7042855), film producer (Q3282637), filmmaker (Q1414443), cinematographer (Q222344), costume designer (Q1323191), production designer (Q2962070), stage actor (Q2259451)”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Victor Hugo (Q535)
List of violations of this constraint: Database reports/Constraint violations/P9102#Item P106

Discussion

Regular expression

What is the format we want to push? Do we want to force to use identifier such as "9144-nae-caranfil" or do we want to mix figures only and figures + letters? Both cases are possible but I would prefer the second because these identifiers works always and I think it is better to have uniform identifiers. That's said I will not use this property so I let you decide. Pamputt (talk) 21:57, 1 February 2021 (UTC)

Apparently, the site is shifting to well-working figures. For now, the older entries work fine this way. - Coagulans (talk) 17:54, 2 February 2021 (UTC)