LMI For All

Documentation & Development

User Tools

Site Tools


data:specsheet_ashehours

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
data:specsheet_ashehours [2019-09-03 15:20]
Luke Bosworth [Hours Data Specification]
data:specsheet_ashehours [2019-09-03 15:21] (current)
Luke Bosworth [Rules for supressing data or raising warning flags]
Line 58: Line 58:
 [[data:​specsheet_working_futures#​classifications_and_aggregations|As for employment]] [[data:​specsheet_working_futures#​classifications_and_aggregations|As for employment]]
  
-====Rules for supressing ​data or raising warning flags====+====Rules for suppressing ​data or raising warning flags====
 The rules of thumb used are: The rules of thumb used are:
  
-  - If the numbers employed in a particular category / cell (defined by the 12 regions, gender, status, occupation, qualification and industry (75 categories)) are below 1,000 then a query should return "no reliable data available"​ and offer to go up a level of aggregation across one or more of the main dimensions (e.g. UK rather than region, some aggregation of industries rather than the 75 level, or SOC 2 digit rather than 4 digit). This information is held in the variable '​weight'​ in the Working Futures employment file ('​WFDataOcc4Dig.csv'​) and in the Pay file ('Pay-20160422.asc') '​Employment'​ (same in both files).+  - If the numbers employed in a particular category / cell (defined by the 12 regions, gender, status, occupation, qualification and industry (75 categories)) are below 1,000 then a query should return "no reliable data available"​ and offer to go up a level of aggregation across one or more of the main dimensions (e.g. UK rather than region, some aggregation of industries rather than the 75 level, or SOC 2 digit rather than 4 digit). This information is held in the variable '​weight'​ in the Working Futures employment file ('​WFDataOcc4Dig.csv'​) and in the Pay file ('ashe_pay_main.csv') '​Employment'​ (same in both files).
   - If the numbers employed in a particular category / cell (defined as in 1.) are between 1,000 and 10,000 then a query should return the number but with a flag to say that this estimate is based on a relatively small sample size and if the user requires more robust estimates they should ​ go up a level of aggregation across one or more of the main dimensions (as in 1).   - If the numbers employed in a particular category / cell (defined as in 1.) are between 1,000 and 10,000 then a query should return the number but with a flag to say that this estimate is based on a relatively small sample size and if the user requires more robust estimates they should ​ go up a level of aggregation across one or more of the main dimensions (as in 1).
  
 This is the same as is done for any queries about Employment (including Replacement Demand calculations) and also for Pay. This is the same as is done for any queries about Employment (including Replacement Demand calculations) and also for Pay.
  
-In the case of Pay and Hours the API needs to use the employment weights included in the relevant 'Pay.asc' or '​Hours.asc' file to do the checks, as in 1.and 2. above, but then to report the corresponding pay or hours values as appropriate.+In the case of Pay and Hours the API needs to use the employment weights included in the relevant 'ashe_pay_main.csv' or '​Hours.csv' file to do the checks, as in 1.and 2. above, but then to report the corresponding pay or hours values as appropriate.
  
 ===Rounding of estimates=== ===Rounding of estimates===
data/specsheet_ashehours.txt ยท Last modified: 2019-09-03 15:21 by Luke Bosworth