A file was downloaded from https://github.com/ThreeSixtyGiving/sample-data/blob/master/ExampleTrust-grants-fixed.xlsx?raw=true on Wednesday, 22 May 2019.
In order to validate your data we needed to convert it to JSON.
Additional checks have been made on your data.
Additional checks highlight some specific areas where the source data may be incorrect or require further attention. They can also suggest ways to increase the usefulness of the data. In any case, these checks do not indicate validation errors and can be ignored if they are not relevant.
|Check Description||First 3 Locations|
2 grants have a Recipient Org:Identifier that starts '360G-'
If the grant is to a recipient organisation that has an external identifier (such as a charity or company number), then this should be used instead. Using external identifiers helps people using your data to match it up against other data - for example to see who else has given grants to the same recipient, even if they’re known by a different name. If no external identifier can be used, then you can ignore this notice.
10 grants do not have either a Recipient Org:Company Number or a Recipient Org:Charity Number
Providing one or both of these, if possible, makes it easier for users to join up your data with other data sources to provide better insight into grantmaking. If your grants are to organisations that don’t have UK Company or UK Charity numbers, then you can ignore this notice.
10 grants do not have recipient organisation location information
Your data is missing information about the geographic location of recipient organisations; either Recipient Org:Postal Code or Recipient Org:Location:Geographic Code combined with Recipient Org:Location:Geographic Code Type. Knowing the geographic location of recipient organisations helps users to understand your data and allows it to be used in tools that visualise grants geographically.
10 grants do not contain any Grant Programme fields
Providing Grant Programme data, if available, helps users to better understand your data.
Review your data.
|360G-KJD-001230||Grant award to Blue Trust||GBP||5000||2017-12-22T00:00:00+00:00|
|360G-KJD-001231||Grant award to Red Charity||GBP||10000||2017-12-22T00:00:00+00:00|
|360G-KJD-001232||Grant award to Green House Charity||GBP||3500||2017-12-22T00:00:00+00:00|
|360G-KJD-001233||Grant award to Purple Community Group||GBP||2000||2017-12-22T00:00:00+00:00|
|360G-KJD-001234||Grant award to Yellow Day Centre||GBP||4500||2017-12-22T00:00:00+00:00|
|360G-KJD-001235||Grant award to Orange Gardens||GBP||15000||2017-12-22T00:00:00+00:00|
|360G-KJD-001236||Grant award to Turquiose Foundation||GBP||1500||2017-12-22T00:00:00+00:00|
|360G-KJD-001237||Grant award to Pink Playing Field||GBP||2500||2017-12-22T00:00:00+00:00|
|360G-KJD-001238||Grant award to Maroon Gallery||GBP||7500||2017-12-22T00:00:00+00:00|
|360G-KJD-001239||Grant award to Grey Scout Group||GBP||8250||2017-12-22T00:00:00+00:00|
Upload, paste or provide a link to data in the 360Giving Data Standard format, and this application will convert between JSON, Excel and CSV formats, allowing you to download the original file, and the converted versions.
You will also be able to inspect key information from the data that the application is able to find, so that you can check the data.
This tool will:
Check your data is valid. When it passes these checks, you will know that it is formatted for re-use
It will not:
Check your data is accurate. Read about common data errors and how to check for them in the Common Errors section.
Check the data against your own open data policy. Read more about Publishing and Using Open Grant Data .
The application accepts data in some of the formats given in the 360Giving Data Standard guidance.
Acceptable files are:
What happens to the data I provide to this site?
We retain the data you upload or paste to this site, on our server, for seven days.
If you supply a link, we fetch the data from that link and store it on our server for seven days.
We delete all data older than seven days from our servers daily, retaining none of the original data.
While the data is on our servers we may access that data to help us understand how people are using this application, what types of data are being supplied, what common errors exist and so on.
We may also retain data in backups of our servers, which means on occasion, some data may be retained longer. We have no intention of using this data for anything other than server recovery in an emergency.
We do retain some metadata about data supplied to this site. Details can be found in the code, but may include information about whether or not the file was uploaded, linked or pasted, the size of the file, the date/time it was supplied and so on.
Why do you delete data after seven days?
This is a service to allow people to explore machine readable data. As such we see no need to store and gather everything people submit to the site forever. We have chosen seven days as a practical time frame that allows people to share results with colleagues, but also allows data to disappear over time to save people having to clean up after themselves.
We believe that deleting supplied data after seven days provides a level of privacy for the users of this service.
Why provide converted versions?
The W3C Data on the Web Best Practices recommend making open data available in a range of formats to meet the needs of different users, for example, developers may want JSON, researchers might prefer a spreadsheet format.