TDRS stores the state_fips (for states and territories) and tribe_code (for tribes) from the header record with each data record (T1,...T7,M1,...,M7) in the db. This helps OFA analysts understand which STT is associated with each record. See example below of the T6 db table from TDRS.
This is currently not happening in TDP. This ticket was created in response to the comment below:
@ADPennington I updated based on your review. I think all the validator changes should live in those tickets you called out. That way we can update all sections for programs in one go. I would also like to make the fips_code/tribe_code addition to the models/documents it's own ticket. Adding those to the models that are missing them will create a new migration. The migration generated will be a big one since it will have to impute a new column and value for the DB tables that don't have it. Those tables are pretty big which will cause a reasonably long running migration.
[ ] perform a category 1 (pre-check) to ensure the submitted file location (STT_CODE) matches what is provided in the file header
[ ] work with @ADPennington to design a query pulling most recent submissions in a given section for all stts
Tasks
[ ] tbd
Notes
relevant to all sections of TANF, SSP, and Tribal TANF.
file pre-check error if the submission stt_code (in the file header) does match the stt code for the location in the db
then a db association can be made between the record and the stt, avoiding having to store header data alongside each record
association already exists between datafile and record, datafile and stt. can use existing relationship to perform stt lookup
- if storing the data alongside each record is necessary, would require more parser/model changes- migrations? how to fill data for previous submissions
ADPennington
commented
6 months ago
Description
TDRS stores the
state_fips(for states and territories) andtribe_code(for tribes) from the header record with each data record (T1,...T7,M1,...,M7) in the db. This helps OFA analysts understand which STT is associated with each record. See example below of the T6 db table from TDRS.This is currently not happening in TDP. This ticket was created in response to the comment below:
Originally posted by @ADPennington in https://github.com/raft-tech/TANF-app/issues/2742#issuecomment-1871458505
Acceptance Criteria
STT_CODE) matches what is provided in the file headerTasks
Notes
- if storing the data alongside each record is necessary, would require more parser/model changes- migrations? how to fill data for previous submissionsSupporting documentation