Software has code repositories and package managers, so installation and maintenance are done in one line (or click).
What are practices for managing data, instead? Apart from manually organized directories with readme files inside, I found a couple solutions:
drakefrom Factual, https://github.com/Factual/drake
CKANfrom OKFN, https://okfn.org/projects/ckan/
- Zotero and other librarian tools, so you save datasets instead of books with them
drake is mostly about workflows, not maintenance. And
CKAN is server-based solution for which I couldn't find a local "package manager".
What would such a package manager ideally do:
- downloading datasets from source in one click
- supporting multiple formats and conversion
- maintaining the directory structure
- updating the data from the repositories
- supporting aliases for datasets
- holding meta information about the datasets
Have you seen anything like this? If not, maybe you'd share your practices of maintaining the data manually?