Basically just removing the ETL files and their references from the scrapers and READMEs
Also re-adds a file that was deleted in the last purge in dfaec1d95602562ea25f558aa0e306dfc398dbf6 and put it in /common/utils since its used by list_pdf_v2 and v3 in circumstances where the extract_tables parameter is true. 7bf4ef60998572364cfa75cf9d57a158e13a7b3f
Alternatively, we could just remove the entire extract_tables behavior and then the pdf_extract.py file would no longer be necessary. I didn't find any other location where extract_tables was used other than a testing file so it shouldn't break anything with its removal.
I also wanted to ask if we were planning to remove the schema.json files too or if they were going to be used in some other manner.
Basically just removing the ETL files and their references from the scrapers and READMEs
Also re-adds a file that was deleted in the last purge in dfaec1d95602562ea25f558aa0e306dfc398dbf6 and put it in
/common/utils
since its used bylist_pdf_v2
andv3
in circumstances where theextract_tables
parameter is true. 7bf4ef60998572364cfa75cf9d57a158e13a7b3f Alternatively, we could just remove the entireextract_tables
behavior and then thepdf_extract.py
file would no longer be necessary. I didn't find any other location whereextract_tables
was used other than a testing file so it shouldn't break anything with its removal.I also wanted to ask if we were planning to remove the
schema.json
files too or if they were going to be used in some other manner.