Reference¶
This page provides reference information on publishing to the 360Giving Data Standard.
It assumes some technical knowledge.
If you are just getting started with the 360Giving Data Standard, visit the guidance for publishers section.
Data formats¶
There are two main formats available for representing 360Giving data.
Spreadsheet
Data placed in a spreadsheet can make use of easy to read, user-friendly column titles, and is ideal for recording one grant per row. This is the most common format that publishers choose. More complex representations of data can also be reported if required.
JSON
Data in JSON format is ideal for direct use by developers building visualisations and web apps. The JSON should conform to the 360Giving JSON Schemas. Anyone automating the publication of their data from their internal databases or via an API may favour this format. The column titles used in spreadsheet representations of data are derived directly from the 360Giving JSON Schemas.
You can use the 360Giving Data Quality Tool to convert data between these formats, providing structured data for developers, and spreadsheet simplicity if you want to browse, sort and filter data on your desktop.
Spreadsheet format¶
To produce 360Giving data in a spreadsheet, it is possible to start with an empty spreadsheet and construct the column titles (and any additional sheets), using the information given below. However, for many people, the starting point is the spreadsheet template described below.
Spreadsheet template¶
For convenience we provide a 360Giving Spreadsheet Template that can be used directly, or adapted to your needs. The spreadsheet template provided is Excel Workbook file type (.xlsx) but may be converted into OpenDocument Spreadsheet file type (.ods) for publication and use if preferred. Comma-separated value file (.csv) versions are also available.
The Excel template is a multi-sheet spreadsheet, and each sheet is described below. The Comma-separated value (CSV) templates correspond to each sheet of the Excel template.
Many data producers will be able to fit all the information about a single grant on one row of a spreadsheet. In fact most data producers do exactly that, and provide a single sheet with many individual grants.
Where data producers have more complex information, for example where a grant has many beneficiary locations, we call this a ‘one to many relationship‘. Information about how to create data with One to many relationships is described below.
The 360Giving Spreadsheet template consists of a ‘grants‘ sheet which contains the most common data fields and fourteen sheets which cover the Additional fields sections.
The Additional fields section provides details of all other possible fields that can be reported. (These are derived from the 360Giving JSON Schemas).
Meta Sheet¶
We also provide a version of the 360Giving Spreadsheet Template with the Metadata template included. The ‘Meta‘ sheet may be used to publish authoritative metadata about the publisher, the file or dataset. The term we use for this is a ‘data package‘. The ‘Meta‘ sheet includes sections for:
- The version of the 360Giving Schema used for the file
- The title and description of the file
- The dates when the file was first issued and last modified
- Information about the publisher such as name, logo, website and identifier
- Links to access and download the file
- A link for the open license that applies to the file
You can read further guidance about how to include metadata in your data files in the Metadata guidance.
| Title | Description | Type | Required |
|---|---|---|---|
| Grants | array[object] | False | |
| Version | The version of the 360Giving schema used in this package, expressed as major.minor For example: 1.1 | string | False |
| Title | The title of the 360Giving data package. Should be a human readable version of information contained in the filename of the data and should be unique | string | False |
| Description | Full description of the information contained in the 360Giving data package. | string | False |
| Issued | The date that this data package was issued. The date must be written as YYYY-MM-DD, or in full date-time format | string | False |
| Modified | The date that this data package was last modified. A full date-time format must be used. | string | False |
| Identifier | A unique identifier for this data package. This should be unique for a particular publisher. | string | False |
| Publisher:Identifier | The organisation identifier as described by Organisation Identifier Standard | string | False |
| Publisher:Name | The name of the entity responsible for publishing this data. | string | True |
| Publisher:Website | URL of the website of the publishing entity. | uri | False |
| Publisher:Logo | URL of the logo of the publishing entity. | uri | False |
| Download URL | URL of where this data package can be downloaded. | uri | False |
| Access URL | URL of the website where this data package can be found. | uri | False |
| License | A link to the license that applies to the data in this package. A Public Domain Dedication or Open Definition Conformant license is strongly recommended. The canonical URI of the license should be used. Documents linked from this file may be under other license conditions. | uri | False |
Grants Sheet¶
The main ‘grants‘ sheet includes sections for:
- Basic information about the grant;
- Planned dates for the grant;
- Details of the recipient organisation or recipient individual;
- Details of the funding organisation;
- The location of beneficiaries;
- Details of the grant programme funding is from;
The main grants sheet also includes fields for including codes to indicate:
- Grants intended for redistribution
- The grant purpose and grant reason for grants to individuals
- The location scope of the grant
For further information read our Guide to codelists.
10 required fields¶
360Giving Data Standard can be used to publish data about grants awarded to organisations or individuals.
All 360Giving data must include 10 required fields of information, and eight of these are consistent to all types of grantmaking:
- Identifier
- Title
- Description
- Currency
- Amount Awarded
- Award Date
- Funding Org:Identifier
- Funding Org:Name
The remaining two required fields are different depending on whether the recipient of the grant is an organisation or an individual.
If the recipient is an organisation:
- Recipient Org:Identifier
- Recipient Org:Name
If the recipient is an individual:
- Recipient Ind:Identifier
- Recipient Ind:Name
Hint
The fields are titled Recipient Ind:Identifier and Recipient Ind:Name however the data shared about individual recipients is expected to be anonymous, with no personal data included that could allow the recipient to be identified.
Each grant record can have EITHER an organisation OR an individual recipient, not both.
If the recipient is an organisation, in addition to the two required fields there is other useful information that can be shared about the organisation, such as charity and company numbers, website address, postcode, description.
If the recipient is an individual there are no additional fields of information about the individual. However further detail about the grant can be provided using specific codelists: Grant to Individuals Purpose and Grant to Individuals Reason.
For further information read our Guide to codelists.
Grants Sheet Table¶
| Title | Description | Type | Required |
|---|---|---|---|
| Identifier | The unique identifier for this grant. Made up of your 360Giving prefix, and an identifier from your records. See the 360Giving Grant identifier guidance for details. | string | False |
| Title | A title for this grant activity. This should be under 140 characters long. | string | False |
| Description | A short description of this grant activity. | string | False |
| Currency | The currency used in amounts. Use the three-letter currency code from ISO 4217 eg: Use GBP for Pounds Sterling. | string | False |
| Amount Applied For | Total amount applied for in numbers (do not include commas or currency symbols such as £). If you have provided detailed transaction information on a separate table, this should equal the sum of all the application transactions for this grant. | number | False |
| Amount Awarded | Total amount awarded in numbers (do not include commas or currency symbols such as £). If you have provided detailed transaction information on a separate table, this should equal the sum of all the award transactions for this grant. | number | False |
| Amount Disbursed | Total amount disbursed (paid) to this grantee when this record was last updated (in numbers: do not include commas or currency symbols such as £)). If you have provided detailed transaction information on a separate table, this should equal the sum of all the disbursement transactions for this grant. | number | False |
| Award Date | When the decision to award this grant was made. The date must be written as YYYY-MM-DD, or in full date-time format. | string | False |
| URL | A URL (Web Address) where further information about this grant can be found. This could point to the website of the recipient organisation, or might link to further details on the funders website. | uri | False |
| Planned Dates:Start Date | All events should have a start date. Dates must be in YYYY-MM-DD or date-time format. If the month or day are not available, these may be omitted. | string | False |
| Planned Dates:End Date | An end date for the grant. Dates must be in YYYY-MM-DD or date-time format. If the month or day are not available, these may be omitted. | string | False |
| Planned Dates:Duration (months) | The duration of the grant, in months. Must be in number format. | number | False |
| Recipient Ind:Identifier | A unique identifier which identifies the person in the dataset | string | True |
| Recipient Ind:Name | The Person‘s full name or a generic name such as “Individual Recipient“ | string | True |
| To Individuals Details:Primary Grant Reason | A code referring to the reason(s) for a grant to an individual. The value for this field should be drawn from the Grant to Individuals Reason codelist | string | False |
| To Individuals Details:Secondary Grant Reason | A code referring to the reason(s) for a grant to an individual. The value for this field should be drawn from the Grant to Individuals Reason codelist | string | False |
| To Individuals Details:Grant Purpose | A code referring to the purpose(s) for a grant to an individual. The value(s) for this field should be drawn from the Grant to Individuals Purpose codelist | array[string] | False |
| Recipient Org:Identifier | A globally unique identifier for this organisation. This is important to enable data on funders and recipients to be linked up across different grant-makers. The Organisation Identifier Standard guidance explains how to create this ID, based either on the known company or charity number, or upon identifiers held in the grantmaker‘s internal systems. | string | True |
| Recipient Org:Name | Organisation name | string | True |
| Recipient Org:Charity Number | Registered charity number, if applicable. | string | False |
| Recipient Org:Company Number | Registered UK company number, if applicable. | string | False |
| Recipient Org:Street Address | Organisation address building number and street name. | string | False |
| Recipient Org:City | Organisation address city or town. | string | False |
| Recipient Org:County | Organisation address county | string | False |
| Recipient Org:Country | Organisation address country | string | False |
| Recipient Org:Postal Code | Organisation address postal code. | string | False |
| Recipient Org:Description | A short description of this organisation and its area of work | string | False |
| Recipient Org:Web Address | A web address for the Organisation | uri | False |
| Beneficiary Location:Name | A name for this location. | string | False |
| Beneficiary Location:Country Code | The 2-character ISO Country Code of the location of this activity. Taken from ISO-3166-1-alpha-2 | string | False |
| Beneficiary Location:Latitude | The latitude of a point location. Using WGS 84 standard, for example 51.501502 | number | False |
| Beneficiary Location:Longitude | The longitude of a point location. Using WGS 84 standard, for example -0.175269 | number | False |
| Beneficiary Location:Geographic Code | A code referring to a geographical area, drawn from an established gazetteer such as the ONS Register of Geographic Codes in the UK. For example, the code for a local authority ward, or parliamentary constituency. | string | False |
| Beneficiary Location:Geographic Code Type | The type of Geographic Code (geoCode) used (e.g. Ward, Parliamentary Constituency etc.). This value for this field should be drawn from the codelist of geographic code types. | string | False |
| Funding Org:Identifier | A globally unique identifier for this organisation. This is important to enable data on funders and recipients to be linked up across different grant-makers. The Organisation Identifier Standard guidance explains how to create this ID, based either on the known company or charity number, or upon identifiers held in the grantmaker‘s internal systems. | string | True |
| Funding Org:Name | Organisation name | string | True |
| Funding Org:Department | The department or sub-unit of this organisation making or receiving the grant. | string | False |
| Grant Programme:Code | An identifier for this grant programme. | string | False |
| Grant Programme:Title | The title of this grant programme. | string | False |
| Grant Programme:URL | A web link to more details of this grant programme. | uri | False |
| From An Open Call? | Was this grant made as the result of an open call for applications? Values must be ‘Yes‘ or ‘No‘ | string | False |
| Related Activity | The identifiers of any related activities (e.g. other grants given as part of a multi-grant project) | array[string] | False |
| Last Modified | When was information on this grant last updated? A full date-time format must be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
| Data Source | A web link pointing to the source of this data. This may be an original 360Giving data file, a file from which the data was converted, or an organisation website. | uri | False |
| For Regrant Type | A code referring to the type of regranting process that this grant represents. The value for this field should be drawn from the Regrant Type codelist | string | False |
| Location Scope | A code referring to the location scope applicable to this grant. The value for this field should be drawn from the Location Scope codelist. | string | False |
Additional fields¶
The main ‘grants‘ sheet only includes the most common information used by most data publishers. For many people this is enough.
The other sheets in the 360Giving Spreadsheet Template provide the details of all the possible fields that can be reported. These sheets serve a dual purpose:
As a way to add more information about the grants
The column titles in the extra sheets provide a handy mapping from the JSON Schema to a more human readable form, showing us all of the possible fields available in the 360Giving Data Standard.
You can use any of these column titles on your main ‘grants‘ sheet if you wish.
As a way of providing information about One to many relationships
If, when creating your data, you only need a few additional fields from the additional sheets, you can copy them from one sheet to the main ‘grants‘ sheet. Any additional sheets that aren‘t used can be deleted.
If you have additional data to report that does not fit any of the columns provided in the spreadsheet, it is okay to create your own column titles in order to report it.
Hint
Naming your own columns.
If you are adding your own column titles it is best to use simple titles and to avoid special characters which could cause problems in data reuse.
Using only lowercase and uppercase alphabetical characters (a-z and A-Z), numerical digits (0-9), colons (:), parentheses (( and )) and single spaces will help to avoid problems. Full-stops (.) are known to cause issues and should be avoided. Other characters could be used, but haven’t been fully tested in all possible situations. Contact 360Giving support with further queries about naming your own columns.
Actual Dates¶
When did this grant activity actually take place. Dates must be in YYYY-MM-DD or date-time format. A date range can include a start date and duration in months, or a start and end date.
| Title | Description | Type | Required |
|---|---|---|---|
| Actual Dates:Title | The title of this event | string | False |
| Actual Dates:Start Date | All events should have a start date. Dates must be in YYYY-MM-DD or date-time format. If the month or day are not available, these may be omitted. | string | False |
| Actual Dates:End Date | An end date for the grant. Dates must be in YYYY-MM-DD or date-time format. If the month or day are not available, these may be omitted. | string | False |
| Actual Dates:Duration (months) | The duration of the grant, in months. Must be in number format. | number | False |
| Actual Dates:Description | A description of this event | string | False |
| Actual Dates:Last Modified | When was information about this event last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Planned Dates¶
When the recipient organisation intends this activity to take place. A date range can include a start date and duration in months, or a start and end date.
| Title | Description | Type | Required |
|---|---|---|---|
| Planned Dates:Title | The title of this event | string | False |
| Planned Dates:Start Date | All events should have a start date. Dates must be in YYYY-MM-DD or date-time format. If the month or day are not available, these may be omitted. | string | False |
| Planned Dates:End Date | An end date for the grant. Dates must be in YYYY-MM-DD or date-time format. If the month or day are not available, these may be omitted. | string | False |
| Planned Dates:Duration (months) | The duration of the grant, in months. Must be in number format. | number | False |
| Planned Dates:Description | A description of this event | string | False |
| Planned Dates:Last Modified | When was information about this event last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Funding Org¶
Details of the funder
| Title | Description | Type | Required |
|---|---|---|---|
| Funding Org:Identifier | A globally unique identifier for this organisation. This is important to enable data on funders and recipients to be linked up across different grant-makers. The Organisation Identifier Standard guidance explains how to create this ID, based either on the known company or charity number, or upon identifiers held in the grantmaker‘s internal systems. | string | True |
| Funding Org:Name | Organisation name | string | True |
| Funding Org:Department | The department or sub-unit of this organisation making or receiving the grant. | string | False |
| Funding Org:Contact Name | The contact person at this organisation. | string | False |
| Funding Org:Charity Number | Registered charity number, if applicable. | string | False |
| Funding Org:Company Number | Registered UK company number, if applicable. | string | False |
| Funding Org:Street Address | Organisation address building number and street name. | string | False |
| Funding Org:City | Organisation address city or town. | string | False |
| Funding Org:County | Organisation address county | string | False |
| Funding Org:Country | Organisation address country | string | False |
| Funding Org:Postal Code | Organisation address postal code. | string | False |
| Funding Org:Phone Number | Contact phone number. | string | False |
| Funding Org:Alternate Name | An alternative name for this organisation (e.g. trading name) | string | False |
| Funding Org:Email | The email address for this organisation. | string | False |
| Funding Org:Description | A short description of this organisation and its area of work | string | False |
| Funding Org:Organisation Type | A description of this organisation | string | False |
| Funding Org:Web Address | A web address for the Organisation | uri | False |
| Funding Org:Last Modified | When was the organisation information for this grant last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Recipient Org¶
Details of the recipient of this grant.
| Title | Description | Type | Required |
|---|---|---|---|
| Recipient Org:Identifier | A globally unique identifier for this organisation. This is important to enable data on funders and recipients to be linked up across different grant-makers. The Organisation Identifier Standard guidance explains how to create this ID, based either on the known company or charity number, or upon identifiers held in the grantmaker‘s internal systems. | string | True |
| Recipient Org:Name | Organisation name | string | True |
| Recipient Org:Department | The department or sub-unit of this organisation making or receiving the grant. | string | False |
| Recipient Org:Contact Name | The contact person at this organisation. | string | False |
| Recipient Org:Charity Number | Registered charity number, if applicable. | string | False |
| Recipient Org:Company Number | Registered UK company number, if applicable. | string | False |
| Recipient Org:Street Address | Organisation address building number and street name. | string | False |
| Recipient Org:City | Organisation address city or town. | string | False |
| Recipient Org:County | Organisation address county | string | False |
| Recipient Org:Country | Organisation address country | string | False |
| Recipient Org:Postal Code | Organisation address postal code. | string | False |
| Recipient Org:Phone Number | Contact phone number. | string | False |
| Recipient Org:Alternate Name | An alternative name for this organisation (e.g. trading name) | string | False |
| Recipient Org:Email | The email address for this organisation. | string | False |
| Recipient Org:Description | A short description of this organisation and its area of work | string | False |
| Recipient Org:Organisation Type | A description of this organisation | string | False |
| Recipient Org:Web Address | A web address for the Organisation | uri | False |
| Recipient Org:Last Modified | When was the organisation information for this grant last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Beneficiary Location¶
Information about the location of beneficiaries. Further information about beneficiaries can be provided through classifications.
| Title | Description | Type | Required |
|---|---|---|---|
| Beneficiary Location:Identifier | Location identifier | string | False |
| Beneficiary Location:Name | A name for this location. | string | False |
| Beneficiary Location:Country Code | The 2-character ISO Country Code of the location of this activity. Taken from ISO-3166-1-alpha-2 | string | False |
| Beneficiary Location:Latitude | The latitude of a point location. Using WGS 84 standard, for example 51.501502 | number | False |
| Beneficiary Location:Longitude | The longitude of a point location. Using WGS 84 standard, for example -0.175269 | number | False |
| Beneficiary Location:Description | A description of this location. This could include details of the element of the activity that takes place here. | string | False |
| Beneficiary Location:Geographic Code | A code referring to a geographical area, drawn from an established gazetteer such as the ONS Register of Geographic Codes in the UK. For example, the code for a local authority ward, or parliamentary constituency. | string | False |
| Beneficiary Location:Geographic Code Type | The type of Geographic Code (geoCode) used (e.g. Ward, Parliamentary Constituency etc.). This value for this field should be drawn from the codelist of geographic code types. | string | False |
| Beneficiary Location:Last Modified | When was this location information last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Funding Org:Location¶
Information about the location of the organisation.
| Title | Description | Type | Required |
|---|---|---|---|
| Funding Org:Location:Identifier | Location identifier | string | False |
| Funding Org:Location:Name | A name for this location. | string | False |
| Funding Org:Location:Country Code | The 2-character ISO Country Code of the location of this activity. Taken from ISO-3166-1-alpha-2 | string | False |
| Funding Org:Location:Latitude | The latitude of a point location. Using WGS 84 standard, for example 51.501502 | number | False |
| Funding Org:Location:Longitude | The longitude of a point location. Using WGS 84 standard, for example -0.175269 | number | False |
| Funding Org:Location:Description | A description of this location. This could include details of the element of the activity that takes place here. | string | False |
| Funding Org:Location:Geographic Code | A code referring to a geographical area, drawn from an established gazetteer such as the ONS Register of Geographic Codes in the UK. For example, the code for a local authority ward, or parliamentary constituency. | string | False |
| Funding Org:Location:Geographic Code Type | The type of Geographic Code (geoCode) used (e.g. Ward, Parliamentary Constituency etc.). This value for this field should be drawn from the codelist of geographic code types. | string | False |
| Funding Org:Location:Last Modified | When was this location information last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Recipient Org:Location¶
Information about the location of the organisation.
| Title | Description | Type | Required |
|---|---|---|---|
| Recipient Org:Location:Identifier | Location identifier | string | False |
| Recipient Org:Location:Name | A name for this location. | string | False |
| Recipient Org:Location:Country Code | The 2-character ISO Country Code of the location of this activity. Taken from ISO-3166-1-alpha-2 | string | False |
| Recipient Org:Location:Latitude | The latitude of a point location. Using WGS 84 standard, for example 51.501502 | number | False |
| Recipient Org:Location:Longitude | The longitude of a point location. Using WGS 84 standard, for example -0.175269 | number | False |
| Recipient Org:Location:Description | A description of this location. This could include details of the element of the activity that takes place here. | string | False |
| Recipient Org:Location:Geographic Code | A code referring to a geographical area, drawn from an established gazetteer such as the ONS Register of Geographic Codes in the UK. For example, the code for a local authority ward, or parliamentary constituency. | string | False |
| Recipient Org:Location:Geographic Code Type | The type of Geographic Code (geoCode) used (e.g. Ward, Parliamentary Constituency etc.). This value for this field should be drawn from the codelist of geographic code types. | string | False |
| Recipient Org:Location:Last Modified | When was this location information last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Classifications¶
Information about a classification associated with the grant
| Title | Description | Type | Required |
|---|---|---|---|
| Classifications:Vocabulary | A vocabulary used for this classification. | string | False |
| Classifications:Code | A codelist value in the chosen vocabulary. | string | False |
| Classifications:Title | The title of this classification. | string | False |
| Classifications:Description | A description of this classification. | string | False |
| Classifications:URL | A web link to more details of this classification. | uri | False |
| Classifications:Last Modified | When was this grant classification information last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Funding Type¶
Information about the type of funding provided by the grant
| Title | Description | Type | Required |
|---|---|---|---|
| Funding Type:Vocabulary | A vocabulary used for this classification. | string | False |
| Funding Type:Code | A codelist value in the chosen vocabulary. | string | False |
| Funding Type:Title | The title of this classification. | string | False |
| Funding Type:Description | A description of this classification. | string | False |
| Funding Type:URL | A web link to more details of this classification. | uri | False |
| Funding Type:Last Modified | When was this grant classification information last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Grant Programme¶
Information about the grant programme under which the grant was awarded
| Title | Description | Type | Required |
|---|---|---|---|
| Grant Programme:Code | An identifier for this grant programme. | string | False |
| Grant Programme:Title | The title of this grant programme. | string | False |
| Grant Programme:Description | A description of this grant programme. | string | False |
| Grant Programme:URL | A web link to more details of this grant programme. | uri | False |
| Grant Programme:Last Modified | When was the link between this grant and its grant programme last modified? A full date-time should be given. Usually this can be generated automatically by the software managing or exporting this data. | date-time | False |
Transactions¶
The 360Giving Data Standard also allows for the reporting of three types of transactions:
- commitmentTransaction
- disbursementTransaction
- applicationTransaction
These do not currently have the more user friendly human readable titles, but can still be added as spreadsheet columns if needed.
To create the column titles, refer to the 360Giving JSON Schema and use the JSON pointer paths as column titles. e.g. commitmentTransaction/0/id
One to many relationships¶
Each of the sections of additional fields above can have multiple occurrences for one grant. There are three ways of describing this in a spreadsheet.
Additional sheets¶
Use the other sheets in the 360Giving Spreadsheet Template. These have the columns described above, plus an extra column at the start for the Identifier of the relevant grant.
For the Funding Org: Location and Recipient Org: Location there is also an extra column for the Identifier of the relevant Funding or Recipient Org.
Numbering¶
You can describe multiple occurrences within the Grants sheet by having multiple columns. Use :<num>: instead of a :. This imitates JSON Pointer‘s approach.
e.g. to have two related documents with their own title and web address:
| Related Document:0:Title | Related Document:0:Web Address | Related Document:1:Title | Related:Document:1:Web Address |
| A Document | http://example.com/adocument | Another Document | http://example.com/anotherdocument |
Multiple Rows¶
There may be cases where you need to release additional information about a grant in a new row, or you can’t update the row where the grant is originally described. In these cases, use the same Identifier for the grant, and place the additional information in a new row under the relevant columns. You should only add new information, because consuming applications may try to merge the information into a single record. So placing contradictory information in fields that cannot have more than one value will result in a validation error.
Original row:
| Identifier | Title | … (other columns) | Amount Disbursed |
| 360G-xyztrust-123 | An example grant title | … |
The new row:
| Identifier | Title | … (other columns) | Amount Disbursed |
| 360G-xyztrust-123 | … | 2500 |
In the second row, the fields which were originally populated with information are left blank so as to avoid conflicts, and the additional information is added to the “Amount Disbursed“ column. This means the multiple rows method can only be used to add new data, and it is not suitable for amending data that has already been published.
Field guidance¶
Field guidance provides further useful information about fields in the 360Giving Data Standard. It provides guidance about the correct data formatting to use and some examples of how to apply the formatting when using spreadsheets.
Dates and times¶
The 360Giving Data Standard requires you to provide information on when a grant was awarded, and allows you to add details of when a project is taking place, and when you last updated information about aspects of the grant.
There are three different rules for validating dates:
Full dates (Award Dates and Transaction Dates)¶
The Award Date must provide a full date, including year, month and day in YYYY-MM-DD format (e.g. 2017-04-02 for the 2nd April 2017).
In some cases, award date data exported from grant systems includes the time of the grant, using a date-time format (e.g. 2017-04-02T16:45:00Z - a grant made at 4.45pm).
Note - The time component is never significant in Award Dates or Transaction Dates. Applications should ignore the time component when processing grants data.
Hint
You can set Excel to present a date column in YYYY-MM-DD format using a custom format as described here.
Uncertain dates (Planned Dates and Actual Dates)¶
Other events in the lifetime of a grant, such as for when the funded activity will take place, may include less specific date information. Funders should aim to be as specific as they can be, but do not need to guess at the particular day or month when an activity will take place if they are not certain or do not yet know.
Dates in the Planned Dates and Actual Dates groups should be provided in YYYY-MM-DD format, but the day or the day can be dropped or on the year provided (e.g. YYYY-MM or YYYY).
For example, if an application only indicates that a project will start in May 2019, then the Planned Dates:Start Date value may be ‘2019-05‘.
It is up to users of the data to judge how to interpret dates which only include a year, or year and month. Different applications and analysis may require different judgements.
Date-time (Last Modified dates)¶
All rows in a 360Giving spreadsheet, and all objects in the JSON structure, can have a Last Modified date.
If used, this must always be in full date-time format so that if multiple updates take place on a single day, consuming applications can work out which version to use.
Hint
You can set Excel to present a date column as a full date-time using the custom format of “yyyy-mm-ddThh:mm:ssZ”. If you also set the formula for the entire column to `=Now()` then this value will be refreshed automatically every time you save the file.
Conformance¶
In order to conform with the spreadsheet standard:
You must:
- Read the column definitions carefully and follow the format they request - for example, formatting identifiers and dates according to the standard. Full reference information is provided below.
- Provide an Identifier for each grant
- Update the Last Modified date whenever the status of a grant changes
You can:
- Remove or hide non-required columns that you are not using - although make sure you check for any hidden columns before publishing your data, and always remove rather than hide sensitive information.
- Re-order the columns so that information is arranged in the way you want
- Add extra columns to include information you want to share, but that is not covered by the standard. (See additional fields).
- Move columns in the 360Giving Spreadsheet Template between sheets.
You must not:
- Add extra rows at the top of the table
- Change the field names provided by the 360Giving Data Standard
JSON format¶
The 360Giving Data Standard is defined by a JSON Schema, which details the entities that can be described using the standard, and the properties it recognises.
At the root of the data model is a ‘grant‘. Grants have a number of direct properties (e.g. Title, Description, Currency, Amount Awarded etc.) and then a number of related entities, including Organisations (Funder and Recipient) or Individuals (Recipient), Locations (Recipient, Beneficiary, Funder), Classifications, Grant Programmes, and Transactions.
360Giving JSON Schemas¶
The 360Giving JSON Schemas are the authoritative source of information about the 360Giving Data Standard, and it should always be possible to transform 360Giving data into structured JSON data according to these schemas.
The 360Giving Grant Schema defines the structure of an individual ‘grant‘ and the documentation from this is displayed below, or fullscreen here.
When exchanging data about a single grant or any number of grants, those grants need to be packaged into a single JSON file. This is to ensure that the way the grant data may be consumed remains consistent regardless of whether there are 10 grants or 10,000 grants. The 360Giving Package Schema describes how grants are packaged into one file and may be used to publish authoritative metadata about the publisher, the file or dataset (not the grants). Metadata is declared using the fields in the package schema (except for “grants“ field, which contains a list of grant data).
In general, most publishers will use a subset of the possible features of the 360Giving Data Standard, but it is designed to accommodate comprehensive data about all stages of a grant process: for a full 360-degree view.
Field names and titles¶
Each entity, property and relationship in the 360Giving Data Standard Schema and 360Giving Package Schema has both a machine-readable field name and an English language title (apart from Transactions in the 360Giving Data Standard Schema).
The English language titles are important for humans working to make sense of the data in everyday desktop software, and so the Spreadsheet Template and the documentation above makes use of titles as opposed to field names.
The field names are important for computers reading the data, and if other language titles are provided in future, the underlying field names will remain constant.
A mapping between column titles and field names for each schema is given below:
360Giving Package Schema (incorporating Metadata)¶
| Title | Name | Type |
|---|---|---|
| Grants | grants | array[object] |
| Version | version | string |
| Title | title | string |
| Description | description | string |
| Issued | issued | string |
| Modified | modified | string |
| Identifier | identifier | string |
| Publisher:Identifier | publisher/identifier | string |
| Publisher:Name | publisher/name | string |
| Publisher:Website | publisher/website | uri |
| Publisher:Logo | publisher/logo | uri |
| Download URL | downloadURL | uri |
| Access URL | accessURL | uri |
| License | license | uri |
360Giving Data Standard Schema¶
| Title | Name | Type |
|---|---|---|
| Identifier | id | string |
| Title | title | string |
| Description | description | string |
| Currency | currency | string |
| Amount Applied For | amountAppliedFor | number |
| Amount Awarded | amountAwarded | number |
| Amount Disbursed | amountDisbursed | number |
| Award Date | awardDate | string |
| URL | url | uri |
| Planned Dates:Title | plannedDates/0/title | string |
| Planned Dates:Start Date | plannedDates/0/startDate | string |
| Planned Dates:End Date | plannedDates/0/endDate | string |
| Planned Dates:Duration (months) | plannedDates/0/duration | number |
| Planned Dates:Description | plannedDates/0/description | string |
| Planned Dates:Last Modified | plannedDates/0/dateModified | date-time |
| Actual Dates:Title | actualDates/0/title | string |
| Actual Dates:Start Date | actualDates/0/startDate | string |
| Actual Dates:End Date | actualDates/0/endDate | string |
| Actual Dates:Duration (months) | actualDates/0/duration | number |
| Actual Dates:Description | actualDates/0/description | string |
| Actual Dates:Last Modified | actualDates/0/dateModified | date-time |
| Recipient Ind:Identifier | recipientIndividual/id | string |
| Recipient Ind:Name | recipientIndividual/name | string |
| To Individuals Details:Primary Grant Reason | toIndividualsDetails/primaryGrantReason | string |
| To Individuals Details:Secondary Grant Reason | toIndividualsDetails/secondaryGrantReason | string |
| To Individuals Details:Grant Purpose | toIndividualsDetails/grantPurpose | array[string] |
| Recipient Org:Identifier | recipientOrganization/0/id | string |
| Recipient Org:Name | recipientOrganization/0/name | string |
| Recipient Org:Department | recipientOrganization/0/department | string |
| Recipient Org:Contact Name | recipientOrganization/0/contactName | string |
| Recipient Org:Charity Number | recipientOrganization/0/charityNumber | string |
| Recipient Org:Company Number | recipientOrganization/0/companyNumber | string |
| Recipient Org:Street Address | recipientOrganization/0/streetAddress | string |
| Recipient Org:City | recipientOrganization/0/addressLocality | string |
| Recipient Org:County | recipientOrganization/0/addressRegion | string |
| Recipient Org:Country | recipientOrganization/0/addressCountry | string |
| Recipient Org:Postal Code | recipientOrganization/0/postalCode | string |
| Recipient Org:Phone Number | recipientOrganization/0/telephone | string |
| Recipient Org:Alternate Name | recipientOrganization/0/alternateName | string |
| Recipient Org:Email | recipientOrganization/0/email | string |
| Recipient Org:Description | recipientOrganization/0/description | string |
| Recipient Org:Organisation Type | recipientOrganization/0/organisationType | string |
| Recipient Org:Web Address | recipientOrganization/0/url | uri |
| Recipient Org:Location:Identifier | recipientOrganization/0/location/0/id | string |
| Recipient Org:Location:Name | recipientOrganization/0/location/0/name | string |
| Recipient Org:Location:Country Code | recipientOrganization/0/location/0/countryCode | string |
| Recipient Org:Location:Latitude | recipientOrganization/0/location/0/latitude | number |
| Recipient Org:Location:Longitude | recipientOrganization/0/location/0/longitude | number |
| Recipient Org:Location:Description | recipientOrganization/0/location/0/description | string |
| Recipient Org:Location:Geographic Code | recipientOrganization/0/location/0/geoCode | string |
| Recipient Org:Location:Geographic Code Type | recipientOrganization/0/location/0/geoCodeType | string |
| Recipient Org:Location:Last Modified | recipientOrganization/0/location/0/dateModified | date-time |
| Recipient Org:Last Modified | recipientOrganization/0/dateModified | date-time |
| Beneficiary Location:Identifier | beneficiaryLocation/0/id | string |
| Beneficiary Location:Name | beneficiaryLocation/0/name | string |
| Beneficiary Location:Country Code | beneficiaryLocation/0/countryCode | string |
| Beneficiary Location:Latitude | beneficiaryLocation/0/latitude | number |
| Beneficiary Location:Longitude | beneficiaryLocation/0/longitude | number |
| Beneficiary Location:Description | beneficiaryLocation/0/description | string |
| Beneficiary Location:Geographic Code | beneficiaryLocation/0/geoCode | string |
| Beneficiary Location:Geographic Code Type | beneficiaryLocation/0/geoCodeType | string |
| Beneficiary Location:Last Modified | beneficiaryLocation/0/dateModified | date-time |
| Funding Org:Identifier | fundingOrganization/0/id | string |
| Funding Org:Name | fundingOrganization/0/name | string |
| Funding Org:Department | fundingOrganization/0/department | string |
| Funding Org:Contact Name | fundingOrganization/0/contactName | string |
| Funding Org:Charity Number | fundingOrganization/0/charityNumber | string |
| Funding Org:Company Number | fundingOrganization/0/companyNumber | string |
| Funding Org:Street Address | fundingOrganization/0/streetAddress | string |
| Funding Org:City | fundingOrganization/0/addressLocality | string |
| Funding Org:County | fundingOrganization/0/addressRegion | string |
| Funding Org:Country | fundingOrganization/0/addressCountry | string |
| Funding Org:Postal Code | fundingOrganization/0/postalCode | string |
| Funding Org:Phone Number | fundingOrganization/0/telephone | string |
| Funding Org:Alternate Name | fundingOrganization/0/alternateName | string |
| Funding Org:Email | fundingOrganization/0/email | string |
| Funding Org:Description | fundingOrganization/0/description | string |
| Funding Org:Organisation Type | fundingOrganization/0/organisationType | string |
| Funding Org:Web Address | fundingOrganization/0/url | uri |
| Funding Org:Location:Identifier | fundingOrganization/0/location/0/id | string |
| Funding Org:Location:Name | fundingOrganization/0/location/0/name | string |
| Funding Org:Location:Country Code | fundingOrganization/0/location/0/countryCode | string |
| Funding Org:Location:Latitude | fundingOrganization/0/location/0/latitude | number |
| Funding Org:Location:Longitude | fundingOrganization/0/location/0/longitude | number |
| Funding Org:Location:Description | fundingOrganization/0/location/0/description | string |
| Funding Org:Location:Geographic Code | fundingOrganization/0/location/0/geoCode | string |
| Funding Org:Location:Geographic Code Type | fundingOrganization/0/location/0/geoCodeType | string |
| Funding Org:Location:Last Modified | fundingOrganization/0/location/0/dateModified | date-time |
| Funding Org:Last Modified | fundingOrganization/0/dateModified | date-time |
| Grant Programme:Code | grantProgramme/0/code | string |
| Grant Programme:Title | grantProgramme/0/title | string |
| Grant Programme:Description | grantProgramme/0/description | string |
| Grant Programme:URL | grantProgramme/0/url | uri |
| Grant Programme:Last Modified | grantProgramme/0/dateModified | date-time |
| From An Open Call? | fromOpenCall | string |
| Funding Type:Vocabulary | fundingType/0/vocabulary | string |
| Funding Type:Code | fundingType/0/code | string |
| Funding Type:Title | fundingType/0/title | string |
| Funding Type:Description | fundingType/0/description | string |
| Funding Type:URL | fundingType/0/url | uri |
| Funding Type:Last Modified | fundingType/0/dateModified | date-time |
| Classifications:Vocabulary | classifications/0/vocabulary | string |
| Classifications:Code | classifications/0/code | string |
| Classifications:Title | classifications/0/title | string |
| Classifications:Description | classifications/0/description | string |
| Classifications:URL | classifications/0/url | uri |
| Classifications:Last Modified | classifications/0/dateModified | date-time |
| Related Document:Identifier | relatedDocument/0/id | string |
| Related Document:Title | relatedDocument/0/title | string |
| Related Document:Web Address | relatedDocument/0/url | uri |
| Related Document:Description | relatedDocument/0/description | string |
| Related Document:Document Type | relatedDocument/0/documentType | string |
| Related Document:Last Modified | relatedDocument/0/dateModified | date-time |
| None | applicationTransaction/0/id | string |
| None | applicationTransaction/0/transactionDate | string |
| None | applicationTransaction/0/currency | string |
| None | applicationTransaction/0/value | number |
| None | applicationTransaction/0/valueDate | string |
| None | applicationTransaction/0/description | string |
| None | applicationTransaction/0/provider | string |
| None | applicationTransaction/0/recipient | string |
| None | applicationTransaction/0/dateModified | date-time |
| None | commitmentTransaction/0/id | string |
| None | commitmentTransaction/0/transactionDate | string |
| None | commitmentTransaction/0/currency | string |
| None | commitmentTransaction/0/value | number |
| None | commitmentTransaction/0/valueDate | string |
| None | commitmentTransaction/0/description | string |
| None | commitmentTransaction/0/provider | string |
| None | commitmentTransaction/0/recipient | string |
| None | commitmentTransaction/0/dateModified | date-time |
| None | disbursementTransaction/0/id | string |
| None | disbursementTransaction/0/transactionDate | string |
| None | disbursementTransaction/0/currency | string |
| None | disbursementTransaction/0/value | number |
| None | disbursementTransaction/0/valueDate | string |
| None | disbursementTransaction/0/description | string |
| None | disbursementTransaction/0/provider | string |
| None | disbursementTransaction/0/recipient | string |
| None | disbursementTransaction/0/dateModified | date-time |
| Related Activity | relatedActivity | array[string] |
| Last Modified | dateModified | date-time |
| Data Source | dataSource | uri |
| For Regrant Type | regrantType | string |
| Location Scope | locationScope | string |
JSON¶
When data is being generated directly out of a database system, publishers should consider using the JSON schema to provide a JSON file.
Developers may also wish to build their applications of JSON versions of the data.
The 360Giving Data Quality Tool supports conversion of data between the Spreadsheet Template and JSON representations.
Getting further help
This guidance aims to support funders through the 360Giving publishing process. If you can't find the information you need or you have further questions email 360Giving Helpdesk. You can help us improve this guidance by filling out our feedback form.