labordynamicsinstitute / qwi_schemas

Unofficial LEHD Schema files
https://lehd.ces.census.gov/data/schema/
Creative Commons Zero v1.0 Universal
1 stars 6 forks source link

Add stable EE/AQ measures and earnings to J2J single node table #147

Open srt1 opened 5 years ago

srt1 commented 5 years ago

We will add the following to the J2J table (variables_j2j.txt)

We also will need to update the indicator availability table (lags_j2j.txt).

Note, these measures already exist (contrary to my prior assertion...)

srt1 commented 5 years ago

Jody/Heath,

I would propose this become version 4.6.0. We can probably branch off 4.4.0, and merge in the PSEO changes at some future date. Should we start a new milestone? Let me know what you think.

Thanks.

srt1 commented 5 years ago

Note, stable EE/AQ counts were added between 4.1.3 and 4.2.0, along with first release of earnings measures.

srt1 commented 5 years ago

updates.4.6.0.zip

Updates to variables_j2j.csv and lags_j2j.csv. Will drop them into Git properly, once I have somewhere appropriate to put them.

srt1 commented 5 years ago

I previously suggested to Jody that the changes to this ticket and the 2019 geo go into the same schema - I realized that this might not work. The hope is that the next J2J release will follow the 2019Q4 QWI production, which is in 2018 geography, so the J2J will be as well. So, we may want one schema with the J2J changes (4.6.0), and a second with both the J2J and 2019 geography changes (4.7.0).

Technically, this matters only if the list of MSAs changes between 2018 and 2019 geography. In past years, there have been very minor changes, such as a region switching between micro and metro status. And then, there is still the possibility that we will not run J2J after the end of next quarter, depending on the data delivery/MOU situation. But to be safe, it's probably better to separate the changes.

heathhayward commented 4 years ago

Looks like there are differences between the 2018 CBSA and 2019 CBSA file, including a couple metro area codes and names that are different (although the areas for those metro areas appear to be identical). I can look into this further if needed.

srt1 commented 4 years ago

Should not be an issue. If we produce J2J in January, it will be in 2018 geo, which is why I wanted 4.6.0. Release 4.7.0 should have both the J2J changes in 4.6, as well as the 2019 geography codes.