Ticket #852 (assigned enhancement) — at Version 5
Dataset upload and archiving (master ticket)
Reported by: | wwaites | Owned by: | wwaites |
---|---|---|---|
Priority: | critical | Milestone: | ckan-v1.5 |
Component: | DGU | Keywords: | |
Cc: | Repository: | ckan | |
Theme: | none |
Description (last modified by pudo) (diff)
3 (4) use cases: (With and without access to auth keys.)
- upload form on ckan (by default local system has auth key for storage)
- datapkg upload (client) (by default without key) (plumbing done)
- background job archiving downloads (by queue client)
Most important are:
- Upload form on ckan.net (with access to keys)
- API for getting credentials for upload from ckan.net api (without access to keys).
Aside: Once 2 was done we could deprecate storage.ckan.net
Sub-tickets
Required infrastructure
- #826 - Resource 'extra' fields
- #358 - Resources in REST API
- #235 - Resource format normalization and detection
User upload via Web UI
User upload via CLI/datapkg
Also related:
- #405 - Interactive retrieval of package resources
Automated archiving using worker process
More Info
- Upload/storage discussion: http://ckan.okfnpad.org/storage
- For api to generate upload key (for e.g. datapkg usage) suggest locating at ckan.net/api/utils/
Change History
Note: See
TracTickets for help on using
tickets.