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
..
data-pipeline	Updating field names to match score M definitions (#1190)	2022-02-01 18:54:43 -05:00
data-serve	dockerize front-end and pass env vars to npm build (#614)	2021-09-07 10:35:11 -07:00