Assign a schema on dataset creation / update

[amercader]

Up until now we've been mentioning low-level modules that take advantage of resources having a schema attached to them, but of course this schema needs to be provided somewhere.

The fist basic step is to be able to provide a schema on the resource create/update form. The end result would be a schema object (or a URL pointing to one?) in the schema field of the resource but the interface could be:

1. A simple text box to paste a schema object, or a file upload / URL field for providing an external one
2. Select a pre-defined schema stored in the database (See point 7)
3. Schema editor (See point 8)

Estimate: 0.5 days (option 1)

Estimate: 2.5 days (option 1)

[amercader]

Even if going for option 1 my estimate was overly optimistic, as this involves:

• Validator to ensure the schema is valid (Using tableschema.validate())
• If using ckanext-scheming (my preference), create a preset and an example schema dataset showing how to integrate the resource schema field.

[amercader]

Done