goodtables.io
goodtables.io copied to clipboard
Data validation as a service. Project retired, got to the current one at frictionsless/repository
# Overview For not API expect `Authorization: ` instead of more correct `Authorization: token `.
While third-party integrations could periodically poll `/api/source/xxx/job/yyy` (or `/api/job/yyyy`, whatever we go for on #166) to check if a job was finished, we can make their* life easier if we...
### Description Coupled with big improvements in UX we need to prioritise a clear and comprehensive documentation that guides users on how to make the most of the service. There...
There is no feedback when things happen (eg activate a repo)
Point to the `PROD` or `DEV` version as relevant from staging / production. May be related to #136
Catch-all issue with minor design things that I can't fix but that will be no problem for @smth (or maybe @roll) ### Layout - [x] proper `Header` visual design including...
# Overview - create s3 bucket with any region except Oregon - prepare your AWS creadentials (root e.g.) - s3/settings -> fill the form -> add bucket - `Error setting...
For GitHub repos. See https://github.com/frictionlessdata/goodtables.io/issues/81#issuecomment-331186818
# Overview Here is an example or errored job with this message - https://goodtables.io/github/loleg/born-died-ch/jobs/1 Behavior seems correct (no tabular files leads to jsonschema validation fail) but error message should be...
# Overview We've implemented token based auth for API. It means to auth a client should add a header `Authorization: token `. It's perfect for server-based applications but browser-based application...