j40-cejst-2/data/data-pipeline/data_pipeline/etl
Emma Nechamkin 49868401be
Updating field names to match score M definitions (#1190)
When implementing definition M for the score, the variable names were not yet updated. For example:

This legacy field naming: 
```
UNEMPLOYMENT_LOW_HS_EDUCATION_FIELD = (
    f"Greater than or equal to the {PERCENTILE}th percentile for unemployment"
    " and has low HS education"
)
``` 

Should actually be renamed something like this:
```
UNEMPLOYMENT_LOW_HS_LOW_HIGHER_ED_FIELD = (
    f"Greater than or equal to the {PERCENTILE}th percentile for unemployment"
    " and has low HS education and low higher ed attendance"
)
``` 

This PR is for the backend updates for this -- keeping the old fields, and adding new, Score M specific fields as listed below: 
- [x] `field_names`: add new fields to capture low_higher_ed
- [x] `score_m`: replace old fields with new fields 
- [x] `DOWNLOADABLE_SCORE_COLUMNS`: replace old fields with new fields
- [x] `TILES_SCORE_COLUMNS`: replace old fields with new fields
2022-02-01 18:54:43 -05:00
..
score Updating field names to match score M definitions (#1190) 2022-02-01 18:54:43 -05:00
sources Esfoobar usds/488 generate score per commit pr (#1211) 2022-01-31 16:07:21 -05:00
__init__.py Data directory should adopt standard Poetry-suggested python package structure (#457) 2021-08-05 15:35:54 -04:00
base.py Issue 844: Add island areas to Definition L (#957) 2021-12-03 15:46:10 -05:00
constants.py Issue 1141: Definition M (#1151) 2022-01-18 14:56:55 -05:00
runner.py Display score L on map (#849) 2021-11-05 16:26:14 -04:00