From 1a702ca3828397dc0420ec9bb64bde152a5b037d Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Thu, 25 Jul 2024 12:06:28 +0100 Subject: [PATCH] Update 1048-uk-gemini-encoding-guidance.asciidoc change two link: targets --- docs/1048-uk-gemini-encoding-guidance.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/1048-uk-gemini-encoding-guidance.asciidoc b/docs/1048-uk-gemini-encoding-guidance.asciidoc index d37436a..cefb4ef 100644 --- a/docs/1048-uk-gemini-encoding-guidance.asciidoc +++ b/docs/1048-uk-gemini-encoding-guidance.asciidoc @@ -438,7 +438,7 @@ content, such as gmd:identificationInfo (Figure 9). The first XML child element of any GEMINI2 metadata instance shall be gmd:fileIdentifier. The content of this XML element is the identifier of the metadata instance. File identifier is not to be confused with the -metadata item link:datasets.html#36[Resource Identifier]. +metadata item link:1062-gemini-datasets-and-data-series.html#36[Resource Identifier]. The content of the XML element shall be a unique managed identifier, such as a system generated UUID. Once the identifier has been set for a @@ -1044,7 +1044,7 @@ series, ISO 19115 hierarchyLevelName element must also be set, to ==== Detailed guidance for each metadata element -link:datasets.html[Datasets] +link:1062-gemini-datasets-and-data-series.html[Datasets] === Metadata for services @@ -1109,7 +1109,7 @@ with null values with the nil reason being missing (Figure 25). ==== Detailed guidance for each metadata element -link:services.html[Services] +link:1063-gemini-services.html[Services] _Last technical update: March 2019_