You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's risky to have our source of truth be the Classic site and Elasticsearch because we have retired Classic and it's now that data in only in Elasticsearch. In addition, we don't have a lot of experience with managing and restoring from backups in elasticsearch.
Improvement plan
We should insert the archived MUR data into postgres for better data preservation and maintenance.
Code references
We should modify this function to scrape from classic, insert into postgres, and upload to s3 if needed (should already be there, but confirm)
What we're after:
It's risky to have our source of truth be the Classic site and Elasticsearch because we have retired Classic and it's now that data in only in Elasticsearch. In addition, we don't have a lot of experience with managing and restoring from backups in elasticsearch.
Improvement plan
We should insert the archived MUR data into postgres for better data preservation and maintenance.
Code references
We should modify this function to scrape from classic, insert into postgres, and upload to s3 if needed (should already be there, but confirm)
openFEC/webservices/legal_docs/load_legal_docs.py
Lines 445 to 462 in 3c78a21
Completion criteria:
The text was updated successfully, but these errors were encountered: