From 32f7c4beb662d159a0db2a974d2e3bc89e8170c6 Mon Sep 17 00:00:00 2001 From: kena vyas Date: Mon, 13 Jan 2025 09:20:04 +0000 Subject: [PATCH] add section for deleting endpoints --- .../How-To-Guides/Retiring/Retire-endpoints.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/data-operations-manual/How-To-Guides/Retiring/Retire-endpoints.md b/docs/data-operations-manual/How-To-Guides/Retiring/Retire-endpoints.md index 8808bef..0047813 100644 --- a/docs/data-operations-manual/How-To-Guides/Retiring/Retire-endpoints.md +++ b/docs/data-operations-manual/How-To-Guides/Retiring/Retire-endpoints.md @@ -33,3 +33,15 @@ digital-land retire-endpoints-and-sources retire.csv 4. **Check the results** Double check if all the endpoints and sources that are meant to be retired have an end-date added to the corresponding line. There should be as many endpoints retired as given in retire.csv. There should be at least the same amount of retired sources (remember that multiple sources can be associated with an endpoint) + +## Deleting endpoints with duplicate entries + +When the same endpoint is associated with two different datasets or organisations, and it is determined that one of them is incorrect, retiring the endpoint using an end-date will impact the other correct entry depending on its position in the file. + +To prevent such issues, the correct approach is to remove the entire entry for the endpoint from both the endpoint and source CSV files. + +1. Locate the entry to be removed using the endpoint hash. + +2. Verify the entry by confirming the associated organisation or dataset. + +3. Delete the entry from both the endpoint and source files. \ No newline at end of file