Closed zelima closed 7 years ago
@zelima what about our discussion about the fact this was causing a 500 error. Whilst we can fix this immediate issue by fixing the data packages what about similar issues in future. We need to think about where in the system we handle "bad" data packages.
FIXED all 4 Data Packages are live and working fine
Following packages have problems after publishing:
https://staging.datapackaged.com/core/geo-nuts-administrative-boundaries | status code: 500 https://staging.datapackaged.com/core/geo-countries | status code: 500 https://staging.datapackaged.com/core/geo-admin1-us | status code: 500 https://staging.datapackaged.com/core/geo-ne-admin1 | status code: 500
heroku logs
For full logs see heroku logs
Acceptance criteria
Tasks
Analysis
Exploring the code further discovered that all 4 Data Packages have common issue:
Inside datapackage.json all of them have property
licenses
that are set as objects Eg https://github.com/datasets/geo-nuts-administrative-boundaries/blob/master/datapackage.json#L20Following the https://specs.frictionlessdata.io description of required and optional properties for a Data Package descriptor https://specs.frictionlessdata.io/data-package/#properties property
licenses
should be list of objectsWe have several options:
licenses
is not set according to specs. This way we are guaranteed that it will always be list of the objectsAs a quick and simple solution for this 4 packages we decided to manually update datapckage.json and rise pull requests
Pull requests: