360Giving Datastore access
For users with more complex data needs, it is possible to directly access the 360Giving Datastore and run queries on it. Potential uses of the Datastore include:
- Creating a filtered dataset as raw data for a research project.
- Producing a bespoke dataset that can be regularly imported into a database powering a web app.
The Datastore is designed to facilitate one-off or repeating data transfers covering a large part of the 360Giving dataset.
How to get access to the 360Giving Datastore
- Fill in this form to register your interest in Datastore access and agree to the 360Giving Datastore code of conduct detailed below.
- Book a 1-1 Data Support call to discuss your needs and project so that we can help advise the best option for you.
- Once confirmed, Datastore access is usually provided through Google Colab python notebook, where we can supply database credentials that can run SQL queries against the Postgres database that holds the data.
Please note that a Google account is required for access to the Colab notebook.
360Giving Datastore code of conduct
360Giving Datastore access is a service from 360Giving and is offered as a resource to help users make the most of the data published by grantmakers. To ensure that the data is useful and available, we ask that 360Giving Datastore users follow the points set out below. If the code of conduct is not followed, then it may be necessary to revoke access.
Make appropriate requests
The 360Giving Datastore is designed for one-off or repeating bulk data requests from researchers and other technical users. Users should design their queries to be efficient with the resources and not make large numbers of requests for bulk data in a short space of time, or perform complex queries repeatedly. Talk to us about your plans for the data, and we’ll help you design an access pattern that meets your needs and is appropriate for the service.
Data is fetched every day, but most 360Giving publishers publish new data less frequently than that. For most purposes, checking for new data once a week would be sufficient.
The Datastore is not designed as a general-purpose API, so large numbers of small requests (for example, for one grant or based on one recipient organisation) are not appropriate uses of the service. The 360Giving API is designed to facilitate this instead.
Be mindful of security
The database credentials you will use will be specific to you and should be kept private. They will give read-only access to the database. The credentials supplied are not permanent and may be removed or replaced after a while (360Giving will contact you when this happens).
Respect licence conditions
360Giving publishers share an open licence for their data. This licence allows a range of different uses of their data, but there may be conditions attached. Most commonly, users of the data need to attribute and link to the data source (the publisher themselves).
Information about the licence under which each data item has been published and the source of the data is available in the Datastore itself and should be used to adhere to any licencing conditions, such as source attribution.
Attributing 360Giving
In addition to attributing the original data, you may wish to attribute the 360Giving Datastore as appropriate. However, the 360Giving logo should not be used without permission when referring to or using the 360Giving data.
Work with data publishers
The 360Giving Datastore is not the original source of the data, and should not be treated as such. For queries about individual published grants or the content of the data, it is generally most appropriate to contact the publisher of the original data. Information about the publisher of each item is included in a table in the database itself.
Use the latest data and respect take down requests
360Giving data changes regularly, and in addition to regularly adding data, publishers sometimes remove data from their files. Datastore users will not be notified of data being added or removed unless it forms part of a takedown request, so you must ensure that the data used is kept up to date in any applications of data taken from the Datastore.
360Giving has a take down policy for managing requests from publishers or others that data, or a portion of it, is removed from the 360Giving Registry and 360Giving online platforms.
The Take down policy sets out how 360Giving deals with these requests. You should also consider how you would respond to take down requests. 360Giving will inform Datastore users if a take down request is received.
Privacy Information
360Giving will collect certain data about you and your usage of the Datastore. This will include:
- Your name and email address, collected at registration
- Usage statistics on how you use the Datastore
We collect your personal data for the following purposes:
- Administering your account such as sending service updates to notify you of system maintenance or updates to the Datastore
- To notify you of take down requests
- Usage statistics for analytics and to monitor the performance of the Datastore to ensure a reliable and stable service for all users
Keep in touch
The Datastore exists to help people use 360Giving data, so please keep us informed of how you’re using it. We’d love to help you explore new ideas about what you can do with the data, and promote exciting and innovative projects that use the data. We also want feedback to make the Datastore and our other services better.