-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catalog harvest does not report error when data.json is invalid #3658
Comments
Maybe related to another bug #3532. |
doc-gov harvest failed at gather stage when a record does not have the required
|
no, still an issue. |
Before schema validation, the gather_stage and import_stage were referring to the |
When a data.json harvest source contains invalid entries according to DCAT-US Schema v1.1, the harvest report a successful harvest job with 0 changes. It is reported by rrb and confirmed on job https://admin-catalog-next.data.gov/harvest/rrb-json/job/2f728b7a-d954-469e-9b3a-81a2364a17b6.
How to reproduce
Create a data.json source containing entries that has no
keyword
andidentifier
. Harvest it.Expected behavior
Harvest report specific errors.
Actual behavior
Successful harvest on the UI and email notification.
Context
If a data.json is not valid using tool https://dashboard.data.gov/validate, the gathering process should pick up the error. We had it working before but I am not sure when it started to be broken.
The text was updated successfully, but these errors were encountered: