From 370dac24dd02b902bee0d6f10d3d0ed2b7713fd3 Mon Sep 17 00:00:00 2001 From: Matt Marshall Date: Fri, 7 Nov 2025 10:27:14 +0000 Subject: [PATCH 1/4] docs: remove links to Registry See https://opendataservices.plan.io/issues/55230 Removed links to data.threesixtygiving.org and replaced with links to the Quality Dashboard. --- documentation/_templates/_parts/navbar.html | 4 ++-- documentation/_templates/_parts/top-bar.html | 4 ++-- documentation/footer.json | 10 +++++----- documentation/technical/metadata.md | 2 +- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/documentation/_templates/_parts/navbar.html b/documentation/_templates/_parts/navbar.html index ae501ef3..9f2826b1 100644 --- a/documentation/_templates/_parts/navbar.html +++ b/documentation/_templates/_parts/navbar.html @@ -8,11 +8,11 @@ - \ No newline at end of file + diff --git a/documentation/_templates/_parts/top-bar.html b/documentation/_templates/_parts/top-bar.html index 6c8e70a3..a85c1e43 100644 --- a/documentation/_templates/_parts/top-bar.html +++ b/documentation/_templates/_parts/top-bar.html @@ -3,7 +3,7 @@ @@ -20,4 +20,4 @@ - \ No newline at end of file + diff --git a/documentation/footer.json b/documentation/footer.json index 5c65f75c..9ce53d1a 100644 --- a/documentation/footer.json +++ b/documentation/footer.json @@ -34,8 +34,8 @@ "description": "" }, { - "url": "https://data.threesixtygiving.org/", - "title": "Data Registry", + "url": "https://qualitydashboard.threesixtygiving.org", + "title": "360Giving Quality Dashboard", "description": "" }, { @@ -104,9 +104,9 @@ "description": "A uniform and consistent way to describe grants data. Publishing data in this standard format means it\u2019s easier to find, understand and compare funding across the UK." }, { - "url": "https://data.threesixtygiving.org/", - "title": "Registry", - "description": "A list of all the organisations that currently publish their grants data in the 360Giving Data Standard, with direct links to their data sources." + "url": "https://qualitydashboard.threesixtygiving.org", + "title": "360Giving Quality Dashboard", + "description": "A dashboard showing the data quality of 360Giving data as a whole and for each individual publisher. It provides insights into the key features that make the data useful for analysis to help publishers to identify opportunities for their data to be improved." } ] } diff --git a/documentation/technical/metadata.md b/documentation/technical/metadata.md index c86a909b..e9ad44f5 100644 --- a/documentation/technical/metadata.md +++ b/documentation/technical/metadata.md @@ -12,7 +12,7 @@ In 360Giving, metadata is information about the 360Giving data in the file; such There are two main types of metadata: - **Authoritative metadata**: This is what the file declares about itself, such as who the publisher is, or where the file can be found. -- **Derived metadata**: This is what can be found out from a file, such as the total value of the grants, or which fields from the 360Giving Data Standard are used. This type of data is not included in the information that is published, instead it can be calculated by tools that use a file, such as the 360Giving Data Registry. +- **Derived metadata**: This is what can be found out from a file, such as the total value of the grants, or which fields from the 360Giving Data Standard are used. This type of data is not included in the information that is published, instead it can be calculated by tools that use a file, such as the 360Giving Quality Dashboard. ## Why include metadata in 360Giving files? Including metadata is one of the features of good quality open data. It helps people to find data that best suits their needs by supporting them to understand what the contents are and if they match what they’re looking for. It also provides publishers the ability to provide valuable context for the data that a user should bear in mind when analysing or using the data. From 50dd8cb04a14a55e20ffb2273229f1a6b0f7cfab Mon Sep 17 00:00:00 2001 From: Matt Marshall Date: Fri, 6 Feb 2026 11:03:23 +0000 Subject: [PATCH 2/4] docs: replace instances of Data Quality Tool As per https://opendataservices.plan.io/issues/55230, replaced instanced of "Data Quality Tool" with "Data Quality Checker". Fixed merge conflicts present after merging #428, which removed non-normative guidance. Have not yet replaced instances of "DQT" in docs --- documentation/_templates/_parts/navbar.html | 2 +- documentation/_templates/_parts/top-bar.html | 2 +- documentation/about/governance.md | 4 ++-- documentation/extensions/dei/prepare.md | 6 +++--- documentation/extensions/index.md | 4 ++-- documentation/technical/metadata.md | 6 +++--- documentation/technical/reference.md | 4 ++-- 7 files changed, 14 insertions(+), 14 deletions(-) diff --git a/documentation/_templates/_parts/navbar.html b/documentation/_templates/_parts/navbar.html index 9f2826b1..8b8b82d8 100644 --- a/documentation/_templates/_parts/navbar.html +++ b/documentation/_templates/_parts/navbar.html @@ -11,7 +11,7 @@ 360Giving Quality Dashboard
  • - Data Quality Tool + Data Quality Checker
    • diff --git a/documentation/_templates/_parts/top-bar.html b/documentation/_templates/_parts/top-bar.html index a85c1e43..e925365f 100644 --- a/documentation/_templates/_parts/top-bar.html +++ b/documentation/_templates/_parts/top-bar.html @@ -4,7 +4,7 @@
    diff --git a/documentation/about/governance.md b/documentation/about/governance.md index ee504b41..0b78ad33 100644 --- a/documentation/about/governance.md +++ b/documentation/about/governance.md @@ -180,11 +180,11 @@ All notable changes are documented by Release via the [Changelog](https://github ### Deprecation Policy -If a term, such as a field title (known as a class or property in JSON schema) is scheduled to be renamed or removed as a result of the revision process, the next release must [deprecate](https://en.wikipedia.org/wiki/Deprecation) the term within the schema. The following MAJOR release must rename or remove the term from the schema, making it obsolete. Data that is published may use deprecated terms, but will receive warnings from the [360Giving Data Quality Tool](https://dataquality.threesixtygiving.org/). Once obsolete, terms in published data will be treated like any other non-Standard fields. +If a term, such as a field title (known as a class or property in JSON schema) is scheduled to be renamed or removed as a result of the revision process, the next release must [deprecate](https://en.wikipedia.org/wiki/Deprecation) the term within the schema. The following MAJOR release must rename or remove the term from the schema, making it obsolete. Data that is published may use deprecated terms, but will receive warnings from the [360Giving Data Quality Checker](https://dataquality.threesixtygiving.org/). Once obsolete, terms in published data will be treated like any other non-Standard fields. ### Support Policy -When a new version upgrade is made to the Standard, support will be offered for one prior version. Support in this context means that data published using this version is recognised as meeting the requirements of the Standard and will be accepted by the 360Giving Data Registry, Data Quality Tool and other tools managed by 360Giving that use 360Giving data. This means that deprecated terms are supported but obsolete terms are not. +When a new version upgrade is made to the Standard, support will be offered for one prior version. Support in this context means that data published using this version is recognised as meeting the requirements of the Standard and will be accepted by the 360Giving Data Registry, Data Quality Checker and other tools managed by 360Giving that use 360Giving data. This means that deprecated terms are supported but obsolete terms are not. Support for any earlier version than this will not be guaranteed when a new version is released. diff --git a/documentation/extensions/dei/prepare.md b/documentation/extensions/dei/prepare.md index 37172f19..b0d1463d 100644 --- a/documentation/extensions/dei/prepare.md +++ b/documentation/extensions/dei/prepare.md @@ -263,7 +263,7 @@ A key step to using the DEI Extension is declaring that you are using it in a ** This Meta sheet is the way 360Giving data publishers include metadata about their grants data in their files. It is separate and different from the metadata fields in the DEI Extension itself which are usually included in the main grants sheet. For further information read our guidance on 360Giving Data Standard [Metadata](../../technical/metadata.md#guide-to-including-metadata-in-spreadsheet-files). -It is only once you have declared that you are using the DEI Extension in the Meta sheet that your data can be checked and validated by the 360Giving [Data Quality Tool](https://dataquality.threesixtygiving.org/) and used by GrantNav and 360Insights. If you miss this crucial step, the Data Quality Tool will not recognise the fields for the DEI Extension and treat them as non-Standard [Additional Fields](../../technical/reference.md#additional-fields). +It is only once you have declared that you are using the DEI Extension in the Meta sheet that your data can be checked and validated by the 360Giving [Data Quality Checker](https://dataquality.threesixtygiving.org/) and used by GrantNav and 360Insights. If you miss this crucial step, the Data Quality Checker will not recognise the fields for the DEI Extension and treat them as non-Standard [Additional Fields](../../technical/reference.md#additional-fields). Once you have a Meta sheet in your file, you can declare the extension by adding the Metadata field with the title \`Extensions\`. Usually this is in column A. In the next column (usually column B), add the value **dei** @@ -291,9 +291,9 @@ It is straightforward to implement the DEI Extension into an existing JSON forma If you're updating an existing publication and your current version is **1.0** or greater, you can declare **1.4** without any problems related to backwards incompatibility (see also: our [Versioning and Upgrade Process](../../about/governance.md#versioning-and-upgrade-process)).  - If you don’t have a **version** field currently, it is safe to add this with the value of **1.4** unless your data isn’t conformant to Version **1.0** or later. You can verify this by checking the 360Giving Data Standard data in your file in the [Data Quality Tool (DQT)](https://dataquality.threesixtygiving.org/), as all data that passes the tool’s validation checks is conformant with Version 1.0 or later. + If you don’t have a **version** field currently, it is safe to add this with the value of **1.4** unless your data isn’t conformant to Version **1.0** or later. You can verify this by checking the 360Giving Data Standard data in your file in the [Data Quality Checker](https://dataquality.threesixtygiving.org/), as all data that passes the tool’s validation checks is conformant with Version 1.0 or later. -2. Create the **extensions** field in your package data if you have not already done so, and add the string **dei**. This declares the extension to tooling such as the Data Quality Tool so you can validate the contents of the extension fields. +2. Create the **extensions** field in your package data if you have not already done so, and add the string **dei**. This declares the extension to tooling such as the Data Quality Checker so you can validate the contents of the extension fields. 3. For each grant that will contain DEI information, add a **grants.deiDetails** property. 1. When a grant has a **deiDetails** property, **deiDetails.leadership**, **deiDetails.mission**, and **deiDetails.project** become required for that grant. diff --git a/documentation/extensions/index.md b/documentation/extensions/index.md index 1984b9f3..047a2025 100644 --- a/documentation/extensions/index.md +++ b/documentation/extensions/index.md @@ -2,9 +2,9 @@ The [360Giving Data Standard](https://standard.threesixtygiving.org/en/latest/about/) is a uniform and consistent way to describe grantmaking data. It consists of a set of information fields that must be included when a grantmaking organisation shares grant data. Organisations publishing grant information using the Standard use the same formatting so the data can be easily understood, collated and compared by anyone. Data published using the 360Giving Data Standard can be located and ‘read’ easily by different applications and machines, including 360Giving’s own tools [GrantNav](https://grantnav.threesixtygiving.org) and [360Insights](https://insights.threesixtygiving.org). -360Giving data publishers may sometimes wish to collect and publish information which is not part of the 360Giving Data Standard. The Standard permits publishers to use any number of “additional fields“ in their data to meet their needs, but these additional fields are not recognised by the Standard. This means that they cannot be validated using tools such as the [Data Quality Tool](https://dataquality.threesixtygiving.org/) or used to filter data in GrantNav and 360Insights, and different publishers including the same kind of information may struggle to coordinate around how to name and structure this additional data. Read our guidance on [Additional fields](../technical/reference.md#additional-fields). +360Giving data publishers may sometimes wish to collect and publish information which is not part of the 360Giving Data Standard. The Standard permits publishers to use any number of “additional fields“ in their data to meet their needs, but these additional fields are not recognised by the Standard. This means that they cannot be validated using tools such as the [Data Quality Checker](https://dataquality.threesixtygiving.org/) or used to filter data in GrantNav and 360Insights, and different publishers including the same kind of information may struggle to coordinate around how to name and structure this additional data. Read our guidance on [Additional fields](../technical/reference.md#additional-fields). -**Extensions** to the 360Giving Data Standard are a way to address some of the issues with additional fields by introducing new optional fields and structures into 360Giving data. Each extension formally defines fields, structures, and rules which can then be recognised by tooling such as the Data Quality Tool which allows the data using extensions to be validated, and also provides further standardisation which supports interoperability between different datasets. +**Extensions** to the 360Giving Data Standard are a way to address some of the issues with additional fields by introducing new optional fields and structures into 360Giving data. Each extension formally defines fields, structures, and rules which can then be recognised by tooling such as the Data Quality Checker which allows the data using extensions to be validated, and also provides further standardisation which supports interoperability between different datasets. Extensions also address the issue of trying to support different use cases of 360Giving data whilst maintaining the stability and integrity of the Standard. A set of fields and features may be important to a significant portion of the 360Giving publishing community while there may not be enough demand to warrant adding the feature to the core set of Standard fields. Developing these features as an Extension can meet the needs of the community in a much shorter timescale, as well as providing a way to test out how the features work in practice. It is possible that an extension to the 360Giving Data Standard may later be integrated into the core Standard. diff --git a/documentation/technical/metadata.md b/documentation/technical/metadata.md index e9ad44f5..f5365903 100644 --- a/documentation/technical/metadata.md +++ b/documentation/technical/metadata.md @@ -32,7 +32,7 @@ Including metadata in the 360Giving Data Standard means we are better able to se If you are using an official Extension to the 360Giving Data Standard in your file, such as the DEI Extension, you should declare it in the file’s metadata to let people know which extension(s) you are using. You do this by adding the short code for the relevant extension into the Extensions field. -Once you have declared the extension in the metadata for your file, the Data Quality Tool will be able to detect and validate the data alongside your 360Giving data. It will also allow the data to be used in 360Giving’s tools, GrantNav and 360Insights. +Once you have declared the extension in the metadata for your file, the Data Quality Checker will be able to detect and validate the data alongside your 360Giving data. It will also allow the data to be used in 360Giving’s tools, GrantNav and 360Insights. Read the [field guidance](#field-guidance) for details of the Extensions field. @@ -63,7 +63,7 @@ You can find the names by looking at the [Meta sheet Table](meta-sheet) or [Exam Some fields require different types of values such as URLs or dates. The information about data format is also provided in the [Meta sheet Table.](meta-sheet) -4\. Once you have filled out the details, you can check whether the formatting is correct by uploading the file into the Data Quality Tool. Follow the feedback to make any changes needed to the metadata before publishing the file. If the Meta sheet is not named correctly the Data Quality Tool will not recognise the metadata and give error messages. +4\. Once you have filled out the details, you can check whether the formatting is correct by uploading the file into the Data Quality Checker. Follow the feedback to make any changes needed to the metadata before publishing the file. If the Meta sheet is not named correctly the Data Quality Checker will not recognise the metadata and give error messages. 5\. Publish the file how you normally do. @@ -222,7 +222,7 @@ Only the relevant information using the correct data formatting should be includ ### How to include additional information in Meta sheet In both the 360Giving Data Standard and Meta sheet, it is possible to include additional information alongside the official fields in the schema. -This could be contact information, disclaimer text or anything else you want users to know about your data. However these fields will not be recognised by the Data Quality Tool so you will need to ensure that the information provided is formatted correctly. +This could be contact information, disclaimer text or anything else you want users to know about your data. However these fields will not be recognised by the Data Quality Checker so you will need to ensure that the information provided is formatted correctly. Also be aware to avoid special characters in the field names. See guidance on adding [Additional fields](additional-fields) for further details of what to consider when adding your own fields. diff --git a/documentation/technical/reference.md b/documentation/technical/reference.md index 91aefd10..1c70d2e1 100644 --- a/documentation/technical/reference.md +++ b/documentation/technical/reference.md @@ -19,7 +19,7 @@ There are two main formats available for representing 360Giving data. 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](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](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. +You can use the 360Giving Data Quality Checker 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 @@ -450,4 +450,4 @@ When data is being generated directly out of a database system, publishers shoul 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. +The 360Giving Data Quality Checker supports conversion of data between the Spreadsheet Template and JSON representations. From 2be1eed54825f9475fce7883a09e6d332fad0850 Mon Sep 17 00:00:00 2001 From: Matt Marshall Date: Wed, 28 Jan 2026 09:04:31 +0000 Subject: [PATCH 3/4] docs: update strings to "Data Quality Dashboard" Erroneously had stated "360Giving Quality Dashboard". This commit fixes that --- documentation/_templates/_parts/navbar.html | 2 +- documentation/_templates/_parts/top-bar.html | 2 +- documentation/footer.json | 2 +- documentation/technical/metadata.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/_templates/_parts/navbar.html b/documentation/_templates/_parts/navbar.html index 8b8b82d8..52874c5e 100644 --- a/documentation/_templates/_parts/navbar.html +++ b/documentation/_templates/_parts/navbar.html @@ -8,7 +8,7 @@