From e788e8458ed2e44034990d0f566c1eb7e2c3978f Mon Sep 17 00:00:00 2001 From: kena vyas Date: Thu, 21 Nov 2024 13:56:19 +0000 Subject: [PATCH 1/2] doc to update project-organisation table --- .../Key-Concepts/Organisation-and-provision.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md b/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md index 652ed38..d88e112 100644 --- a/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md +++ b/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md @@ -19,7 +19,11 @@ The [Provision Rule](https://datasette.planning.data.gov.uk/digital-land/provisi For example, in the case of the Article 4 Direction dataset: -* The role is set to local-planning-authority. Organisations linked to this role are stored in the [Role Organisation](https://datasette.planning.data.gov.uk/digital-land/role_organisation?role=local-planning-authority) Table, and all organisations associated with this role are added as expected for the dataset. -* Additionally, the dataset is associated with the project Open Digital Planning. Organisations linked to this project, found in the [Project Organisation](https://datasette.planning.data.gov.uk/digital-land/project_organisation?project=open-digital-planning) Table, are also added as expected for this dataset. +* The role is set to local-planning-authority. Organisations linked to this role are stored in the [Role Organisation](https://datasette.planning.data.gov.uk/digital-land/role_organisation?role=local-planning-authority) Table, and all organisations associated with this role are added for the dataset. +* Additionally, the dataset is associated with the project Open Digital Planning. Organisations linked to this project, found in the [Project Organisation](https://datasette.planning.data.gov.uk/digital-land/project_organisation?project=open-digital-planning) Table, are also added for this dataset. + +To modify the Project Organisation list, navigate to the [project](https://github.com/digital-land/specification/tree/main/content/project) folder within the specification repository and select the file depending on the project you wish to update. + +**Note:** Avoid making changes to any files in the [specification](https://github.com/digital-land/specification/tree/main/content) folder in specification repository, as any changes made here will be automatically reverted. This process ensures that all relevant organisations, based on their roles and project affiliations, are accurately associated with each dataset. \ No newline at end of file From 13eb6a94faf4e2d23a6254144eb8d173a5e38e4d Mon Sep 17 00:00:00 2001 From: kena vyas Date: Thu, 21 Nov 2024 15:07:08 +0000 Subject: [PATCH 2/2] address comment --- .../Explanation/Key-Concepts/Organisation-and-provision.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md b/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md index d88e112..29f8c77 100644 --- a/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md +++ b/docs/data-operations-manual/Explanation/Key-Concepts/Organisation-and-provision.md @@ -24,6 +24,6 @@ For example, in the case of the Article 4 Direction dataset: To modify the Project Organisation list, navigate to the [project](https://github.com/digital-land/specification/tree/main/content/project) folder within the specification repository and select the file depending on the project you wish to update. -**Note:** Avoid making changes to any files in the [specification](https://github.com/digital-land/specification/tree/main/content) folder in specification repository, as any changes made here will be automatically reverted. +**Note:** Avoid making changes to any files in the [specification](https://github.com/digital-land/specification/tree/main/specification) folder. The specification files are automatically built from the content files after every commit. Any changes made here will be automatically reverted. This process ensures that all relevant organisations, based on their roles and project affiliations, are accurately associated with each dataset. \ No newline at end of file