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

Expand the scope of the IATI validator #60

Open
pelleaardema opened this issue Dec 10, 2019 · 1 comment
Open

Expand the scope of the IATI validator #60

pelleaardema opened this issue Dec 10, 2019 · 1 comment

Comments

@pelleaardema
Copy link

"The tool checks data against all rules and guidance (musts & shoulds) in the IATI Standard. The tool aims to improve the quality of IATI data to ensure it is accessible and useful to anyone working with data on development and humanitarian resources and results."

From https://discuss.iatistandard.org/t/new-iati-validator-launched-for-public-testing/1870

I understand the validator currently only checks the Musts and Shoulds of the standard. Is there room for more elaborate feedback to data publishers, especially looking at the aim "to ensure it is accessible and useful"?

Currently there are quite a few things that are not provided with feedback, which make the data hard to use/less useful:
- No budget --> no message
- No results --> no message
- No implementing orgs --> no message
- 2 accountable orgs --> no message

Just to give a few random examples….

@PetyaKangalova
Copy link
Collaborator

Hi Pelle,

Thanks. Yes, you are right that currently the IATI validator checks data against all rules and guidance (musts & shoulds) in the IATI Standard. In this testing phase we want to ensure that all bugs related to musts and shoulds are fixed as well as messages clarified (based on feedbacke going live.

Once we go live with the current validator, there will be an opportunity to consult and build on additional checks. I will keep this issue open as 'enhacement' as it will be relevant to look at later next year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants