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:

However, 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
  • tags

Have you seen anything like this? If not, maybe you'd share your practices of maintaining the data manually?

  • you want version control?
    – albert
    May 23, 2015 at 0:28
  • @albert Why not? Though I found only GitHub LFS and other solutions not integrated in data package managers. May 23, 2015 at 10:29

1 Answer 1


Ecosystem image from Data Packages website


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.