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
The new archivers are working, but we don't have the infrastructure set up to run them on an automated schedule. Instead up them manually, adding new archive lineages for the new datasets
π New Dataset
β Updated Existing Archive
β No Update
π Archiver is broken
The content you are editing has changed. Please copy your edits and refresh the page.
All of the other archivers use a file naming pattern like:
dataset-part1-part2.ext
where:
- dataset is the name of the dataset (e.g. ferc1, eia923, mshamines)
- part1 is the value of the first partition dimension contained in
the file (e.g. ca, ny, wy, for states, 2019 if it's a year)
- part2 is the value of the second partition dimension contained in
the file, if applicable.
- ext is the file name extension indicating file type.
I've changed the naming for phmsagas to follow the `dataset-*` part of
the naming convention, but have left the filename in place rather than
using only the dataset and start year, since if we just use the start
year it looks like years are missing in the archive, as each file
contains several years of data.
The dataset and start_year partitions are still used in datapackage.json
to refer to the individual resources for programmatic purposes.
This came up when working on #79
The new archivers are working, but we don't have the infrastructure set up to run them on an automated schedule. Instead up them manually, adding new archive lineages for the new datasets
Tasks
The text was updated successfully, but these errors were encountered: