Property talk:P3744

From Wikidata
Jump to navigation Jump to search

Documentation

number of subscribers
number of subscribers for subscription-based companies, e.g. telecommunication companies, newspapers, pay-TV channels, software, etc.
DescriptionNumber of subscribers for subscription based companies, e.g. telecommunication companies, newspapers, pay-tv channels, etc.
Representssubscriber (Q10638511), number of subscribers (Q114771100)
Data typeQuantity
Allowed values
According to this template: numbers
According to statements in the property:
0 ≤ 𝓧 ≤ 10,000,000,000
When possible, data should only be stored as statements
Allowed unitsInstances of: subscriber
not applicable
ExampleChina Mobile (Q741618) → 851,000,000
Styr & Ställ (Q6198848) → 28,000
Gazeta Wyborcza (Q741296) → 218,000
See alsomember count (P2124), units sold (P2664), readership (P4295), social media followers (P8687), number of viewers/listeners (P5436)
Lists
Proposal discussionProposal discussion
Current uses
Total342,620
Main statement4550.1% of uses
Qualifier341,90499.8% of uses
Reference261<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P3744#Range, hourly updated report
Units: “novalue”: value unit must be one of listed. (Help)
List of violations of this constraint: Database reports/Constraint violations/P3744#Units, hourly updated report
Integer: values should be integers (ie. they shouldn't have a fractional part) (Help)
List of violations of this constraint: Database reports/Constraint violations/P3744#integer, hourly updated report, SPARQL
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/P3744#mandatory qualifier, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P3744#Item P31, hourly updated report, 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/P3744#Single value, SPARQL
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P3744#Scope, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
List of violations of this constraint: Database reports/Constraint violations/P3744#Entity types, hourly updated report
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/P3744#citation needed
Conflicts with “instance of (P31): subreddit (Q28464970): this property must not be used with the listed properties and values. (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/P3744#Conflicts with P31, SPARQL

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

Before 1700
(Help)
Violations query: SELECT DISTINCT ?item { ?item wdt:P3744 ?value . ?item wdt:P571 ?dateF . FILTER (YEAR(?dateF) < 1700) }
List of this constraint violations: Database reports/Complex constraint violations/P3744#Before 1700
unit violations when used as qualifier: list
detailed list (Help)
Violations query: SELECT ?unit ?unitLabel ?item ?itemLabel ?statement ?prop ?propLabel { { SELECT * { ?statement pqv:P3744/wikibase:quantityUnit ?unit . FILTER( ?unit != wd:Q199 ) } } hint:Query hint:optimizer "None". ?item ?p ?statement . ?prop wikibase:claim ?p . SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". } } LIMIT 500
List of this constraint violations: Database reports/Complex constraint violations/P3744#unit violations when used as qualifier: list

Is this really suitable for Wikidata?[edit]

This can sometimes be fake as pushed by zombie fans. --Liuxinyu970226 (talk) 23:41, 7 June 2018 (UTC)[reply]

Came here after finding on Overwatch (Q18515944) that its reporting the sub reddit subscriber count. I don't think this is what anyone wanted when it was proposed. Dispenser (talk) 02:56, 18 June 2018 (UTC)[reply]

Proposition of a extra property for the number of twitter followers[edit]

In 65% of the usage of X username (P2002) this qualifier is used. For me the functionality of a qualifier is too limited, e.g. we cannot state the date when the follower count was determined. Therefore, I requested a new property for this functionality at Wikidata:Property proposal/Number of twitter follower. Sk!d (talk) 12:32, 6 July 2018 (UTC)[reply]

What to do with number of followers[edit]

Please see Wikidata:Property proposal/social media followers, an additional proposal mentioned there is to move them to Commons data pages. --- Jura 07:42, 27 June 2020 (UTC)[reply]

Add subscriber (Q28008243) as property unit[edit]

That would seem appropriate to me. Opinions? Ogoorcs (talk) 07:01, 30 July 2020 (UTC)[reply]

Acepto Torres sixto (talk) 06:36, 18 March 2021 (UTC)[reply]

Complex constraint: units used[edit]

This property seems to have the same problem as social media followers (P8687): a few uses of 1,000,000 (Q38526) and 1000 (Q43016) as units can make comparisons difficult (see Property_talk:P8687#units).

On items directly, these appear as constraint violations, but the report at Wikidata:Database_reports/Constraint_violations/P3744#"Units"_violations doesn't include them as it only runs on main statements. To find them, I added a complex constraint above, that should eventually list them at Wikidata:Database_reports/Complex_constraint_violations/P3744. You can also just run query on the constraint template. --- Jura 11:44, 22 April 2021 (UTC)[reply]