-
The 360Giving CoVE checks for good and bad prefixes but this isn't part of the [OCDS validator](http://standard.open-contracting.org/validator).
It would be a useful additional so we can feed back …
-
We should provide a controlled codelist for organisation type.
Suggested values:
- Registered Charity
- Registered Company
- ???
-
Related to #950
When we present an error to a user because their data is structurally wrong in some way (eg invalid date), we should provide an example of how it looks if correct.
Prep require…
-
We've seen cases where publishers using additional fields of their own use dots in the title e.g. `field.name`
While this shouldn't be expected to be a problem it has created issues when reprocessi…
-
This should happen roughly in line with these changes to 360Giving's identifier docs: https://github.com/ThreeSixtyGiving/standard/pull/199
-
**Issue**
a number of grants published are intended for redistribution (in the form of subsequent grants) to other organisations. If all these grants are published with the 360Giving standard ther…
-
Based on the list in issue #3
-
Use existing IRS schema, a custom/modified schema, or existing industry standard (e.g. hGrant, IATI, 360Giving)?
[hGrant JSON](https://github.com/smartergiving/hgrant-json)
[360Giving](http://ww…
-
See https://github.com/ThreeSixtyGiving/standard/issues/210#issuecomment-319090718
We should switch to using the org-id.guide list instead of the IATI register.
-
Report should consist -
- What we tried to achieve?
- What worked well and why ?
- What worked bad and why?
- Recommendation for future pilot and recommendations of what to do in the future i…