roll
Hi @rgaiacs, yes, it will be the main focus. It's on our roadmap for Q3 - https://software.frictionlessdata.io/pages/roadmap.html
Hi @amercader, I would vote for `frictionless-py` way as `tableschema-js` is more like in maintenance-only mode and a more realistic understanding of the situation is that OFKN will not be...
@amercader Yes, it's a good flow description :+1: By default, frictionless uses quite a minimalistic: - buffer size for encoding inference - 10 000 bytes - sample size for dialect/schema...
The editor itself on bs3 should be responsive. I guess it's a integration/ bs2 backport issue
I think it should be easily doable in pure CSS on CKAN side.
@amercader I guess it makes sense moving it to some documentation (e.g. readme)?
Hi @amercader @wardi, I think migration from `goodtables` to `frictionless` is reasonably simple. I can help with the mapping of the options (we anyway are going to write this migration...
BTW we're currently working on a new generation of visual components that will allow providing a simple way to integrate validation options like editing Schema or validation Inquiry for the...
Hi @amercader @wardi, I've created a fork - https://github.com/frictionlessdata/goodtables-py - and a CKAN team (you're invited too) with the maintain permissions on it. I can assist going forward with setting...
@amercader To run ckan with schema editor: - checkout `docker-ckan-unhcr/pull/6` - `docker-compose -f docker-compose.val.yml up`