Ian Ward

@florianm free-form extras should work if we just add the edit fields back to the template. Care to give that a try? The only problem is: how do we handle...

I'd love this too. At the moment there's no plugin interface like IDatasetForm or IGroupForm for users. Should we move this issue to the ckan ideas repo instead?

What's the traceback in the server logs?

strict dependencies in install_requires causes cli commands to fail before they start if the version is ever changed. What is this change for? Can you use a version range instead?

@frafra I think you're saying you want to store fields from old dataset schema versions so you want to skip the errors that might happen due to a schema change....

sounds like it would be better to use a different schema for your "parent/meta" datasets that have no fields defined except the ones you need.

this looks interesting. Would you include some tests that demonstrate how simple subfields would be represented as JSON in the API and how simple subfields support server-side validation?

Simple subfields in the API look a lot like repeating subfields. Is there anything that prevents users from inserting more than one record into a simple subfield and returns a...

Much earlier I removed another simple subfields-like feature because I was thinking it would be cleaner to implement this kind of feature on the front-end only by visually grouping field...

`"required": true` should be the only thing necessary. The preset for the multiple choice fields use a [different validator](https://github.com/open-data/ckanext-scheming/blob/master/ckanext/scheming/presets.json#L72-L86) Either that validator should be honouring "required", or we should use...