Skip to content
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

Provide a breakdown of failure reasons in the interface #34

Open
duncandewhurst opened this issue Apr 12, 2021 · 2 comments
Open

Provide a breakdown of failure reasons in the interface #34

duncandewhurst opened this issue Apr 12, 2021 · 2 comments
Labels
compiled release checks Relating to compiled release-level check pages
Milestone

Comments

@duncandewhurst
Copy link

For example, in https://dqt.datlab.eu/resource/239/detail/reference.buyer_in_parties I can see that the first few examples in the sample of failures have meta/failed/reason set to "id missing" but I don't know if there are any other reasons for the failures.

So that I can tell the publisher how to fix the issue, I need to know the reasons for checks failing.

The interface could include a breakdown of failure reasons, e.g.

id missing in buyer: 302,039
id not present in parties: 142,903

etc.

@jpmckinney
Copy link
Member

jpmckinney commented Apr 12, 2021

Related: open-contracting/pelican#35

@duncandewhurst
Copy link
Author

Similarly, it would be good to have a summary of the failed_paths metadata in the coherent.dates check.

@jpmckinney jpmckinney transferred this issue from open-contracting-archive/pelican Sep 14, 2021
@jpmckinney jpmckinney added the compiled release checks Relating to compiled release-level check pages label Sep 14, 2021
@jpmckinney jpmckinney added this to the Priority milestone Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiled release checks Relating to compiled release-level check pages
Projects
None yet
Development

No branches or pull requests

2 participants