Property talk:P9107
Jump to navigation
Jump to search
![]() | This property was previously considered for deletion but kept. |
Documentation
number of vaccinations
number of people vaccinated, qualify with "point in time" (P585)
number of people vaccinated, qualify with "point in time" (P585)
Data type | Quantity | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Allowed values | 0 ≤ 𝓧 ≤ not applicable | |||||||||
Allowed units | not applicable | |||||||||
Example | COVID-19 pandemic in France (Q83873593) → 510 COVID-19 pandemic in the United States (Q83873577) → 4,660,000 | |||||||||
Lists |
| |||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
|
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “novalue”: value unit must be one of listed. (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/P9107#Units
Integer: values should be integers (ie. they shouldn't have a fractional part) (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/P9107#integer, SPARQL
Citation needed: the property must have at least one reference (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/P9107#citation needed
Required qualifier “point in time (P585)”: this property should be used with the listed qualifier. (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/P9107#mandatory qualifier, 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/P9107#Scope, 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/P9107#Entity types
Range from “0” to “+∞”: values should be in the range from “0” to “+∞”. (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/P9107#Range
What in earth?
[edit]The property description does not restrict the number to any certain vaccine. Does the property include anybody vaccinated since 1796? –LPfi (talk) 23:55, 2 February 2021 (UTC)
- I.e. when used for a country or a city. And does the number include people vaccinated there who have moved away or people vaccinated elsewhere? I think the property should have such specifications at least suggested. –LPfi (talk) 23:59, 2 February 2021 (UTC)
- Not the original proposer of the property, but I think it's meant to be more for items about specific notable pandemic/outbreak events, not for the entire history of a disease. So only vaccinations issued in response to such an event, and within the time scope of that event, should be considered, I believe. It also probably makes sense that it applies to the number of vaccinations issued within the area of concern, since that's the most likely statistic to be published by the local health authority. But I guess it'd help if this was explicitly mentioned in the property usage instructions? --Btcprox (talk) 04:53, 17 February 2021 (UTC)
Categories:
- Properties for deletion
- All Properties
- Properties with quantity-datatype
- Properties used on 100+ items
- Properties with units constraints
- Properties with integer constraints
- Properties with citation needed constraints
- Properties with required qualifiers constraints
- Properties with scope constraints
- Properties with entity type constraints
- Properties with range constraints