Pilot overview

[amercader]

@gabelula @roll @jobarratt

This is the working repo that we will use for test-driving goodtables.io and at the same time cleaning up and improving the the upstream causanatura repo. We will send pull requests with the relevant changes for @gabelula to review and merge.

Validation is set up here:

https://goodtables.io/github/frictionlessdata/causanatura

As you can see there's work to do :) The first issue has been logged in https://github.com/frictionlessdata/goodtables.io/issues/225. All issues related to the service itself will be logged in the https://github.com/frictionlessdata/goodtables.io repo, with the pilots label.

The rough plan is this:

• [x] Get validation working without internal errors
• [ ] Identify issues with failing files, and provide fixes (if feasible from our side)
• [ ] Introduce schema based validation, at least in some of the files/folders.

Ideally we want to create data packages that package the data and provide the schema information needed.

@gabelula can you give us a brief overview of the data files? Does it make sense to create one data package per folder? Are there any files that we should skip completely? Cheers

[roll]

There is only one issue remaining - https://github.com/frictionlessdata/goodtables.io/issues/225 - to have this repository works as expected. And I'm on it.

Also @gabelula here is causanatura-datos report - http://goodtables.io/github/roll/causanatura-datos - it should work now for gabelula/causanatura-datos too.

[roll]

Our report is available - http://goodtables.io/github/frictionlessdata/pilot-causanatura

[gabelula]

Great. How can I run it for my own project? http://goodtables.io/github/gabelula/causanatura

[roll]

@gabelula Please deactivate and activate gabelula/causanatura github source at http://goodtables.io/settings (for now you have it activated for staging site - https://staging.goodtables.io/github/gabelula/causanatura/jobs/13)