Property talk:P1603

From Wikidata
Jump to navigation Jump to search

Documentation

number of cases
cumulative number of confirmed, probable and suspected occurrences
Descriptionthe cumulative number of confirmed, probable and suspected occurrences
Representsnumber of infected (Q23696805)
Data typeQuantity
Template parameterNone. Values often shoehorned into 'casualties1' and 'casualties2' in Template:Infobox event
Domaindisease outbreak (Q3241045) (note: this should be moved to the property statements)
Allowed values
According to this template: Non-negative integers
According to statements in the property:
0 ≤ 𝓧 ≤ 10,000,000,000
When possible, data should only be stored as statements
Allowed unitsnot applicable
Example
According to this template: Western African Ebola virus epidemic (Q15989108) number of cases 13,703 point in time (P585) 25. October 2014
According to statements in the property:
Western African Ebola virus epidemic (Q15989108) → 13,703
COVID-19 pandemic (Q81068910) → 563,421,090
When possible, data should only be stored as statements
SourceHealth institutes, e.g. World Health Organization, US Centers for Disease Control and Prevention (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usageCategory:Pages using Wikidata property P1603 (Q87270736)
See alsoprevalence (P1193), incidence (P2844), number of recoveries (P8010), number of medical tests (P8011), number of deaths (P1120), number of hospitalized cases (P8049), tabular case data (P8204), number confirmed (P1674), number probable (P1675), number suspected (P1676)
Lists
Proposal discussionProposal discussion
Current uses
Total166,198
Main statement166,00999.9% of uses
Qualifier1890.1% of 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)
List of violations of this constraint: Database reports/Constraint violations/P1603#Units, hourly updated report
Range from “0” to “10000000000”: values should be in the range from “0” to “10000000000”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1603#Range, hourly updated report
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/P1603#integer, 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/P1603#Scope, 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/P1603#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/P1603#mandatory qualifier, SPARQL
This property is being used by:

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

Discussion[edit]

This appears to be total number of cases ever. It does not appear to be either prevalence (the number of cases at a given point of time) or incidence (the number of new cases typically in a year) Doc James (talk · contribs · email) (if I write on your page reply on mine) 22:50, 22 September 2017 (UTC)[reply]

@Doc James: The ambiguity is even worse, see COVID-19 pandemic in Denmark (Q86597685): There it is not the prevalence in a given country but qualified on location, so you have to sum to get the "entire prevalence" (at a given point in time). I wonder if we can do anything to fix these issues. Note that there is the prevalence (P1193) (as I suppose you know). It is only used 22 times. — Finn Årup Nielsen (fnielsen) (talk) 09:33, 3 March 2020 (UTC)[reply]
Another problem is the prevalence versus the confirmed prevalence. — Finn Årup Nielsen (fnielsen) (talk) 09:35, 3 March 2020 (UTC)[reply]
Yah if we have prevalence we can just use that now. Doc James (talk · contribs · email) 17:21, 3 March 2020 (UTC)[reply]
P1603 can be the number of cases at a given point of time, not just the total number of cases ever. The value of P1603 is a number, while that of P1193 (prevalence) or P2844 (incidence) is a ratio (case number per total population, or new case number per 100,000 persons). They are different. Adding number of cases at different points of time can generate a line chart in a query. It should be allowed. --Neo-Jay (talk) 01:10, 13 March 2020 (UTC)[reply]

Need to differentiate cumulative numbers (total since start) from annual frequency[edit]

See Property talk:P1120. Tomastvivlaren (talk) 18:12, 13 May 2020 (UTC)[reply]