Property talk:P9780

Documentation

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

The Women's Print History Project person ID
numerical identifier for a person in the The Women’s Print History Project database

Applicable "stated in" value	The Women’s Print History Project (Q107689125)
Data type	External identifier
Domain	human (Q5)
Allowed values	[1-9][0-9]*
Example	Catherine Hubback (Q2484790) → 211 Dorothy Ripley (Q3037183) → 3078 Maria W. Stewart (Q13560246) → 4667
Source	https://womensprinthistoryproject.com/person/
Formatter URL	https://womensprinthistoryproject.com/person/$1
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Mix'n'match (Report) Database reports/Constraint violations/P9780 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 1,721 Main statement 1,689 out of 3,534 (48% complete) 98.1% of uses Qualifier 3 0.2% of uses Reference 29 1.7% of uses
Search for values

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

Format “[1-9][0-9]*”: 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/P9780#Format, SPARQL

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/P9780#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

List of violations of this constraint: Database reports/Constraint violations/P9780#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)

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/P9780#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/P9780#Scope, SPARQL

Type “human (Q5)”: item must contain property “instance of (P31)” with classes “human (Q5)” 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/P9780#Type Q5, SPARQL

Item “sex or gender (P21)”: Items with this property should also have “sex or gender (P21)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P9780#Item P21, hourly updated report, search, SPARQL

P21 constraint

Hi,

I'm wondering if the constraint item-requires-statement constraint (Q21503247)sex or gender (P21)female (Q6581072) should be maintained. Presently there is 769 violations, plus the 3 exceptions, out of 1646 uses. There is still roughly 1800 items to match, among them more violations are to be expected. I don't thing that stating all the exceptions is a viable way. Pinging participant in the proposal and others who worked on the constraint : @Gamaliel, Epìdosis, Pamputt, Dcflyer, Andre Engels, Eihel: --Jahl de Vautban (talk) 08:08, 15 January 2022 (UTC)

@Jahl de Vautban: I agree of course; I transformed the constraint into simply requiring sex or gender (P21) without specified value. It seems quite clear that the values can be not only female (Q6581072), as you showed. --Epìdosis 08:15, 15 January 2022 (UTC)

Agree, seems reasonable. Gamaliel (talk) 17:19, 15 January 2022 (UTC)