-
This isn't a "bug", but neither is it a feature request
The footer link for GitHub is to https://github.com/threesixtygiving/. This then requires me to navigate to where I think grantnav code/issu…
-
It seems that the hashcomments setting still has to be explicitly referenced in the Meta sheet of an IATI workbook - is that correct?
I know that we bundled this in as a default for 360 CoVE (and m…
-
-
This package is also used by 360Giving, so in the longer term it’d be best to separate standard-specific methods
For 0.2.x, we can import those methods into the main module, so that users will see …
-
-
To address issues from CRM-6536. `data.json` is attached to that issue.
I ran:
```
pip install memory_profiler matplotlib
time mprof run libcoveoc4ids data.json
mprof plot
```
`time`'s ou…
-
In the schema widget (docson) make the required fields show with an asterisk.
Example of how it will look when resolved:
![Screenshot_2020-08-19 360Giving Data Standard documentation](https://us…
-
* Titles aren't used, instead field names are appended after titles from template
* rollup fields don't appear in the main sheet
-
We should consider / implement a header that can link users back from 360 CoVE to the documentation and main site
@morchickit - take a look at OCDS example: http://standard.open-contracting.org/val…
-
This reuses a subset of 360Giving fields, with an extended purpose enum from SEDL, and has the option to link out to published 360 data.
/Id
/360_giving_identifier
/title
/award_date
/currency
…