[This is a debate ticket, someone should create a counter ticket, e.g. "run Webstore inside CKAN"]
This may involve:
- proper user interface, probably based on recline
- account management
- background queue
- web-based config of ACL, webhooks, input converters
- web-based basic ETL (messytables runtime env, essentially)
The easiest way to do this is to push in the datahub code base minus a few things (datasets).
But it also means limiting scope, IMO to:
- Tabular data with micro-conventions
- Not a document store (tm)
[This is a debate ticket, someone should create a counter ticket, e.g. "run Webstore inside CKAN"]
This may involve:
The easiest way to do this is to push in the datahub code base minus a few things (datasets).
But it also means limiting scope, IMO to: