Closed konklone closed 10 years ago
I'm running this once on my production server before merging, and will merge if there are no errors along the way.
It seems like either the parameter, archive
, should be renamed to something self explanatory (like oldest_report_year) or the comments saying "# Oldest report year" should be retained. As it is, archive = 2002 at the top of a scraper doesn't have much inherent meaning. To me, archive
is a verb and sounds, at best, like a boolean parameter controlling whether results should be archived.
Probably oldest
would be the better term for the variable, I just wanted to keep an obvious link between --archive
and the variable. I don't feel strongly enough about it to go and change them all again myself, though (it was pretty tedious).
I've fixed several errors I saw pop up during the re-archive, and after fixing them I think this is good for merging.
Great work! :+1:
inspector.year_range
now takes options and an archive year, so any scraper that passes a year to that function will support an--archive
flag.I've updated each scraper to replace its top-of-file comment with an actual variable declaration (e.g.
archive = 2006
), and each call toinspector.year_range
to pass this variable in.The
--archive
flag will work in either form of running a scraper:It's now possible to easily re-run the scrapers over their entire archive, and keep up with improvements to scraping and metadata that affect the entire set.