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
As noted in #372 and #377, hardcoding the range of years archived by our data means that our archivers will never automatically catch a new year's release of data. There will be no 2024 AEO release, but to be able to catch the release of AEO in 2025 we should remove the hardcoded years in the archiver.
Ideally, we would do this by:
identifying a directory or page where all years of data are listed
querying this list to establish the date range
iterating through this data range to feed a year parameter to the open data URL currently used in the archiver
If no such directory is found, we could attempt to download all years of data since the first year using a try/except clause. This would be less robust and less ideal, however.
The text was updated successfully, but these errors were encountered:
As noted in #372 and #377, hardcoding the range of years archived by our data means that our archivers will never automatically catch a new year's release of data. There will be no 2024 AEO release, but to be able to catch the release of AEO in 2025 we should remove the hardcoded years in the archiver.
Ideally, we would do this by:
year
parameter to the open data URL currently used in the archiverIf no such directory is found, we could attempt to download all years of data since the first year using a try/except clause. This would be less robust and less ideal, however.
The text was updated successfully, but these errors were encountered: