Property talk:P2296

From Wikidata
Jump to navigation Jump to search

Documentation

money supply
amount of currency the central bank has injected in the economy (MO, M1, M2, M3)
Representsmoney supply (Q842206)
Data typeQuantity
Template parameter|Money supply=
Domain
According to this template: Country, region and city articles for the Global Economic Map
According to statements in the property:
administrative territorial entity (Q56061)
When possible, data should only be stored as statements
Allowed valuesnumber with 'currency' dimension, use P794 (P794) as a qualifier to give the type of money supply (M0, M1, M2, M3) (note: this should be moved to the property statements)
Allowed unitsUnited States dollar (Q4917)
Sourcehttp://research.stlouisfed.org/fred2/categories/24
Robot and gadget jobsBots should be doing this task
Lists
Proposal discussionProposal discussion
Current uses
Total1
Main statement1100% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “administrative territorial entity (Q56061): item must contain property “instance of (P31)” with classes “administrative territorial entity (Q56061)” 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/P2296#Type Q56061, 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/P2296#mandatory qualifier, SPARQL
Units: “United States dollar (Q4917): 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/P2296#Units
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P2296#Scope, hourly updated report, SPARQL

Should this property be separted into M0, M1, M2 and M3?

[edit]

@ArthurPSmith: I feel like this property should be separtated into four separate properties (one for each type of money supply indicator). I am willing to propose the four main variants of the money supply statistic. What do you think? Mcnabber091 (talk) 09:01, 20 December 2015 (UTC)[reply]

@Mcnabber091: I'm concerned that this property has never been used though it's been around for a while. Also once again there is no specific example so it's not clear even how it would be used. Why is it constrained to be US dollars? Is the subject item of this property the currency, or the nation or central bank that controls the currency? I might expect a proper example/use to look something like this: Canadian dollar (Q1104069) -> 1364111000000 Canadian dollar (Q1104069) with qualifiers applies to part, aspect, or form (P518) "M2" and point in time (P585) "October 2015". It's always going to need a point-in-time qualifier, so it might as well have the "applies to part" qualifier also that defines which definition of money supply is being given. I don't think there's a need for additional properties right now at least as this one hasn't even been used yet. ArthurPSmith (talk) 16:41, 21 December 2015 (UTC)[reply]
@ArthurPSmith: That is good to hear. I agree that this property should be able to be used for multiple definitions such as currency type, year, M0, M1, M2 and M3. I will need help on the other properties I proposed to determine how they will work in Wikidata. Thanks for your help. Mcnabber091 (talk) 06:35, 23 December 2015 (UTC)[reply]

Time series datatype

[edit]
@ Mcnabber091: I'm wondering if the value for a property like this would be better some sort of time-series table: i.e. a collection of pairs of "date/timestamp" and "number". There's no such property value allowed now in wikidata, but I have the feeling it would be highly useful. Maybe we should go over to project chat and propose it there? Now is probably kind of a quiet time though with holidays... ArthurPSmith (talk) 14:36, 23 December 2015 (UTC)[reply]
@ArthurPSmith: I agree that would be useful but is it possible for us to use qualifiers? Property: Money Supply. Value: 5,430,323,432. Qualifier (money supply type): M0. Currency: USD. Date: 12/31/14. In that case should we make a property for 'Money supply type'? What project chat are you referring to?Mcnabber091 (talk) 20:01, 25 December 2015 (UTC)[reply]
@Filceolaire: Filceolaire, is it possible to do data on in a time-series table? That would be useful for properties like this one, unemployment rate, population, GDP by industry, Employment by industry and many different economic statistics? And how does my suggestion of qualifier/properties in the previous comment work within Wikidata? I will go ahead and propose 'Money supply type' on the property proposal page. Mcnabber091 (talk) 20:05, 25 December 2015 (UTC)[reply]
There are lots of properties where we need to state a value and a date - population for instance. Till now wikidata has in everyone of these cases used a qualifier such as point in time (P585) and I don't think this is going to change. Changes to how these series are displayed is however a real possibility as are tools to convert these series into graphs (IMHO). Joe Filceolaire (talk) 18:31, 29 December 2015 (UTC)[reply]