Upload or provide a link to a file, or paste JSON to check and convert your data and get feedback on whether it is valid 360Giving data.
Submit your 360Giving data file to the 360Giving Data Registry. Your file will also be checked to make sure you are submitting valid 360Giving data.
Upload, paste or provide a link to data using the 360Giving Data Standard format, and this application will check whether it is valid 360Giving data, and provide feedback so that you can check for errors and see ways to improve its quality.
The tool will convert between JSON, Excel and CSV formats, allowing you to download the original file, and the converted versions.
This tool will:
Check your data is valid.
The term ‘valid‘ means the data includes the 10 core fields and the information has all the correct data formatting that is required by 360Giving Data Standard. When it passes these checks, you will know that it is formatted for use alongside other valid 360Giving data and can be included in 360Giving tools, such as GrantNav and 360Insights.
It will not:
Check your data is accurate.
Check the data against your own open data policy.
This means there may be further checks you need to carry out to make sure the information is accurate, and that the data does not include information that is unsuitable for publishing as open data. Read more about what to consider when publishing open grants data.
Read about common data errors and what causes them in the Common Errors section.
To preview how this tool works, try loading some sample data.
The application accepts data in the formats set out in the 360Giving Data Standard guidance.
Acceptable files are:
Once 360Giving data has been published by an organisation, the file must be added to the 360Giving Data Registry so that the data to appear in 360Giving’s tools such as GrantNav and 360Insights.
Publishers of 360Giving data can add their valid 360Giving data files to the Data Registry using the 360Giving data file submission form.
The submission form allows users to:
Only publishers with an authorised website domain can use this submission process.
By default, the website domain used by existing publishers to host their 360Giving data files will be authorised.
Organisations that publish 360Giving data for the first time can also use the 360Giving data file submission process once they have registered their website domain with 360Giving. To register to your website domain prior to publishing for the first time please contact 360Giving Helpdesk via firstname.lastname@example.org.
Publishers can opt out of authorising their website domain and using the 360Giving data file submission process on request.
Data files published on multi-user hosting platforms like open data repositories, or file sharing services Google Sheets or Dropbox, cannot be authorised for use with the 360Giving data file submission process because the domain cannot be authorised as being unique to a particular organisation.
Files published in this way can be added to the 360Giving Data Registry by emailing 360Giving Helpdesk via email@example.com.
Read our full guidance on how to use the 360Giving data submission process.
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 it 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. See the terms and conditions for further information about how this tool uses data.
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.