360Giving Data Quality Tool

Common Errors

Invalid 'uri' found

This message means you have a problem, usually with a website address in your data.
Common mistakes include:

• Not starting the address with 'http://' e.g. example.com is not a 'uri' but http://example.com is.
• Having extra spaces at the start or end of the address - these should be removed
• Putting more than one address in the same field e.g. "http://example.com and http:example2.com" is not a 'uri'

Date is not in the correct format

Dates should be in the formats defined by the 360Giving Standard.

All Last Modified fields should be in datetime format (see below for further details)

All other dates should be in the YYYY-MM-DD format, or in datetime format.

Other common errors include

• providing non-existent dates e.g. 2016-02-31 (31st February)
• non-date content in a date field (by accident)

Datetimes format used for Last Modified fields

A datetime format is a very specific form of a date and time that is specified by the 360Giving Standard.

A datetime should be in the form of YYYY-MM-DDThh:mm:ss±hh:mm where:

• YYYY represent a year e.g. 2016
• MM represents a 2 digit month of the year e.g. 01 for January
• DD represents a 2 digit day of the month e.g. 01 for the 1st
• T is simply the letter 'T'
• hh is a 2 digit representation of an hour e.g. 01 for 1AM, 13 for 1PM
• mm is a 2 digit representation of minutes in an hour e.g. 05 for 5 past
• ss is a 2 digit representation of seconds
• +hh:mm or -hh:mm is a timezone offset from UTC. For most UK data producers this can simply be replaced with a 'Z'

Example: 2016-05-15T12:00:00Z is 12 noon on the 15th May 2016 in UTC time

Read further guidance about date and datetime fields and formatting tips when publishing using spreadsheets.

(something) is missing but is required

Many fields are required in the 360Giving data standard in order for others to make sense of the data supplied

If any of the following fields are missing the data is seen as invalid against the schema.

Field	JSON value	Notes	Documentation
Amount Awarded	amountAwarded	Every grant needs to specify the amount of money awarded
Award Date	awardDate	Every grant needs to specify the date that it was awarded.	Dates
Currency	currency	Every grant needs to specify the currency that the grant was made in.
Description	description	Every grant needs a human readable description.
Identifier	id	Every grant needs a unique identifier so we can tell them apart	Grant Identifiers
Funding Org	fundingOrganization	Every grant needs a funding organisation that makes the award.
Funding Org:Identifier	fundingOrganization/id	Every organisation needs a unique identifier so we can tell them apart..	Organisation Identifiers
Funding Org:Name	fundingOrganization/name	Every organisation needs a human readable name.
Recipient Org	recipientOrganization	Every grant needs a to specify an organisation to which the grant is awarded.
Recipient Org:Identifier	recipientOrganization/id	Every organisation a unique identifier so we can tell them apart.	Organisation Identifiers
Recipient Org:Name	recipientOrganization/name	Every organisation needs a human readable name.
Title	title	Every grant needs a human readable title.

Invalid code found in (something)

In 360Giving data when we talk about currencies, countries and organisation types we ask publishers to use values from a predefined list. When we ask whether or not this grant was from an open call we expect either 'yes' or no' and nothing else. When we validate people's data, we check the values of those fields against those lists.

This error tells us that we have found something not on the list.

The lists are referenced in the 360Giving Grants Schema. See 360Giving JSON Schemas for more information.

Field x is not a string

Data in the standard is expected to be provided in a certain format.

Strings are generally text, but can contain other characters such as numbers. Sometimes spreadsheet software can alter the format of data so that it is no longer a string.

To fix these kinds of errors, check the field to make sure you are supplying a string.

Value is not a number

Field x is not a number

Data in the standard is expected to be provided in a certain format.

To fix these kinds of errors, check the field to make sure you are supplying a number.