Standardize VA scraper about warn-transformer HOT 2 CLOSED

Ok, let's move this to the warn-analysis repo.

It looks like closing vs layoff refers to whether a plant/business was closed entirely or there was merely a reduction in staff. This could be useful for a story about how many businesses needed to close operation due to COVID-19.

from warn-transformer.

@ydoc5212 We generally want to perform "value add" such as value standardizations, date standardizations, etc. as a post-processing step. Scrapers in the WARN repo should generally retain a high degree of fidelity with the source data. For our scrapers, we want to perform the bare minimum related to data transformation when scraping, though this bare minimum can vary depending on the nature of the data acquisition. A simple case would be downloading a CSV; a more involved case would be downloading and converting a PDF or Excel file. In the latter more involved cases, we generally want to extract data in the format it appeared in the original (e.g. leaving dates in their original formats) and leave transformations for post-processing. That's a long way of saying that you should continue to perform tasks such as those described in this ticket (e.g. standardizing the "Closing" and "Layoff" fields) in the warn-analysis repo, as opposed to applying such changes in WARN.

Regarding "Closing" vs. "Layoff" in particular, do we have a clear sense of what these fields actually denote?

from warn-transformer.