diff --git a/csw-server/src/test/java/org/fao/geonet/kernel/csw/services/getrecords/es/EsJsonHelper.java b/csw-server/src/test/java/org/fao/geonet/kernel/csw/services/getrecords/es/EsJsonHelper.java
index 08b345f0ef9..629247c8825 100644
--- a/csw-server/src/test/java/org/fao/geonet/kernel/csw/services/getrecords/es/EsJsonHelper.java
+++ b/csw-server/src/test/java/org/fao/geonet/kernel/csw/services/getrecords/es/EsJsonHelper.java
@@ -31,7 +31,7 @@
import java.util.List;
/**
- * Tools to build up ElasticSearch JSON structures via Jackson.
+ * Tools to build up Elasticsearch JSON structures via Jackson.
*
* @author bhoefling
*
diff --git a/datastorages/README.md b/datastorages/README.md
new file mode 100644
index 00000000000..721c1687d55
--- /dev/null
+++ b/datastorages/README.md
@@ -0,0 +1,12 @@
+# Data storage
+
+Extensions for data storage (used for storage resources such as record attachments and thumbnails).
+
+Core provides the default implementation for a data directory:
+
+* org.fao.geonet.resource.FileResources
+
+For more information see:
+
+* org.fao.geonet.resource.Resources
+
diff --git a/datastorages/cmis/README.md b/datastorages/cmis/README.md
new file mode 100644
index 00000000000..5bd20e924f1
--- /dev/null
+++ b/datastorages/cmis/README.md
@@ -0,0 +1,11 @@
+# CMIS Data storage
+
+Extension for data storage (used for storage resources such as record attachments and thumbnails).
+
+* cmis: content management interoperability services
+
+This data storage is based on the Apache Chemistry project which has been retired.
+
+Reference:
+
+* https://chemistry.apache.org/java/opencmis.html
diff --git a/datastorages/cmis/pom.xml b/datastorages/cmis/pom.xml
new file mode 100644
index 00000000000..e664f2104d3
--- /dev/null
+++ b/datastorages/cmis/pom.xml
@@ -0,0 +1,208 @@
+
+
+
+
+
+ gn-datastorages
+ org.geonetwork-opensource.datastorage
+ 4.4.2-SNAPSHOT
+
+ 4.0.0
+
+ gn-datastorage-cmis
+ CMIS datastorage
+
+
+
+ org.geonetwork-opensource
+ gn-core
+ ${project.version}
+ provided
+
+
+
+ org.springframework
+ spring-context
+ provided
+
+
+
+ org.springframework
+ spring-context-support
+ provided
+
+
+
+ org.apache.chemistry.opencmis
+ chemistry-opencmis-client-api
+
+
+
+ org.apache.chemistry.opencmis
+ chemistry-opencmis-client-impl
+
+
+
+
+
+
+ maven-jar-plugin
+
+
+ test-jar
+
+ test-jar
+
+
+
+
+
+
+
+ src/main/resources
+ true
+
+
+
+
+
+
+ run-static-analysis
+
+
+ !skipTests
+
+
+
+
+
+ org.codehaus.mojo
+ findbugs-maven-plugin
+
+
+
+
+
+
+ release
+
+
+
+ release
+
+
+
+
+
+
+ maven-dependency-plugin
+
+
+ stage-libs
+ prepare-package
+
+ copy-dependencies
+
+
+
+ true
+ runtime
+ provided
+ com.google.code.findbugs
+ false
+ ${project.build.directory}/lib
+ false
+ true
+
+
+
+
+
+
+ com.ruleoftech
+ markdown-page-generator-plugin
+
+
+ readme
+ process-resources
+
+ generate
+
+
+ ${project.basedir}/src/main/assembly
+ ${project.build.directory}/html
+
+
+
+ licenses
+ process-resources
+
+ generate
+
+
+ ${project.basedir}/../../
+ ${project.build.directory}/html/license
+
+
+
+
+ false
+ true
+ ${project.basedir}/../../release/src/markdown/html/header.html
+ ${project.basedir}/../../release/src/markdown/html/footer.html
+ TABLES,FENCED_CODE_BLOCKS
+ true
+
+
+
+
+ maven-assembly-plugin
+
+
+ release-zip
+ package
+
+ single
+
+
+ ${project.artifactId}-${project.version}
+ false
+
+ src/main/assembly/assembly.xml
+
+
+
+
+
+
+
+
+
+
+
+ ${basedir}/..
+
+
diff --git a/datastorages/cmis/src/main/assembly/README.md b/datastorages/cmis/src/main/assembly/README.md
new file mode 100644
index 00000000000..ee08bc7a3e3
--- /dev/null
+++ b/datastorages/cmis/src/main/assembly/README.md
@@ -0,0 +1,27 @@
+# CMIS data storage provider library
+
+To install the CMIS data storage provider in GeoNetwork:
+
+1. Copy the `lib` folder jar files into to `{GEONETWORK_DIR}/WEB-INF/lib` folder.
+
+2. Define the following environmental variables:
+
+ - Use CMIS data storage provider:
+
+ ```bash
+ export GEONETWORK_STORE_TYPE=cmis
+ ```
+
+ - Setup CMIS connection (check with your setup):
+
+ ```bash
+ export CMIS_REPOSITORY_ID=-default-
+ export CMIS_USERNAME=username
+ export CMIS_PASSWORD=password
+ export CMIS_SERVICES_BASE_URL=http://localhost:8080/alfresco
+ export CMIS_BASE_REPOSITORY_PATH=geonetwork
+ export CMIS_BINDING_TYPE=browser
+ export CMIS_BROWSER_URL=/api/-default-/public/cmis/versions/1.1/browser
+ ```
+
+3. Start GeoNetwork
diff --git a/datastorages/cmis/src/main/assembly/assembly.xml b/datastorages/cmis/src/main/assembly/assembly.xml
new file mode 100644
index 00000000000..86569455568
--- /dev/null
+++ b/datastorages/cmis/src/main/assembly/assembly.xml
@@ -0,0 +1,31 @@
+
+ bin
+
+ zip
+
+
+
+ ${project.build.directory}/lib
+ /lib
+
+
+
+
+
+ ${project.build.directory}/${project.artifactId}-${project.version}.jar
+ /lib
+
+
+
+ ${project.build.directory}/html/README.html
+ /
+
+
+
+ ${project.build.directory}/html/license/LICENSE.html
+ /license
+
+
+
diff --git a/core/src/main/java/org/fao/geonet/api/records/attachments/CMISStore.java b/datastorages/cmis/src/main/java/org/fao/geonet/api/records/attachments/CMISStore.java
similarity index 99%
rename from core/src/main/java/org/fao/geonet/api/records/attachments/CMISStore.java
rename to datastorages/cmis/src/main/java/org/fao/geonet/api/records/attachments/CMISStore.java
index 87f74ab9982..769267a5a14 100644
--- a/core/src/main/java/org/fao/geonet/api/records/attachments/CMISStore.java
+++ b/datastorages/cmis/src/main/java/org/fao/geonet/api/records/attachments/CMISStore.java
@@ -617,7 +617,7 @@ protected Path getBaseMetadataDir(ServiceContext context, Path metadataFullDir)
}
private GeonetworkDataDirectory getDataDirectory(ServiceContext context) {
- return context.getBean(GeonetworkDataDirectory.class);
+ return ApplicationContextHolder.get().getBean(GeonetworkDataDirectory.class);
}
/**
@@ -690,7 +690,7 @@ protected MetadataResourceExternalManagementProperties getMetadataResourceExtern
if (metadataResourceExternalManagementPropertiesUrl.contains("{lang}") || metadataResourceExternalManagementPropertiesUrl.contains("{ISO3lang}")) {
final IsoLanguagesMapper mapper = ApplicationContextHolder.get().getBean(IsoLanguagesMapper.class);
- String contextLang = context.getLanguage() == null ? Geonet.DEFAULT_LANGUAGE : context.getLanguage();
+ String contextLang = context==null || context.getLanguage() == null ? Geonet.DEFAULT_LANGUAGE : context.getLanguage();
String lang;
String iso3Lang;
diff --git a/core/src/main/java/org/fao/geonet/resources/CMISConfiguration.java b/datastorages/cmis/src/main/java/org/fao/geonet/resources/CMISConfiguration.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/CMISConfiguration.java
rename to datastorages/cmis/src/main/java/org/fao/geonet/resources/CMISConfiguration.java
diff --git a/core/src/main/java/org/fao/geonet/resources/CMISResources.java b/datastorages/cmis/src/main/java/org/fao/geonet/resources/CMISResources.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/CMISResources.java
rename to datastorages/cmis/src/main/java/org/fao/geonet/resources/CMISResources.java
diff --git a/core/src/main/java/org/fao/geonet/resources/CMISUtils.java b/datastorages/cmis/src/main/java/org/fao/geonet/resources/CMISUtils.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/CMISUtils.java
rename to datastorages/cmis/src/main/java/org/fao/geonet/resources/CMISUtils.java
diff --git a/core/src/main/resources/config-store/config-cmis-overrides.properties b/datastorages/cmis/src/main/resources/config-store/config-cmis-overrides.properties
similarity index 100%
rename from core/src/main/resources/config-store/config-cmis-overrides.properties
rename to datastorages/cmis/src/main/resources/config-store/config-cmis-overrides.properties
diff --git a/core/src/main/resources/config-store/config-cmis.xml b/datastorages/cmis/src/main/resources/config-store/config-cmis.xml
similarity index 100%
rename from core/src/main/resources/config-store/config-cmis.xml
rename to datastorages/cmis/src/main/resources/config-store/config-cmis.xml
diff --git a/datastorages/jcloud/README.md b/datastorages/jcloud/README.md
new file mode 100644
index 00000000000..43723d5659c
--- /dev/null
+++ b/datastorages/jcloud/README.md
@@ -0,0 +1,10 @@
+# JCloud Data storage
+
+Extension for data storage (used for storage resources such as record attachments and thumbnails).
+
+This extension uses the Apache JCloud library for portable storage across different cloud providers.
+
+Reference:
+
+* https://jclouds.apache.org
+
diff --git a/datastorages/jcloud/pom.xml b/datastorages/jcloud/pom.xml
new file mode 100644
index 00000000000..ebd05a9cbc9
--- /dev/null
+++ b/datastorages/jcloud/pom.xml
@@ -0,0 +1,235 @@
+
+
+
+
+
+ gn-datastorages
+ org.geonetwork-opensource.datastorage
+ 4.4.2-SNAPSHOT
+
+ 4.0.0
+
+ gn-datastorage-jcloud
+ JCloud datastorage
+
+
+
+ org.geonetwork-opensource
+ gn-core
+ ${project.version}
+ provided
+
+
+
+ org.geonetwork-opensource
+ gn-domain
+ ${project.version}
+ provided
+
+
+
+ org.geonetwork-opensource
+ gn-core
+ ${project.version}
+ tests
+ test
+
+
+
+ org.geonetwork-opensource
+ gn-domain
+ ${project.version}
+ tests
+ test
+
+
+
+ org.geonetwork-opensource
+ gn-services
+ ${project.version}
+ tests
+ test
+
+
+
+ org.springframework
+ spring-context
+ provided
+
+
+
+ org.springframework
+ spring-context-support
+ provided
+
+
+
+ org.apache.jclouds
+ jclouds-all
+
+
+
+
+
+
+
+ maven-jar-plugin
+
+
+ test-jar
+
+ test-jar
+
+
+
+
+
+
+
+ src/main/resources
+ true
+
+
+
+
+
+
+ run-static-analysis
+
+
+ !skipTests
+
+
+
+
+
+ org.codehaus.mojo
+ findbugs-maven-plugin
+
+
+
+
+
+
+ release
+
+
+
+ release
+
+
+
+
+
+
+ maven-dependency-plugin
+
+
+ stage-libs
+ prepare-package
+
+ copy-dependencies
+
+
+
+ true
+ runtime
+ provided
+ com.google.code.findbugs
+ false
+ ${project.build.directory}/lib
+ false
+ true
+
+
+
+
+
+
+ com.ruleoftech
+ markdown-page-generator-plugin
+
+
+ readme
+ process-resources
+
+ generate
+
+
+ ${project.basedir}/src/main/assembly
+ ${project.build.directory}/html
+
+
+
+ licenses
+ process-resources
+
+ generate
+
+
+ ${project.basedir}/../../
+ ${project.build.directory}/html/license
+
+
+
+
+ false
+ true
+ ${project.basedir}/../../release/src/markdown/html/header.html
+ ${project.basedir}/../../release/src/markdown/html/footer.html
+ TABLES,FENCED_CODE_BLOCKS
+ true
+
+
+
+
+ maven-assembly-plugin
+
+
+ release-zip
+ package
+
+ single
+
+
+ ${project.artifactId}-${project.version}
+ false
+
+ src/main/assembly/assembly.xml
+
+
+
+
+
+
+
+
+
+
+
+ ${basedir}/..
+
+
diff --git a/datastorages/jcloud/src/main/assembly/README.md b/datastorages/jcloud/src/main/assembly/README.md
new file mode 100644
index 00000000000..2d6ff271b9f
--- /dev/null
+++ b/datastorages/jcloud/src/main/assembly/README.md
@@ -0,0 +1,17 @@
+# JCloud data storage provider library
+
+To install the JCloud data storage provider in GeoNetwork:
+
+1. Copy the `lib` folder jar files into to `{GEONETWORK_DIR}/WEB-INF/lib` folder.
+
+2. Define the following environmental variables:
+
+ - Use JCloud data storage provider:
+
+ ```bash
+ export GEONETWORK_STORE_TYPE=jcloud
+ ```
+
+ - Setup JCloud connection `TODO`
+
+3. Start GeoNetwork
diff --git a/datastorages/jcloud/src/main/assembly/assembly.xml b/datastorages/jcloud/src/main/assembly/assembly.xml
new file mode 100644
index 00000000000..86569455568
--- /dev/null
+++ b/datastorages/jcloud/src/main/assembly/assembly.xml
@@ -0,0 +1,31 @@
+
+ bin
+
+ zip
+
+
+
+ ${project.build.directory}/lib
+ /lib
+
+
+
+
+
+ ${project.build.directory}/${project.artifactId}-${project.version}.jar
+ /lib
+
+
+
+ ${project.build.directory}/html/README.html
+ /
+
+
+
+ ${project.build.directory}/html/license/LICENSE.html
+ /license
+
+
+
diff --git a/core/src/main/java/org/fao/geonet/api/records/attachments/JCloudStore.java b/datastorages/jcloud/src/main/java/org/fao/geonet/api/records/attachments/JCloudStore.java
similarity index 99%
rename from core/src/main/java/org/fao/geonet/api/records/attachments/JCloudStore.java
rename to datastorages/jcloud/src/main/java/org/fao/geonet/api/records/attachments/JCloudStore.java
index d7ed09b1837..c4f11d4a365 100644
--- a/core/src/main/java/org/fao/geonet/api/records/attachments/JCloudStore.java
+++ b/datastorages/jcloud/src/main/java/org/fao/geonet/api/records/attachments/JCloudStore.java
@@ -30,6 +30,7 @@
import jeeves.server.context.ServiceContext;
import org.apache.commons.lang.StringUtils;
+import org.fao.geonet.ApplicationContextHolder;
import org.fao.geonet.api.exception.ResourceNotFoundException;
import org.fao.geonet.constants.Geonet;
import org.fao.geonet.domain.MetadataResource;
@@ -381,7 +382,7 @@ private Path getBaseMetadataDir(ServiceContext context, Path metadataFullDir) {
}
private GeonetworkDataDirectory getDataDirectory(ServiceContext context) {
- return context.getBean(GeonetworkDataDirectory.class);
+ return ApplicationContextHolder.get().getBean(GeonetworkDataDirectory.class);
}
/**
diff --git a/core/src/main/java/org/fao/geonet/resources/JCloudConfiguration.java b/datastorages/jcloud/src/main/java/org/fao/geonet/resources/JCloudConfiguration.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/JCloudConfiguration.java
rename to datastorages/jcloud/src/main/java/org/fao/geonet/resources/JCloudConfiguration.java
diff --git a/core/src/main/java/org/fao/geonet/resources/JCloudResources.java b/datastorages/jcloud/src/main/java/org/fao/geonet/resources/JCloudResources.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/JCloudResources.java
rename to datastorages/jcloud/src/main/java/org/fao/geonet/resources/JCloudResources.java
diff --git a/core/src/main/resources/config-store/config-jcloud-overrides.properties b/datastorages/jcloud/src/main/resources/config-store/config-jcloud-overrides.properties
similarity index 100%
rename from core/src/main/resources/config-store/config-jcloud-overrides.properties
rename to datastorages/jcloud/src/main/resources/config-store/config-jcloud-overrides.properties
diff --git a/core/src/main/resources/config-store/config-jcloud.xml b/datastorages/jcloud/src/main/resources/config-store/config-jcloud.xml
similarity index 100%
rename from core/src/main/resources/config-store/config-jcloud.xml
rename to datastorages/jcloud/src/main/resources/config-store/config-jcloud.xml
diff --git a/services/src/test/java/org/fao/geonet/api/records/attachments/JCloudStoreTest.java b/datastorages/jcloud/src/test/java/org/fao/geonet/api/records/attachments/JCloudStoreTest.java
similarity index 100%
rename from services/src/test/java/org/fao/geonet/api/records/attachments/JCloudStoreTest.java
rename to datastorages/jcloud/src/test/java/org/fao/geonet/api/records/attachments/JCloudStoreTest.java
diff --git a/datastorages/pom.xml b/datastorages/pom.xml
new file mode 100644
index 00000000000..eecab5b2dab
--- /dev/null
+++ b/datastorages/pom.xml
@@ -0,0 +1,86 @@
+
+
+
+
+
+ geonetwork
+ org.geonetwork-opensource
+ 4.4.2-SNAPSHOT
+
+ 4.0.0
+
+
+ org.geonetwork-opensource.datastorage
+ gn-datastorages
+ GeoNetwork datastorage providers
+ pom
+
+
+
+
+ datastorage-cmis
+
+
+
+ release
+
+
+
+ cmis
+
+
+
+
+ datastorage-s3
+
+
+
+ release
+
+
+
+ s3
+
+
+
+
+ datastorage-jcloud
+
+
+
+ release
+
+
+
+ jcloud
+
+
+
+
+
+ ../..
+
+
diff --git a/datastorages/s3/README.md b/datastorages/s3/README.md
new file mode 100644
index 00000000000..10cbc40199e
--- /dev/null
+++ b/datastorages/s3/README.md
@@ -0,0 +1,9 @@
+# S3 Data storage
+
+Extension for data storage (used for storage resources such as record attachments and thumbnails).
+
+This extension uses Amazon Web Services Simple Storage Service (S3) data storage directly.
+
+Reference:
+
+* https://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html
diff --git a/datastorages/s3/pom.xml b/datastorages/s3/pom.xml
new file mode 100644
index 00000000000..9be23df9a98
--- /dev/null
+++ b/datastorages/s3/pom.xml
@@ -0,0 +1,235 @@
+
+
+
+
+
+ gn-datastorages
+ org.geonetwork-opensource.datastorage
+ 4.4.2-SNAPSHOT
+
+ 4.0.0
+
+ gn-datastorage-s3
+ S3 datastorage
+
+
+
+ org.geonetwork-opensource
+ gn-core
+ ${project.version}
+ provided
+
+
+
+ org.geonetwork-opensource
+ gn-domain
+ ${project.version}
+ provided
+
+
+
+ org.geonetwork-opensource
+ gn-core
+ ${project.version}
+ tests
+ test
+
+
+
+ org.geonetwork-opensource
+ gn-domain
+ ${project.version}
+ tests
+ test
+
+
+
+
+ org.geonetwork-opensource
+ gn-services
+ ${project.version}
+ tests
+ test
+
+
+
+ org.springframework
+ spring-context
+ provided
+
+
+
+ org.springframework
+ spring-context-support
+ provided
+
+
+
+ com.amazonaws
+ aws-java-sdk-s3
+
+
+
+
+
+
+ maven-jar-plugin
+
+
+ test-jar
+
+ test-jar
+
+
+
+
+
+
+
+ src/main/resources
+ true
+
+
+
+
+
+
+ run-static-analysis
+
+
+ !skipTests
+
+
+
+
+
+ org.codehaus.mojo
+ findbugs-maven-plugin
+
+
+
+
+
+
+ release
+
+
+
+ release
+
+
+
+
+
+
+ maven-dependency-plugin
+
+
+ stage-libs
+ prepare-package
+
+ copy-dependencies
+
+
+
+ true
+ runtime
+ provided
+ com.google.code.findbugs
+ false
+ ${project.build.directory}/lib
+ false
+ true
+
+
+
+
+
+
+ com.ruleoftech
+ markdown-page-generator-plugin
+
+
+ readme
+ process-resources
+
+ generate
+
+
+ ${project.basedir}/src/main/assembly
+ ${project.build.directory}/html
+
+
+
+ licenses
+ process-resources
+
+ generate
+
+
+ ${project.basedir}/../../
+ ${project.build.directory}/html/license
+
+
+
+
+ false
+ true
+ ${project.basedir}/../../release/src/markdown/html/header.html
+ ${project.basedir}/../../release/src/markdown/html/footer.html
+ TABLES,FENCED_CODE_BLOCKS
+ true
+
+
+
+
+ maven-assembly-plugin
+
+
+ release-zip
+ package
+
+ single
+
+
+ ${project.artifactId}-${project.version}
+ false
+
+ src/main/assembly/assembly.xml
+
+
+
+
+
+
+
+
+
+
+
+ ${basedir}/..
+
+
diff --git a/datastorages/s3/src/main/assembly/README.md b/datastorages/s3/src/main/assembly/README.md
new file mode 100644
index 00000000000..7d10887aa70
--- /dev/null
+++ b/datastorages/s3/src/main/assembly/README.md
@@ -0,0 +1,17 @@
+# Amazon S3 data storage provider library
+
+To install the Amazon S3 data storage provider in GeoNetwork:
+
+1. Copy the `lib` folder jar files into to `{GEONETWORK_DIR}/WEB-INF/lib` folder.
+
+2. Define the following environmental variables:
+
+ - Use S3 data storage provider:
+
+ ```shell
+ export GEONETWORK_STORE_TYPE=s3
+ ```
+
+ - Setup S3 connection as described in https://geonetwork-opensource.org/manuals/4.0.x/en/install-guide/customizing-data-directory.html#using-a-s3-object-storage
+
+3. Start GeoNetwork
diff --git a/datastorages/s3/src/main/assembly/assembly.xml b/datastorages/s3/src/main/assembly/assembly.xml
new file mode 100644
index 00000000000..86569455568
--- /dev/null
+++ b/datastorages/s3/src/main/assembly/assembly.xml
@@ -0,0 +1,31 @@
+
+ bin
+
+ zip
+
+
+
+ ${project.build.directory}/lib
+ /lib
+
+
+
+
+
+ ${project.build.directory}/${project.artifactId}-${project.version}.jar
+ /lib
+
+
+
+ ${project.build.directory}/html/README.html
+ /
+
+
+
+ ${project.build.directory}/html/license/LICENSE.html
+ /license
+
+
+
diff --git a/core/src/main/java/org/fao/geonet/api/records/attachments/S3Store.java b/datastorages/s3/src/main/java/org/fao/geonet/api/records/attachments/S3Store.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/api/records/attachments/S3Store.java
rename to datastorages/s3/src/main/java/org/fao/geonet/api/records/attachments/S3Store.java
diff --git a/core/src/main/java/org/fao/geonet/resources/S3Credentials.java b/datastorages/s3/src/main/java/org/fao/geonet/resources/S3Credentials.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/S3Credentials.java
rename to datastorages/s3/src/main/java/org/fao/geonet/resources/S3Credentials.java
diff --git a/core/src/main/java/org/fao/geonet/resources/S3Resources.java b/datastorages/s3/src/main/java/org/fao/geonet/resources/S3Resources.java
similarity index 100%
rename from core/src/main/java/org/fao/geonet/resources/S3Resources.java
rename to datastorages/s3/src/main/java/org/fao/geonet/resources/S3Resources.java
diff --git a/core/src/main/resources/config-store/config-s3.xml b/datastorages/s3/src/main/resources/config-store/config-s3.xml
similarity index 100%
rename from core/src/main/resources/config-store/config-s3.xml
rename to datastorages/s3/src/main/resources/config-store/config-s3.xml
diff --git a/services/src/test/java/org/fao/geonet/api/records/attachments/S3StoreTest.java b/datastorages/s3/src/test/java/org/fao/geonet/api/records/attachments/S3StoreTest.java
similarity index 100%
rename from services/src/test/java/org/fao/geonet/api/records/attachments/S3StoreTest.java
rename to datastorages/s3/src/test/java/org/fao/geonet/api/records/attachments/S3StoreTest.java
diff --git a/docs/README.md b/docs/README.md
index 5eb45d9295f..67dc7dd7004 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -1,9 +1,10 @@
-Documentation
-=============
+# Documentation
This module contains:
-* Documentation in RST format
-* Change logs
-* Copyright template
-* Licenses for library
-* Utility folder with scripts to generate extra docs
\ No newline at end of file
+* `manual` in Markdown format for MkDocs
+* `manuals` in RST format for sphinx-build (via https://github.com/geonetwork/doc) - Legacy
+* Change logs txt files
+* [copyright.txt](copyright.txt) Copyright template
+* `licenses` for library
+* Utility folder with scripts to generate extra docs
+* `translate` python module for help with Sphinx-build migration to MkDocs
diff --git a/docs/changes4.4.0-0.txt b/docs/changes4.4.0-0.txt
new file mode 100644
index 00000000000..cf38bb0f885
--- /dev/null
+++ b/docs/changes4.4.0-0.txt
@@ -0,0 +1,182 @@
+================================================================================
+===
+=== GeoNetwork 4.4.0: List of changes
+===
+================================================================================
+- Doc / Changelog / 4.2.6 and 4.4.0 (#7392)
+- Changed GENERATEUUID to NOTHING based on discussion on issue #7274
+- Make samples generate new uuid so that they don't overwrite any existing data. Fix for #7274
+- Jetty bundle / Add JAVA_OPTS configuration for the /monitor/metrics endpoint to work correctly (#7385)
+- Documentation 4.4: Update Java references to Java 11, update link to the manual and release scripts (#7378)
+- Fixed typos for SOURCE.md (#7384)
+- Update Java version and include the information in the readme.html in the release bundle (#7383)
+- Update MkDocs configuration to publish to gh-pages branch (#7375)
+- Workflow / Related records of the draft (#7377)
+- Create CNAME
+- User Manual refresh using Markdown and MkDocs (#7329)
+- batch edit user profile check in APIs (#7243)
+- Record view / Support multiple status.
+- Groups maintenance / fix the display of the metadata owned by a group (#7371)
+- Map viewer / Option to configure WMS tiling (#7312)
+- Fix working copy display so that links go to working copy (#7248)
+- Move datastorage providers to maven modules and include them in the build on demand (#7302)
+- Send metadata mail notifications for public metadata when is re-approved - fill missing information for submitter, reviewer and publisher user (#7292)
+- Map viewer / context map / only WMS layers have dimensions information
+- Formatter / Remove unused Groovy mode. (#7346)
+- fix for untranslated userRecord and userRecords labels in user admin page (#7354)
+- Standard / ISO19110 improvements
+- Add support for emails with subdomains (#7314)
+- Improved handling of empty titles (#7362)
+- Merge pull request #7337 from geonetwork/ha
+- Indexing / Bounding Polygon / Coordinate order (#7364)
+- Indexing / Bounding Polygon / Reproject if needed #7340
+- Editor / Online source / Fix button icon
+- Fix CORSInterceptor, usage of a variable before is defined. Related to #5941 (#7361)
+- Add a new DOI icon (#7357)
+- Display the login menu for authenticated users when the setting 'gnCfg.mods.authentication.enabled' is disabled
+- Map / WMS dimension saved in map (#7339)
+- Add icons for related types (association and initiative) (#7264)
+- Update harvesters/src/main/java/org/fao/geonet/kernel/harvest/RefreshHarvesterJob.java
+- Java doc. Check also GeoNetworkDataDirectory for description of folders.
+- WFS layer improvements (#7317)
+- Map / WPS / Add support for custom parameter CRS
+- Don't override proxy configuration when saving the settings, if the http proxy is configured in Java system properties (#7325)
+- Create metadata category - check doesn't exist a category with the same name (#7296)
+- Editor / Preserve scroll position on Firefox
+- Portal / RSS feeds point to current portal (#7343)
+- Fix HTML/Javascript prettier formatting / main branch
+- Prevent invalid date written into xml (#7321)
+- Record view / Add configuration to support statistics on more than 100 (#7348)
+- Update xalan dependency (remove potential vuln) (#7140)
+- Fix write after response commit on proxy response (#7353)
+- Standard / ISO / Labels improvements (#7341)
+- RSS / Fix number of records parameter
+- Display metadata user and group owner in the transfer ownership dialog
+- Adding schemapublication_dir to admin info panel
+- DOI / ISO19115-3 / Support DOI set in resource identifier or distribution (#7288)
+- Map / Localisation / Empty results if no query (#7338)
+- Record view / Social network link points to permalink. (#7347)
+- Metadata editor / link to remote dataset improvements (#7324)
+- Indexing / Do not create empty object if no text (#7349)
+- Batch Editing access level in general system settings (#7238)
+- Indexing / Do not create empty object if no text (#7294)
+- User feedback API fixes: - Update mail message, related to #6792. - Don't fail the user feedback creation if the mail server is not configured
+- Jetty / Update version and fix sending mail
+- Jetty / Form config consistent with default docker one
+- Test / Remove duplicated prop.
+- Test / Add new properties.
+- HA / Introducing scheduled refresh of harvesterjobs.
+- HA / Added hostname to the system information panel.
+- Remove configuration for the UI setting 'isMenubarAccessible', removed in #7138
+- Batch editing / Update xpath spec link
+- Library / Update to wro4j 1.10.1 (#7315)
+- Fix robots.txt and sitemap 500 errors if no right content type is provided (#7327)
+- API / Sitemap / Improve speed
+- Merge remote-tracking branch 'origin/main' into ha
+- INSPIRE ATOM - retrieve the metadata ATOM feed using only the resource identifier (#7305)
+- Hide thumbnail image in metadata page when the image can't be loaded due to an error. (#7319)
+- Merge pull request #7253 from tkohr/core-main-ods-api
+- Bump actions/checkout from 3 to 4 (#7318)
+- Updated embedded documentation on naming convention for postprocessing files for sub-portals (#7310)
+- Fix permalink option in the application footer
+- Fix the check to display the Transfer ownership option in the metadata detail page
+- Merge branch '440-harvesterscheduleconfig' into ha
+- Merge branch '424-multipleinstances' into ha
+- Minor cleanup (#7301)
+- Record view / Lineage & Quality section improvements (#7180)
+- Editor / Top bar / Avoid hiding editor tabs with tool bar actions. (#7073)
+- Fix metadata editor tooltips close button when using the icon mode
+- Extend ElasticSearch proxy to filter out elements defined in the schema filters configurations (#6869)
+- Notifications / Errors / Fix message on group creation (#7295)
+- Metadata editor / recommended values for fields show an empty value. (#7232)
+- Standard / ISO / Mimefiletype encoding.
+- WMS tile images - if HEAD request fails, default to OL image src set
+- Search / Aggregation on organisation in Dutch (#7290)
+- Do not break link in the middle of a word.
+- API / CSV export / Add support for custom export. (#7132)
+- Extend keyword picker directive to support displaying all the suggested values when there is a selected value.
+- Set html emails as utf-8
+- ISO19139 / ISO19115-3.2018 / Don't index resource identifiers with empty code
+- Metadata tooltips - improve the check method to try to find a match a standard default with no context defined, if there is no entry with the element context
+- Update GeonetHttpRequestFactory to use system proxy defined in JAVA_OPTS
+- Update AbstractHttpRequest to use system proxy defined in JAVA_OPTS
+- INSPIRE / Validation / Add API usage.
+- fix ui issue (#7256)
+- Use resource files for messages (#7281)
+- API / Attachements / Stream files to servlet response (#7287)
+- Metadata index set of records - index the approved and working copies when the workflow is enabled (#7269)
+- Bump actions/setup-java from 3.10.0 to 3.12.0 (#7239)
+- Metadata editor / display metadata uuid for remote resources if the metadata title is not available
+- Handle empty allGroupOpsAfter instead of throwing error. If we cannot find publishedAfter then default to publishedBefore so that no emails are sent.
+- Full view on working copy fails. Fixes #7270
+- WMS time dimension - basic support for time intervals (#7280)
+- Fix error that would occur when there were duplicate languages. (#7275)
+- Standard / ISO19115-3 / Processing / Metadata contact lost. (#7278)
+- Merge pull request #7186 from geonetwork/lib-spring5java11
+- Add XmlTransient annotation to ISODate.getDateAndTimeUtc
+- Make editor snippets referenceable and reusable
+- Fix directive to display the most popular records, to display the most popular first
+- Allow mulitple conditional default tabs in a single editor view
+- Fix deletion sequence in editor: wait for DOM update before saving
+- Fix DOI logging
+- Use http proxy in DOI client
+- feat(ods): use ods explore api for CI_OnlineResource linkages
+- Fix record history parameter name. Related to #7074 (#7249)
+- Fix German typo of the label for 'otherRestrictions' (#7245)
+- fix(ods): add CI_OnlineResource linkages for ods v1
+- Escape {{ to avoid error parsing argument. (#7237)
+- Update skin.xsl so that it works better in nojs mode. (#7015)
+- Fix wmsQueue clear method logic
+- When authenticating user, only update the usergroups in the database if they have changed (#7165)
+- Map viewer / 'Default map' javascript error. Fixes #7228
+- Add support for OL Attributions (#7062)
+- Update MetadataExtentApiTest hashes, probably images differ due to JVM change to version 11
+- Update status emails to contain link to metadata which does not contain anchor. (#7130)
+- Update GitHub actions configuration
+- Update GitHub actions configuration
+- Remove Java 8 maven configuration
+- Update services/src/main/java/org/fao/geonet/api/OpenApiController.java
+- Update harvesters/src/main/java/org/fao/geonet/kernel/harvest/harvester/geoPREST/Harvester.java
+- Update harvesters/src/main/java/org/fao/geonet/kernel/harvest/harvester/geoPREST/Harvester.java
+- Update harvesters/src/main/java/org/fao/geonet/kernel/harvest/harvester/geoPREST/Harvester.java
+- Update harvesters/src/main/java/org/fao/geonet/kernel/harvest/harvester/geoPREST/Harvester.java
+- Update GitHub actions configuration
+- Merge branch 'main' into lib-spring5java11
+- Use Apache Commons StringUtils to join keywords in atom service description
+- Update to version 4.4.x (#7223)
+- Record view / Contact / Move website to popup (#7220)
+- ISO19139 - Improve metadata full view for contacts when fields information is missing (#7214)
+- Prettier formatting updates (#7222)
+- Record view / Decorate map with geographic identifier or description. (#7221)
+- Prettier.
+- Standard / ISO19139 / Indexing / Temporal range in GML 3.2.0 (#7218)
+- ArcSDE harvester / If the metadata stored in ArcSDE is matched against a known metadata schema, harvest the record as it is.
+- Increase the limit to retrieve the related metadata in the search results
+- System info / Add env variables related to database migration and harvester scheduler. Add some more precise doc links.
+- Java header.
+- Proposal to disable harvesters.
+- Bad configuration of a harvester could prevent geonetwork startup
+- Missing translations.
+- Translations / Add better message in case of harvester save issue.
+- Standard / ISO19115-3 / Do not declare main language in other languages (#7188)
+- changed english display text for batch editor xpath gn_add and gn_update modes
+- Standard / ISO19115-3 / Formatter / Layout improvements (#7187)
+- avoid race condition, resize map once target size ok (#6931)
+- camel tests, avoid side effects (#6836)
+- [gn] Support negative dates for temporal extents (#6843)
+- Metadata workflow / Don't increase popularity when viewing a metadata working copy
+- Map / WFS Features / Improvements (#7000)
+- Standard / ISO19110 / Add cardinality. (#7182)
+- Update version to 4.2.6-SNAPSHOT
+- Test / Fix related to XSD publication dir.
+- Lib / update snakeyaml to version 2.0
+- Remove toolchain for Java 8 and update maven compiler configuration for integration tests to use Java 11
+- Lib / Update / Spring 5, Hibernate 5, Jetty 9.
+- harvesters - disabling tests
+- harvester - attempt to fix date parsing tests with Jdk11
+- commons - jdk11 - better fix for test
+- jdk11 - fixing tests
+- being able to use a more recent jdk (11)
+- API / Site info / Add all data directory info
+- Data directory / Add parameter for XML schemas.
+- WRO4J / Move cache to HTML cache folder.
\ No newline at end of file
diff --git a/docs/changes4.4.1-0.txt b/docs/changes4.4.1-0.txt
new file mode 100644
index 00000000000..c82d73a4136
--- /dev/null
+++ b/docs/changes4.4.1-0.txt
@@ -0,0 +1,65 @@
+================================================================================
+===
+=== GeoNetwork 4.4.1: List of changes
+===
+================================================================================
+- Changelog / 441 and 427. (#7508)
+- i18n / Transifex update. (#7505)
+- Security / Jolokia update. (#7501)
+- Add web/src/main/webapp/WEB-INF/data/data/resources/schemapublication folder to .gitignore
+- Check http links in documentation (#7496)
+- Add more db information to the site information page. (#7403)
+- Update manual links to use https://docs.geonetwork-opensource.org/ (#7487)
+- Change the structure of the MkDocs assets. Stylesheets and logos are moved to the `overrides` directory (#7429)
+- Fix url link in full view. bracket ") " could be included in link (#7483)
+- Batch edit access level for editor role (#7464)
+- Fixed broken links and formatting in BUILDING.md (#7471)
+- Editor / Remove extra space on mandatory add action (#7438)
+- WRO4J / Fix unresolvable source map file on Windows (#7476)
+- Add node identifier parameter for xlst processing. Required in skin.xsl (#7454)
+- change label to "Access to the catalogue" (#7467)
+- API / Batch editing / XPath / Add support for attribute with namespace.
+- Remove exception class name from the error message (#6977)
+- Release / Create SQL migration script for new version (#7395)
+- Standard / Formatter / Citation improvements (#7434)
+- Update to GeoTools 30.0 Release (#7416)
+- Record view / Series / Technical information
+- List styling for related records (#7442)
+- Standard / Processes / Collection merge (#7436)
+- Indexing / Add related record title to the full text search (#7437)
+- Update docker.md
+- Fix cookies path when deployed on root "/" context (#7446)
+- Search results / Fix button size
+- Standard / Feature catalogues / Do not index empty codelist value (#7440)
+- Remove the `Download metadata` button in the metadata block on the Metadata page.
+- Fixed typos, formatting and numbering (#7430)
+- Fix issue with canViewRecord when calling related api (#7373)
+- Transifex updates (#7432)
+- Fix exception handling from schematron validation so that it flags the metadata as invalid if there is an exception (#6978)
+- Rename ElasticSearch to Elasticsearch (#7404)
+- Sort the portals by label, not by name (identifier) (#7424)
+- Metadata editor / ISO19115-3.2008 / Filter out metadata templates in the online resources dialog
+- Fix system info when ES throw errors (#7413)
+- Remove old password field for admins (#7417)
+- Add documentation to GitHub workflows (#7411)
+- GeoNetwork 4.4.x minor versions library updates
+- Change the url the icon in the homepage is linking to (#7422)
+- Fixed typos and updated SearchManager to EsSearchManager in core readme (#7418)
+- Update the links to documentation in the sofware development pages (#7408)
+- Update the CONTRIBUTING guide to detail the steps, before merging the pull requests (#7419)
+- Transifex updates
+- [feat] allow to open COG links in external viewer (#7387)
+- please prettier-java
+- Add 3DTILES support to gn_relatedresources_service module
+- add badge support for 3dtiles
+- add OGC:3DTILES to gnSearchSettings.mapProtocols.layers
+- support OGC:3DTILES protocol, set type to 3dtiles in buildAddToMapConfig
+- add OGC:3DTILES to possible values for gmd:protocol
+- Record view / fix double approved parameter in the metadata working copy page, for the buttons in the online resources panel. Related to #7248 (#7402)
+- Doc / Fix list (#7401)
+- Fixed typos in code_quality readme (#7407)
+- Use default mike settings to fix interaction between language chooser and versions
+- Correct canical_version to stable
+- Add 3.12.11 changelog and fix the display of the changelogs in the navigation bar (#7397)
+- Doc / 4.4.0 / Add note about datastore changes (#7398)
+- Update version to 4.4.1-SNAPSHOT
\ No newline at end of file
diff --git a/docs/manual/LICENSE b/docs/manual/LICENSE
new file mode 100644
index 00000000000..1d658d6d376
--- /dev/null
+++ b/docs/manual/LICENSE
@@ -0,0 +1,319 @@
+Creative Commons Legal Code
+
+Attribution 3.0 Unported
+
+ CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
+ LEGAL SERVICES. DISTRIBUTION OF THIS LICENSE DOES NOT CREATE AN
+ ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
+ INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
+ REGARDING THE INFORMATION PROVIDED, AND DISCLAIMS LIABILITY FOR
+ DAMAGES RESULTING FROM ITS USE.
+
+License
+
+THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVE
+COMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY
+COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS
+AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.
+
+BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE
+TO BE BOUND BY THE TERMS OF THIS LICENSE. TO THE EXTENT THIS LICENSE MAY
+BE CONSIDERED TO BE A CONTRACT, THE LICENSOR GRANTS YOU THE RIGHTS
+CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND
+CONDITIONS.
+
+1. Definitions
+
+ a. "Adaptation" means a work based upon the Work, or upon the Work and
+ other pre-existing works, such as a translation, adaptation,
+ derivative work, arrangement of music or other alterations of a
+ literary or artistic work, or phonogram or performance and includes
+ cinematographic adaptations or any other form in which the Work may be
+ recast, transformed, or adapted including in any form recognizably
+ derived from the original, except that a work that constitutes a
+ Collection will not be considered an Adaptation for the purpose of
+ this License. For the avoidance of doubt, where the Work is a musical
+ work, performance or phonogram, the synchronization of the Work in
+ timed-relation with a moving image ("synching") will be considered an
+ Adaptation for the purpose of this License.
+ b. "Collection" means a collection of literary or artistic works, such as
+ encyclopedias and anthologies, or performances, phonograms or
+ broadcasts, or other works or subject matter other than works listed
+ in Section 1(f) below, which, by reason of the selection and
+ arrangement of their contents, constitute intellectual creations, in
+ which the Work is included in its entirety in unmodified form along
+ with one or more other contributions, each constituting separate and
+ independent works in themselves, which together are assembled into a
+ collective whole. A work that constitutes a Collection will not be
+ considered an Adaptation (as defined above) for the purposes of this
+ License.
+ c. "Distribute" means to make available to the public the original and
+ copies of the Work or Adaptation, as appropriate, through sale or
+ other transfer of ownership.
+ d. "Licensor" means the individual, individuals, entity or entities that
+ offer(s) the Work under the terms of this License.
+ e. "Original Author" means, in the case of a literary or artistic work,
+ the individual, individuals, entity or entities who created the Work
+ or if no individual or entity can be identified, the publisher; and in
+ addition (i) in the case of a performance the actors, singers,
+ musicians, dancers, and other persons who act, sing, deliver, declaim,
+ play in, interpret or otherwise perform literary or artistic works or
+ expressions of folklore; (ii) in the case of a phonogram the producer
+ being the person or legal entity who first fixes the sounds of a
+ performance or other sounds; and, (iii) in the case of broadcasts, the
+ organization that transmits the broadcast.
+ f. "Work" means the literary and/or artistic work offered under the terms
+ of this License including without limitation any production in the
+ literary, scientific and artistic domain, whatever may be the mode or
+ form of its expression including digital form, such as a book,
+ pamphlet and other writing; a lecture, address, sermon or other work
+ of the same nature; a dramatic or dramatico-musical work; a
+ choreographic work or entertainment in dumb show; a musical
+ composition with or without words; a cinematographic work to which are
+ assimilated works expressed by a process analogous to cinematography;
+ a work of drawing, painting, architecture, sculpture, engraving or
+ lithography; a photographic work to which are assimilated works
+ expressed by a process analogous to photography; a work of applied
+ art; an illustration, map, plan, sketch or three-dimensional work
+ relative to geography, topography, architecture or science; a
+ performance; a broadcast; a phonogram; a compilation of data to the
+ extent it is protected as a copyrightable work; or a work performed by
+ a variety or circus performer to the extent it is not otherwise
+ considered a literary or artistic work.
+ g. "You" means an individual or entity exercising rights under this
+ License who has not previously violated the terms of this License with
+ respect to the Work, or who has received express permission from the
+ Licensor to exercise rights under this License despite a previous
+ violation.
+ h. "Publicly Perform" means to perform public recitations of the Work and
+ to communicate to the public those public recitations, by any means or
+ process, including by wire or wireless means or public digital
+ performances; to make available to the public Works in such a way that
+ members of the public may access these Works from a place and at a
+ place individually chosen by them; to perform the Work to the public
+ by any means or process and the communication to the public of the
+ performances of the Work, including by public digital performance; to
+ broadcast and rebroadcast the Work by any means including signs,
+ sounds or images.
+ i. "Reproduce" means to make copies of the Work by any means including
+ without limitation by sound or visual recordings and the right of
+ fixation and reproducing fixations of the Work, including storage of a
+ protected performance or phonogram in digital form or other electronic
+ medium.
+
+2. Fair Dealing Rights. Nothing in this License is intended to reduce,
+limit, or restrict any uses free from copyright or rights arising from
+limitations or exceptions that are provided for in connection with the
+copyright protection under copyright law or other applicable laws.
+
+3. License Grant. Subject to the terms and conditions of this License,
+Licensor hereby grants You a worldwide, royalty-free, non-exclusive,
+perpetual (for the duration of the applicable copyright) license to
+exercise the rights in the Work as stated below:
+
+ a. to Reproduce the Work, to incorporate the Work into one or more
+ Collections, and to Reproduce the Work as incorporated in the
+ Collections;
+ b. to create and Reproduce Adaptations provided that any such Adaptation,
+ including any translation in any medium, takes reasonable steps to
+ clearly label, demarcate or otherwise identify that changes were made
+ to the original Work. For example, a translation could be marked "The
+ original work was translated from English to Spanish," or a
+ modification could indicate "The original work has been modified.";
+ c. to Distribute and Publicly Perform the Work including as incorporated
+ in Collections; and,
+ d. to Distribute and Publicly Perform Adaptations.
+ e. For the avoidance of doubt:
+
+ i. Non-waivable Compulsory License Schemes. In those jurisdictions in
+ which the right to collect royalties through any statutory or
+ compulsory licensing scheme cannot be waived, the Licensor
+ reserves the exclusive right to collect such royalties for any
+ exercise by You of the rights granted under this License;
+ ii. Waivable Compulsory License Schemes. In those jurisdictions in
+ which the right to collect royalties through any statutory or
+ compulsory licensing scheme can be waived, the Licensor waives the
+ exclusive right to collect such royalties for any exercise by You
+ of the rights granted under this License; and,
+ iii. Voluntary License Schemes. The Licensor waives the right to
+ collect royalties, whether individually or, in the event that the
+ Licensor is a member of a collecting society that administers
+ voluntary licensing schemes, via that society, from any exercise
+ by You of the rights granted under this License.
+
+The above rights may be exercised in all media and formats whether now
+known or hereafter devised. The above rights include the right to make
+such modifications as are technically necessary to exercise the rights in
+other media and formats. Subject to Section 8(f), all rights not expressly
+granted by Licensor are hereby reserved.
+
+4. Restrictions. The license granted in Section 3 above is expressly made
+subject to and limited by the following restrictions:
+
+ a. You may Distribute or Publicly Perform the Work only under the terms
+ of this License. You must include a copy of, or the Uniform Resource
+ Identifier (URI) for, this License with every copy of the Work You
+ Distribute or Publicly Perform. You may not offer or impose any terms
+ on the Work that restrict the terms of this License or the ability of
+ the recipient of the Work to exercise the rights granted to that
+ recipient under the terms of the License. You may not sublicense the
+ Work. You must keep intact all notices that refer to this License and
+ to the disclaimer of warranties with every copy of the Work You
+ Distribute or Publicly Perform. When You Distribute or Publicly
+ Perform the Work, You may not impose any effective technological
+ measures on the Work that restrict the ability of a recipient of the
+ Work from You to exercise the rights granted to that recipient under
+ the terms of the License. This Section 4(a) applies to the Work as
+ incorporated in a Collection, but this does not require the Collection
+ apart from the Work itself to be made subject to the terms of this
+ License. If You create a Collection, upon notice from any Licensor You
+ must, to the extent practicable, remove from the Collection any credit
+ as required by Section 4(b), as requested. If You create an
+ Adaptation, upon notice from any Licensor You must, to the extent
+ practicable, remove from the Adaptation any credit as required by
+ Section 4(b), as requested.
+ b. If You Distribute, or Publicly Perform the Work or any Adaptations or
+ Collections, You must, unless a request has been made pursuant to
+ Section 4(a), keep intact all copyright notices for the Work and
+ provide, reasonable to the medium or means You are utilizing: (i) the
+ name of the Original Author (or pseudonym, if applicable) if supplied,
+ and/or if the Original Author and/or Licensor designate another party
+ or parties (e.g., a sponsor institute, publishing entity, journal) for
+ attribution ("Attribution Parties") in Licensor's copyright notice,
+ terms of service or by other reasonable means, the name of such party
+ or parties; (ii) the title of the Work if supplied; (iii) to the
+ extent reasonably practicable, the URI, if any, that Licensor
+ specifies to be associated with the Work, unless such URI does not
+ refer to the copyright notice or licensing information for the Work;
+ and (iv) , consistent with Section 3(b), in the case of an Adaptation,
+ a credit identifying the use of the Work in the Adaptation (e.g.,
+ "French translation of the Work by Original Author," or "Screenplay
+ based on original Work by Original Author"). The credit required by
+ this Section 4 (b) may be implemented in any reasonable manner;
+ provided, however, that in the case of a Adaptation or Collection, at
+ a minimum such credit will appear, if a credit for all contributing
+ authors of the Adaptation or Collection appears, then as part of these
+ credits and in a manner at least as prominent as the credits for the
+ other contributing authors. For the avoidance of doubt, You may only
+ use the credit required by this Section for the purpose of attribution
+ in the manner set out above and, by exercising Your rights under this
+ License, You may not implicitly or explicitly assert or imply any
+ connection with, sponsorship or endorsement by the Original Author,
+ Licensor and/or Attribution Parties, as appropriate, of You or Your
+ use of the Work, without the separate, express prior written
+ permission of the Original Author, Licensor and/or Attribution
+ Parties.
+ c. Except as otherwise agreed in writing by the Licensor or as may be
+ otherwise permitted by applicable law, if You Reproduce, Distribute or
+ Publicly Perform the Work either by itself or as part of any
+ Adaptations or Collections, You must not distort, mutilate, modify or
+ take other derogatory action in relation to the Work which would be
+ prejudicial to the Original Author's honor or reputation. Licensor
+ agrees that in those jurisdictions (e.g. Japan), in which any exercise
+ of the right granted in Section 3(b) of this License (the right to
+ make Adaptations) would be deemed to be a distortion, mutilation,
+ modification or other derogatory action prejudicial to the Original
+ Author's honor and reputation, the Licensor will waive or not assert,
+ as appropriate, this Section, to the fullest extent permitted by the
+ applicable national law, to enable You to reasonably exercise Your
+ right under Section 3(b) of this License (right to make Adaptations)
+ but not otherwise.
+
+5. Representations, Warranties and Disclaimer
+
+UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR
+OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY
+KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE,
+INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY,
+FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF
+LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS,
+WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION
+OF IMPLIED WARRANTIES, SO SUCH EXCLUSION MAY NOT APPLY TO YOU.
+
+6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE
+LAW, IN NO EVENT WILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR
+ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES
+ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK, EVEN IF LICENSOR HAS
+BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+7. Termination
+
+ a. This License and the rights granted hereunder will terminate
+ automatically upon any breach by You of the terms of this License.
+ Individuals or entities who have received Adaptations or Collections
+ from You under this License, however, will not have their licenses
+ terminated provided such individuals or entities remain in full
+ compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will
+ survive any termination of this License.
+ b. Subject to the above terms and conditions, the license granted here is
+ perpetual (for the duration of the applicable copyright in the Work).
+ Notwithstanding the above, Licensor reserves the right to release the
+ Work under different license terms or to stop distributing the Work at
+ any time; provided, however that any such election will not serve to
+ withdraw this License (or any other license that has been, or is
+ required to be, granted under the terms of this License), and this
+ License will continue in full force and effect unless terminated as
+ stated above.
+
+8. Miscellaneous
+
+ a. Each time You Distribute or Publicly Perform the Work or a Collection,
+ the Licensor offers to the recipient a license to the Work on the same
+ terms and conditions as the license granted to You under this License.
+ b. Each time You Distribute or Publicly Perform an Adaptation, Licensor
+ offers to the recipient a license to the original Work on the same
+ terms and conditions as the license granted to You under this License.
+ c. If any provision of this License is invalid or unenforceable under
+ applicable law, it shall not affect the validity or enforceability of
+ the remainder of the terms of this License, and without further action
+ by the parties to this agreement, such provision shall be reformed to
+ the minimum extent necessary to make such provision valid and
+ enforceable.
+ d. No term or provision of this License shall be deemed waived and no
+ breach consented to unless such waiver or consent shall be in writing
+ and signed by the party to be charged with such waiver or consent.
+ e. This License constitutes the entire agreement between the parties with
+ respect to the Work licensed here. There are no understandings,
+ agreements or representations with respect to the Work not specified
+ here. Licensor shall not be bound by any additional provisions that
+ may appear in any communication from You. This License may not be
+ modified without the mutual written agreement of the Licensor and You.
+ f. The rights granted under, and the subject matter referenced, in this
+ License were drafted utilizing the terminology of the Berne Convention
+ for the Protection of Literary and Artistic Works (as amended on
+ September 28, 1979), the Rome Convention of 1961, the WIPO Copyright
+ Treaty of 1996, the WIPO Performances and Phonograms Treaty of 1996
+ and the Universal Copyright Convention (as revised on July 24, 1971).
+ These rights and subject matter take effect in the relevant
+ jurisdiction in which the License terms are sought to be enforced
+ according to the corresponding provisions of the implementation of
+ those treaty provisions in the applicable national law. If the
+ standard suite of rights granted under applicable copyright law
+ includes additional rights not granted under this License, such
+ additional rights are deemed to be included in the License; this
+ License is not intended to restrict the license of any rights under
+ applicable law.
+
+
+Creative Commons Notice
+
+ Creative Commons is not a party to this License, and makes no warranty
+ whatsoever in connection with the Work. Creative Commons will not be
+ liable to You or any party on any legal theory for any damages
+ whatsoever, including without limitation any general, special,
+ incidental or consequential damages arising in connection to this
+ license. Notwithstanding the foregoing two (2) sentences, if Creative
+ Commons has expressly identified itself as the Licensor hereunder, it
+ shall have all rights and obligations of Licensor.
+
+ Except for the limited purpose of indicating to the public that the
+ Work is licensed under the CCPL, Creative Commons does not authorize
+ the use by either party of the trademark "Creative Commons" or any
+ related trademark or logo of Creative Commons without the prior
+ written consent of Creative Commons. Any permitted use will be in
+ compliance with Creative Commons' then-current trademark usage
+ guidelines, as may be published on its website or otherwise made
+ available upon request from time to time. For the avoidance of doubt,
+ this trademark restriction does not form part of this License.
+
+ Creative Commons may be contacted at http://creativecommons.org/.
diff --git a/docs/manual/README.md b/docs/manual/README.md
new file mode 100644
index 00000000000..6a32791b9e9
--- /dev/null
+++ b/docs/manual/README.md
@@ -0,0 +1,146 @@
+# GeoNetwork Manual and Help
+
+Documentation for GeoNetwork opensource is available via https://docs.geonetwork-opensource.org.
+
+This documentation is written under the Creative Commons license [Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0)](LICENSE).
+
+Reference:
+
+* [Documentation Writing Guide](docs/devel/docs/index.md)
+
+## Communication
+
+The [project issue tracker](https://github.com/geonetwork/core-geonetwork/issues) is used for communication, with ongoing topics tagged [documentation](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+label%3Adocumenation).
+
+## Material for MkDocs
+
+Documentation is [MkDocs-material](https://squidfunk.github.io/mkdocs-material/) which is a Markdown documentation framework written on top of [MkDocs](https://www.mkdocs.org/).
+
+If you are using Python3:
+
+1. Install using ``pip3`` and build:
+
+ ```bash
+ pip3 install -r requirements.txt
+ ```
+
+2. Use ***mkdocs** to preview locally:
+
+ ```bash
+ mkdocs serve
+ ```
+
+3. Preview: http://localhost:8000
+
+ Preview uses a single version, so expect some warnings from version chooser:
+ ```
+ "GET /versions.json HTTP/1.1" code 404
+ ```
+
+4. Optional: Preview online help:
+
+ ```bash
+ mkdocs serve --config-file help.yml
+ ```
+
+### VirtualEnv
+
+If you use a Python virtual environment:
+
+1. Activate virtual environment:
+
+ ```bash
+ virtualenv venv
+ source venv/bin/activate
+ pip install -r requirements.txt
+ ```
+
+2. Use ***mkdocs*** to preview from virtual environment:
+
+ ```bash
+ mkdocs serve
+ ```
+
+3. Preview: http://localhost:8000
+
+### Docker
+
+If you are not familiar with Python the MkDocs-material website has instructions for Docker:
+
+1. Run MkDocs in Docker environment:
+
+ ```
+ docker pull squidfunk/mkdocs-material
+ docker run --rm -it -p 8000:8000 -v ${PWD}:/docs squidfunk/mkdocs-material
+ ```
+
+2. Preview: http://localhost:8000
+
+## Maven Integration
+
+1. Build documentation with ``compile`` phase:
+ ```
+ mvn compile
+ ```
+
+2. Assemble ``zip`` with ``package`` phase:
+ ```bash
+ mvn package
+ ```
+
+3. Both ``install`` and ``deploy`` are skipped (so ``mvn clean install`` is fine).
+
+4. Use default profile to only build the default English docs:
+
+ ```
+ mvn install -Pdefault
+ ```
+
+## Deploy
+
+We use ``mike`` for publishing to https://geonetwork.github.io using `.` version:
+
+1. To deploy docs from the `main` branch to website `gh-pages` branch:
+
+ ```bash
+ mike deploy --push --no-redirect --update-aliases 4.4 latest
+ ```
+
+2. To deploy documentation for a new release:
+
+ ```bash
+ mike deploy --push --no-redirect --update-aliases 4.2 stable
+ ```
+
+3. When starting a new branch you can make it the default:
+
+ ```bash
+ mike set-default --push 4.2
+ ```
+
+ Hint: When starting a new branch update `overview/changelog/` navigation tree also.
+
+4. To publish documentation for a maintenance release:
+
+ ```bash
+ mike deploy --push --no-redirect --update-aliases 3.12 maintenance
+ ```
+
+5. To show published versions:
+
+ ```bash
+
+ mike list
+ ```
+
+6. To preview things locally (uses your local ``gh-pages`` branch):
+
+ ```bash
+ mike serve
+ ```
+
+Reference:
+
+* https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/
+* https://github.com/squidfunk/mkdocs-material-example-versioning
+* https://github.com/jimporter/mike
diff --git a/docs/manual/docs/_static/GN3.png b/docs/manual/docs/_static/GN3.png
new file mode 100644
index 00000000000..caee39b62de
Binary files /dev/null and b/docs/manual/docs/_static/GN3.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/css-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/css-configuration.md
new file mode 100644
index 00000000000..d1c2c10f5ee
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/css-configuration.md
@@ -0,0 +1,13 @@
+# Configuring CSS & Style {#css-configuration}
+
+To get to the CSS & Style configuration, you must be logged on as administrator. Open 'Settings' from the Administration page and select ``CCS & Style`` configuration.
+
+
+
+This page allows you to change various colors of page elements. Note that 'background' refers to the background color of elements, and 'color' to the font color used in the element. The above configuration will result in the visualization below:
+
+
+
+There is also an option to link to a background image. When linking to an image, make sure to use (the full web address to) an image from a https source if you're running GeoNetwork in https. Placing the image (upload as logo) on the same server is the best option to prevent potential browser blocks.
+
+Note that you can save a configuration locally for reuse later or on alternative servers. Saving a configuration will take a long time, because all scripts and styles will be rebuilt from sources. Temporary files are stored on the server in an application folder, you may need to revisit this page after an upgrade the system (or redeploy of a docker container).
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/csw-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/csw-configuration.md
new file mode 100644
index 00000000000..902c451848d
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/csw-configuration.md
@@ -0,0 +1,108 @@
+# Configuring CSW {#csw-configuration}
+
+To get to the CSW server configuration, you must be logged on as administrator first. Open 'Settings' from the Administration page and select CSW Server configuration.
+
+
+
+The CSW service provides a description of itself, the human who administers it, and other information through a `es` request (eg. ). This form allows you to configure the CSW server and fill out some of the properties returned in response to a GetCapabilities request.
+
+Configuration options:
+
+- *CSW Enabled*: By default CSW endpoint is enabled, but it can be disabled.
+
+ 
+
+ The Open Geospatial Catalogue Service for the Web (OGC-CSW) service, is a self-describing service that allows query, update and insertion of metadata records.
+
+- *Record to use for GetCapabilities*: The capabilities document is created using the record selected here.
+
+- *Inserted metadata is public*: By default, metadata inserted with the CSW Harvest and CSW Transaction operations is not publicly viewable. A user with the appropriate access rights could do this after the CSW Harvest and CSW Transaction operations, but this is not always convenient. If this option is checked all metadata inserted using the CSW Harvest and CSW Transaction operations will be publicly viewable.
+
+- *Create element if it does not exist when using XPath in CSW transaction.*: If not checked, only existing elements can be updated.
+
+## Service Metadata Record {#csw-configuration_service_record}
+
+In order to create a custom capabilities, it is recommended to create a dedicated service metadata record (using ISO19115-3 or ISO19139 standards). This record is used to build the capabilities document using the template `web/src/main/webapp/xml/csw/capabilities.xml`.
+
+When creating such record, the following information will be used to create the capabilities:
+
+- title
+- abstract
+- keywords
+- fees (from Distribution --> ordering instructions field)
+- Access constraints (from Access constraints --> Other constraints field)
+- Contact (from Identification --> First point of contact)
+
+The service record MUST be public.
+
+If an error occurred while building the capabilities document from the service record, a WARNING is reported using a comment and the default capabilities is used:
+
+
+
+## CSW Configuration for INSPIRE {#csw-configuration_inspire}
+
+If your catalogue also focus on INSPIRE (see [Configuring for the INSPIRE Directive](inspire-configuration.md)), it may be relevant to also populate the following to properly configure your discovery service:
+
+- metadata language (+ additional languages if any) (use for SupportedLanguages, DefaultLanguage)
+- INSPIRE themes
+- temporal coverage
+- metadata contact
+- metadata conformity regarding Commission regulation 1089/2010
+
+With this information the CSW can be validated using the INSPIRE validator.
+
+## CSW post processing
+
+In some situation, user may want to modify XML encoding of records when retrieved using CSW. For example:
+
+- to make record more consistent
+- to adapt encoding in order to validate records with INSPIRE rules (eg. as a workaround for workaround for )
+
+For this, user can add extra conversion step during output of GetRecords and GetRecordById operation:
+
+- Adding post process to srv/eng/csw by creating for each output schema a file eg. for gmd, present/csw/gmd-csw-postprocessing.xsl
+- Adding post process to a portal inspire/eng/csw by creating for each output schema a file eg. for gmd, present/csw/gmd-inspire-postprocessing.xsl
+
+For a portal INSPIRE, create an "inspire" portal in the admin --> settings --> sources. User can then setup a post processing phase for the INSPIRE CSW of the portal. Create a post processing file gmd-inspire-postprocessing.xsl in yourschema/present/csw folder. The following example, remove contact with no email and link not starting with HTTP to conform to INSPIRE validator rules.
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+The service can be tested with:
+
+``` shell
+curl 'http://localhost:8080/geonetwork/inspire/eng/csw' \
+ -H 'Content-type: application/xml' \
+ --data-binary $'full3de9790e-529f-431f-ac4f-e86d827bde8e\n'
+```
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/css-result.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/css-result.png
new file mode 100644
index 00000000000..2f077a63be0
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/css-result.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/css-screen.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/css-screen.png
new file mode 100644
index 00000000000..678fe7513d3
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/css-screen.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw-error.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw-error.png
new file mode 100644
index 00000000000..96fdbb238a4
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw-error.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw-off.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw-off.png
new file mode 100644
index 00000000000..bae5454dd32
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw-off.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw.png
new file mode 100644
index 00000000000..9314c97407e
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/csw.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/geopublication-add-mapserver.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/geopublication-add-mapserver.png
new file mode 100644
index 00000000000..a38da19aea5
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/geopublication-add-mapserver.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-configuration.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-configuration.png
new file mode 100644
index 00000000000..4b32f20ede1
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-configuration.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-etf-test-configuration.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-etf-test-configuration.png
new file mode 100644
index 00000000000..995b380c54d
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-etf-test-configuration.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-from-registry-config.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-from-registry-config.png
new file mode 100644
index 00000000000..6ffa5161b76
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-from-registry-config.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-from-registry.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-from-registry.png
new file mode 100644
index 00000000000..2ffce1bdc75
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-from-registry.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-keyword-editing.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-keyword-editing.png
new file mode 100644
index 00000000000..c2dd7b92a0c
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-keyword-editing.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-keyword-encoding-type.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-keyword-encoding-type.png
new file mode 100644
index 00000000000..87d0e963d00
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-keyword-encoding-type.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-portal.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-portal.png
new file mode 100644
index 00000000000..a3cfae9d346
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-portal.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-validation-menu.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-validation-menu.png
new file mode 100644
index 00000000000..3b75f591d6b
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-validation-menu.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-validation-report.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-validation-report.png
new file mode 100644
index 00000000000..5488a2eb4a6
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/inspire-validation-report.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/log-view.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/log-view.png
new file mode 100644
index 00000000000..45ef2998206
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/log-view.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/logos.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/logos.png
new file mode 100644
index 00000000000..012c6d16ce5
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/logos.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-delete.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-delete.png
new file mode 100644
index 00000000000..ae2be2dd2a9
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-delete.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-import.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-import.png
new file mode 100644
index 00000000000..00d88f52b9c
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-import.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-publication.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-publication.png
new file mode 100644
index 00000000000..f057dec1986
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/metadata-publication.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-access.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-access.png
new file mode 100644
index 00000000000..47c8781dc09
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-access.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-geocatch.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-geocatch.png
new file mode 100644
index 00000000000..5c18e4b4a61
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-geocatch.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-header.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-header.png
new file mode 100644
index 00000000000..0b3d5c0c8d6
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-header.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-list.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-list.png
new file mode 100644
index 00000000000..82def6b62d2
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-list.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-oca-newrecord.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-oca-newrecord.png
new file mode 100644
index 00000000000..22a5ea85163
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-oca-newrecord.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-oca-privileges.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-oca-privileges.png
new file mode 100644
index 00000000000..3df2e9b26df
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-oca-privileges.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-subportal.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-subportal.png
new file mode 100644
index 00000000000..1fdbebb7e81
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-subportal.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-types.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-types.png
new file mode 100644
index 00000000000..bbd7f36d3d9
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/portal-types.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/settings.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/settings.png
new file mode 100644
index 00000000000..58f98a690ff
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/settings.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/standards.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/standards.png
new file mode 100644
index 00000000000..ed742be8ab9
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/standards.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-filter.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-filter.png
new file mode 100644
index 00000000000..d7b8699f15d
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-filter.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-footer.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-footer.png
new file mode 100644
index 00000000000..16fb041e953
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-footer.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-gazzetteer.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-gazzetteer.png
new file mode 100644
index 00000000000..1af02315645
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-gazzetteer.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-homepage.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-homepage.png
new file mode 100644
index 00000000000..661ea58f12a
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-homepage.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-humanizedate.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-humanizedate.png
new file mode 100644
index 00000000000..99078c8e839
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-humanizedate.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-indent.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-indent.png
new file mode 100644
index 00000000000..cba6512f194
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-indent.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-json.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-json.png
new file mode 100644
index 00000000000..8de039334a7
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-json.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mappage.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mappage.png
new file mode 100644
index 00000000000..626ce0fad85
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mappage.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mappage2.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mappage2.png
new file mode 100644
index 00000000000..e63e4ad3e40
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mappage2.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection.png
new file mode 100644
index 00000000000..5b878fe2bf3
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection2.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection2.png
new file mode 100644
index 00000000000..b779dcbca9c
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection2.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection3.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection3.png
new file mode 100644
index 00000000000..300cffd40ee
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojection3.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojectionslist.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojectionslist.png
new file mode 100644
index 00000000000..3a079191202
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapprojectionslist.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapviewer.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapviewer.png
new file mode 100644
index 00000000000..8c2a64f000d
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapviewer.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapviewerlayers.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapviewerlayers.png
new file mode 100644
index 00000000000..eea99e98383
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-mapviewerlayers.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-optionaltools.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-optionaltools.png
new file mode 100644
index 00000000000..114e5205932
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-optionaltools.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage.png
new file mode 100644
index 00000000000..06bc3bff312
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage2.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage2.png
new file mode 100644
index 00000000000..4fb9e53d575
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage2.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage3.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage3.png
new file mode 100644
index 00000000000..55b0cf2d50f
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage3.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage4.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage4.png
new file mode 100644
index 00000000000..71b7f3a8b9e
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchpage4.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults.png
new file mode 100644
index 00000000000..39613d720cb
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults2.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults2.png
new file mode 100644
index 00000000000..08b01fecdc8
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults2.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults3.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults3.png
new file mode 100644
index 00000000000..668f6679ce7
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-searchresults3.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-toptoolbar.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-toptoolbar.png
new file mode 100644
index 00000000000..2db6994d944
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-toptoolbar.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-toptoolbarlogo.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-toptoolbarlogo.png
new file mode 100644
index 00000000000..b5e2704fd54
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings-toptoolbarlogo.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings.png
new file mode 100644
index 00000000000..4a5732100b6
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/ui-settings.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/img/xlink-cache-clear.png b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/xlink-cache-clear.png
new file mode 100644
index 00000000000..5966279b4b2
Binary files /dev/null and b/docs/manual/docs/administrator-guide/configuring-the-catalog/img/xlink-cache-clear.png differ
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/index.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/index.md
new file mode 100644
index 00000000000..0e84f5ea037
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/index.md
@@ -0,0 +1,9 @@
+# Configuring the catalog
+
+- [System configuration](system-configuration.md)
+- [User Interface Configuration](user-interface-configuration.md)
+- [Configuring CSS & Style](css-configuration.md)
+- [Configuring CSW](csw-configuration.md)
+- [Portal configuration](portal-configuration.md)
+- [Configuring for the INSPIRE Directive](inspire-configuration.md)
+- [Map servers configuration for geopublication](map-server-configuration.md)
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/inspire-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/inspire-configuration.md
new file mode 100644
index 00000000000..0dea7a3ce98
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/inspire-configuration.md
@@ -0,0 +1,166 @@
+# Configuring for the INSPIRE Directive {#inspire-configuration}
+
+## Enabling INSPIRE
+
+From the **Admin console --> Settings** user can configure INSPIRE directive support.
+
+When enabled, the INSPIRE support activate the following:
+
+- Enable indexing of INSPIRE themes and annexes (INSPIRE themes thesaurus MUST be added to the list of thesaurus from the INSPIRE Registry - see [Managing thesaurus](../managing-classification-systems/managing-thesaurus.md)).
+
+ 
+
+To configure the discovery service, a dedicated service metadata record MUST be created in order to provide a complete GetCapabilities document ([CSW Configuration for INSPIRE](csw-configuration.md#csw-configuration_inspire)).
+
+## Loading INSPIRE codelists
+
+To describe INSPIRE datasets and series, it is recommended to load relevant codelists from the [INSPIRE Registry](https://inspire.ec.europa.eu/registry/), the following codelists are relevant in the scope of metadata guidelines v2.0:
+
+- [INSPIRE Theme](https://inspire.ec.europa.eu/theme)
+- [Application schema](https://inspire.ec.europa.eu/applicationschema)
+- [Media types](https://inspire.ec.europa.eu/media-types)
+- Metadata codelist register --> [Protocols](https://inspire.ec.europa.eu/metadata-codelist/ProtocolValue)
+- Metadata codelist register --> [Spatial scope](https://inspire.ec.europa.eu/metadata-codelist/SpatialScope)
+- Metadata codelist register --> [INSPIRE priority data set](https://inspire.ec.europa.eu/metadata-codelist/PriorityDataset)
+- Metadata codelist register --> [Spatial Data Service Category](https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory)
+- Metadata codelist register --> [Conditions applying to Access and Use](https://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse)
+- Metadata codelist register --> [Limitations on Public Access](https://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess)
+- Metadata codelist register --> [OnLine Description Code](https://inspire.ec.europa.eu/metadata-codelist/OnLineDescriptionCode)
+- Metadata codelist register --> [Quality of Service Criteria](https://inspire.ec.europa.eu/metadata-codelist/QualityOfServiceCriteria)
+
+From `Admin console` --> `Classification systems` --> `Thesaurus`, administrators can manage thesauri. One of the options is to load a thesaurus straight from the registry.
+
+
+
+Click `Use INSPIRE registry` to use the default INSPIRE registry but any instance of the [Registry software](https://joinup.ec.europa.eu/solution/re3gistry) can be used.
+
+
+
+Select one or more languages depending on your needs. Choose a category or directly a thesaurus, depending on the thesaurus. By default the type of thesaurus will be `Theme` but you can adapt it if needed.
+
+By clicking the `Upload` button the catalogue will contact the registry, download the files for each languages and combined them in a thesaurus in SKOS format supported by the catalogue.
+
+User can also use the well known [GEMET thesaurus](https://www.eionet.europa.eu/gemet/en/themes/). Some SKOS format version of the thesaurus are available [here](https://github.com/geonetwork/util-gemet/tree/master/thesauri).
+
+Once loaded, a thesaurus can be used in metadata records to select keywords from:
+
+
+
+The type of encoding of keywords can be defined using the gear icon (See validation section for more information):
+
+
+
+Via the schema plugin form configuration it is an option to configure a thesaurus to be used for a specific `or` element. The thesaures concepts are used to populate an auto complete text field for that element.
+
+## INSPIRE validation
+
+INSPIRE validation of metadata records is available at [the INSPIRE Validator](https://inspire.ec.europa.eu/validator/about/). It is using [ETF which is an open source testing framework for spatial data and services](https://github.com/etf-validator/etf-webapp). GeoNetwork is able to `te` any record using a service provided by an instance of ETF. To configure remote validation, go to `Admin console` --> `Settings` and set the URL of the validator. The url of the main INSPIRE validator is `https://inspire.ec.europa.eu/validator/`.
+
+
+
+Once enabled, the editor will show the remote validation option in the menu:
+
+
+
+The standard validate option will use the internal validation system (ie. XSD, Schematron rules for ISO, INSPIRE, \... depending on the configuration). In the internal system the INSPIRE validation is based on INSPIRE Technical guidance version 1.3 and results will be different from ETF reports.
+
+The remote INSPIRE validation will open the validator in a popup. Choose one of the options depending on the level of validation and type of resource to validate. The list of options can be customized in [this configuration file](https://github.com/geonetwork/core-geonetwork/blob/master/services/src/main/resources/config-spring-geonetwork.xml#L61-L94). The configuration is made by selecting one or more test suite from the ETF options:
+
+
+
+During the validation, the record is sent to the ETF service and processed. Once ETF completes the validation, the catalogue will display a link to the validation report.
+
+
+
+Note, that if you are validating a private record, that record will be pushed to the validator. To secure this process we recommend to set up a local (private) installation of the validator.
+
+### Configure validation test suites
+
+The set of test that runs for each schema can be configured using the file [WEB-INF/config-etf-validator.xml](https://github.com/geonetwork/core-geonetwork/blob/5156bae32d549e6d09cd6a86065791265eb09027/web/src/main/webapp/WEB-INF/config-etf-validator.xml).
+
+The list of available test suites are defined in the `inspireEtfValidatorTestsuites` bean. It is a map with an entry for each test suite. The `key` attribute is the name of the test suite. Each map entry is an `array` with the tests to execute in the test suite. The value of each array item (``)is the test's title written exactly as defined in the remote INSPIRE validator service. For example:
+
+``` xml
+
+
+
+ Conformance class: INSPIRE Profile based on EN ISO 19115 and EN ISO 19119
+ Conformance class: XML encoding of ISO 19115/19119 metadata
+ Conformance class: Conformance class: Metadata for interoperability
+
+
+
+
+ Common Requirements for ISO/TC 19139:2007 based INSPIRE metadata records.
+ Conformance Class 1: INSPIRE data sets and data set series baseline metadata.
+ Conformance Class 2: INSPIRE data sets and data set series interoperability metadata.
+
+
+
+
+ Common Requirements for ISO/TC 19139:2007 based INSPIRE metadata records.
+
+ Conformance Class 3: INSPIRE Spatial Data Service baseline metadata.
+ Conformance Class 4: INSPIRE Network Services metadata.
+
+
+
+
+```
+
+Array's `value-type` attribute must be defined as Java strings: ``.
+
+To define which test suites will be executed when using the editor dashboard's INSPIRE validation option you can modify the `inspireEtfValidatorTestsuitesConditions` bean. It's a map with an entry for each schema and test suite to execute. The map entry key attribute must be in the format `SCHEMA_ID::TEST_SUITE_NAME`, where `TEST_SUITE_NAME` is one of the `inspireEtfValidatorTestsuites` map entry key. For each entry you can define a XPath condition that the metadata must pass to be sent to the validator.
+
+!!! note
+
+ If a metadata schema doesn't match, the schema dependency hierarchy is checked to verify if any parent schema matches any rules.
+
+
+!!! warning
+
+ The Xpath must return a node-set or a node to work. XPaths returning a boolean `true` or `false` value will be interpreted as always matching by GeoNetwork.
+
+
+``` xml
+
+
+
+
+
+
+
+```
+
+## INSPIRE access point
+
+In many cases only a part of the metadata records in a catalog are related to the INSPIRE Directive. In that case, it may be relevant to filter the set of records falling in the scope of the Directive and promote them through a sub portal. In this way a European portal can easily harvest the records related to INSPIRE.
+
+First define a filtering mechanism to identify the records in the scope of the directive. Frequently used method are:
+
+- Create a group `INSPIRE` and publish those record in that group (or a category).
+- Add a specific keyword in the metadata record.
+- Filter based on the conformance quality report having a reference to the EU directive.
+
+From the `Admin console` --> `Settings` --> `Sources`, an administrator can create a sub portal. Create a portal `inspire` and set the filter to select only records related to INSPIRE (eg. `+_groupPublished:INSPIRE` to select all records published in group INSPIRE).
+
+
+
+Once saved, the portal is accessible at and the CSW service at .
+
+## INSPIRE reference documents
+
+- [INSPIRE IR](https://inspire.ec.europa.eu/)
+- [INSPIRE Technical Guidelines Metadata v2.0.1](https://inspire.ec.europa.eu/sites/default/files/documents/metadata/inspire-tg-metadata-iso19139-2.0.1.pdf)
+- [INSPIRE validator](https://inspire.ec.europa.eu/validator/)
+- [GeoNetwork at the INSPIRE forum](https://inspire.ec.europa.eu/forum/search?q=geonetwork)
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/map-server-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/map-server-configuration.md
new file mode 100644
index 00000000000..07924ce61f8
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/map-server-configuration.md
@@ -0,0 +1,21 @@
+# Map servers configuration for geopublication {#map-server-configuration}
+
+To publish information from the catalog as OGC services (WMS, WFS, WCS), catalog administrator need to register one or more map servers to publish on. Map servers MUST support the GeoServer REST API in order to work with the catalog. The 2 following implementations have been tested:
+
+- [GeoServer](https://geoserver.org)
+- [Mapserver](https://mapserver.org) and [Mapserver REST API](https://github.com/neogeo-technologies/mra)
+
+Setup you map server and then register it from the administration interface:
+
+
+
+The following parameters are required:
+
+- Name: The map server label which will be displayed when geopublishing information.
+- Description: The map server description.
+- REST API configuration: The URL of the service providing access to the remote configuration using the REST API.
+- Username and password to be used to connect to the REST API.
+- Workspace prefix and URL: The workspace information in which data will be pushed into.
+- WMS/WFS/WCS service URL: URLs of services which will be used when adding references to the services in the metadata record after publication.
+
+See [Publishing GIS data in a map server](../../user-guide/workflow/geopublication.md).
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/portal-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/portal-configuration.md
new file mode 100644
index 00000000000..6ef0fc230a5
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/portal-configuration.md
@@ -0,0 +1,87 @@
+# Portal configuration
+
+Portals can be configured under the `sources` section in `admin console` --> `settings`.
+
+
+
+There are 3 types of sources:
+
+- the main catalogue,
+- sub-portal, which can be a subset of the main catalogue
+- harvesters.
+
+
+
+The main catalogue corresponds to the current installation.
+
+When harvesting, at least one source is created to represent the harvester. When harvesting from another GeoNetwork node, sources from the target catalogue are also harvested to keep track of the true origin of records. This only applies to the GeoNetwork protocols which use MEF ([Metadata Exchange Format (MEF)](../../annexes/mef-format.md)) which contain the source catalogue information.
+
+The last type is sub-portal, which is described in details below.
+
+## Configuring a sub-portal
+
+Sub-portals can be used to create a space in the main catalogue only focusing on a subset of records.
+
+A sub-portal is defined by:
+
+
+
+When creating a sub-portal with an identifier `ìnspire` for example, a new entry point on your catalogue will be available: . Accessing the catalogue through it will only provide access to records matching the filter defined for this sub-portal. The `search filter` parameter value uses the Lucene query parser syntax (see ) and is applied to all searches.
+
+User privileges apply as in the main instance.
+
+The logo and name of the sub-portal will be displayed instead of the main instance information in case the option `Display in the portal switcher` is selected:
+
+
+
+A CSW service is also available for this sub-portal (and replacing the virtual CSW feature).
+
+A sub-portal can also use a specific user interface configuration.
+
+The list of sub-portal available is at
+
+
+
+## Example of usage
+
+### Creating an INSPIRE directive sub-portal
+
+For the INSPIRE directive, a catalogue administrator needs to publish an entry point providing access only to INSPIRE related records. An INSPIRE sub-portal can be created with a filter on keywords `+thesaurusName:"GEMET - INSPIRE themes, version 1.0"`.
+
+### Creating a sub-portal for partners
+
+Some organizations need to open the catalogue to a set of partners. In such cases, each partner generally accesses the catalogue and creates their records in dedicated groups. A good example is providing a main search filter `catalogue`.
+
+
+
+The concept of a sub-portal allows the possibility of creating a dedicated URL for each partner. The header can contain the partner identification with name and logo. Optionally the user interface can also be customized (see [User Interface Configuration](user-interface-configuration.md)).
+
+To setup this kind of configuration, the basic principle is to have:
+
+- One group for each partner with one or more users
+- One sub-portal for each partner with a filter matching records in that group
+
+To configure this, apply the following steps:
+
+- Create a group for the partner eg. `oca` (see [Creating group](../managing-users-and-groups/creating-group.md)).
+- Create at least one user for the partner (see [Creating user](../managing-users-and-groups/creating-user.md)). The user must be member of the group `oca`. If you want the user to be able to configure the sub-portal (eg. change the name, choose a logo), the user must have at least the `UserAdmin` profile for the group `oca`.
+- Create a sub-portal. This can have the same name as the group, eg. `oca` but this is not essential. The filter can be created using the fact that a record published in the group `oca` should be in this sub-portal, using the syntax `+_groupPublished:oca`. Once created the sub-portal is accessible at .
+- (Optional) Link the sub-portal to a user admin group to allow `UserAdmin` to configure their sub-portal.
+
+With this type configuration, ie. one partner = one group = one sub-portal and users are only member of one group, then when connecting to a partner sub-portal:
+
+- user will only see records published in that group in the entire application
+- when creating new records, no group selection is provided because user is member of one group only
+
+
+
+Remember that a record is visible in the `oca` sub-portal because it is published in the group `oca`:
+
+
+
+If the `publish` operation is removed from `oca` group, then records will not longer be visible in that sub-portal.
+
+In some situations, you also want to share templates among partners. There are 2 options for this:
+
+- Publish the template in all partner's groups. The main drawback in this case is that if a new group is added, the templates need to be published to that new group.
+- Create a dedicated group for shared records eg. `sharedGroup`. Publish templates in that shared space. Alter the sub-portal filter to match either the partner group or the shared one. `+_groupPublished:(oca OR sharedGroup)`.
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/system-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/system-configuration.md
new file mode 100644
index 00000000000..37a665a169a
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/system-configuration.md
@@ -0,0 +1,235 @@
+# System configuration
+
+Most of the system configuration parameters can be changed by administrator users using the web interface in `Admin console` --> `Settings`.
+
+!!! info "Important"
+
+ Configuration of these parameters is critically important for the catalog in an operational context. Misunderstanding some settings may result in a system that does not function as expected. For example, downloads may fail to be correctly processed, or metadata harvesting from other servers may not work.
+
+
+
+
+Since the settings form is a long form, the `save` button is repeated between the sections and will save all settings.
+
+## Catalog description
+
+- **Catalog name** The name of the node. Information that helps identify the catalogue to a human user. The name is displayed on the banner, in the CSW GetCapabilities.
+- **Catalog identifier** A universally unique identifier (uuid) that distinguishes your catalog from any other catalog. This a unique identifier for your catalogue and its best to leave it as a uuid. It will be used by harvester using GeoNetwork protocol to identify the source catalog.
+- **Organization** The organization the node belongs to. Again, this is information that helps identify the catalogue to a human user.
+- **SVN UUID** Subversion repository attached to the node. This identifier is created and/or checked on startup to verify that the database match the SVN repository. The repository is used for metadata versioning.
+
+## Catalog
+
+- **Version** The version of the catalog (readonly, version of the database)
+- **Minor version** The minor version of the catalog (readonly, version of the database)
+
+## Catalog Server {#system-config-server}
+
+- **Host** The node's name or IP number (without ). For example, they are used during metadata editing to create resource links and when returning the server's capabilities during a CSW request.
+ - If your node is publicly accessible from the Internet, you have to use the domain name.
+ - If your node is hidden inside your private network and you have a firewall or web server that redirects incoming requests to the node, you have to enter the public address of the firewall or web server. A typical configuration is to have an Apache web server on address A that is publicly accessible and redirects the requests to a Tomcat server on a private address B. In this case you have to enter A in the host parameter.
+- **Port** The server's port number (usually 80 or 8080). If using HTTP, set it to 80.
+- **Preferred Protocol** Defined the protocol to access the catalog. The HTTP protocol used to access the server. Choosing http means that all communication with the catalog will be visible to anyone listening to the protocol. Since this includes usernames and passwords this is not secure. Choosing https means that all communication with the catalog will be encrypted and thus much harder for a listener to decode.
+- **Log level** Define the logging level of the application. After modification, log can be checked in the `Statistics & status` section under `Activity`.
+
+
+
+## Intranet parameters
+
+A common need for an organisation is to automatically discriminate between anonymous internal users that access the node from within an organisation (Intranet) and anonymous external users from the Internet. The catalog defines anonymous users from inside the organisation as belonging to the group *Intranet*, while anonymous users from outside the organisation are defined by the group *All*. To automatically distinguish users that belong to the Intranet group you need to tell the catalog the intranet IP address and netmask.
+
+- **Network** The intranet address in IP form (eg. 147.109.100.0). It can be a comma separated list of IP addresses.
+- **Netmask** The intranet netmask (eg. 255.255.255.0). Define as many netmask and IP addresses.
+
+If intranet parameters are empty, the group *Intranet* will not be displayed in the sharing panel.
+
+## Proxy server
+
+The settings page offers to set the configuration of a proxy server. This configuration is used by the application to access the internet to get online resources, for example as part of a harvest process.
+
+- **Use proxy** Enable the proxy in case the catalog is behind a proxy and need to use it to access remote resources.
+- **Proxy Host** The proxy IP address or name
+- **Port** The proxy port
+- **Proxy username** The username
+- **Proxy user password** The username password
+- **Ignore host list** To bypass specific hosts enter a specific IP address or host name such as www.mydomain.com or an address range using wildcards, such as 192.168.2.*. Use | to separate the different host values.
+
+JVM proxy parameters may also be required to properly set the proxy for all remote access.
+
+## Feedback {#system-config-feedback}
+
+Email may be sent by the catalog.
+
+- you are using the User Self-registration system
+- you are using the metadata status workflow (See [Life cycle](../../user-guide/workflow/life-cycle.md))
+- a file uploaded with a metadata record is downloaded and notify privilege is selected
+
+This section configure the mail server to use.
+
+- **Email** This is the administrator's email address used to send feedback.
+- **SMTP host** The mail server name or IP address to use for sending emails.
+- **SMTP port** The SMTP port.
+- **Use SSL** Enable SSL mode
+- **User name** Username if connection is required on the SMTP server
+- **Password** Username password if connection is required on the SMTP server
+
+## Metadata search results
+
+Configuration settings in this group determine what the limits are on user interaction with the search results.
+
+- **Maximum Selected Records** The maximum number of search results that a user can select and process with the batch operations eg. Set Privileges, Categories etc. This parameter avoid to trigger long action which could generate out of memory error.
+
+## Catalog Service for the Web (CSW)
+
+See [Configuring CSW](csw-configuration.md).
+
+## Shibboleth
+
+See [Configuring Shibboleth](../managing-users-and-groups/authentication-mode.md#authentication-shibboleth).
+
+## User self-registration
+
+Enable the self registration form. See [User Self-Registration](../managing-users-and-groups/user-self-registration.md).
+
+## system/userFeedback
+
+!!! warning "Deprecated"
+
+ 3.0.0
+
+
+## Link in metadata records
+
+!!! warning "Deprecated"
+
+ 3.0.0 Defined by the formatter.
+
+
+## Metadata rating
+
+If enabled, the catalog will calculate user ratings for metadata from this node only (not distributed among other GeoNetwork nodes). This only applies to records harvested using the GeoNetwork protocol.
+
+## Metadata XLink {#xlink_config}
+
+The XLink resolver replaces the content of elements with an attribute @xlink:href (except for some elements like srv:operatesOn) with the content obtained from the URL content of @xlink:href. The XLink resolver should be enabled if you want to harvest metadata fragments or reuse fragments of metadata in your metadata records (eg. when using a contact directory).
+
+- **Enable XLink resolution**: Enables/disables the XLink resolver.
+- **Enable local XLink** Local XLinks are using local:/// URL to make references to related sections instead of HTTP URL. Local XLinks are usually faster than HTTP XLinks.
+
+!!! info "See Also"
+
+ To improve performance the catalog will cache content that is not in the local catalog. Clear the cache of XLink from the `Admin console` --> `Tools` if the fragments were updated.
+
+
+
+
+## Metadata update
+
+For each metadata schema, the catalog has an XSL transformation (`update-fixed-info.xsl`) that it can apply to a metadata record belonging to that schema. The aim of this transformation is to allow fixed schema, site and catalog information to be applied to a metadata record every time the metadata record is saved in the editor. As an example, this transformation is used to build and store the URL of any files uploaded and stored with the metadata record in the editor.
+
+- **Automatic Fixes**: Enabled by default. It is recommended you do not use the metadata editor when auto-fixing is disabled. See for more details.
+
+## Search Statistics {#search_stats_config}
+
+Enables/disables search statistics capture. Search statistics are stored in the database and can be queried using the `Search Statistics` page.
+
+There is very little compute overhead involved in storing search statistics as they are written to the database in a background thread. However database storage for a very busy site must be carefully planned.
+
+## Open Archive Initiative (OAI-PMH) Provider
+
+Options in this group control the way in which the OAI Server responds to OAIPMH harvest requests from remote sites.
+
+- **Datesearch**: OAI Harvesters may request records from GeoNetwork in a date range. GeoNetwork can use one of two date fields from the metadata to check for a match with this date range. The default choice is *Temporal extent*, which is the temporal extent from the metadata record. The other option, *Modification date*, uses the modification date of the metadata record in the GeoNetwork database. The modification date is the last time the metadata record was updated in or harvested by GeoNetwork.
+- **Resumption Token Timeout**: Metadata records that match an OAI harvest search request are usually returned to the harvester in groups with a fixed size (eg. in groups of 10 records). With each group a resumption token is included so that the harvester can request the next group of records. The resumption token timeout is the time (in seconds) that GeoNetwork OAI server will wait for a resumption token to be used. If the timeout is exceeded GeoNetwork OAI server will drop the search results and refuse to recognize the resumption token. The aim of this feature is to ensure that resources in the GeoNetwork OAI server are released.
+- **Cache size**: The maximum number of concurrent OAI harvests that the GeoNetwork OAI server can support.
+
+Restart the catalog to take all OAI settings into account.
+
+## INSPIRE Directive configuration
+
+See [Configuring for the INSPIRE Directive](inspire-configuration.md).
+
+## INSPIRE Atom Feed
+
+Allows to define the configuration of Atom Feeds referenced by the metadata to provide services related to the [INSPIRE technical guidance for download services](https://inspire.ec.europa.eu/documents/Network_Services/Technical_Guidance_Download_Services_3.0.pdf):
+
+- Select the type of atom feed:
+
+ - Remote: retrieve the atom feeds referenced by the metadata in the online resources.
+ - Local (to implement in future versions): create the atom feed using the metadata content.
+
+- Schedule for feed retrieval: the retrieval of the atom feeds can be scheduled to be done periodically.
+
+- Atom protocol value: value of the protocol in the metadata online resources to identify the atom feed resources (the default value is INSPIRE Atom). GeoNetwork identifies an Atom file from other resources by looking at the protocol value of the onlineresource. Since there is no general accepted value for this protocol, GeoNetwork allows an administrator to set the value to be used as protocol identifying Atom resources:
+
+
+
+
+
+
+ http://geodata.nationaalgeoregister.nl/atom/index.xml
+
+
+ INSPIRE Atom
+
+
+
+
+
+
+The following services are available:
+
+-
+-
+-
+-
+-
+
+In above URLs {UUID} is the fileidentifier of the download service metadata.
+
+In the service feed of your download service make sure to add the GeoNetwork OpenSearch endpoint as the OpenSearchDescription for the service:
+
+
+
+The INSPIRE Atom/OpenSearch implementation can be verified with the Atom tests in Esdin Test Framework () or INSPIRE metadata validator ().
+
+## Multi-Threaded Indexing
+
+Configuration settings in this group determine how many processor threads are allocated to indexing tasks in GeoNetwork. If your machine has many processor cores, you can now determine how many to allocate to GeoNetwork indexing tasks. This can bring dramatic speed improvements on large indexing tasks (eg. changing the privileges on 20,000 records) because GeoNetwork can split the indexing task into a number of pieces and assign them to different processor cores.
+
+*Number of processing threads* The maximum number of processing threads that can be allocated to an indexing task.
+
+Note: this option is only available for databases that have been tested. Those databases are PostGIS and Oracle. You should also carefully consider how many connections to the database you allocate in the database configuration as each thread could tie up one database connection for the duration of a long indexing session (for example). See the advanced configuration for more details of how to configure the number of connections in the database connection pool.
+
+## Metadata Privileges
+
+*Only set privileges to user's groups*: If enabled then only the groups that the user belongs to will be displayed in the metadata privileges page (unless the user is an Administrator). At the moment this option cannot be disabled and is likely to be deprecated in the next version of GeoNetwork.
+
+## Metadata import {#editing_harvested_records}
+
+- **Restrict import to schemas** List of all allowed schemas for metadata to be imported. If the metadata schema is not allowed, then the import is not done. Use an empty value to allow all schemas.
+- **Minimum user profile allowed to import metadata** Minimum user profile allowed to import metadata (`Editor`, `Reviewer` or `Administrator`). The default value is `Editor`.
+
+
+
+## Metadata delete
+
+Allows to configure the user profile allowed to delete published metadata.
+
+- **Minimum user profile allowed to delete published metadata** Minimum user profile allowed to delete metadata (`Editor`, `Reviewer` or `Administrator`). The default value is `Editor`.
+
+
+
+## Metadata publication
+
+Allows to configure the user profile allowed to publish and un-publish metadata.
+
+- **Minimum user profile allowed to publish metadata** Minimum user profile allowed to publish metadata (`Reviewer` or `Administrator`). The default value is `Reviewer`.
+- **Minimum user profile allowed to un-publish metadata** Minimum user profile allowed to un-publish metadata (`Reviewer` or `Administrator`). The default value is `Reviewer`.
+
+
+
+## Harvesting
+
+*Allow editing on harvested records*: Enables/Disables editing of harvested records in the catalogue. By default, harvested records cannot be edited.
diff --git a/docs/manual/docs/administrator-guide/configuring-the-catalog/user-interface-configuration.md b/docs/manual/docs/administrator-guide/configuring-the-catalog/user-interface-configuration.md
new file mode 100644
index 00000000000..cc87db286e5
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/configuring-the-catalog/user-interface-configuration.md
@@ -0,0 +1,264 @@
+# User Interface Configuration
+
+Most of the configuration parameters for the user interface can be changed by an administrator using the web interface in `Admin console` --> `Settings` --> `User Interface`.
+
+!!! info "Important"
+
+ Configuration of these parameters is critically important for the catalog in an operational context. Misunderstanding some settings may result in a system that does not function as expected. For example, the map can become unusable.
+
+
+
+
+By default the catalog will use the default UI configuration, named `srv`. To view and edit the settings for this configuration, choose `Create a default UI configuration`.
+
+To add a new configuration, such as for a sub-portal (see [Portal configuration](portal-configuration.md)) choose `Add new UI configuration` and choose one or more portal identifiers from the dropdown list `UI Configuration identifier`. Additional configurations can also be used for building an external JS application, which is able to load a specific configuration.
+
+!!! note
+
+ Since the settings form is a long form, the `save` button is repeated at the base of the page. In either case, all settings are saved.
+
+
+- **Filter settings**: This search box can be used to filter settings in the form, for example searching for "social" will show only the settings related to the Social Bar.
+
+
+
+## General options
+
+- **Humanize dates**: check this box to show dates in a human-friendly format. If not set, the full date will be shown.
+
+
+
+## Footer {#user-interface-config-footer}
+
+- **Footer**: Select this checkbox to determine whether the GeoNetwork footer is shown. If not set, no footer will be visible.
+- **Social bar**: Select this check box to show the social bar (links to twitter, facebook, linkedin etc) in the footer.
+
+
+
+## Top Toolbar {#user-interface-config-toptoolbar}
+
+- **Top toolbar**: Select this check box to determine whether the GeoNetwork top toolbar will be shown. If not set, no toolbar will be visible.
+- **List of languages**: Choose the languages from the list that should be available for translating the interface strings (available from the dropdown list in the top toolbar). If only one language remains, then no dropdown will be shown. Note that additional languages can be added, if translations are available, by selecting the `+` button below the list and adding the appropriate ISO codes.
+
+
+
+- **Show the logo in the header**: This determines where the catalog logo should be positioned. If selected, the logo will be positioned in the header, above the top toolbar and the toolbar logo (default) removed. If unset, the logo will appear in the top toolbar.
+- **Position of logo**: These options determine where on the header the logo will be positioned.
+
+
+
+## Home Page {#user-interface-config-homepage}
+
+- **Home page**: Select this check box to determine whether the Logo and Link to the Home Page are visible in the top toolbar. If not set, no logo and link is shown.
+- **Application URL**: Define the URL for the home page. In the majority of cases this can be left as the default.
+- **Fluid container for Home and Search**: Select this check box to determine whether the search box is full width in the browser page or if it is fixed width and centred.
+
+
+
+## Search application {#user-interface-config-searchpage}
+
+- **Search application**: Select this check box to determine whether the search application is visible in the top toolbar. If not set, no link is shown.
+- **Application URL**: Define the URL for the search application. In the majority of cases this can be left as the default.
+- **Number of records per page**: Define the options to determine the number of records shown per page of results, and the default.
+- **Type of facet**: Define the set of search facets should be visible in the search page. The default is `details` but `manager` can be used to show the facets more normally used on the editor page.
+- **Default search**: Define a default filter for the search.
+
+
+
+- **Facet field to display using tabs**: This option creates a tab for each configured facet above the search results. This can be used to further narrow down the search results. The list of facet names can be found at . For example, to include the Topic Category filter above the search results, the administrator would add `topicCat` as the facet field to display.
+- **List of facets**: This can be used to restrict the facets available for searching. For example, adding `topicCat` to this list would restrict the search options to `Topic Category` only. This can be useful for restricting the search options in a sub-portal or external web application. To add additional facets to the list, select the blue `+` button.
+- **Filters**: Define additional search criteria added to all searches and again are used primarily for external applications and sub-portals.
+
+
+
+- **Type of sort options**: Define the different ways by which a user can sort a set of search results. The **default sort by option** is shown below. Note that to search for example on `title` in alphabetical order it is necessary to set the order to `reverse`.
+- **List of templates for search results**: This section allows the administrator to configure templates for the layout of the search results. The default is `grid` whereas `list` is the default for the editor board.
+
+
+
+- **Default template used for search results**: Define the template page for the search. Generally this can be left as the default.
+- **List of formatter for record view**: Determine the formatter used to display the search results. See [Customizing metadata views](../../customizing-application/creating-custom-view.md) for information on creating a new formatter. To add an additional view, click the blue `+` button below the list and provide a name and a URL.
+
+
+
+### Search results configuration {#user-interface-config-searchresults}
+
+- **Related metadata types to query**: Use this section to define the metadata types displayed when showing search results in the grid. format To add additional types, click the blue `+` button. The possible types are shown below the form.
+
+
+
+### List of link types {#user-interface-config-linktypes}
+
+- **Links**: This section determines the types of links displayed when showing search results in the grid format. They are separated into `links`, `downloads`, `layers` and `maps` and for each type, a new entry can be added by clicking the blue `+` button below the list.
+
+
+
+- **Display filter tags in the search results**: When checked, the filter tags are visible above the search results. The default is to not show them.
+
+### User custom searches {#user-interface-customsearches}
+
+- **Enabled**: If checked the user will have the ability to create and save custom searches in the search tab. This functionality will be visible above the facets list on the left.
+- **Display featured user searches panel in home page**: If this is also enabled, an additional tab will be shown on the home page alongside `Latest news` and `Most popular`.
+
+### Saved Selections
+
+- **Enabled**: If checked the user will have the ability to save a selection of records in the search tab.
+
+
+
+## Map Application {#user-interface-config-mappage}
+
+This section describes how an administrator can configure the different maps in the user interface (the main map, the mini map displayed on the search result page, and the map used in the editor to draw an extent).
+
+- **Map Application**: The initial checkbox allows the main map tab to be disabled. In this case there will be no map tab shown in the top toolbar but the mini map and extent map described above will still be visible.
+- **Application URL**: This defines the URL for the map tab. In the majority of cases this can be left as the default.
+
+### External viewer
+
+- **Use an external viewer**: This option allows a third party mapping application to be used in place of the default GeoNetwork map. In this case, most of the settings below will no longer be used.
+- **Allow 3D mode**: If enabled, the user has the option to switch to 3D mode in the main map (see [Quick start](../../user-guide/quick-start/index.md)).
+- **Allow users to save maps as metadata record**: This option enables users to save layers and base maps configuration as a record in the catalog. Optionally users can add a title and an abstract.
+- **Export map as image**: If enabled, users can export the map as an image but requires CORS to be enabled on any external WMS services displayed on the map. This option is disabled by default to avoid issues with WMS layers.
+
+
+
+- **User preference persistence**: This option determines the behaviour of cookies related to the map. The various options are listed below.
+- **Bing Map Key**: If this option is filled in, then it is possible to use Bing Maps as base layers within the map application. You must get your own key for this to work.
+
+
+
+### List of preferred OGC services
+
+Default **wms** and **wmts** services can be defined here that will be available by default to the end user. New services can be added using the blue `+` button below the protocol lists.
+
+You can configure each map with different layers and projections.
+
+- **Map Projection** This is the default projection of the map. Make sure the projection is defined in **Projections to display maps into** below.
+
+
+
+- **List of map projections to display bounding box coordinates in** This is used in the map when editing a record and defining the bounding box extent. Note that the coordinates will be stored in WGS84 regardless of the projection used to draw them.
+
+
+
+- **Projections to display maps into** This is where the different projections available to the map are defined. All projections will be shown in the `Projection Switcher` tool of the map.
+
+
+
+In order to enable a new projection it must be defined here using the **proj4js** syntax, which can be found at . Additionally the default bounding box extent, maximum bounding box extent, and allowed resolutions (if required) can be defined.
+
+Ensure that the coordinates inserted are in the correct units for and are local to the projection. A list of resolutions is only relevant if the main map layer has a XYZ source, which does not follow the common tiling pattern.
+
+Check that this configuration is valid by opening the map.
+
+
+
+!!! info "Important"
+
+ If the configuration of a projection is incomplete or invalid, the map may fail to load.
+
+
+If a projection is defined which is not supported by the source of the map layer, the map application will reproject map images at the client side. This may cause unexpected behaviour, such as rotated or distorted labels.
+
+- **Optional Map Viewer Tools** The checkboxes in this section define the tools available to the user in the right toolbar of the main map. Elements that are not checked are not visible.
+- **OGC Service to use as a graticule**: This is optional and allows the use of an external service to display the graticule on the map.
+
+### Viewer Map Configuration {#user-interface-config-viewermap}
+
+This section is for configuring the map shown when viewing a record.
+
+- **Path to the context file (XML)**: An optional path to an XML file defining base layers and other configuration options. See `web/src/main/webapp/WEB-INF/data/data/resources/map/config-viewer.xml` for an example.
+- **Extent, expressed in current projection**: Use this option to override the extent defined in the context file.
+
+
+
+- **Layer objects in JSON**: Define additional layers to be shown on the map using JSON syntax. The supported types are:
+ - **wms**: generic WMS layer, required properties: `name, url`.
+ - **wmts**: generic WMTS layer, required properties: `name, url`.
+ - **tms**: generic TMS layer, required property: `url`.
+ - **osm**: OpenStreetMap default layer, no other property required.
+ - **stamen**: Stamen layers, required property: `name`.
+ - **bing_aerial**: Bing Aerial background, required property: `key` containing the license key.
+
+
+
+All layers can also have some optional extra properties:
+
+- **title** The title/label of the layer.
+- **projectionList** Projection array to restrict this layer to certain projections on the map.
+
+Examples of layers:
+
+This layer will use OpenStreetMap Stamen style, but only when the map is in `EPSG:3857`:
+
+``` json
+{"type":"stamen","projectionList":["EPSG:3857"]}
+```
+
+This WMS layer will be shown but only when the map is on `EPSG:4326`:
+
+``` json
+{"type":"wms","title":"OI.OrthoimageCoverage","name":"OI.OrthoimageCoverage",
+"url":"http://www.ign.es/wms-inspire/pnoa-ma?request=GetCapabilities&service=WMS",
+"projectionList":["EPSG:4326"]}
+```
+
+### Search Map Configuration
+
+This section defines the configuration for the mini map shown on the search page. It uses the same options as in [Viewer Map Configuration](user-interface-configuration.md#user-interface-config-viewermap).
+
+### Editor Map Configuration
+
+This section defines the configuration for the map shown when editing a record. It uses the same options as in [Viewer Map Configuration](user-interface-configuration.md#user-interface-config-viewermap).
+
+## Gazetteer
+
+- **Gazetteer**: If enabled a gazetteer will be shown in the top left of the main map.
+- **Application URL**: Set the application URL used for the gazetteer. In general this should be left as the default, but additional filtering can be applied using the syntax described at , for example to restrict results to a particular country (`country=FR`).
+
+
+
+## Record View
+
+- **Record view**:
+- **Show Social bar**: If enabled the social bar (links to facebook, twitter etc) are enabled in record view.
+
+## Editor Application
+
+- **Editor application**: If enabled the editor page, or contribute tab is available to users with the appropriate privileges. If not enabled the contribute tab is not shown in the top toolbar.
+- **Application URL**: This is the URL to the editor application and can generally be left as the default.
+- **Only my records**: If this checkbox is enabled then the "Only my records" checkbox in the editor dashboard will be checked by default.
+- **Display filters in dashboard**: If enabled, the currently selected facets will be shown above the search results in both the editor dashboard the batch editor page.
+- **Fluid container for the Editor**: If enabled, the editor application will have a full width container. If disabled it will have a fixed width and centered container.
+- **New metadata page layout**: Choose from the options for the layout of the `add new metadata` page. The default is `Horizontal` but a vertical layout can be chosen, or a custom layout based on a supplied template.
+- **Editor page indent type**: Choose from the options for the indent style when editing a record. The default is for minimal indents, select `Colored indents` to use the style shown below:
+
+
+
+## Admin console
+
+- **Admin console**:
+- **Application URL**: Set the application URL for the admin console. In general this should be left as the default.
+
+## Sign in application
+
+- **Sign in application**:
+- **Application URL**: Set the application URL for the sign in page. In general this should be left as the default.
+
+## Sign out application
+
+- **Application URL**: Set the application URL for the sign out. In general this should be left as the default.
+
+## Search application
+
+- **Search application**:
+- **Application URL**: Set the application URL for the search page. In general this should be left as the default.
+
+## JSON Configuration
+
+This section shows the JSON configuration for the currently applied User Interface settings. From here, the json can be saved to a file (by copying and pasting).
+
+- **Test client configuration**: Click this button to test the configuration in a new browser tab.
+- **Reset configuration**: Click this button to reset the configuration back to the default. Note that this will revert any changes you have made in the above page.
+
+
diff --git a/docs/manual/docs/administrator-guide/img/admin.png b/docs/manual/docs/administrator-guide/img/admin.png
new file mode 100644
index 00000000000..ff06c848dbb
Binary files /dev/null and b/docs/manual/docs/administrator-guide/img/admin.png differ
diff --git a/docs/manual/docs/administrator-guide/index.md b/docs/manual/docs/administrator-guide/index.md
new file mode 100644
index 00000000000..7d2a75603e7
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/index.md
@@ -0,0 +1,10 @@
+# Administrator guide
+
+- [Configuring the catalog](configuring-the-catalog/index.md)
+- [Managing users and groups](managing-users-and-groups/index.md)
+- [Managing classification system](managing-classification-systems/index.md)
+- [Managing metadata & template](managing-metadata-standards/index.md)
+
+
+
+All Admin functions are available from the Admin Dashboard from the main menu. On the Admin Dashboard you will find shortcuts to any administration option your role can access.
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/categories.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/categories.png
new file mode 100644
index 00000000000..60919d7be78
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/categories.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-api-collect.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-api-collect.png
new file mode 100644
index 00000000000..d5a2f913eed
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-api-collect.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-api-synch.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-api-synch.png
new file mode 100644
index 00000000000..dbb4244b346
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-api-synch.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-cache.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-cache.png
new file mode 100644
index 00000000000..c1bb06ffe0f
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-cache.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-editor-popup.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-editor-popup.png
new file mode 100644
index 00000000000..02c293c383c
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-editor-popup.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-editor-popupopen.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-editor-popupopen.png
new file mode 100644
index 00000000000..6a01da316e8
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-editor-popupopen.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-import.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-import.png
new file mode 100644
index 00000000000..efd3373fe80
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-import.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-manager.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-manager.png
new file mode 100644
index 00000000000..0b0242abeed
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-manager.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-search.png b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-search.png
new file mode 100644
index 00000000000..b10d8fba12c
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-classification-systems/img/directories-search.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/index.md b/docs/manual/docs/administrator-guide/managing-classification-systems/index.md
new file mode 100644
index 00000000000..b7cbca16ebe
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-classification-systems/index.md
@@ -0,0 +1,5 @@
+# Managing classification system
+
+- [Managing categories](managing-categories.md)
+- [Managing directories](managing-directories.md)
+- [Managing thesaurus](managing-thesaurus.md)
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/managing-categories.md b/docs/manual/docs/administrator-guide/managing-classification-systems/managing-categories.md
new file mode 100644
index 00000000000..6afc42ce6fe
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-classification-systems/managing-categories.md
@@ -0,0 +1,9 @@
+# Managing categories
+
+GeoNetwork has a concept of categories that can be assigned to metadata documents, but these are not represented in the metadata. So when the metadata is exported, the category will be lost. You can use these categories to separate documents into groups, without changing the actual content of the metadata. Categories can be used to filter a search result, or limit the output of a custom csw endpoint.
+
+To assign a category to a metadata document. Go to the metadata modification form and select the requested category from the pull down in the menu. Then save your metadata.
+
+To modify the available categories in the catalog, from the admin page, open the "classification systems" and then the "category" tab.
+
+Note: If you add or modify categories, they may not obtain an appropriate icon. These icon are managed in `/catalog/style/gn_icons.less`. In this file category-classes are mapped to font-awesome variables that map to a certain [font-awesome icon](https://fontawesome.io).
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/managing-directories.md b/docs/manual/docs/administrator-guide/managing-classification-systems/managing-directories.md
new file mode 100644
index 00000000000..19ffb269aac
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-classification-systems/managing-directories.md
@@ -0,0 +1,196 @@
+# Managing directories
+
+The catalog supports metadata records that are composed from fragments of metadata. The idea is that the fragments of metadata can be used in more than one metadata record.
+
+Here is a typical example of a fragment. This is a responsible party and it could be used in the same metadata record more than once or in more than one metadata record if applicable.
+
+``` xml
+
+
+ John D'Ath
+
+
+ Mulligan & Sons, Funeral Directors
+
+
+ Undertaker
+
+
+
+
+
+```
+
+Metadata fragments that are saved in the catalogue database are called subtemplates. This is mainly for historical reasons as a subtemplate is like a template metadata record in that it can be used as a 'template' for constructing a new metadata record.
+
+Fragments can be inserted in metadata record in 2 modes:
+
+- by copy/paste
+- by link (if xlink support is enabled. See [Metadata XLink](../configuring-the-catalog/system-configuration.md#xlink_config))
+
+When using XLinks, if the fragment is updated, then the related fragment in all metadata records will also be updated (check the XLink cache).
+
+Fragments may be created by harvesting (see [Harvesting Fragments of Metadata to support re-use](../../user-guide/harvesting/index.md#harvesting_fragments)) or imported using the metadata import page.
+
+This section of the manual describes:
+
+- how to manage directories of subtemplates
+- how to extract fragments from an existing set of metadata records and store them as subtemplates
+- how to manage the fragment cache used to speed up access to fragments that are not in the local catalogue
+
+## Managing Directories of subtemplates
+
+There are some differences between the handling of subtemplates and metadata records. Unlike metadata records, subtemplates do not have a consistent root element, the metadata schema they use may not be recognizable, they do not appear in the main search results (unless they are part of a metadata record). Therefore, the editor board allows you to search and manage privileges for directory entries.
+
+
+
+From the editor board, choose `Manage directory` to access the editor for directory entries:
+
+
+
+If you do not see the `Organizations and Contacts` tab then ensure that you have created subtemplates for contacts for your metadata profile, and that you have loaded them using the `Metadata and Templates` section.
+
+From this page, editors can choose a type of directory using the top tabs, edit/remove/import new subtemplates.
+
+To import new entries, use the metadata import page and choose the appropriate type of record:
+
+
+
+Like metadata records, they are allocated an integer id and are stored in the catalog metadata table (with template field set to "y").
+
+## Insert a directory entry in a metadata record
+
+From the metadata editor, the directory can be used to populate contacts for example.
+
+
+
+Open the directory selector, choose a contact and then choose the contact role.
+
+
+
+## Extracting subtemplates from metadata records
+
+Many sites have existing metadata records with common information eg. contact information in an ISO CI_Contact element. Directory entries such as these can be extracted from a selected set of metadata records using the "Extract subtemplates" API.
+
+To use this function the following set of steps should be followed:
+
+- Make sure you understand what an XPath is - see for example.
+- Identify fragments of metadata that they would like to manage as reusable subtemplates in the metadata record. This can be done using an XPath. eg. the XPath `.//gmd:CI_ResponsibleParty` identifies all responsible party in a records. An example of such a fragment (taken from one of the sample records) is shown in the following example:
+
+``` xml
+
+
+ Jippe Hoogeveen
+
+
+ FAO - NRCW
+
+
+ Technical Officer
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Viale delle Terme di Caracalla
+
+
+ Rome
+
+
+
+
+
+ 00153
+
+
+ Italy
+
+
+ jippe.hoogeveen@fao.org
+
+
+
+
+
+
+
+
+
+```
+
+- Identify and record the XPath of a field or fields within the fragment which text content will be used as the id of the subtemplate. This XPath should be relative to the root element of the fragment identified in the previous step. So for example, in the fragment above we could choose `.//gmd:electronicMailAddress/gco:CharacterString/text()` as the id for the fragments to be created.
+- On the API page, choose the registries / collect operation:
+
+
+
+- Fill in the form with the information collected in the previous steps.
+- Extracted subtemplates can be previewed using the GET mode and once validated, use the PUT method to save results in the catalog.
+
+Finally, go to the subtemplate directory management interface and you should be able to select the root element of your subtemplates to examine the extracted subtemplates.
+
+Subtemplate indexing is based on the schema (see index-fields folder for details). Currently ISO19139 index subtemplates using as root element:
+
+- gmd:CI_ResponsibleParty
+- gmd:MD_Distribution
+- gmd:CI_OnlineResource
+- gmd:EX_Extent
+
+In ISO19115-3
+
+- cit:CI_Responsibility
+- *[mdq:result]
+- gex:EX_Extent
+
+Other configuration examples to collect:
+
+- Parties in ISO19115-3
+ - `xpath`: `.//cit:CI_Responsibility`
+ - `identifierXpath`: `.//cit:electronicMailAddress/*/text()`
+- Quality specifications in ISO19115-3
+ - `xpath`: `.//*[mdq:result]`
+ - `identifierXpath`: `.//cit:title/*/text()`
+- Extent in ISO19115-3
+ - `xpath`: `.//gex:EX_Extent`
+ - `identifierXpath`: `concat(.//gex:westBoundLongitude/*/text(), ', ', .//gex:eastBoundLongitude/*/text(), ', ', .//gex:southBoundLatitude/*/text(), ', ',.//gex:northBoundLatitude/*/text())` or `gex:description/*/text()`
+- Constraints in ISO19115-3
+ - `xpath`: `.//mri:resourceConstraints/*`
+
+## Synchronizing subtemplates with metadata records
+
+Once created, the catalog provides the capability to synchronize metadata records with directory entries. For this, use the API testing page.
+
+The synchronize process use the same parameters as the collecting process with 2 optionals arguments:
+
+- `propertiesToCopy` to preserve some element which may be defined in the fragment in the metadata (eg. contact role)
+- `substituteAsXLink` to indicate if copy/paste mode or XLink mode should be used.
+
+
+
+## Managing the fragment cache
+
+If metadata records in your catalog link in fragments from external sites, the catalog caches these fragments after the first look up so as to reduce the amount of network traffic and speed up the display of metadata records in search results.
+
+The cache is handled automatically using the Java Cache System (JCS). JCS handles large caches intelligently by:
+
+- defining a maximum number of cached objects
+- using as much main memory as possible before moving to secondary storage (disk)
+- providing cache persistence: the cache is saved to disk when the web application is shutdown and restores the cache from disk when restarting
+
+You can configure JCS parameters in GeoNetwork using the JCS configuration file in **INSTALL_DIR/web/geonetwork/WEB-INF/classes/cache.ccf**.
+
+Some operations in the catalog (such as harvesting) that generate metadata fragments, will automatically refresh the XLink cache when a new fragment is generated. However, if you are linking fragments from an external site, then depending on how often the change, you will need to manually refresh the XLink cache. To do this you should navigate to the Administration page and select the "Clear XLink Cache and Rebuild Index of Records with XLinks" function as highlighted in the following screenshot of the "Administration" page.
+
+
diff --git a/docs/manual/docs/administrator-guide/managing-classification-systems/managing-thesaurus.md b/docs/manual/docs/administrator-guide/managing-classification-systems/managing-thesaurus.md
new file mode 100644
index 00000000000..ca161024dd9
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-classification-systems/managing-thesaurus.md
@@ -0,0 +1,207 @@
+# Managing thesaurus
+
+## Introduction
+
+A thesaurus is a list of concepts from a specialized field of knowledge. In a metadata catalog, concepts from a thesaurus can be assigned to a metadata record (as keywords) as a way of associating it with one or more concepts from a field of knowledge. For example, a record may be assigned a keyword 'AGRICULTURE - Crops' meaning that the record describes a resource or activity relating to crops in the field of Agriculture. It's a good practice to look for existing thesauri before creating your own thesaurus.
+
+In GeoNetwork, the process of assigning keywords to a metadata record takes place in the metadata editor. The user can choose concepts from one or more thesauri to associate the record with the concepts described by those concepts. This process is supported for both ISO19115/19139 and dublin core metadata records using an thesaurus picker.
+
+Concepts within a field of knowledge or in different fields of knowledge may be related or even be equivalent. For example, in a thesaurus describing geographic regions, the Australian state of 'Tasmania' is a specialization of the country of Australia. As an example of overlapping concepts in different fields, a thesaurus describing science activities in the field of global change may have concepts relating to agricultural activities that will be equivalent to terms from a thesaurus that describes the themes used in a map series.
+
+In GeoNetwork, thesauri are represented as SKOS () and stored in an application/xml+rdf encoding. SKOS captures concepts and relationships between concepts. SKOS thesauri can be imported from standalone files or they can be generated from ISO19135 register records in a GeoNetwork catalog. ISO19135 (more on this below) not only captures the concepts and relationships between the concepts, but (amongst other things) how the concepts have evolved and most importantly, who has contributed to and managed the evolution of the concepts and the thesauri itself.
+
+## External, Local and Register Thesauri
+
+There are three types of thesaurus in GeoNetwork. The different types are based on where the thesaurus comes from:
+
+- *External*: A thesaurus managed by an external organisation and imported as a SKOS file. It is flagged to `external` which means that users are not allowed to edit the thesaurus.
+- *Local*: A thesaurus built in the GeoNetwork thesaurus editor and stored as a SKOS file. It is flagged as `local` which means that users are allowed to edit the thesaurus.
+- *Register*: A SKOS thesaurus created from an ISO19135 register record. Users can edit the thesaurus by changing the content of the ISO19135 register record in the GeoNetwork metadata editor and then regenerating the thesaurus. Users cannot edit the thesaurus in thesaurus manager.
+
+## ISO19115/19139 Thesaurus Categories
+
+All thesauri in GeoNetwork are categorized using the code list values for the gmd:MD_KeywordTypeCode element from ISO19115/19139. The categories and their meanings are given below but can also be found in :
+
+| ISO Thesaurus Category | Description |
+|------------------------|------------------------------------------------------------------------------------|
+| place | Thesaurus has concepts identifying a location |
+| stratum | Thesaurus has concepts identifying layers of any deposited substance |
+| temporal | Thesaurus has concepts identifying a time period |
+| theme | Thesaurus has concepts identifying a particular subject or topic |
+| discipline | Thesaurus has concepts identifying a branch of instruction or specialized learning |
+
+## SKOS format
+
+The Simple Knowledge Organisation Systems (SKOS) is an area of work developing specifications and standards to support the use of knowledge organisation systems (KOS) such as thesauri, classification schemes. This format is used by GeoNetwork to store thesaurus information.
+
+A concept is defined by an identifier, a preferred label, a definition and links with other concepts. Labels and definitions could be stored in multiple languages (using the xml:lang attributes). Three type of links between concepts have been defined in the SKOS format:
+
+- related terms
+- broader terms
+- narrower terms
+
+For example, a concept `ABLETTE` could be defined as follow with a label in French and English, linked to broader concept:
+
+
+ ABLETTE
+ BLEAK
+
+
+
+GeoNetwork supports multilingual thesauri (e.g. Agrovoc). Search and editing takes place in the current user interface language (i.e. if the interface is in English, when editing metadata, GeoNetwork will only search for concept in English).
+
+We use SKOS to represent thesauri in GeoNetwork because:
+
+- it provides a simple and compact method of describing concepts and relationships between concepts from a field of knowledge
+- SKOS concepts can be queried and managed by the sesame/openRDF software used by GeoNetwork
+
+## ISO19135 register format
+
+ISO19135 is an ISO standard that describes procedures for registering an item and the schema for describing a list (or register) of items and the processes by which the items can be created and evolve. This schema is available as a plugin for use in GeoNetwork. To use it, you must download and load the iso19135 plugin schema into GeoNetwork. FIXME: We need a standard way of referring to plugin schemas and a standard place from which they can be downloaded.
+
+A typical ISO19135 register record describes:
+
+- the name and a description of the register
+- version and language information
+- contact information of those that have a role in the register (eg. manager, contributor, custodian, publisher etc)
+- the elements used to describe an item in the register
+- the items
+
+The standard information used to describe a register item includes:
+
+- identifier
+- name and description of item
+- field of application
+- lineage and references to related register items
+
+An example of a register item from register of the NASA GCMD (Global Change Master Directory) science keywords is shown below.
+
+
+
+ 7
+
+
+ Aquaculture
+
+
+ valid
+
+
+ 2006
+
+
+
+
+
+
+ 5
+
+
+
+
+
+
+
+
+As mentioned earlier, to use a thesaurus described by an ISO19135 register record, GeoNetwork uses an XSLT called xml_iso19135ToSKOS.xsl (from the convert subdirectory in the iso19135 plugin schema) to extract the following from the ISO19135 register record:
+
+- valid concepts (grg:itemIdentifier, grg:name, grg:status)
+- relationships to other concepts (grg:specificationLineage)
+- title, version and other management info
+
+This information is used build a SKOS file. The SKOS file is then available for query and management by the sesame/openRDF software used in GeoNetwork.
+
+## Creating or Importing a Thesaurus
+
+External and local thesauri are created or imported using the thesaurus manager. You can use the thesaurus manager by:
+
+- logging in as an administrator
+- navigating to the 'Administration' page and clicking on the link `Manage thesauri`
+
+The thesaurus manager page will show a list of thesauri that have been created or imported. The upper part of the page provides the user with functions to edit, add, modify or search a thesaurus. The lower part provides a function to upload an external thesaurus in SKOS format.
+
+### Creating a local thesaurus
+
+To create a local thesaurus, click the `+` sign on the category you want your thesaurus to be in. Once created, the thesaurus can be updated through the edit interface. The meaning of each column is as follows:
+
+- **Type** - This is an identifier assigned to the thesaurus in GeoNetwork. It is composed of the ISO category to which the thesaurus has been assigned (see the codelist for the gmd:MD_KeywordTypeCode element in ), whether the thesaurus is a local, external or register thesaurus and the filename of the SKOS file that holds the thesaurus. (Note: the name of the file used to hold a register thesaurus is the uuid of the ISO19135 register record that describes the thesaurus).
+- **Name** - This is the name of the thesaurus which is the administrator on creation or the filename if the thesaurus is ting a thesaurus, the name of the thesaurus will be the filename of the thesaurus.
+
+For each thesaurus the following buttons are available:
+
+- **Download** - Link to the SKOS RDF file.
+- **Delete** - Remove thesaurus from the current node.
+- **View** - If type is external, the view button allows to search and view concepts.
+- **Edit** - If type is local, the edit button allows to search, add, remove and view concepts.
+
+### Import an external thesaurus
+
+GeoNetwork allows thesaurus import in SKOS format. Once uploaded, an external thesaurus cannot be updated. Select the category, browse for the thesaurus file and click upload. The SKOS file will be in `GEONETWORK_DATA_DIR/config/codelist/external/thesauri/`.
+
+At the bottom of the page there are the following buttons:
+
+1. *Back*: Go back to the main administration page.
+2. *Upload*: Upload the selected RDF file to the node. Then it will list all thesaurus available on the node.
+
+### Creating a register thesaurus
+
+An ISO19135 record in the local GeoNetwork catalog can be turned into a SKOS file and used as a thesaurus in GeoNetwork. ISO19135 records not in the local catalog can be harvested from other catalogs (eg. the catalog of the organisation that manages the register). Once the ISO19135 register record is in the local catalog, the process of turning it into a thesaurus for use in the keywords selector begins a search for the record. Having located the record in the search results, one of the actions on the record is to 'Create/Update Thesaurus'.
+
+> *Search results showing ISO19135 record with thesaurus creation action*
+
+After selecting this action, you can choose the ISO thesaurus category appropriate for this thesaurus:
+
+> *Selecting the ISO thesaurus category when creating a thesaurus*
+
+After selecting the ISO thesaurus category, the ISO19135 register record is converted to a SKOS file and installed as a thesaurus ready for use in the metadata editor. As described above in the section on ISO19135, only the valid register items are included in the thesaurus. This behaviour and any of the mappings between ISO19135 register items and the SKOS thesaurus file can be changed or inspected by looking at the XSLT xml_iso19135TOSKOS.xsl in the convert subdirectory of the iso19135 schema plugin.
+
+## Editing/browsing a local or external thesaurus: add/remove/browse keywords
+
+From the thesaurus administration interface, click on the edit button for a local thesaurus or the view button for an external thesaurus. This interface allows:
+
+- keywords search
+- add/remove keywords for local thesaurus.
+
+Use the textbox and the type of search in order to search for keywords.
+
+## Editing a register thesaurus
+
+A register thesaurus is created from an ISO19135 metadata record as described above, so a register thesaurus is updated by editing the ISO19135 metadata record and then regenerating the register thesaurus. The ISO19135 metadata record can be created and edited in the GeoNetwork editor.
+
+### Preparing to edit an ISO19135 register record {#xlinks_thesaurus}
+
+Register records can be very large. For example, a register record describing the ANZLIC Geographic Extent Names register has approx 1800 register items. Each register item holds not only the name of the geographic extent, but also its geographic extent and details of the lineage, relationships to other terms and potentially, the evolution of the extent (changes to name, geographic extent) including the details of changes and why those changes occurred. Editing such a large record in the GeoNetwork editor can cause performance problems for both the browser and the server because the editor constructs an HTML form describing the entire record. Fortunately, a much more scalable approach exists which is based on extracting the register items from the ISO19135 register record, storing them as subtemplates (essentially small metadata records with just the content of the register item). The process for extracting register items from an ISO19135 register record is as follows:
+
+- search for and select the register record
+- choose 'Extract register items' from the 'Actions on selected set' menu
+- After the register items have been extracted, you should see a results summary like the following.
+- The figure for 'Subtemplates extracted' is the number of register items extracted from the ISO19135 register record.
+
+### Editing a register item
+
+To edit/change any of the register items that have been extracted as subtemplates, you can use the Directory management interface. This interface is accessed from the 'Administration' menu, under 'Manage Directories'. In this interface:
+
+- select 'Register Item (GeoNetwork)' as the type of subtemplate to edit as follows.
+- enter a search term or just select the search option to return the first 50 register items.
+- register items will appear in the left hand side bar, selecting on one will open an editing interface in the right hand panel.
+
+### Editing global register information
+
+To edit/change any of the global register information (eg. register owner, manager, version, languages), edit the register record in the normal GeoNetwork metadata editing interface.
+
+## Metadata editing: adding keywords
+
+When editing an ISO metadata record, a keyword (or concept) picker can be used which allows the editor to:
+
+- do searches for keywords in one or more thesauri in the catalog (search results are displayed on the left).
+- select one or more keywords and add them to the selected items list (using arrows or drag & drop) on the right.
+- add the selected keywords directly into metadata, grouping keywords by thesaurus.
+
+The editor can also control how many keywords from searches are displayed in the keyword picker (default is 50).
+
+Notice that a URL pointing to the source thesaurus is included in the Thesaurus Name citation (the actual element used for this is gmd:otherCitationDetails/gmx:FileName). The thesaurus can be downloaded as a SKOS file if it is a local or external thesaurus. For register thesauri the URL refers to the ISO19135 register record from which the thesaurus was created.
+
+## Search criteria: keywords
+
+You can search on keywords using the facet panel. All keywords are stored in the index field `tag` and are also available in field depending on thesaurus name eg. `th_theme` for INSPIRE themes. The field name is based on the thesaurus type and filename.
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/configure-validation.md b/docs/manual/docs/administrator-guide/managing-metadata-standards/configure-validation.md
new file mode 100644
index 00000000000..07ac9f00bce
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-metadata-standards/configure-validation.md
@@ -0,0 +1,27 @@
+# Configuring validation levels {#configure-validation}
+
+Each standard defines validation levels (using schematron - see [Implementing schema plugins](../../customizing-application/implementing-a-schema-plugin.md)). By default, ISO19139 proposes validation using:
+
+- ISO rules
+- INSPIRE rules (TG v1.3)
+- GeoNetwork rules (only related to multilingual records)
+- URL checker
+
+All levels will be applied by default during validation and the admin interface allows customization if a rule:
+
+- is required to be valid (will be reported in green/red depending on the status)
+- is for information only (will be reported in blue)
+- is ignored.
+
+
+
+Also conditions can be set to only apply rules to specific records. The condition can be defined on:
+
+- XPath
+- Group
+- User profile
+- Keyword
+
+For example, [geocat.ch](https://www.geocat.ch/) defines for the GM03 ISO19139 profile rules depending on groups (ie. partners) and the type of dataset eg. a basic geodata.
+
+
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-choice.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-choice.png
new file mode 100644
index 00000000000..764dfe7e58d
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-choice.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-config.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-config.png
new file mode 100644
index 00000000000..678d75bfbb6
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-config.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-custom.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-custom.png
new file mode 100644
index 00000000000..bcbfa61e436
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-custom.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-customform.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-customform.png
new file mode 100644
index 00000000000..bc40fa9752e
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-customform.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-setting.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-setting.png
new file mode 100644
index 00000000000..c28c31fe2db
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/mit-setting.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/validation-level-example.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/validation-level-example.png
new file mode 100644
index 00000000000..d538765be4d
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/validation-level-example.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/img/validation-level.png b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/validation-level.png
new file mode 100644
index 00000000000..110e18e3450
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-metadata-standards/img/validation-level.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/index.md b/docs/manual/docs/administrator-guide/managing-metadata-standards/index.md
new file mode 100644
index 00000000000..4b5c7cb1d90
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-metadata-standards/index.md
@@ -0,0 +1,5 @@
+# Managing metadata & template {#metadata-and-template}
+
+- [Managing metadata standards](standards.md)
+- [Configuring validation levels](configure-validation.md)
+- [Configuring metadata identifier](metadata-identifier.md)
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/metadata-identifier.md b/docs/manual/docs/administrator-guide/managing-metadata-standards/metadata-identifier.md
new file mode 100644
index 00000000000..b45b2049f88
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-metadata-standards/metadata-identifier.md
@@ -0,0 +1,34 @@
+# Configuring metadata identifier {#metadata_identifier}
+
+Some organisations require the definition of metadata identifiers using [URN](https://en.wikipedia.org/wiki/Uniform_Resource_Name) templates.
+
+From the `admin console` --> `metadata and template` --> `Metadata identifier templates` users can customise the behaviour of the catalog when creating new metadata:
+
+- Create a random UUID. This is the "standard" behaviour of GeoNetwork and it's set as default.
+- Use metadata URN templates to define the metadata identifiers. This option allows the user to enter a metadata identifier from the metadata URN templates defined by an administrator user.
+
+To enable the usage of metadata URN templates for the metadata identifiers, the user should disable the following setting:
+
+
+
+Once enabled the metadata create page displays a new panel, that allows the user to select the metadata identifier template:
+
+
+
+- Custom identifier: Allows the user to enter a free-text value for the metadata identifier.
+
+
+
+- Autogenerated identifier: the catalog creates a random UUID.
+- A list of custom templates: A list of the metadata identifier templates. When the user selects one of these templates, the form request the different template values.
+
+
+
+New templates can be added in the configuration interface:
+
+
+
+For each template a user can define some parameters to fill in the metadata create form. Parameters are defined between curly braces. For example:
+
+- ::{TT}{AA}{II}{CCCC}
+- au.gov.bom::{IDCODE}
diff --git a/docs/manual/docs/administrator-guide/managing-metadata-standards/standards.md b/docs/manual/docs/administrator-guide/managing-metadata-standards/standards.md
new file mode 100644
index 00000000000..63fe7a73e40
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-metadata-standards/standards.md
@@ -0,0 +1,52 @@
+# Managing metadata standards
+
+Metadata records in GeoNetwork are described by a schema. The schema sets out the structuring of the metadata record and provides all the ancillary data and functions to use the schema in GeoNetwork.
+
+A metadata schema plugin capability was introduced in GeoNetwork 2.8.0. In 3.0.0 the plugin capability was expanded to facilitate the fact that plugins can contain java-code.
+
+!!! note
+
+ Adding a metadata schema to GeoNetwork that is incorrect or invalid can thoroughly break your GeoNetwork instance. This section is for catalogue administrators who are confident about metadata schemas and understand the different technologies involved with a GeoNetwork metadata schema.
+
+
+A detailed description of what constitutes a metadata schema for GeoNetwork can be found in the GeoNetwork Developers Manual. This section will describe how to access the schema add, update and delete functions and how those functions should be used.
+
+!!! note
+
+ Metadata schemas should be thoroughly tested in a development instance of GeoNetwork **before** they are deployed in a production instance. Errors in a schema plugin (particularly in the presentation XSLTs) may make your GeoNetwork instance unusable.
+
+
+## Adding a schema
+
+To add a metadata schema to the catalog, a rebuild of the sources is required. In a source-code tree there are 4 actions to be done in the settings (database).
+
+- Place the schema-folder in /schemas
+
+- Verify and if compatible update the version of GeoNetwork (parent) referenced from the pom.xml file in the schema plugin.
+
+- Add a reference in /schemas/pom.xml to the newly added schema
+
+ ``` xml
+ {myschema}
+ ```
+
+- Add references to the newly added schema in /web/pom.xml
+
+ ``` xml
+
+ ${project.groupId}
+ {myschema}
+ ${project.version}
+
+ ```
+
+- and
+
+ ``` xml
+
+ ${project.basedir}/../schemas/{myschema}/src/main/plugin
+ ${basedir}/src/main/webapp/WEB-INF/data/config/schema_plugins
+
+ ```
+
+Then Build and deploy your instance of GeoNetwork.
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/authentication-mode.md b/docs/manual/docs/administrator-guide/managing-users-and-groups/authentication-mode.md
new file mode 100644
index 00000000000..61b53c68e47
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-users-and-groups/authentication-mode.md
@@ -0,0 +1,845 @@
+# Authentication mode
+
+By default the catalog uses the internal database for user management and authentication. However there are some other authentication mechanisms available:
+
+- [Configuring LDAP](authentication-mode.md#authentication-ldap)
+- [Configuring LDAP - Hierarchy](authentication-mode.md#authentication-ldap-hierarchy)
+- [Configuring CAS](authentication-mode.md#authentication-cas)
+- [Configuring OAUTH2 OpenID Connect](authentication-mode.md#authentication-openid)
+- [Configuring Keycloak](authentication-mode.md#authentication-keycloak)
+- [Configuring Shibboleth](authentication-mode.md#authentication-shibboleth)
+
+Which mode to use is configured in **`WEB-INF/config-security/config-security.xml`** or via an environment variable `geonetwork.security.type`.
+
+Uncomment the relevant line in **`WEB-INF/config-security/config-security.xml`**:
+
+``` xml
+
+```
+
+## Configuring LDAP {#authentication-ldap}
+
+[Lightweight Directory Access Protocol (LDAP)](https://en.wikipedia.org/wiki/Ldap) enables GeoNetwork to verify usernames and passwords to a remote identity store. LDAP implementation uses the default GeoNetwork Login User Interface elements.
+
+GeoNetwork currently has 2 approaches to configure LDAP. Verify also the alternative approach in [Configuring LDAP - Hierarchy](authentication-mode.md#authentication-ldap-hierarchy).
+
+The LDAP configuration is defined in `WEB-INF/config-security/config-security.properties`, you can then configure your environment updating the previous file or overriding the properties in the file `WEB-INF/config-security/config-security-overrides.properties`.
+
+1. Define the LDAP connection:
+
+ - `ldap.base.provider.url`: This tells the portal where the LDAP server is located. Make sure that the computer with the catalog can hit the computer with the LDAP server. Check to make sure that the appropriate ports are opened, etc.
+ - `ldap.base.dn`: this will usually look something like: "dc=[organizationnamehere],dc=org"
+ - `ldap.security.principal` / `ldap.security.credentials`: Define LDAP administrator user to use to bind to LDAP. If not define, an anonymous bind is made. Principal is the username and credentials property the password.
+
+ ``` text
+ # LDAP security properties
+ ldap.base.provider.url=ldap://localhost:389
+ ldap.base.dn=dc=fao,dc=org
+ ldap.security.principal=cn=admin,dc=fao,dc=org
+ ldap.security.credentials=ldap
+ ```
+
+ To verify that you have the correct settings, try to connect to the LDAP server using an LDAP browser application.
+
+2. Define where to find users in LDAP structure for authentication:
+
+ - `ldap.base.search.base`: this is where the catalog will look for users for authentication.
+ - `ldap.base.dn.pattern`: this is the distinguished name for the user to bind with. `{0}` is replaced by the user name typed in the sign in screen.
+
+ ``` text
+ ldap.base.search.base=ou=people
+ ldap.base.dn.pattern=uid={0},${ldap.base.search.base}
+ #ldap.base.dn.pattern=mail={0},${ldap.base.search.base}
+ ```
+
+### Authorization Settings
+
+When using LDAP, the user information and privileges for GeoNetwork could be defined from the LDAP attributes.
+
+#### User information
+
+The user information could be retrieved from the LDAP configuring for each user attribute in the catalog database which LDAP attributes match. If the attribute is empty or not defined, a default value could be defined. The property value is composed by two parts separated by `,` character. The first part is the attribute name and the second part is the default value in case the attribute name is not define or the attribute value in LDAP is empty.
+
+The configuration is the following:
+
+``` text
+# Map user information to LDAP attributes and default values
+# ldapUserContextMapper.mapping[name]=ldap_attribute,default_value
+ldapUserContextMapper.mapping[name]=cn,
+ldapUserContextMapper.mapping[surname]=givenName,
+ldapUserContextMapper.mapping[mail]=mail,data@myorganization.org
+ldapUserContextMapper.mapping[organisation]=,myorganization
+ldapUserContextMapper.mapping[kind]=,
+ldapUserContextMapper.mapping[address]=,
+ldapUserContextMapper.mapping[zip]=,
+ldapUserContextMapper.mapping[state]=,
+ldapUserContextMapper.mapping[city]=,
+ldapUserContextMapper.mapping[country]=,
+```
+
+#### Privileges configuration
+
+User groups and user profiles could be set optionally from LDAP information or not. By default user privileges are managed from the local database. If LDAP information should be used to define user privileges, set the `ldap.privilege.import` property `true`:
+
+``` text
+ldap.privilege.import=true
+```
+
+When importing privileges from LDAP, the catalog administrator could decide to create groups defined in the LDAP and not defined in local database. For this set the following property to true:
+
+``` text
+ldap.privilege.create.nonexisting.groups=false
+```
+
+In order to define which groups the user is member of and which profile is the user:
+
+``` text
+ldapUserContextMapper.mapping[privilege]=groups,sample
+# If not set, the default profile is RegisteredUser
+# Valid profiles are ADMINISTRATOR, USER_ADMIN, REVIEWER, EDITOR, REGISTERED_USER, GUEST
+ldapUserContextMapper.mapping[profile]=privileges,RegisteredUser
+```
+
+Attributes configuration:
+
+- privilege attribute contains the group this user is member of. More than one group is allowed.
+- profile attribute contains the profile of the user.
+
+User valid profiles are:
+
+- Administrator
+- UserAdmin
+- Reviewer
+- Editor
+- RegisteredUser
+- Guest
+
+If LDAP attribute containing profiles does not match the catalog profile list, a mapping could be defined:
+
+``` text
+# Map LDAP custom profiles to catalog profiles. Not used if ldap.privilege.pattern is defined.
+ldapUserContextMapper.profileMapping[Admin]=Administrator
+ldapUserContextMapper.profileMapping[Editor]=Reviewer
+ldapUserContextMapper.profileMapping[Public]=RegisteredUser
+```
+
+For example, in the previous configuration, the attribute value `Admin` will be mapped to `Administrator` (which is a valid profile for the catalog).
+
+An attribute could define both the profile and the group for a user. To extract this information, a custom pattern could be defined to populate user privileges according to that attribute:
+
+1. Define one attribute for the profile and one for groups in `WEB-INF/config-security/config-security-overrides.properties`
+
+ ``` text
+ # In config-security-overrides.properties
+ ldapUserContextMapper.mapping[privilege]=cat_privileges,sample
+ ```
+
+2. Define one attribute for the privilege and define a custom pattern:
+
+ ``` text
+ # In config-security.properties
+ ldap.privilege.pattern=CAT_(.*)_(.*)
+ ldap.privilege.pattern.idx.group=1
+ ldap.privilege.pattern.idx.profil=2
+ ```
+
+ Enable the bean `er` for `LDAPUserDetailsContextMapperWithPattern` ( in `WEB-INF/config-security/config-security-ldap.xml`).
+
+ ``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+3. Define custom location for extracting group and role (no support for group/role combination) (use LDAPUserDetailsContextMapperWithProfileSearch in **`config-security.xml`**).
+
+ ``` text
+ ldap.privilege.search.group.attribute=cn
+ ldap.privilege.search.group.object=ou=groups
+ #ldap.privilege.search.group.query=(&(objectClass=*)(memberUid=uid={0},${ldap.base.search.base},${ldap.base.dn})(cn=EL_*))
+ ldap.privilege.search.group.queryprop=memberuid
+ ldap.privilege.search.group.query=(&(objectClass=*)(memberUid=uid={0},${ldap.base.search.base},${ldap.base.dn})(|(cn=SP_*)(cn=EL_*)))
+ ldap.privilege.search.group.pattern=EL_(.*)
+ ldap.privilege.search.privilege.attribute=cn
+ ldap.privilege.search.privilege.object=ou=groups
+ ldap.privilege.search.privilege.query=(&(objectClass=*)(memberUid=uid={0},${ldap.base.search.base},${ldap.base.dn})(cn=SV_*))
+ ldap.privilege.search.privilege.pattern=SV_(.*)
+ ```
+
+ The LDAP attribute can contains the following configuration to define the different type of users, for example:
+
+ ``` text
+ cat_privileges=CAT_ALL_Administrator
+
+ -- Define a reviewer for the group GRANULAT
+ cat_privileges=CAT_GRANULAT_Reviewer
+
+ -- Define a reviewer for the group GRANULAT and editor for MIMEL
+ cat_privileges=CAT_GRANULAT_Reviewer
+ cat_privileges=CAT_MIMEL_Editor
+
+ -- Define a reviewer for the group GRANULAT and editor for MIMEL and RegisteredUser for NATURA2000
+ cat_privileges=CAT_GRANULAT_Reviewer
+ cat_privileges=CAT_MIMEL_Reviewer
+ cat_privileges=CAT_NATURA2000_RegisteredUser
+
+ -- Only a registered user for GRANULAT
+ cat_privileges=CAT_GRANULAT_RegisteredUser
+ ```
+
+#### Synchronization
+
+A synchronization task is taking care of removing LDAP users that may be deleted. For example:
+
+- T0: User A signs in to the catalog. A local user A is created in the user database.
+- T1: User A is deleted from the LDAP (User A cannot sign in to the catalog anymore).
+- T2: The synchronization task will check that all local LDAP users exist in LDAP:
+ - If the user does not own any records, it will be deleted.
+ - If the user owns metadata records, a warning message will be written to the catalog logging system. The owner of the record should be changed to another user before the task can remove the current owner.
+
+By default the task runs once every day. This can be changed in the following property:
+
+``` text
+# Run LDAP sync every day at 23:30
+ldap.sync.cron=0 30 23 * * ?
+```
+
+The following properties allow advanced configuration of the synchronisation process:
+
+``` text
+ldap.sync.user.search.base=${ldap.base.search.base}
+ldap.sync.user.search.filter=(&(objectClass=*)(mail=*@*)(givenName=*))
+ldap.sync.user.search.attribute=uid
+ldap.sync.group.search.base=ou=groups
+ldap.sync.group.search.filter=(&(objectClass=posixGroup)(cn=EL_*))
+ldap.sync.group.search.attribute=cn
+ldap.sync.group.search.pattern=EL_(.*)
+```
+
+#### Debugging
+
+If the connection fails, try to increase the logging level for LDAP in `WEB-INF/classes/log4j.xml`:
+
+``` xml
+
+
+
+```
+
+Or from the Configuration Settings set the `Log level` to `DEV` temporarily:
+
+
+
+## Configuring LDAP - Hierarchy {#authentication-ldap-hierarchy}
+
+A slightly different method for LDAP configuration was introduced in mid-2020.
+
+This extends the original configuration infrastructure (original configurations still work without any changes).
+
+Before you start configuring, you will need to know;
+
+1. URL to your LDAP Server
+2. Username/password to login to the LDAP Server (to execute queries)
+3. LDAP query to find a user (given what they type in on the login screen)
+4. Details of how to convert the LDAP user's attributes to GeoNetwork user attributes
+5. LDAP query to find groups a user is a member of
+6. How to convert a LDAP group to a GeoNetwork Group/Profile
+
+!!! note
+
+ There is a [video developer chat](https://www.youtube.com/watch?v=f8rvbEdnE-g) that goes into details for how to configure LDAP including setting up a pre-configured LDAP server (using Apache Directory Studio) for testing/debugging/learning.
+
+
+!!! note
+
+ Should I use the Hierarchy or Original configuration?
+
+ If you already have an existing (Original) configuration, there's no need to move to the new one. Most of the code between the two is the same.
+
+ If you are starting a new configuration, I would recommend the Hierarchy configuration. It's a little simpler and supported by test cases and test infrastructure. It also supports LDAPs where users/groups are in multiple directories.
+
+
+### Configuring LDAP Beans (Hierarchy)
+
+GeoNetwork comes with a sample LDAP configuration that you can use in Apache Directory Studio to create the same LDAP server used in the test cases. There is also a sample GeoNetwork configuration that connects to this LDAP server. Please see `core-geonetwork/blob/master/core/src/test/resources/org/fao/geonet/kernel/security/ldap/README.md`{.interpreted-text role="repo"} or the [video developer chat](https://www.youtube.com/watch?v=f8rvbEdnE-g) for instructions.
+
+!!! note
+
+ To use this configuration, uncomment the "" line in ``web/src/main/webapp/WEB-INF/config-security/config-security.xml``
+
+
+1. Configure the `ce` bean with a reference to your LDAP server and a user that can execute LDAP queries.
+
+ ``` xml
+
+
+
+
+
+
+ ```
+
+2. Configure the `ch` bean with the query used to find the user (given what was typed in the login page).
+
+ NOTE: Set `ee` to `ue` to do a recursive search of the LDAP. Use `se` to control which directory the search starts in ("" means start from the root).
+
+ ``` xml
+
+
+
+
+
+
+
+ ```
+
+3. Configure the `er` bean with how to convert the LDAP user's attributes to GeoNetwork user attributes (see the original configuration documentation, above).
+
+ NOTE: The `ue` portion has two parts. The first part is the name of LDAP attribute (can be blank). The second part is the default value if the LDAP attribute is missing or empty (see the original configuration documentation, above).
+
+ ``` xml
+
+
+
+
+
+
+
+ ```
+
+4. Continue configuring the `er` bean so the LDAP can also provide group/profile roles for the user.
+
+ NOTE: The `ry` is the LDAP directory where the membership query will be start ("" means start at the root of the LDAP).
+
+ ``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+5. Continue configuring the `er` bean so the LDAP roles can be converted to GeoNetwork Groups/Profiles.
+
+ NOTE: You can use multiple `rs`.
+
+ ``` xml
+
+
+
+
+
+
+
+
+
+ ```
+
+There are currently two ways to convert an LDAP group to GeoNetwork Groups/Profiles.
+
+- The `er`, which works the same as the original LDAP configuration. It uses a regular expression to parse the LDAP group name into a GeoNetwork Group/Profile. This will convert the LDAP role `OR` into the GeoNetwork group `AL` with Profile `r.`
+
+ ``` xml
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+- There is also a more direct way using `er`. This directly converts the LDAP group name into a list of GeoNetwork Groups/Profiles.
+
+ ``` xml
+
+
+
+
+
+
+ ```
+
+## Configuring CAS {#authentication-cas}
+
+To enable CAS, set up authentication by including `WEB-INF/config-security/config-security-cas.xml` in `WEB-INF/config-security/config-security.xml`, uncommenting the following lines:
+
+``` xml
+
+
+```
+
+CAS can use either LDAP or a database for user management. To use a database uncomment the following lines instead:
+
+``` xml
+
+
+```
+
+The CAS configuration is defined in `WEB-INF/config-security/config-security.properties`. You can configure your environment by updating the previous file or by defining property overrides in the file `WEB-INF/config-security/config-security-overrides.properties`:
+
+``` text
+cas.baseURL=https://localhost:8443/cas
+cas.ticket.validator.url=${cas.baseURL}
+cas.login.url=${cas.baseURL}/login
+cas.logout.url=${cas.baseURL}/logout?url=${geonetwork.https.url}/
+```
+
+## Configuring OAUTH2 OpenID Connect {#authentication-openid}
+
+[OAUTH2 OpenID Connect](https://openid.net/connect/) is an authentication and authorization system based on OAUTH2. Geonetwork's OpenID Connect plugin has been tested with [Keycloak](https://keycloak.org) and [Azure AD](https://azure.microsoft.com/en-ca/services/active-directory/), but should work with any provider.
+
+Basic Setup Steps:
+
+1. Configure your IDP Server (i.e. Keycloak or Azure AD)
+ 1. Ensure that the ID Token provides role/group information
+ 2. Authorize your Geonetwork URLs for redirects (i.e. `http://localhost:8080/geonetwork/login/oauth2/code/geonetwork-oicd`)
+ 3. Record the Client ID
+ 4. Record the Client Secret
+ 5. Get the Server's JSON metadata document
+2. Configure Geonetwork via environment variables
+ 1. ``GEONETWORK_SECURITY_TYPE=openidconnect``
+ 2. ``OPENIDCONNECT_CLIENTSECRET=\...`` (from your IDP server)
+ 3. ``OPENIDCONNECT_CLIENTID=\...`` (from your IDP server)
+ 4. ``OPENIDCONNECT_SERVERMETADATA_JSON_TEXT='\...'`` (the text of your Server's JSON metadata document)
+ 5. ``OPENIDCONNECT_IDTOKENROLELOCATION=\...`` (location of the user's roles in the ID Token)
+
+Geonetwork's Open ID Connect plugin has a lot of configuration options - please see the `WEB-INF/config-security/config-security-openidconnect.xml` and `WEB-INF/config-security/config-security-openidconnect-overrides.properties` files.
+
+### Environment Variable and Meaning
+
+**GEONETWORK_SECURITY_TYPE**
+
+Should be `ct`.
+
+**OPENIDCONNECT_CLIENTID**
+
+The name of the client/application you configured on your OpenID server.
+
+**OPENIDCONNECT_CLIENTSECRET**
+
+The `et` you configured on your OpenID server.
+
+**OPENIDCONNECT_SERVERMETADATA_CONFIG_URL**
+
+URL to the external OIDC server's JSON metadata document. This is typically at ``/.well-known/openid-configuration`` on the IDP server.
+
+!!! note
+
+ This will download the server's configuration everytime GeoNetwork starts up, which could be a security concern. For security, use a `ps` URL.
+
+
+**OPENIDCONNECT_SERVERMETADATA_JSON_TEXT**
+
+Should be the text of your OpenID server's metadata configuration (JSON).
+
+**OPENIDCONNECT_SERVERMETADATA_FNAME**
+
+Instead of putting the OpenID server's metadata configuration as text in a variable (``OPENIDCONNECT_SERVERMETADATA_JSON_TEXT``), you can put the JSON contents in a file and reference it with this variable (ie. `/WEB-INF/config-security/openid-configuration.json`)
+
+**OPENIDCONNECT_IDTOKENROLELOCATION**
+
+Where, in the ID Token, are the users roles/groups stored (i.e. "groups", "roles", or "resource_access.gn-key.roles")
+
+**OPENIDCONNECT_ROLECONVERTER**
+
+This provides simple role conversion from the OpenID server to Geonetwork roles.
+
+ie. ``"GeonetworkAdmin=Administrator,GeonetworkEditor=Editor"``
+
+This will convert "GeonetworkAdmin" (from the OpenID Server) to the Geonetwork "Administrator" role.
+
+!!! note
+
+ Like the keycloak plugin, you can use role/group names of the form "group:role" to assign a user to Geonetwork group and permission level.
+
+
+**OPENIDCONNECT_MINIMUMPROFILE**
+
+Every user who authenticates against the OpenID server will be given this role.
+
+Default is ``"RegisteredUser"``.
+
+**OPENIDCONNECT_USERPROFILEUPDATEENABLED**
+
+When a user logs on, update their Geotwork profile from the OpenID server's ID Token.
+
+Default is ``"true"``.
+
+**OPENIDCONNECT_USERGROUPUPDATEENABLED**
+
+When a user logs on, update their Geotwork group/role permissions.
+
+Default is ``"true"``.
+
+**OPENIDCONNECT_SCOPES**
+
+Limit the requested scope access to the OpenID server.
+
+Default "openid email profile", and "openid email profile offline_access" (for bearer tokens).
+
+**OPENIDCONNECT_LOGINTYPE**
+
+How Geonetwork deals with users who are not logged on.
+
+Default is "LINK" - users can click on the "login" link on the main page.
+
+"AUTOLOGIN" - No login form provided which will automatically login the user when possible.
+
+**OPENIDCONNECT_LOGSENSITIVE_INFO**
+
+"true" or "false" (default)
+
+Logs: CODE, ACCESS TOKEN, ID TOKEN, userinfo endpoint result, and calculated GeoNetwork authorities.
+
+LOGGING THIS INFORMATION IS PROBABLY A SECURITY AND PERSONAL INFORMATION RISK. DO NOT TURN THIS ON IN A SYSTEM THAT IS ACTUALLY BEING USED.
+
+We try not to log very sensitive information - we don't log the full access or id token (just the claims part). We log the single-use CODE, but it should have already been deactivated by the server before we log it.
+
+The access token, userinfo, and id token contain sensitive information (i.e. real names, email address, etc\...)
+
+### Configuration for a Keycloak Server
+
+It's outside the scope of this document to fully describe the steps to configure keycloak, but this should serve as a guide.
+
+This will configure keycloak backed by **another OpenID IDP** (for example, by an Azure AD). In keycloak:
+
+1. Create a realm (i.e. `lm`)
+2. Create an openid client (i.e. `nt`). This is your ClientID.
+ 1. Root URL: ``http://localhost:7777/geonetwork`` (this is the GN root URL)
+ 2. Valid Redirect URIs: ``http://localhost:7777/geonetwork/*``
+ 3. Access Type: Confidential
+ 4. On the `ls` tab, get the secret (this is your Client Secret)
+ 5. On the `es` tab, create some roles: Administrator, Editor, Reviewer, RegisteredGuest
+3. Create your backing Identity Provider (i.e. to another OpenID server). Or you can configure users directly in keycloak.
+ 1. At the bottom of the page, choose "import from URL" and import the backing server's configuration location.
+ 2. Add the Client Secret (from the backing service)
+ 3. Add the Client ID (from the backing service)
+ 4. set "Client Authentication" to "Client secret sent as post"
+4. Configure role translation
+ 1. Edit the "Identity Provider" you just created, and go to the "Mappers" tab.
+ 2. Press "Create" and and add a "Claim to Role".
+ 3. Set Sync Mode Override to "Force"
+ 4. Claim: `es`
+ 5. Claim Value: `DP`
+ 6. Role: choose the "Administrator" role from the `nt` client.
+ 7. Repeat the above for Administrator, Editor, Reviewer, and RegisteredGuest
+5. Configure details for your backing IDP
+ 1. Edit the "Identity Provider" you just configured
+ 2. On the Mappers tab, "Add Builtin" and tick "client roles (User Client Role)" then "Add selected"
+ 3. Edit the "client roles" mapper and make sure "Add to ID token" and "Add to userinfo" are on
+
+You should have Keycloak's Client id ("myclient") and the client secret. The configuration JSON is available at `https://YOUR_KEYCLOAK_HOST/realms/{YOUR REALM NAME}/.well-known/openid-configuration`
+
+Your environment variables will looks like this:
+
+``` properties
+GEONETWORK_SECURITY_TYPE=openidconnect
+OPENIDCONNECT_CLIENTSECRET='...'
+OPENIDCONNECT_CLIENTID='...'
+OPENIDCONNECT_SERVERMETADATA_JSON_TEXT='...big json text...'
+OPENIDCONNECT_IDTOKENROLELOCATION='resource_access.{your client id}.roles'
+```
+
+### Azure AD Configuration
+
+There are two ways to setup Azure AD. The first is with user and groups (a more traditional LDAP method) or with Application Roles.
+
+#### With Users and Groups
+
+Setup the Azure Application:
+
+1. Create a new `on`
+2. use `http://localhost:8080/geonetwork/login/oauth2/code/geonetwork-oicd` as a redirect URIs
+3. On the "Certificates & Secrets" add a new secret and record it (make sure you get the secret value and NOT the object id)
+4. Make sure the groups are in the ID token - on the "Manifest" tab, edit the JSON so that "groupMembershipClaims": "SecurityGroup" is set
+5. On the summary page, get the Application (client) ID
+6. On the summary page, choose "Endpoints" (at the top) and get the JSON text from the "OpenID Connect metadata document" Endpoints
+
+Setup users and groups:
+
+1. In Azure AD, go to groups
+2. Add new Groups - "geonetworkAdmin", "geonetworkReviewer", etc\... Record the name and the group's **Object ID**
+3. Edit a User, and choose Groups, and add them to appropriate group.
+
+Your environment variables will looks like this:
+
+``` properties
+GEONETWORK_SECURITY_TYPE=openidconnect
+OPENIDCONNECT_CLIENTSECRET='...'
+OPENIDCONNECT_CLIENTID='...'
+OPENIDCONNECT_SERVERMETADATA_JSON_TEXT='...big json text...'
+OPENIDCONNECT_IDTOKENROLELOCATION='groups'
+OPENIDCONNECT_ROLECONVERTER='3a94275f-7d53-4205-8d78-11f39e9ffa5a=Administrator,d93c6444-feee-4b67-8c0f-15d6796370cb=Reviewer'
+```
+
+!!! note
+
+ The roles are in the "roles" part of the ID Token.
+
+
+!!! note
+
+ The OPENIDCONNECT_ROLECONVERTER converts the Azure AD Group's Object ID to a Geonetwork Role.
+
+
+#### With Application Roles
+
+Setup the Azure Application:
+
+1. Create a new Enterprise application
+2. use `http://localhost:8080/geonetwork/login/oauth2/code/geonetwork-oicd` as a redirect URIs
+3. On the "Certificates & Secrets" add a new secret and record it (make sure you get the secret value and NOT the object id)
+4. Make sure the groups are in the ID token - on the "Manifest" tab, edit the JSON so that "groupMembershipClaims": "ApplicationGroup" is set
+5. On the summary page, get the Application (client) ID
+6. On the summary page, choose "Endpoints" (at the top) and get the JSON text from the "OpenID Connect metadata document" Endpoints
+
+Setup Application Roles:
+
+1. In Application you created, go to "App Roles".
+2. Add new Groups - "Editor", "Reviewer", etc\...
+
+Assign Users:
+
+1. Go to Azure AD, Enterprise Application, then the application you created
+2. Choose "Assign users and groups"
+3. Press the "Add user/group" (top)
+4. Press "None Selected" (under Users) and choose some users
+5. Press "None Selected" (Under Select a Role) and choose some roles
+6. Configure all your users with roles
+
+Your environment variables will looks like this:
+
+``` properties
+GEONETWORK_SECURITY_TYPE=openidconnect
+OPENIDCONNECT_CLIENTSECRET='...'
+OPENIDCONNECT_CLIENTID='...'
+OPENIDCONNECT_SERVERMETADATA_JSON_TEXT='...big json text...'
+OPENIDCONNECT_IDTOKENROLELOCATION='roles'
+```
+
+!!! note
+
+ The roles are in the "roles" part of the ID Token.
+
+
+!!! note
+
+ You don't typically have to do any role conversion since the role name will be used in the ID Token.
+
+
+### OIDC Bearer Tokens {#oidc_bearer_tokens}
+
+Bearer Tokens are also supported - you can attach the JWT Bearer token to any request by setting the HTTP header like this:
+
+``` properties
+Authorization: Bearer:
+```
+
+Bearer Tokens are mostly used for automated (desktop or application) API calls - real users should just login normally using OIDC.
+
+1. Setup your OIDC configuration (see [Configuring OAUTH2 OpenID Connect](authentication-mode.md#authentication-openid))
+2. Setup the OIDC Bearer token configuration (see [Configuration](authentication-mode.md#bearer_token_configuration))
+3. Obtain a Bearer token from the OIDC server. This is the hard part and there are several ways to do this. One way that is used is via the OAuth 2.0 Device Authorization Grant ("Device Flow") workflow.
+4. Attach it to your request headers (see [OIDC Bearer Tokens](authentication-mode.md#oidc_bearer_tokens))
+5. Make protected requests to the Geonetwork API
+
+This has been tested with Keycloak and with Azure AD. It should work with other JWT-based OIDC services.
+
+#### Validation
+
+The token is validated in three major ways:
+
+1. The bearer token will be used to access the `fo` ("token validation") endpoint specified in the OIDC configuration. This means the IDP validates the token (at the very least its signature and expiry).
+2. The bearer token (JWT) will be checked that the audience for it is the same as our configurated OIDC configuration. This will ensure that someone isn't getting a token from a different service and attempting to use it here. See ``AudienceAccessTokenValidator.java``
+3. The bearer token (JWT) will be checked that the subject of the JWT and the `fo` (returned from the IDP) are the same. This shouldnt be a problem in our use-case, but the OAUTH2 specification recommends this check. See ``SubjectAccessTokenValidator.java``
+
+#### Configuration {#bearer_token_configuration}
+
+Configure OIDC as above - ensure this is working.
+
+Instead of using `GEONETWORK_SECURITY_TYPE=openidconnect`, use `GEONETWORK_SECURITY_TYPE=openidconnectbearer`.
+
+Inside `WEB-INF/config-security/config-security-openidconnectbearer.xml`:
+
+1. If you are using keycloak (configured with Groups in the `fo` response), then uncomment the `er` bean and comment out the `er` bean.
+2. If you are using Azure AD (MS Graph API for the user's groups), then then uncomment the `er` bean and comment out the `er` bean.
+
+The easiest way to test is to obtain a Bearer Token, and then use a browser plugin to add the ``Authorization: Bearer `` header to all requests. When you visit the Geonetwork website, you should see yourself logged in with the appropriate permissions.
+
+#### Other Providers
+
+This has been tested with Azure AD (groups in the MS Graph API) and KeyCloak (groups in the `fo`).
+
+For other IDP, you might have to make some modifications.
+
+1. Make sure the `or` and `or` work correctly for your JWT bearer tokens.
+2. Make sure that the user's groups are available - see the `er` interface and its two implementations - `er` and `er`.
+
+## Configuring Keycloak {#authentication-keycloak}
+
+[Keycloak](https://keycloak.org) is a software solution to facilitate storage of authentication details, user federation, identity brokering and social login. GeoNetwork can be set up to use a keycloak instance for authentication.
+
+Install keycloak from its instructions or use this example setup in docker
+
+Keycloak details are defined via environment variables
+
+``` text
+KEYCLOAK_AUTH_SERVER_URL={keycloak url}
+KEYCLOAK_REALM={realm name}
+KEYCLOAK_RESOURCE={client name}
+KEYCLOAK_SECRET={client secret}
+KEYCLOAK_DISABLE_TRUST_MANAGER={true|false}
+```
+
+You can setup more advance keycloak settings by editing the file **`WEB-INF/config-security/keycloak.json`**
+
+### Geonetwork client URL configuration
+
+Ensure that when you configure your client that you setup the valid redirect uris to your geonetwork installation. i.e. `https://localhost:8443/geonetwork/*`. If this is not setup correctly you may get and error indicating that a wrong redirect uri was supplied. Also if wanting to test the client backchannel logout then ensure that the admin URL is also set to the geonetwork installation.
+
+### Sample user/role/group setup
+
+#### Sample Role setup
+
+In your client role settings (clients -> myclient -> roles). Add the following roles
+
+``` text
+Administrator
+RegisteredUser
+Guest
+sample:UserAdmin
+sample:Reviewer
+sample:Editor
+sample:RegisteredUser
+```
+
+#### Sample Group configuration
+
+1. Go to keycloak groups (left menu).
+2. Create a new group called "Administrator"
+3. Edit the group. Go to Role Mappings -> Client Roles (myclient) -> select the administrator roles and click on "Add selected" Any user joined to the Administrator group will be a geonetwork administrator.
+
+#### Sample User configuration
+
+1. Go to keycloak users (left menu)
+2. Add or select existing user. Then go to that user.
+3. Go to role Mappings -> Client Roles (myclient) -> select the available roles to be applied and click on "Add selected" or go to Groups -> Available Groups -> Click on the Administrator Group and then click on "Join"
+
+A similar setup is described for geoserver in the [geoserver documentation](https://docs.geoserver.org/latest/en/user/community/keycloak/index.html).
+
+## Configuring EU Login {#authentication-ecas}
+
+EU Login is the central login mechanism of the European Commission. You can enable login against that central service in case your intended users have ar can acquire a EU Login.
+
+To enable EU Login, set up authentication by including `WEB-INF/config-security/config-security-ecas.xml` in `WEB-INF/config-security/config-security.xml`, uncommenting the following line:
+
+``` xml
+
+```
+
+EU-login requires an ecas-plugin provided by the European Union. The ecas plugin is available via [CITnet](https://citnet.tech.ec.europa.eu/CITnet/nexus) for various java containers, such as Tomcat and JBoss.
+
+For tomcat, add two files to the tomcat lib folder: ecas-tomcat-x.y.z.jar and log4j-x.y.z.jar. Inside the lib folder copy two folders from **`eulogin-tomcat-x.y.z-config.zip`**: **`org/apache/catalina/authenticator`** and **`org/apache/catalina/startup`**. The mbeans folder contains a file **`mbeans-descriptors.xml`**. The startup folder contains a file **`Authenticators.properties`**. Verify that the JDK trusts the [ECAS certificates](https://webgate.ec.europa.eu/CITnet/confluence/display/IAM/Downloads-Certificates) else import them on the keystore of the JVM.
+
+The EU Login configuration is defined in **`WEB-INF/config-security/config-security.properties`**. You can configure your environment by updating the previous file or by defining property overrides in the file **`WEB-INF/config-security/config-security-overrides.properties`**:
+
+``` text
+cas.baseURL=https://webgate.ec.europa.eu/cas
+```
+
+Restart the service and check the authentication menchanism.
+
+## Configuring Shibboleth {#authentication-shibboleth}
+
+The catalog can operate in a SAML secured federation. Shibboleth should be installed in Apache as described [here](https://wiki.shibboleth.net/confluence/display/SHIB2/Installation). The catalog is accessed via Apache. Setup Shibboleth authentication by including `WEB-INF/config-security/config-security-shibboleth.xml` in `WEB-INF/config-security/config-security.xml`. You can then configure your environment in `config-security-shibboleth-overrides.properties`.
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/creating-group.md b/docs/manual/docs/administrator-guide/managing-users-and-groups/creating-group.md
new file mode 100644
index 00000000000..3cfe17939da
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-users-and-groups/creating-group.md
@@ -0,0 +1,28 @@
+# Creating group
+
+The administrator can create new groups of users. User groups could correspond to logical units within an organisation, for example `es`, `re`, `nd`, `er`, `th` and so on.
+
+To create new groups you should be logged on with an account that has administrative privileges.
+
+1. Select the *Administration* button in the menu. On the Administration page, select *Group management*.
+
+2. Select *Add a new group*. You may want to remove the *Sample* group;
+
+3. Fill out the details. The email address will be used to send feedback on data downloads when they occur for resources that are part of the Group.
+
+ !!! warning
+
+ The Name should *NOT* contain spaces! You can use the Localization panel to provide localized names for groups.
+
+
+4. Click *Save*
+
+Access privileges can be set per metadata record. You can define privileges on a per Group basis.
+
+Privileges that can be set relate to visibility of the Metadata (*Publish*), data *Download*, *Interactive Map* access and display of the record in the *Featured* section of the home page.
+
+*Editing* defines the groups for which editors can edit the metadata record.
+
+*Notify* defines what Groups are notified when a file managed by GeoNetwork is downloaded.
+
+Below is an example of the privileges management table related to a dataset.
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/creating-user.md b/docs/manual/docs/administrator-guide/managing-users-and-groups/creating-user.md
new file mode 100644
index 00000000000..240fac6944b
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-users-and-groups/creating-user.md
@@ -0,0 +1,10 @@
+# Creating user
+
+To add a new user to the GeoNetwork system, please do the following:
+
+1. Select the *Administration* button in the menu. On the Administration page, select *User management*.
+2. Click the button *Add a new user*;
+3. Provide the *information* required for the new user;
+4. Assign the correct *profile* (see [Users, Groups and Roles](index.md#user_profiles));
+5. Assign the user to a *group* (see [Creating group](creating-group.md));
+6. Click *Save*.
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/password-forgot.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/password-forgot.png
new file mode 100644
index 00000000000..d1bc512667d
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/password-forgot.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/selfregistration-form.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/selfregistration-form.png
new file mode 100644
index 00000000000..09321a4e4b5
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/selfregistration-form.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/selfregistration-start.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/selfregistration-start.png
new file mode 100644
index 00000000000..7e9a6f8084f
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/selfregistration-start.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-about-to-be-cancelled.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-about-to-be-cancelled.png
new file mode 100644
index 00000000000..9dfe2b17dbe
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-about-to-be-cancelled.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-has-expired.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-has-expired.png
new file mode 100644
index 00000000000..d449d7b6c5e
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-has-expired.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-will-expire-soon.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-will-expire-soon.png
new file mode 100644
index 00000000000..ead6a368e00
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/session-will-expire-soon.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/img/setting-log-level.png b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/setting-log-level.png
new file mode 100644
index 00000000000..4c694145e1b
Binary files /dev/null and b/docs/manual/docs/administrator-guide/managing-users-and-groups/img/setting-log-level.png differ
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/index.md b/docs/manual/docs/administrator-guide/managing-users-and-groups/index.md
new file mode 100644
index 00000000000..d05f35d0354
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-users-and-groups/index.md
@@ -0,0 +1,78 @@
+# Managing users and groups
+
+- [Creating group](creating-group.md)
+- [Creating user](creating-user.md)
+- [User Self-Registration](user-self-registration.md)
+- [Authentication mode](authentication-mode.md)
+
+## Default user {#user-defaults}
+
+Upon installation a default user with name `admin` and password `admin` is created. It is recommended to log in with these credentials directly after the installation has completed and to change the default password.
+
+## User session
+
+After the authentication process, a user session is created. This session will be closed automatically at some point by the server for security reasons. The default session timeout is set to 35 min (see [User session timeout configuration](../../customizing-application/advanced-configuration.md#session-timeout-configuration) for details).
+
+When there is no activity in the browser and the session is about to expire, a warning is displayed next to the user details 3 minutes before the timeout takes place:
+
+
+
+One (1) minute before the timeout, another message is displayed:
+
+
+
+When the session seems to have been destroyed by the catalog, a message recommends to refresh the page and sign in again if needed:
+
+
+
+## Users, Groups and Roles {#user_profiles}
+
+The catalog uses the concept of Users, Groups and User Profiles.
+
+- A User can be part of one or more Groups.
+- A User has a Role in a Group.
+- The Administrator Role is not related to a Group.
+
+The combination of Role and Group defines what tasks the User can perform on the system or on specific metadata records.
+
+Users can have different roles in different groups. A role defines what tasks the user can perform.
+
+Roles are hierarchical and based on inheritance. This means that a user with an Editor profile can create and modify new metadata records, but can also use all functions a Registered user can use.
+
+Rights associated with the roles are illustrated in detail in the list below:
+
+1. **Administrator Profile**
+
+ The Administrator has special privileges that give access to all available functions.
+
+ These include:
+
+ - Full rights for creating new groups and new users.
+ - Rights to change users/groups profiles.
+ - Full rights for creating/editing/deleting new/old metadata.
+ - Perform system administration and configuration tasks.
+
+2. **User Administrator Profile**
+
+ The user administrator is the administrator of his/her own group(s) with the following privileges:
+
+ - Full rights on creating new users within their own groups.
+ - Rights to change users profiles within their own groups.
+
+3. **Content Reviewer Profile**
+
+ The content reviewer is the only person allowed to give final clearance on the metadata publication on the Intranet and/or on the Internet:
+
+ - Rights on reviewing metadata content within their own groups and authorising its approval and publication.
+
+4. **Editor Profile**
+
+ The editor works on metadata with following privileges:
+
+ - Full rights on creating/editing/ deleting new/old data within their own groups.
+
+5. **Registered User Profile**
+
+ The Registered User has more access privileges than non-authenticated Guest users:
+
+ - Right to download protected data.
diff --git a/docs/manual/docs/administrator-guide/managing-users-and-groups/user-self-registration.md b/docs/manual/docs/administrator-guide/managing-users-and-groups/user-self-registration.md
new file mode 100644
index 00000000000..2594a81f727
--- /dev/null
+++ b/docs/manual/docs/administrator-guide/managing-users-and-groups/user-self-registration.md
@@ -0,0 +1,107 @@
+# User Self-Registration {#user_self_registration}
+
+To enable the self-registration functions, see [System configuration](../configuring-the-catalog/system-configuration.md). When self-registration is enabled, for users that are not logged in, an additional link is shown on the login page:
+
+
+
+Click the `Create an account` button and fill out the registration form:
+
+
+
+The fields in this form are self-explanatory except for the following:
+
+- **Email**: The user's email address. This is mandatory and will be used as the username.
+- **Profile**: By default, self-registered users are given the `Registered User` profile (see previous section). If any other profile is selected:
+ - the user will still be given the `Registered User` profile
+ - an email will be sent to the Email address nominated in the Feedback section of the 'System Administration' menu, informing them of the request for a more privileged profile
+
+## What happens when a user self-registers?
+
+When a user self-registration occurs, the user receives an email with the new account details that looks something like the following:
+
+ Dear User,
+
+ Your registration at The Greenhouse GeoNetwork Site was successful.
+
+ Your account is:
+ username : dubya.shrub@greenhouse.gov
+ password : 0110O3
+ usergroup: GUEST
+ usertype : REGISTEREDUSER
+
+ You've told us that you want to be "Editor", you will be contacted by our office soon.
+
+ To log in and access your account, please click on the link below.
+ http://greenhouse.gov/geonetwork
+
+ Thanks for your registration.
+
+ Yours sincerely,
+ The team at The Greenhouse GeoNetwork Site
+
+Notice that the user has requested an 'Editor' profile. As a result an email will be sent to the Email address nominated in the Feedback (see [Feedback](../configuring-the-catalog/system-configuration.md#system-config-feedback)) section of the `System Administration` menu which looks something like the following:
+
+Notice also that the user has been added to the built-in user group 'GUEST'. This is a security restriction. An administrator/user-administrator can add the user to other groups if that is required later.
+
+If you want to change the content of this email, you should modify `xslt/service/account/registration-pwd-email.xsl`.
+
+ Dear Admin,
+
+ Newly registered user dubya.shrub@greenhouse.gov has requested "Editor" access for:
+
+ Instance: The Greenhouse GeoNetwork Site
+ Url: http://greenhouse.gov/geonetwork
+
+ User registration details:
+
+ Name: Dubya
+ Surname: Shrub
+ Email: dubya.shrub@greenhouse.gov
+ Organisation: The Greenhouse
+ Type: gov
+ Address: 146 Main Avenue, Creationville
+ State: Clerical
+ Post Code: 92373
+ Country: Mythical
+
+ Please action.
+
+ The Greenhouse GeoNetwork Site
+
+If you want to change the content of this email, you should modify `xslt/service/account/registration-prof-email.xsl`.
+
+## The 'Forgot your password?' function
+
+This function allows users who have forgotten their password to request a new one. Go to the sign in page to access the form:
+
+
+
+For security reasons, only users that have the `Registered User` profile can request a new password.
+
+If a user takes this option they will receive an email inviting them to change their password as follows:
+
+ You have requested to change your Greenhouse GeoNetwork Site password.
+
+ You can change your password using the following link:
+
+ http://localhost:8080/geonetwork/srv/en/password.change.form?username=dubya.shrub@greenhouse.gov&changeKey=635d6c84ddda782a9b6ca9dda0f568b011bb7733
+
+ This link is valid for today only.
+
+ Greenhouse GeoNetwork Site
+
+The catalog has generated a changeKey from the forgotten password and the current date and emailed that to the user as part of a link to a change password form.
+
+If you want to change the content of this email, you should modify `xslt/service/account/password-forgotten-email.xsl`.
+
+When the user clicks on the link, a change password form is displayed in their browser and a new password can be entered. When that form is submitted, the changeKey is regenerated and checked with the changeKey supplied in the link, if they match then the password is changed to the new password supplied by the user.
+
+The final step in this process is a verification email sent to the email address of the user confirming that a change of password has taken place:
+
+ Your Greenhouse GeoNetwork Site password has been changed.
+
+ If you did not change this password contact the Greenhouse GeoNetwork Site helpdesk
+
+ The Greenhouse GeoNetwork Site team
+
+If you want to change the content of this email, you should modify `xslt/service/account/password-changed-email.xsl`.
diff --git a/docs/manual/docs/annexes/gallery/img/agroenvgeo_data_inra_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/agroenvgeo_data_inra_fr_geonetwork.png
new file mode 100644
index 00000000000..d776bbfff43
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/agroenvgeo_data_inra_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/catalogue-imos_aodn_org_au_geonetwork.png b/docs/manual/docs/annexes/gallery/img/catalogue-imos_aodn_org_au_geonetwork.png
new file mode 100644
index 00000000000..31d355a5b07
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/catalogue-imos_aodn_org_au_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/catalogue_ec_gc_ca_geonetwork.png b/docs/manual/docs/annexes/gallery/img/catalogue_ec_gc_ca_geonetwork.png
new file mode 100644
index 00000000000..775347e1e60
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/catalogue_ec_gc_ca_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/catalogue_geo-ide_developpement-durable_gouv_fr_catalogue.png b/docs/manual/docs/annexes/gallery/img/catalogue_geo-ide_developpement-durable_gouv_fr_catalogue.png
new file mode 100644
index 00000000000..6d6302d4e2d
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/catalogue_geo-ide_developpement-durable_gouv_fr_catalogue.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/cdgp_u-strasbg_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/cdgp_u-strasbg_fr_geonetwork.png
new file mode 100644
index 00000000000..d4ed9dea306
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/cdgp_u-strasbg_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/doterr_fr_accueil.png b/docs/manual/docs/annexes/gallery/img/doterr_fr_accueil.png
new file mode 100644
index 00000000000..5ab95a954c4
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/doterr_fr_accueil.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/download_data_grandlyon_com_catalogue.png b/docs/manual/docs/annexes/gallery/img/download_data_grandlyon_com_catalogue.png
new file mode 100644
index 00000000000..9e401ad00d8
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/download_data_grandlyon_com_catalogue.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/ecat_ga_gov_au_geonetwork.png b/docs/manual/docs/annexes/gallery/img/ecat_ga_gov_au_geonetwork.png
new file mode 100644
index 00000000000..9b1b122e3f5
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/ecat_ga_gov_au_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/fao_org_geonetwork.png b/docs/manual/docs/annexes/gallery/img/fao_org_geonetwork.png
new file mode 100644
index 00000000000..cac6dbe78b6
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/fao_org_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/gatt_lmi_is_geonetwork.png b/docs/manual/docs/annexes/gallery/img/gatt_lmi_is_geonetwork.png
new file mode 100644
index 00000000000..23126e28fb0
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/gatt_lmi_is_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/gdk_gdi-de_org_gdi-de.png b/docs/manual/docs/annexes/gallery/img/gdk_gdi-de_org_gdi-de.png
new file mode 100644
index 00000000000..96ab86e3f38
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/gdk_gdi-de_org_gdi-de.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geo2france_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geo2france_fr_geonetwork.png
new file mode 100644
index 00000000000..0ed098a8e0f
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geo2france_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geo_be_catalogs_1_resources.png b/docs/manual/docs/annexes/gallery/img/geo_be_catalogs_1_resources.png
new file mode 100644
index 00000000000..c64aee29c6a
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geo_be_catalogs_1_resources.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geo_gob_bo_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geo_gob_bo_geonetwork.png
new file mode 100644
index 00000000000..37770c934c2
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geo_gob_bo_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geocat_ch_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geocat_ch_geonetwork.png
new file mode 100644
index 00000000000..3884e9b4274
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geocat_ch_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geocatalog_webservice-energy_org_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geocatalog_webservice-energy_org_geonetwork.png
new file mode 100644
index 00000000000..f9880c7e29b
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geocatalog_webservice-energy_org_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geocatalogue_apur_org_catalogue.png b/docs/manual/docs/annexes/gallery/img/geocatalogue_apur_org_catalogue.png
new file mode 100644
index 00000000000..f5902e67194
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geocatalogue_apur_org_catalogue.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geocatalogue_geoportail_lu.png b/docs/manual/docs/annexes/gallery/img/geocatalogue_geoportail_lu.png
new file mode 100644
index 00000000000..9f0ce89fb88
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geocatalogue_geoportail_lu.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geodata_nz_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geodata_nz_geonetwork.png
new file mode 100644
index 00000000000..33447750289
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geodata_nz_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geograndest_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geograndest_fr_geonetwork.png
new file mode 100644
index 00000000000..42866e34e35
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geograndest_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geoguyane_fr_catalogue.png b/docs/manual/docs/annexes/gallery/img/geoguyane_fr_catalogue.png
new file mode 100644
index 00000000000..bdf3ca710fd
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geoguyane_fr_catalogue.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geomartinique_fr_accueil.png b/docs/manual/docs/annexes/gallery/img/geomartinique_fr_accueil.png
new file mode 100644
index 00000000000..d4d34a9e381
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geomartinique_fr_accueil.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geometadatensuche_inspire_gv_at.png b/docs/manual/docs/annexes/gallery/img/geometadatensuche_inspire_gv_at.png
new file mode 100644
index 00000000000..9736daebc93
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geometadatensuche_inspire_gv_at.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geonorge_no_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geonorge_no_geonetwork.png
new file mode 100644
index 00000000000..a2026372215
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geonorge_no_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geonormandie_fr_accueil.png b/docs/manual/docs/annexes/gallery/img/geonormandie_fr_accueil.png
new file mode 100644
index 00000000000..ac7a6998450
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geonormandie_fr_accueil.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geopal_org_accueil.png b/docs/manual/docs/annexes/gallery/img/geopal_org_accueil.png
new file mode 100644
index 00000000000..d4f8f1e3845
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geopal_org_accueil.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geoportail_lepuyenvelay_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geoportail_lepuyenvelay_fr_geonetwork.png
new file mode 100644
index 00000000000..650fb9a973d
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geoportail_lepuyenvelay_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/geoportal_kscnet_ru_geonetwork.png b/docs/manual/docs/annexes/gallery/img/geoportal_kscnet_ru_geonetwork.png
new file mode 100644
index 00000000000..9f6a3ad65ff
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/geoportal_kscnet_ru_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/georep_nc.png b/docs/manual/docs/annexes/gallery/img/georep_nc.png
new file mode 100644
index 00000000000..2c39b830f5f
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/georep_nc.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/gis_ices_dk_geonetwork.png b/docs/manual/docs/annexes/gallery/img/gis_ices_dk_geonetwork.png
new file mode 100644
index 00000000000..fdf1efe6dea
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/gis_ices_dk_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/iandc_pnra_aq.png b/docs/manual/docs/annexes/gallery/img/iandc_pnra_aq.png
new file mode 100644
index 00000000000..94a5cb9d9fa
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/iandc_pnra_aq.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/ide_cat_en_catalogue.png b/docs/manual/docs/annexes/gallery/img/ide_cat_en_catalogue.png
new file mode 100644
index 00000000000..768cc7c01e0
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/ide_cat_en_catalogue.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/idee_es_csw-codsi-idee.png b/docs/manual/docs/annexes/gallery/img/idee_es_csw-codsi-idee.png
new file mode 100644
index 00000000000..4e95630b82e
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/idee_es_csw-codsi-idee.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/ids_craig_fr_geocat.png b/docs/manual/docs/annexes/gallery/img/ids_craig_fr_geocat.png
new file mode 100644
index 00000000000..e2129485ce4
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/ids_craig_fr_geocat.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/indores_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/indores_fr_geonetwork.png
new file mode 100644
index 00000000000..6015af6e5e7
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/indores_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/inspire_gov_hu_geonetwork.png b/docs/manual/docs/annexes/gallery/img/inspire_gov_hu_geonetwork.png
new file mode 100644
index 00000000000..6c05423ef28
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/inspire_gov_hu_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/karugeo_fr_accueil.png b/docs/manual/docs/annexes/gallery/img/karugeo_fr_accueil.png
new file mode 100644
index 00000000000..233fbe77584
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/karugeo_fr_accueil.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/meta_data-za_org_catalogue.png b/docs/manual/docs/annexes/gallery/img/meta_data-za_org_catalogue.png
new file mode 100644
index 00000000000..869c8215284
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/meta_data-za_org_catalogue.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/metadados_snirh_gov_br_geonetwork.png b/docs/manual/docs/annexes/gallery/img/metadados_snirh_gov_br_geonetwork.png
new file mode 100644
index 00000000000..faa9f636d85
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/metadados_snirh_gov_br_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/metadata_geopunt_be_zoekdienst.png b/docs/manual/docs/annexes/gallery/img/metadata_geopunt_be_zoekdienst.png
new file mode 100644
index 00000000000..c4fa4fb230b
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/metadata_geopunt_be_zoekdienst.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/metadata_vlaanderen_be.png b/docs/manual/docs/annexes/gallery/img/metadata_vlaanderen_be.png
new file mode 100644
index 00000000000..d17b8050766
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/metadata_vlaanderen_be.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/metadata_vlaanderen_be_metadatacenter.png b/docs/manual/docs/annexes/gallery/img/metadata_vlaanderen_be_metadatacenter.png
new file mode 100644
index 00000000000..62dfbb7f8c3
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/metadata_vlaanderen_be_metadatacenter.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/metawal_wallonie_be.png b/docs/manual/docs/annexes/gallery/img/metawal_wallonie_be.png
new file mode 100644
index 00000000000..cea6dfc456c
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/metawal_wallonie_be.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/mongeosource_fr_geosource.png b/docs/manual/docs/annexes/gallery/img/mongeosource_fr_geosource.png
new file mode 100644
index 00000000000..f2ceb587b2d
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/mongeosource_fr_geosource.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/msdi_data_gov_mt_geonetwork.png b/docs/manual/docs/annexes/gallery/img/msdi_data_gov_mt_geonetwork.png
new file mode 100644
index 00000000000..c601779bf0b
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/msdi_data_gov_mt_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/nationaalgeoregister_nl_geonetwork.png b/docs/manual/docs/annexes/gallery/img/nationaalgeoregister_nl_geonetwork.png
new file mode 100644
index 00000000000..32e66f9c815
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/nationaalgeoregister_nl_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/opendata_zuid-holland_nl_geonetwork.png b/docs/manual/docs/annexes/gallery/img/opendata_zuid-holland_nl_geonetwork.png
new file mode 100644
index 00000000000..4bb65ef66e0
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/opendata_zuid-holland_nl_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/paikkatietohakemisto_fi.png b/docs/manual/docs/annexes/gallery/img/paikkatietohakemisto_fi.png
new file mode 100644
index 00000000000..2c18932666c
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/paikkatietohakemisto_fi.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/picto-occitanie_fr_accueil.png b/docs/manual/docs/annexes/gallery/img/picto-occitanie_fr_accueil.png
new file mode 100644
index 00000000000..ce3a2dd248d
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/picto-occitanie_fr_accueil.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/pigma_org_geonetwork.png b/docs/manual/docs/annexes/gallery/img/pigma_org_geonetwork.png
new file mode 100644
index 00000000000..03e94e4ecad
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/pigma_org_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/prodige_cerema_fr.png b/docs/manual/docs/annexes/gallery/img/prodige_cerema_fr.png
new file mode 100644
index 00000000000..ed1834f6067
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/prodige_cerema_fr.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/santegraphie_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/santegraphie_fr_geonetwork.png
new file mode 100644
index 00000000000..864a7ab900b
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/santegraphie_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/services_data_shom_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/services_data_shom_fr_geonetwork.png
new file mode 100644
index 00000000000..be83c3bb1d3
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/services_data_shom_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/sextant_ifremer_fr_eng.png b/docs/manual/docs/annexes/gallery/img/sextant_ifremer_fr_eng.png
new file mode 100644
index 00000000000..b3e9b0e4d34
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/sextant_ifremer_fr_eng.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/sigloire_fr.png b/docs/manual/docs/annexes/gallery/img/sigloire_fr.png
new file mode 100644
index 00000000000..f799c5d8ea7
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/sigloire_fr.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/www_cdata_cerema_fr_geonetwork.png b/docs/manual/docs/annexes/gallery/img/www_cdata_cerema_fr_geonetwork.png
new file mode 100644
index 00000000000..29cb719ff76
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/www_cdata_cerema_fr_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/www_metadados_geo_ibge_gov_br_geonetwork_ibge.png b/docs/manual/docs/annexes/gallery/img/www_metadados_geo_ibge_gov_br_geonetwork_ibge.png
new file mode 100644
index 00000000000..b057834f737
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/www_metadados_geo_ibge_gov_br_geonetwork_ibge.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/www_metadados_idesp_sp_gov_br_catalogo.png b/docs/manual/docs/annexes/gallery/img/www_metadados_idesp_sp_gov_br_catalogo.png
new file mode 100644
index 00000000000..c287616928c
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/www_metadados_idesp_sp_gov_br_catalogo.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/www_sandre_eaufrance_fr_atlas.png b/docs/manual/docs/annexes/gallery/img/www_sandre_eaufrance_fr_atlas.png
new file mode 100644
index 00000000000..c80b9d02319
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/www_sandre_eaufrance_fr_atlas.png differ
diff --git a/docs/manual/docs/annexes/gallery/img/www_wodgik_katowice_pl_8080_geonetwork.png b/docs/manual/docs/annexes/gallery/img/www_wodgik_katowice_pl_8080_geonetwork.png
new file mode 100644
index 00000000000..891abf8986f
Binary files /dev/null and b/docs/manual/docs/annexes/gallery/img/www_wodgik_katowice_pl_8080_geonetwork.png differ
diff --git a/docs/manual/docs/annexes/gallery/index.md b/docs/manual/docs/annexes/gallery/index.md
new file mode 100644
index 00000000000..5fc50ed761e
--- /dev/null
+++ b/docs/manual/docs/annexes/gallery/index.md
@@ -0,0 +1,243 @@
+# Some GeoNetwork nodes {#gallery}
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+-
+
+ 
+
+To add your catalog to this list, add it to [this list](https://github.com/geonetwork/doc/tree/develop/source/annexes/gallery/gallery-urls.csv).
diff --git a/docs/manual/docs/annexes/index.md b/docs/manual/docs/annexes/index.md
new file mode 100644
index 00000000000..5ac9b9c66c6
--- /dev/null
+++ b/docs/manual/docs/annexes/index.md
@@ -0,0 +1,5 @@
+# Annexes
+
+- [Metadata Exchange Format (MEF)](mef-format.md)
+- [Some GeoNetwork nodes](gallery/index.md)
+- [Standards](standards/index.md)
diff --git a/docs/manual/docs/annexes/mef-format.md b/docs/manual/docs/annexes/mef-format.md
new file mode 100644
index 00000000000..f550478e1b1
--- /dev/null
+++ b/docs/manual/docs/annexes/mef-format.md
@@ -0,0 +1,148 @@
+# Metadata Exchange Format (MEF) {#mef_format}
+
+## Introduction
+
+The metadata exchange format (MEF in short) is a specially designed file format for the purpose of metadata exchange between different platforms. A metadata exported as a MEF can be imported by any platform which is able to understand MEF. This format has been developed with GeoNetwork in mind so the information it contains is mainly related to GeoNetwork. Nevertheless, it can be used as an interoperability format between different platforms.
+
+This format has been designed with the following needs in mind:
+
+1. Export a metadata record for backup purposes
+2. Import a metadata record from a previous backup
+3. Import a metadata record from a different GeoNetwork version to allow a smooth migration from one version to another.
+4. Capture metadata plus thumbnails and any data uploaded with the metadata record.
+
+In the paragraphs below, some terms should be intended as follows:
+
+1. the term actor is used to indicate any system (application, service etc\...) that operates on metadata.
+2. the term reader will be used to indicate any actor that can import metadata from a MEF file.
+3. the term writer will be used to indicate any actor that can generate a MEF file.
+
+## MEF v1 file format
+
+A MEF file is simply a ZIP file which contains the following files:
+
+``` text
+Root
+ |
+ +--- metadata.xml
+ +--- info.xml
+ +--- public
+ | +---- all public documents and thumbnails
+ +--- private
+ +---- all private documents and thumbnails
+```
+
+1. *metadata.xml*: this file contains the metadata itself, in XML format. The text encoding of the metadata (eg. UTF-8) is specified in the XML declaration.
+2. *info.xml*: this is a special XML file which contains information related to the metadata (metadata about the metadata). Examples of the information in the info.xml file are: creation date, modification date, privileges This information is needed by GeoNetwork.
+3. *public*: this is a directory used to store the metadata thumbnails and other public files. There are no restrictions on the image format but it is strongly recommended to use the portable network graphics (PNG), JPEG or GIF format.
+4. *private*: this is a directory used to store all data (maps, shape files etc\...) uploaded with the metadata in the GeoNetwork editor. Files in this directory are *private* in the sense that authorisation is required to access them. There are no restrictions on the file types that can be stored into this directory.
+
+Any other file or directory present in the MEF file should be ignored by readers that don't recognise them. This allows actors to add custom extensions to the MEF file.
+
+A MEF file can have empty public and private folders depending upon the export format, which can be:
+
+- *simple*: both public and private are omitted.
+- *partial*: only public files are provided.
+- *full*: both public and private files are provided.
+
+It is recommended to use the .mef extension when naming MEF files.
+
+## MEF v2 file format
+
+MEF version 2 support the following:
+
+- multi-metadata support: more than one metadata record and data can be stored in a single MEF file.
+- multi-schema support: be able to store in a single MEF n formats (eg. for an ISO profile, also store a version of that record in the base ISO19115/ISO19139 schema).
+
+Current export services that create MEF files from a metadata record with related records (eg. paent, feature catalog etc), can include these related metadata records in the MEF.
+
+MEF v2 format structure is the following:
+
+``` text
+Root
+ |
+ + 0..n metadata
+ |
+ +--- metadata
+ | +--- metadata.xml
+ | +--- (optional) metadata.iso19139.xml
+ +--- info.xml
+ +--- applschema
+ | +--- (optional) metadata.xml (ISO19110 Feature Catalog)
+ +--- public
+ | +---- all public documents and thumbnails
+ +--- private
+ +---- all private documents and thumbnails
+```
+
+!!! note
+
+ metadata.iso19139.xml is generated by GeoNetwork actors on export if the metadata record in metadata.xml is an ISO19115/19139 profile. On import, this record may be selected for loading if the ISO19115/19139 profile is not present.
+
+
+## The info.xml file
+
+This file contains general information about a metadata. It must have an info root element with a mandatory version attribute. This attribute must be in the X.Y form, where X represents the major version and Y the minor one. The purpose of this attribute is to allow future changes of this format maintaining compatibility with older readers. The policy behind the version is this:
+
+1. A change to Y means a minor change. All existing elements in the previous version must be left unchanged: only new elements or attributes may be added. A reader capable of reading version X.Y is also capable of reading version X.Y' with Y'>Y.
+2. A change to X means a major change. Usually, a reader of version X.Y is not able to read version X'.Y with X'>X.
+
+The root element must have the following children:
+
+1. *general*: a container for general information. It must have the following children:
+ - *uuid*: this is the universally unique identifier assigned to the metadata and must be a valid UUID. This element is optional and, when omitted, the reader should generate one. A metadata without a UUID can be imported several times into the same system without breaking uniqueness constraints. When missing, the reader should also generate the siteId value.
+ - *createDate*: This date indicates when the metadata was created.
+ - *changeDate*: This date keeps track of the most recent change to the metadata.
+ - *siteId*: This is an UUID that identifies the actor that created the metadata and must be a valid UUID. When the UUID element is missing, this element should be missing too. If present, it will be ignored.
+ - *siteName*: This is a human readable name for the actor that created the metadata. It must be present only if the siteId is present.
+ - *schema*: The name of the schema for the metadata record in metadata.xml. When the MEF is imported by a GeoNetwork actor, this name should be the name of a metadata schema handled by the actor (eg. iso19139). If the GeoNetwork actor does not have such a schema, it may try and select another metadata with a schema that is present (eg. the metadata in metadata-iso19139.xml could be loaded because the iso19139 schema is present).
+ - *format*: Indicates the MEF export format. The element's value must belong to the following set: { *simple*, *partial*, *full* }.
+ - *localId*: This is an optional element. If present, indicates the id used locally by the sourceId actor to store the metadata. Its purpose is just to allow the reuse of the same local id when reimporting a metadata.
+ - *isTemplate*: A boolean field that indicates if this metadata is a template used to create new ones. There is no real distinction between a real metadata and a template but some actors use it to allow fast metadata creation. The value must be: { *true*, *false* }.
+ - *rating*: This is an optional element. If present, indicates the users' rating of the metadata ranging from 1 (a bad rating) to 5 (an excellent rating). The special value 0 means that the metadata has not been rated yet. Can be used to sort search results.
+ - *popularity*: Another optional value. If present, indicates the popularity of the metadata. The value must be positive and high values mean high popularity. The criteria used to set the popularity is left to the writer. Its main purpose is to provide a metadata ordering during a search.
+2. *categories*: a container for categories associated to this metadata. A category is just a name, like 'audio-video' that classifies the metadata to allow an easy search. Each category is specified by a category element which must have a name attribute. This attribute is used to store the category's name. If there are no categories, the categories element will be empty.
+3. *privileges*: a container for privileges associated to this metadata. Privileges are operations that a group (which represents a set of users) can do on a metadata and are specified by a set of group elements. Each one of these, has a mandatory name attribute to store the group's name and a set of operation elements used to store the operations allowed on the metadata. Each operation element must have a name attribute which value must belong to the following set: { *view*, *download*, *notify*, *dynamic*, *featured* }. If there are no groups or the actor does not have the concept of group, the privileges element will be empty. A group element without any operation element must be ignored by readers.
+4. *public*: All metadata thumbnails (and any other public file) must be listed here. This container contains a file element for each file. Mandatory attributes of this element are name, which represents the file's name and changeDate, which contains the date of the latest change to the file. The public element is optional but, if present, must contain all the files present in the metadata's public directory and any reader that imports these files must set the latest change date on these using the provided ones. The purpose of this element is to provide more information in the case the MEF format is used for metadata harvesting.
+5. *private*: This element has the same purpose and structure of the public element but is related to maps and all other private files.
+
+Any other element or attribute should be ignored by readers that don't understand them. This allows actors to add custom attributes or subtrees to the XML.
+
+### Date format {#info_xml}
+
+Unless differently specified, all dates in this file must be in the ISO/8601 format. The pattern must be ``YYYY-MM-DDTHH:mm:SS`` and the timezone should be the local one.
+
+Example of info file:
+
+``` xml
+
+
+ 0619abc0-708b-eeda-8202-000d98959033
+ 2006-12-11T10:33:21
+ 2006-12-14T08:44:43
+ 0619cc50-708b-11da-8202-000d9335906e
+ FAO main site
+ iso19139
+ full
+ 204
+ false
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
diff --git a/docs/manual/docs/annexes/standards/dublin-core.md b/docs/manual/docs/annexes/standards/dublin-core.md
new file mode 100644
index 00000000000..0550f369ebd
--- /dev/null
+++ b/docs/manual/docs/annexes/standards/dublin-core.md
@@ -0,0 +1,1193 @@
+# Dublin core (dublin-core) {#dublin-core}
+
+The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for
+
+: use in resource description. The name "Dublin" is due to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" because its elements are broad and generic, usable for describing a wide range of resources.
+
+More details:
+
+## Metadata editor
+
+This standard can be encoded using 3 view(s).
+
+- [View: Simple (default)](dublin-core.md#dublin-core-view-default)
+- [View: Full (advanced)](dublin-core.md#dublin-core-view-advanced)
+- [View: XML (xml)](dublin-core.md#dublin-core-view-xml)
+
+### View: Simple (default) {#dublin-core-view-default}
+
+This view is composed of1tab(s).
+
+- [Tab: Simple (default)](dublin-core.md#dublin-core-tab-default)
+
+This view also allows to add the following element even if not in the current record:
+
+- Subject and Keywords (dc:subject)
+
+#### Tab: Simple (default) {#dublin-core-tab-default}
+
+
+
+This tab display elements from the XML metadata record.
+
+##### Section: Metadata
+
+See [Metadata](dublin-core.md#dublin-core-elem-simpledc-8506dd4a73872a53513368db419204a3)
+
+### View: Full (advanced) {#dublin-core-view-advanced}
+
+This view is composed of1tab(s).
+
+- [Tab: Full (advanced)](dublin-core.md#dublin-core-tab-advanced)
+
+#### Tab: Full (advanced) {#dublin-core-tab-advanced}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata
+
+See [Metadata](dublin-core.md#dublin-core-elem-simpledc-8506dd4a73872a53513368db419204a3)
+
+### View: XML (xml) {#dublin-core-view-xml}
+
+This view is composed of1tab(s).
+
+- [Tab: XML (xml)](dublin-core.md#dublin-core-tab-xml)
+
+#### Tab: XML (xml) {#dublin-core-tab-xml}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+## Schema technical details
+
+Standard identifier
+
+:
+
+> dublin-core
+
+Version
+
+:
+
+> 1.0
+
+Schema location
+
+:
+
+Schema namespaces
+
+:
+
+-
+-
+-
+
+Schema detection mode
+
+:
+
+> gns:elements (root)
+
+Schema detection elements
+
+:
+
+- simpledc
+
+## Standard elements
+
+List of all elements available in the standard.
+
+### Contributor {#dublin-core-elem-dc-contributor-0974cafd6cf5302fe8501874dbe3b3ac}
+
+Name
+
+:
+
+> dc:contributor
+
+Description
+
+:
+
+```{=html}
+An entity responsible for making contributions to the content of the resource.
+```
+### Coverage {#dublin-core-elem-dc-coverage-8a3ad050a5c9949ad92271f646817e10}
+
+Name
+
+:
+
+> dc:coverage
+
+Description
+
+:
+
+```{=html}
+The extent or scope of the content of the resource. Typically, Coverage will
+ include spatial location (a place name or geographic coordinates), temporal period (a period
+ label, date, or date range), or jurisdiction (such as a named administrative entity).
+```
+``` xml
+
+ North 45.668, South 45.635, East 4.805, West 4.768. CHARLY
+
+```
+
+### Creator {#dublin-core-elem-dc-creator-f6d71ca3a0b4e9aeb0e518f195f8256e}
+
+Name
+
+:
+
+> dc:creator
+
+Description
+
+:
+
+```{=html}
+An entity primarily responsible for making the content of the resource.
+```
+``` xml
+
+ Métropole de Lyon / Direction Innovation Numérique et Systèmes d'Information
+ (DINSI) (Géomatique et données métropolitaines)
+
+```
+
+### Date {#dublin-core-elem-dc-date-23c64254f66925f9eb6e3bd19c442233}
+
+Name
+
+:
+
+> dc:date
+
+Description
+
+:
+
+```{=html}
+A date of an event in the lifecycle of the resource. Typically, Date will be
+ associated with the creation or availability of the resource.
+```
+### Description {#dublin-core-elem-dc-description-8918d5eea5202286bfa9ceaac948b704}
+
+Name
+
+:
+
+> dc:description
+
+Description
+
+:
+
+```{=html}
+An account of the content of the resource.
+```
+``` xml
+
+ La maquette 3D de la commune (2009 ou 2012) est composée de deux à six
+ couches de données. A minima, toutes les maquettes se composent des deux
+ couches suivantes : - Le Modèle numérique de terrain (TIN) et ses textures
+ associées ; - Les bâtiments 3D texturés (BATIS). Elle est complétée par une
+ ou plusieurs des couches ci-dessous : - Les surfaces en eau (WATER) et leurs
+ textures associées ; - Les bâtiments « remarquables » (Mairies, Eglises
+ etc…) ; - Les ponts « remarquables » ; - Les objets « remarquables »
+ (Statues, Fontaines etc…). Ces données sont modélisées suivant la norme
+ CityGML et fournies dans ce format. Ces maquettes sont produites avec le
+ logiciel RhinoTerrain/RhinoCity.
+
+```
+
+### Format {#dublin-core-elem-dc-format-3842730cdb5c8559fe6f2737815429ea}
+
+Name
+
+:
+
+> dc:format
+
+Description
+
+:
+
+```{=html}
+The physical or digital manifestation of the resource. Typically, Format will
+ include the media-type or dimensions of the resource. Format may be used to identify the
+ software, hardware, or other equipment needed to display or operate the resource.
+```
+### Resource Identifier {#dublin-core-elem-dc-identifier-7d64a0a5c40868491c49bf7df7574752}
+
+Name
+
+:
+
+> dc:identifier
+
+Description
+
+:
+
+```{=html}
+An unambiguous reference to the resource within a given context.
+```
+``` xml
+a806d3e1-c240-43a9-bbc3-643e8c93b10d
+```
+
+### Language {#dublin-core-elem-dc-language-74e0ef625be0b45d0e6c64d5f76e1895}
+
+Name
+
+:
+
+> dc:language
+
+Description
+
+:
+
+```{=html}
+A language of the intellectual content of the resource. Recommended best practice
+ is to use RFC 3066, which, in conjunction with ISO 639, defines two- and three-letter primary
+ language tags with optional subtags.
+```
+``` xml
+fre
+```
+
+### Publisher {#dublin-core-elem-dc-publisher-5534d3efaa13b75c3aa34c379dd91025}
+
+Name
+
+:
+
+> dc:publisher
+
+Description
+
+:
+
+```{=html}
+An entity responsible for making the resource available.
+```
+``` xml
+
+ Métropole de Lyon / Direction Innovation Numérique et Systèmes d'Information
+ (DINSI) (Géomatique et données métropolitaines)
+
+```
+
+### Relation {#dublin-core-elem-dc-relation-3772ef19f1f075e519d2d0a60ec6f05a}
+
+Name
+
+:
+
+> dc:relation
+
+Description
+
+:
+
+```{=html}
+A reference to a related resource.
+```
+### Rights Management {#dublin-core-elem-dc-rights-32dce43ec1342a098287b03b6a5cb72f}
+
+Name
+
+:
+
+> dc:rights
+
+Description
+
+:
+
+```{=html}
+Information about rights held in and over the resource.
+```
+### Source {#dublin-core-elem-dc-source-104607b158c41c5855de1ed62ae223dd}
+
+Name
+
+:
+
+> dc:source
+
+Description
+
+:
+
+```{=html}
+A Reference to a resource from which the present resource is derived. The present
+ resource may be derived from the Source resource in whole or in part.
+```
+``` xml
+
+ Le Modèle numérique de terrain est issu d’une saisie photogrammétrique
+ réalisée à partir de la prise de vue aérienne (2009 ou 2012). Les fichiers
+ des textures associées plaquées sur le MNT correspondent à
+ l’orthophotographie aérienne qui possède une résolution de 10 cm pour 2012
+ et 16 cm pour 2009. - Les surfaces en eau (WATER) ont été identifiées à
+ partir d’une saisie photogrammétrique réalisée à partir de la même prise de
+ vue aérienne. - Les bâtiments 3D proviennent de la saisie photogrammétrique
+ réalisée à partir de la prise de vue aérienne. Les textures plaquées sur ces
+ bâtiments proviennent des clichés issus de la prise de vue aérienne. - Les
+ bâtiments « remarquables » (Mairies, Eglises etc…), les ponts « remarquables
+ » et les objets « remarquables » (Statues, Fontaines etc…) ont été texturés
+ à partir de photographies terrestres.
+
+```
+
+### Subject and Keywords {#dublin-core-elem-dc-subject-a88bd90b4991695f8c45fe01df3f64d6}
+
+Name
+
+:
+
+> dc:subject
+
+Description
+
+:
+
+```{=html}
+A topic of the content of the resource. Typically, Subject will be expressed as
+ keywords, key phrases, or classification codes that describe a topic of the resource.
+```
+``` xml
+Localisation
+```
+
+### Title {#dublin-core-elem-dc-title-18e3be863c870257c8b70d577038ee5f}
+
+Name
+
+:
+
+> dc:title
+
+Description
+
+:
+
+```{=html}
+A name given to the resource. Typically, Title will be a name by which the resource
+ is formally known.
+```
+``` xml
+
+ Maquette 3D texturée de la commune de Charly (la Métropole de Lyon)
+
+```
+
+### Resource Type {#dublin-core-elem-dc-type-15bbc75f8dbe617d6ed609fcf1202ee1}
+
+Name
+
+:
+
+> dc:type
+
+Description
+
+:
+
+```{=html}
+The nature or genre of the content of the resource. Type includes terms describing
+ general categories, functions, genres, or aggregation levels for content.
+```
+Recommended values
+
+| code | label |
+|---------|---------|
+| dataset | Dataset |
+| service | Service |
+
+``` xml
+nonGeographicDataset
+```
+
+### URI {#dublin-core-elem-dc-URI-8f2cb1e27778e1b1977e670ca7e7a282}
+
+Name
+
+:
+
+> dc:URI
+
+Description
+
+:
+
+### Abstract {#dublin-core-elem-dct-abstract-a48c3a17636153c58749c5fc29d1bd28}
+
+Name
+
+:
+
+> dct:abstract
+
+Description
+
+:
+
+```{=html}
+A summary of the content of the resource.
+```
+### Access Rights {#dublin-core-elem-dct-accessRights-972cd1c89a0274325b1a3b99e34c95be}
+
+Name
+
+:
+
+> dct:accessRights
+
+Description
+
+:
+
+```{=html}
+Information about who can access the resource or an indication of its security
+ status.
+```
+### Accrual Method {#dublin-core-elem-dct-accrualMethod-6fa8ea67638a1578c231025e31dd40e9}
+
+Name
+
+:
+
+> dct:accrualMethod
+
+Description
+
+:
+
+```{=html}
+The method by which items are added to a collection.
+```
+### Accrual Periodicity {#dublin-core-elem-dct-accrualPeriodicity-2a4c9a8426dd588e960559174a3df263}
+
+Name
+
+:
+
+> dct:accrualPeriodicity
+
+Description
+
+:
+
+```{=html}
+The frequency with which items are added to a collection.
+```
+Recommended values
+
+| code | label |
+|-------------|-------------|
+| continual | Continual |
+| daily | Daily |
+| weekly | Weekly |
+| fortnightly | Fortnightly |
+| monthly | Monthly |
+| quarterly | Quarterly |
+| biannually | Biannually |
+| annually | Annually |
+| asNeeded | As needed |
+| irregular | Irregular |
+| notPlanned | Not planned |
+| unknown | Unknown |
+
+``` xml
+Irregular
+```
+
+### Accrual Policy {#dublin-core-elem-dct-accrualPolicy-0ae937a1f9081db219a5dd04ed4610d4}
+
+Name
+
+:
+
+> dct:accrualPolicy
+
+Description
+
+:
+
+```{=html}
+The policy governing the addition of items to a collection.
+```
+### Alternative Title {#dublin-core-elem-dct-alternative-2518e8fc9fa67f5a10348016aae8bb0f}
+
+Name
+
+:
+
+> dct:alternative
+
+Description
+
+:
+
+```{=html}
+An alternative name for the resource.
+```
+### Audience {#dublin-core-elem-dct-audience-a610cbdc155d7cd9c87c8f22ef245521}
+
+Name
+
+:
+
+> dct:audience
+
+Description
+
+:
+
+```{=html}
+A class of entity for whom the resource is intended or useful.
+```
+### Bibliographic Citation {#dublin-core-elem-dct-bibliographicCitation-0d3ba175bdb84be48dec71bdb6b318da}
+
+Name
+
+:
+
+> dct:bibliographicCitation
+
+Description
+
+:
+
+```{=html}
+A bibliographic reference for the resource.
+```
+### Conforms To {#dublin-core-elem-dct-conformsTo-703d80b57bd6629b2bff3f57efd52dc5}
+
+Name
+
+:
+
+> dct:conformsTo
+
+Description
+
+:
+
+```{=html}
+An established standard to which the described resource conforms.
+```
+### Date Created {#dublin-core-elem-dct-created-9aebe20151c1c962d66737fcb9b87c2c}
+
+Name
+
+:
+
+> dct:created
+
+Description
+
+:
+
+```{=html}
+Date of creation of the resource.
+```
+``` xml
+2014-12-19
+```
+
+### Date Accepted {#dublin-core-elem-dct-dateAccepted-9f6f7b46bae794b317c939c75170b0f1}
+
+Name
+
+:
+
+> dct:dateAccepted
+
+Description
+
+:
+
+```{=html}
+Date of acceptance of the resource.
+```
+### Date Copyrighted {#dublin-core-elem-dct-dateCopyrighted-1a3940c001fd2db761829940957d8bf7}
+
+Name
+
+:
+
+> dct:dateCopyrighted
+
+Description
+
+:
+
+```{=html}
+Date of copyright.
+```
+### Date Submitted {#dublin-core-elem-dct-dateSubmitted-0e038c3b8ac6daca57211a938eca6154}
+
+Name
+
+:
+
+> dct:dateSubmitted
+
+Description
+
+:
+
+```{=html}
+Date of submission of the resource
+```
+``` xml
+2015-01-23
+```
+
+### Audience Education Level {#dublin-core-elem-dct-educationLevel-fa33466d34d56fb066753a6d97089631}
+
+Name
+
+:
+
+> dct:educationLevel
+
+Description
+
+:
+
+```{=html}
+A class of entity, defined in terms of progression through an educational or
+ training context, for which the described resource is intended.
+```
+### Extent {#dublin-core-elem-dct-extent-8a3a9adeaaac054e64dff722ad23c776}
+
+Name
+
+:
+
+> dct:extent
+
+Description
+
+:
+
+```{=html}
+The size or duration of the resource.
+```
+### Has Format {#dublin-core-elem-dct-hasFormat-d136ed16dc44af39fdf1b98b9fb4bc33}
+
+Name
+
+:
+
+> dct:hasFormat
+
+Description
+
+:
+
+```{=html}
+A related resource that is substantially the same as the pre-existing described
+ resource, but in another format.
+```
+### Has Part {#dublin-core-elem-dct-hasPart-f251f156dd8774a81f44c13c7b4a9e7d}
+
+Name
+
+:
+
+> dct:hasPart
+
+Description
+
+:
+
+```{=html}
+A related resource that is included either physically or logically in the described
+ resource.
+```
+### Has Version {#dublin-core-elem-dct-hasVersion-b8dc08cd4fc15cf1df605c2905b0c5e3}
+
+Name
+
+:
+
+> dct:hasVersion
+
+Description
+
+:
+
+```{=html}
+A related resource that is a version, edition, or adaptation of the described
+ resource.
+```
+### Instructional Method {#dublin-core-elem-dct-instructionalMethod-d220d889250a4a0f7e3efe29fc0f0ada}
+
+Name
+
+:
+
+> dct:instructionalMethod
+
+Description
+
+:
+
+```{=html}
+A process, used to engender knowledge, attitudes and skills, that the resource is
+ designed to support.
+```
+### Is Format Of {#dublin-core-elem-dct-isFormatOf-8378903643254b5b83ae2acdc251b6a6}
+
+Name
+
+:
+
+> dct:isFormatOf
+
+Description
+
+:
+
+```{=html}
+A related resource that is substantially the same as the described resource, but in
+ another format.
+```
+### Is part of {#dublin-core-elem-dct-isPartOf-6697c98943756abf56d4c2a50f9dc9a2}
+
+Name
+
+:
+
+> dct:isPartOf
+
+Description
+
+:
+
+```{=html}
+A related resource in which the described resource is physically or logically
+ included.
+```
+``` xml
+8017c69a-5b17-404f-acdd-d9c37a0afac4
+```
+
+### Is Referenced By {#dublin-core-elem-dct-isReferencedBy-4cf2c75a368a7773ec781eaa6f4a7c03}
+
+Name
+
+:
+
+> dct:isReferencedBy
+
+Description
+
+:
+
+```{=html}
+A related resource that references, cites, or otherwise points to the described
+ resource.
+```
+### Is Replaced By {#dublin-core-elem-dct-isReplacedBy-1e391e071c75e45dcf0a309285a642a0}
+
+Name
+
+:
+
+> dct:isReplacedBy
+
+Description
+
+:
+
+```{=html}
+A related resource that supplants, displaces, or supersedes the described
+ resource.
+```
+### Is Required By {#dublin-core-elem-dct-isRequiredBy-def534523d854e3440e36701bea47cc4}
+
+Name
+
+:
+
+> dct:isRequiredBy
+
+Description
+
+:
+
+```{=html}
+A related resource that requires the described resource to support its function,
+ delivery, or coherence.
+```
+### Date Issued {#dublin-core-elem-dct-issued-9f6ad8cb4b5e6225c1cb755489adb774}
+
+Name
+
+:
+
+> dct:issued
+
+Description
+
+:
+
+```{=html}
+Date of formal issuance (e.g., publication) of the resource.
+```
+### Is Version Of {#dublin-core-elem-dct-isVersionOf-d1658a9e84f777d0a335528e82921417}
+
+Name
+
+:
+
+> dct:isVersionOf
+
+Description
+
+:
+
+```{=html}
+A related resource of which the described resource is a version, edition, or
+ adaptation.
+```
+### License {#dublin-core-elem-dct-license-865405c25292b886c12f7d056ebaabda}
+
+Name
+
+:
+
+> dct:license
+
+Description
+
+:
+
+```{=html}
+A legal document giving official permission to do something with the resource.
+```
+### Mediator {#dublin-core-elem-dct-mediator-ab02c72730e6dbccbfb74b07e00edf10}
+
+Name
+
+:
+
+> dct:mediator
+
+Description
+
+:
+
+```{=html}
+An entity that mediates access to the resource and for whom the resource is
+ intended or useful.
+```
+### Medium {#dublin-core-elem-dct-medium-95f834fde8ee306293ebebcfd7a3aba5}
+
+Name
+
+:
+
+> dct:medium
+
+Description
+
+:
+
+```{=html}
+The material or physical carrier of the resource.
+```
+### Date Modified {#dublin-core-elem-dct-modified-66ecff9b0ec74fad28c5babebc1eec7d}
+
+Name
+
+:
+
+> dct:modified
+
+Description
+
+:
+
+```{=html}
+Data metadata was modified
+```
+``` xml
+2016-02-03T21:33:45
+```
+
+### Provenance {#dublin-core-elem-dct-provenance-4ec9c18f260230d4455195d6a6f28c17}
+
+Name
+
+:
+
+> dct:provenance
+
+Description
+
+:
+
+```{=html}
+A statement of any changes in ownership and custody of the resource since its
+ creation that are significant for its authenticity, integrity and interpretation.
+```
+### Related resource {#dublin-core-elem-dct-references-3a44416fcd20eea0684aad2fd3228fdd}
+
+Name
+
+:
+
+> dct:references
+
+Description
+
+:
+
+```{=html}
+A related resource that is referenced, cited, or otherwise pointed to by the
+ described resource.
+```
+### Replaces {#dublin-core-elem-dct-replaces-c5b09017642a464af7a04db426f6d74f}
+
+Name
+
+:
+
+> dct:replaces
+
+Description
+
+:
+
+```{=html}
+A related resource that is supplanted, displaced, or superseded by the described
+ resource.
+```
+### Requires {#dublin-core-elem-dct-requires-2ad52ab491717dc624f79f92303f4679}
+
+Name
+
+:
+
+> dct:requires
+
+Description
+
+:
+
+```{=html}
+A related resource that is required by the described resource to support its
+ function, delivery, or coherence.
+```
+### Rights Holder {#dublin-core-elem-dct-rightsHolder-0f4304cc1135f8fc29f7a0ede8daa268}
+
+Name
+
+:
+
+> dct:rightsHolder
+
+Description
+
+:
+
+```{=html}
+A person or organization owning or managing rights over the resource.
+```
+### Spatial {#dublin-core-elem-dct-spatial-5100d679492a6f79fd3e53db624bcab2}
+
+Name
+
+:
+
+> dct:spatial
+
+Description
+
+:
+
+```{=html}
+Spatial characteristics of the intellectual content of the resource.
+```
+``` xml
+RGF93 / CC46 (EPSG:3946)
+```
+
+### Table Of Contents {#dublin-core-elem-dct-tableOfContents-c20c496386cad7aa48ad05ca41a6340b}
+
+Name
+
+:
+
+> dct:tableOfContents
+
+Description
+
+:
+
+```{=html}
+A list of subunits of the resource.
+```
+### Temporal Coverage {#dublin-core-elem-dct-temporal-0a2abb1d37421418cafeb48bd21e6854}
+
+Name
+
+:
+
+> dct:temporal
+
+Description
+
+:
+
+```{=html}
+Temporal characteristics of the resource.
+```
+### Date Valid {#dublin-core-elem-dct-valid-343768fccc581bc0822c69e6ca19c70c}
+
+Name
+
+:
+
+> dct:valid
+
+Description
+
+:
+
+```{=html}
+Date (often a range) of validity of a resource.
+```
+### Metadata {#dublin-core-elem-simpledc-8506dd4a73872a53513368db419204a3}
+
+Name
+
+:
+
+> simpledc
+
+Description
+
+:
+
+``` xml
+
+
+ Maquette 3D texturée de la commune de Charly (la Métropole de Lyon)
+
+
+ Métropole de Lyon / Direction Innovation Numérique et Systèmes d'Information
+ (DINSI) (Géomatique et données métropolitaines)
+
+ Localisation
+
+ La maquette 3D de la commune (2009 ou 2012) est composée de deux à six
+ couches de données. A minima, toutes les maquettes se composent des deux
+ couches suivantes : - Le Modèle numérique de terrain (TIN) et ses textures
+ associées ; - Les bâtiments 3D texturés (BATIS). Elle est complétée par une
+ ou plusieurs des couches ci-dessous : - Les surfaces en eau (WATER) et leurs
+ textures associées ; - Les bâtiments « remarquables » (Mairies, Eglises
+ etc…) ; - Les ponts « remarquables » ; - Les objets « remarquables »
+ (Statues, Fontaines etc…). Ces données sont modélisées suivant la norme
+ CityGML et fournies dans ce format. Ces maquettes sont produites avec le
+ logiciel RhinoTerrain/RhinoCity.
+
+
+ Métropole de Lyon / Direction Innovation Numérique et Systèmes d'Information
+ (DINSI) (Géomatique et données métropolitaines)
+
+ nonGeographicDataset
+ application/zip
+ CityGML (taille : 260.0 Mo)
+ application/zip
+ executable (taille : 829.2 Mo)
+ application/zip
+ CityGML (taille : 113.5 Mo)
+ application/zip
+ executable (taille : 339.2 Mo)
+ application/pdf
+ pdf (taille : 315 Ko)
+
+ Le Modèle numérique de terrain est issu d’une saisie photogrammétrique
+ réalisée à partir de la prise de vue aérienne (2009 ou 2012). Les fichiers
+ des textures associées plaquées sur le MNT correspondent à
+ l’orthophotographie aérienne qui possède une résolution de 10 cm pour 2012
+ et 16 cm pour 2009. - Les surfaces en eau (WATER) ont été identifiées à
+ partir d’une saisie photogrammétrique réalisée à partir de la même prise de
+ vue aérienne. - Les bâtiments 3D proviennent de la saisie photogrammétrique
+ réalisée à partir de la prise de vue aérienne. Les textures plaquées sur ces
+ bâtiments proviennent des clichés issus de la prise de vue aérienne. - Les
+ bâtiments « remarquables » (Mairies, Eglises etc…), les ponts « remarquables
+ » et les objets « remarquables » (Statues, Fontaines etc…) ont été texturés
+ à partir de photographies terrestres.
+
+ fre
+
+ https://download.data.grandlyon.com/files/grandlyon/localisation/bati3d/CHARLY_2012.zip
+
+
+ https://download.data.grandlyon.com/files/grandlyon/localisation/bati3d/_EXE_CHARLY_2012.zip
+
+
+ https://download.data.grandlyon.com/files/grandlyon/localisation/bati3d/CHARLY_2009.zip
+
+
+ https://download.data.grandlyon.com/files/grandlyon/localisation/bati3d/_EXE_CHARLY_2009.zip
+
+
+ https://download.data.grandlyon.com/files/grandlyon/localisation/bati3d/Maquettes_3D_CityGML.pdf
+
+
+ https://download.data.grandlyon.com/files/grandlyon/LicenceOuverte.pdf
+
+
+ North 45.668, South 45.635, East 4.805, West 4.768. CHARLY
+
+ Licence Ouverte
+ Pas de restriction d'accès public selon INSPIRE
+ 2014-12-19
+ 2015-01-23
+ 8017c69a-5b17-404f-acdd-d9c37a0afac4
+ RGF93 / CC46 (EPSG:3946)
+ Irregular
+ 2016-02-03T21:33:45
+ a806d3e1-c240-43a9-bbc3-643e8c93b10d
+
+```
+
+## Standard codelists
+
+List of all codelists available in the standard.
+
+No codelist defined.
diff --git a/docs/manual/docs/annexes/standards/img/dublin-core-tab-default.png b/docs/manual/docs/annexes/standards/img/dublin-core-tab-default.png
new file mode 100644
index 00000000000..5b4fc460099
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/dublin-core-tab-default.png differ
diff --git a/docs/manual/docs/annexes/standards/img/iso19110-tab-default.png b/docs/manual/docs/annexes/standards/img/iso19110-tab-default.png
new file mode 100644
index 00000000000..cd8909c6217
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/iso19110-tab-default.png differ
diff --git a/docs/manual/docs/annexes/standards/img/iso19139-tab-dataQualityInfo.png b/docs/manual/docs/annexes/standards/img/iso19139-tab-dataQualityInfo.png
new file mode 100644
index 00000000000..064802f8923
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/iso19139-tab-dataQualityInfo.png differ
diff --git a/docs/manual/docs/annexes/standards/img/iso19139-tab-default.png b/docs/manual/docs/annexes/standards/img/iso19139-tab-default.png
new file mode 100644
index 00000000000..32c64280131
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/iso19139-tab-default.png differ
diff --git a/docs/manual/docs/annexes/standards/img/iso19139-tab-identificationInfo.png b/docs/manual/docs/annexes/standards/img/iso19139-tab-identificationInfo.png
new file mode 100644
index 00000000000..7e5b536046c
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/iso19139-tab-identificationInfo.png differ
diff --git a/docs/manual/docs/annexes/standards/img/iso19139-tab-inspire.png b/docs/manual/docs/annexes/standards/img/iso19139-tab-inspire.png
new file mode 100644
index 00000000000..30a57aa728f
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/iso19139-tab-inspire.png differ
diff --git a/docs/manual/docs/annexes/standards/img/iso19139-tab-referenceSystemInfo.png b/docs/manual/docs/annexes/standards/img/iso19139-tab-referenceSystemInfo.png
new file mode 100644
index 00000000000..b7ab16adb50
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/iso19139-tab-referenceSystemInfo.png differ
diff --git a/docs/manual/docs/annexes/standards/img/metawal-tramedesaxes.png b/docs/manual/docs/annexes/standards/img/metawal-tramedesaxes.png
new file mode 100644
index 00000000000..2be2d504954
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/metawal-tramedesaxes.png differ
diff --git a/docs/manual/docs/annexes/standards/img/sextant-checkpoint.png b/docs/manual/docs/annexes/standards/img/sextant-checkpoint.png
new file mode 100644
index 00000000000..937e3b5521a
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/sextant-checkpoint.png differ
diff --git a/docs/manual/docs/annexes/standards/img/standardlist.png b/docs/manual/docs/annexes/standards/img/standardlist.png
new file mode 100644
index 00000000000..bda4e3c7191
Binary files /dev/null and b/docs/manual/docs/annexes/standards/img/standardlist.png differ
diff --git a/docs/manual/docs/annexes/standards/index.md b/docs/manual/docs/annexes/standards/index.md
new file mode 100644
index 00000000000..6216f402afd
--- /dev/null
+++ b/docs/manual/docs/annexes/standards/index.md
@@ -0,0 +1,16 @@
+# Standards
+
+The catalog support the following standards:
+
+
+
+- [Geographic information -- Metadata (iso19115-3.2018)](iso19115-3.2018.md)
+- [Geographic information -- Metadata (iso19139:2007) (iso19139)](iso19139.md)
+- [Geographic information -- Methodology for feature cataloguing (Deprecated - use ISO19115-3) (iso19110)](iso19110.md)
+- [Dublin core (dublin-core)](dublin-core.md)
+
+ISO19110 can be used to encode feature catalogue (but ISO19115-3 is recommended).
+
+Dublin core (for CSW only) is only used to test OGC CSW testsuites.
+
+Others standards and community profiles are available on .
diff --git a/docs/manual/docs/annexes/standards/iso19110.md b/docs/manual/docs/annexes/standards/iso19110.md
new file mode 100644
index 00000000000..dea7a09042e
--- /dev/null
+++ b/docs/manual/docs/annexes/standards/iso19110.md
@@ -0,0 +1,1877 @@
+# Geographic information -- Methodology for feature cataloguing (Deprecated - use ISO19115-3) (iso19110) {#iso19110}
+
+More details:
+
+## Metadata editor
+
+This standard can be encoded using 3 view(s).
+
+- [View: Simple (default)](iso19110.md#iso19110-view-default)
+- [View: Full (advanced)](iso19110.md#iso19110-view-advanced)
+- [View: XML (xml)](iso19110.md#iso19110-view-xml)
+
+### View: Simple (default) {#iso19110-view-default}
+
+This view is composed of1tab(s).
+
+- [Tab: Simple (default)](iso19110.md#iso19110-tab-default)
+
+This view also allows to add the following element even if not in the current record:
+
+- Code (gfc:code)
+- Codelist (gfc:listedValue)
+
+#### Tab: Simple (default) {#iso19110-tab-default}
+
+
+
+This tab display elements from the XML metadata record.
+
+##### Name
+
+```{=html}
+Feature catalogue name
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gmx:name
+
+See [Name](iso19110.md#iso19110-elem-gmx-name-5ec0c4442ad2b94944636103e556d401)
+
+##### Name
+
+```{=html}
+Feature catalogue name
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:name
+
+See [Name](iso19110.md#iso19110-elem-gfc-name-134285dc9b9a3268556039e2fe3f370e)
+
+##### Scope
+
+```{=html}
+Scope definition
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gmx:scope
+
+See [Scope](iso19110.md#iso19110-elem-gmx-scope-14efac6982297b09ba1324e80138092f)
+
+##### Scope
+
+```{=html}
+Scope definition
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:scope
+
+See [Scope](iso19110.md#iso19110-elem-gfc-scope-4f044fce55b8e0b6dd0d77516ad9e66d)
+
+##### Field of application
+
+```{=html}
+Field of application
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gmx:fieldOfApplication
+
+See [Field of application](iso19110.md#iso19110-elem-gmx-fieldOfApplication-66508d1f139317e01e1decd095915428)
+
+##### Field of application
+
+```{=html}
+Field of application
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:fieldOfApplication
+
+See [Field of application](iso19110.md#iso19110-elem-gfc-fieldOfApplication-548e0631e3ea92f7dd05ac533b6c14d2)
+
+##### Version
+
+```{=html}
+Catalogue version
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gmx:versionNumber
+
+See [Version](iso19110.md#iso19110-elem-gmx-versionNumber-075201f18225aec432b46c75a93589a2)
+
+##### Version
+
+```{=html}
+Catalogue version
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:versionNumber
+
+See [Version](iso19110.md#iso19110-elem-gfc-versionNumber-d66ec9fd5c22c70a69dd2b759d66cc4f)
+
+##### Date
+
+```{=html}
+Catalogue date
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gmx:versionDate
+
+See [Date](iso19110.md#iso19110-elem-gmx-versionDate-6c27e2ee0b2daa4ab1aea9ef374bc08f)
+
+##### Catalogue producer
+
+```{=html}
+Catalogue responsible
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:producer
+
+See [Catalogue producer](iso19110.md#iso19110-elem-gfc-producer-5a13bfab8b07441bc9f9f71dcfdf7f6c)
+
+##### Functional language
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:functionalLanguage
+
+See [Functional language](iso19110.md#iso19110-elem-gfc-functionalLanguage-7a21d9c35ed9c400c40959ede97b8d76)
+
+##### Property description
+
+```{=html}
+Property description
+```
+
+XPath
+
+:
+
+> /gfc:FC_FeatureCatalogue/gfc:featureType
+
+See [Property description](iso19110.md#iso19110-elem-gfc-featureType-d6099a684b15337451388dd46048c48f)
+
+Type
+
+:
+
+> suggest
+
+### View: Full (advanced) {#iso19110-view-advanced}
+
+This view is composed of1tab(s).
+
+- [Tab: Full (advanced)](iso19110.md#iso19110-tab-advanced)
+
+#### Tab: Full (advanced) {#iso19110-tab-advanced}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Feature Catalogue description
+
+See [Feature Catalogue description](iso19110.md#iso19110-elem-gfc-FC_FeatureCatalogue-a4de444fdd9a6e86e8ba63bb96be363c)
+
+### View: XML (xml) {#iso19110-view-xml}
+
+This view is composed of1tab(s).
+
+- [Tab: XML (xml)](iso19110.md#iso19110-tab-xml)
+
+#### Tab: XML (xml) {#iso19110-tab-xml}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+## Schema technical details
+
+Standard identifier
+
+:
+
+> iso19110
+
+Version
+
+:
+
+> 1.0
+
+Schema location
+
+:
+
+>
+
+Schema namespaces
+
+:
+
+-
+-
+-
+-
+
+Schema detection mode
+
+:
+
+> elements (root)
+
+Schema detection elements
+
+:
+
+- gfc:FC_FeatureCatalogue
+- gfc:FC_FeatureType
+
+## Standard elements
+
+List of all elements available in the standard.
+
+### Text {#iso19110-elem-gco-CharacterString-44f4a753bad9d1df04d0611f28f05110}
+
+Name
+
+:
+
+> gco:CharacterString
+
+Description
+
+:
+
+### Lower cardinality {#iso19110-elem-gco-lower-52bfcbb528e9aaefc2e33f4fdc55aa5f}
+
+Name
+
+:
+
+> gco:lower
+
+Description
+
+:
+
+```{=html}
+Lower cardinality
+```
+``` xml
+
+ 1
+
+```
+
+### Nil reason {#iso19110-elem-gco-nilReason-59d9c7937eb12ff82e61921ee335d062}
+
+Name
+
+:
+
+> gco:nilReason
+
+Description
+
+:
+
+### Range {#iso19110-elem-gco-range-6709132eada2bd317e3ad342849df5ef}
+
+Name
+
+:
+
+> gco:range
+
+Description
+
+:
+
+``` xml
+
+
+
+ 1
+
+
+ 1
+
+
+
+
+```
+
+### Upper cardinality {#iso19110-elem-gco-upper-a58d7645455b8f20c0d2608c5bc1b6ab}
+
+Name
+
+:
+
+> gco:upper
+
+Description
+
+:
+
+```{=html}
+Upper cardinality
+```
+``` xml
+
+ 1
+
+
+```
+
+### Affects value of {#iso19110-elem-gfc-affectsValueOf-3cc26e7cd38219c7bb06fbe8e5438598}
+
+Name
+
+:
+
+> gfc:affectsValueOf
+
+Description
+
+:
+
+### Aliases {#iso19110-elem-gfc-aliases-7ec87797f5b619c461f2acf995b56b2e}
+
+Name
+
+:
+
+> gfc:aliases
+
+Description
+
+:
+
+### Cardinalities {#iso19110-elem-gfc-cardinality-36c218fd045f824ca4f9d1ceb6ffbcc2}
+
+Name
+
+:
+
+> gfc:cardinality
+
+Description
+
+:
+
+```{=html}
+Cardinalities
+```
+``` xml
+
+
+
+
+
+ 1
+
+
+ 1
+
+
+
+
+
+
+```
+
+### Elements {#iso19110-elem-gfc-carrierOfCharacteristics-c804ac9130fc47e8753b8d2e3776840b}
+
+Name
+
+:
+
+> gfc:carrierOfCharacteristics
+
+Description
+
+:
+
+```{=html}
+Association, attribute, operation, ...
+```
+``` xml
+
+
+
+ VALUE
+
+
+
+
+
+
+
+
+
+ 1
+
+
+ 1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Low coasts
+
+
+ 1
+
+
+ Areas within 10km from the coastline and with an elevation
+ below 50m.
+
+
+
+
+
+
+
+ High coasts
+
+
+ 2
+
+
+ Areas within 10km from the coastline and with an elevation
+ above 50m.
+
+
+
+
+
+
+
+ Inlands
+
+
+ 3
+
+
+ Areas between 0 and 200 m outside the coastal strip.
+
+
+
+
+
+
+
+ Uplands
+
+
+ 4
+
+
+ Zones between 200 and 500 m plus the flat areas between 500 and
+ 1000m.
+
+
+
+
+
+
+
+ Mountains
+
+
+ 5
+
+
+ Slopy areas between 500 and 1000m and all the areas over
+ 1000m.
+
+
+
+
+
+
+
+ INTEGER
+
+
+
+
+
+```
+
+### Code {#iso19110-elem-gfc-code-c62e74de82d004d4ec09d403e4b59c3b}
+
+Name
+
+:
+
+> gfc:code
+
+Description
+
+:
+
+### Constrained by {#iso19110-elem-gfc-constrainedBy-5e5ace57efe55c1890bec294427a780a}
+
+Name
+
+:
+
+> gfc:constrainedBy
+
+Description
+
+:
+
+### Definition {#iso19110-elem-gfc-definition-4bc2a8f5046951fa9e77311ef6d927f2}
+
+Name
+
+:
+
+> gfc:definition
+
+Description
+
+:
+
+```{=html}
+Property definition
+```
+### Definition reference {#iso19110-elem-gfc-definitionReference-30806ed7d5bf82b19c877082a919216e}
+
+Name
+
+:
+
+> gfc:definitionReference
+
+Description
+
+:
+
+### Definition source {#iso19110-elem-gfc-definitionSource-7f9ab04b040daf81d7d761ea83101e88}
+
+Name
+
+:
+
+> gfc:definitionSource
+
+Description
+
+:
+
+### Description {#iso19110-elem-gfc-description-87db9aea10cf7281b199782a15b17015}
+
+Name
+
+:
+
+> gfc:description
+
+Description
+
+:
+
+### Association role {#iso19110-elem-gfc-FC_AssociationRole-48c91ffbc9251a3377010490882da453}
+
+Name
+
+:
+
+> gfc:FC_AssociationRole
+
+Description
+
+:
+
+### Constraint {#iso19110-elem-gfc-FC_Constraint-8b0503c998a5c3cfd079077286bcc18c}
+
+Name
+
+:
+
+> gfc:FC_Constraint
+
+Description
+
+:
+
+### Feature association {#iso19110-elem-gfc-FC_FeatureAssociation-7bfc562c6ffccb3dd540692bd8c0fda7}
+
+Name
+
+:
+
+> gfc:FC_FeatureAssociation
+
+Description
+
+:
+
+### Attribute {#iso19110-elem-gfc-FC_FeatureAttribute-f3f350a00639f88ab53dd23d5ad5724e}
+
+Name
+
+:
+
+> gfc:FC_FeatureAttribute
+
+Description
+
+:
+
+``` xml
+
+
+ VALUE
+
+
+
+
+
+
+
+
+
+ 1
+
+
+ 1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Low coasts
+
+
+ 1
+
+
+ Areas within 10km from the coastline and with an elevation
+ below 50m.
+
+
+
+
+
+
+
+ High coasts
+
+
+ 2
+
+
+ Areas within 10km from the coastline and with an elevation
+ above 50m.
+
+
+
+
+
+
+
+ Inlands
+
+
+ 3
+
+
+ Areas between 0 and 200 m outside the coastal strip.
+
+
+
+
+
+
+
+ Uplands
+
+
+ 4
+
+
+ Zones between 200 and 500 m plus the flat areas between 500 and
+ 1000m.
+
+
+
+
+
+
+
+ Mountains
+
+
+ 5
+
+
+ Slopy areas between 500 and 1000m and all the areas over
+ 1000m.
+
+
+
+
+
+
+
+ INTEGER
+
+
+
+
+```
+
+### Feature Catalogue description {#iso19110-elem-gfc-FC_FeatureCatalogue-a4de444fdd9a6e86e8ba63bb96be363c}
+
+Name
+
+:
+
+> gfc:FC_FeatureCatalogue
+
+Description
+
+:
+
+``` xml
+
+
+ Elevation breakdown feature catalogue
+
+
+ Dataset elevation breakdown (raster 1 km)
+
+
+ 1.0
+
+
+ 2012-11-05T10:56:11
+
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ mauro.michielon@eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Elevation breakdown
+
+
+ The Elevation breakdown is used to allocate Land cover changes into
+ homogeneous areas as function of height, slope and distance to the sea.
+
+
+
+ false
+
+
+
+
+
+ VALUE
+
+
+
+
+
+
+
+
+
+ 1
+
+
+ 1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Low coasts
+
+
+ 1
+
+
+ Areas within 10km from the coastline and with an elevation
+ below 50m.
+
+
+
+
+
+
+
+ High coasts
+
+
+ 2
+
+
+ Areas within 10km from the coastline and with an elevation
+ above 50m.
+
+
+
+
+
+
+
+ Inlands
+
+
+ 3
+
+
+ Areas between 0 and 200 m outside the coastal strip.
+
+
+
+
+
+
+
+ Uplands
+
+
+ 4
+
+
+ Zones between 200 and 500 m plus the flat areas between 500 and
+ 1000m.
+
+
+
+
+
+
+
+ Mountains
+
+
+ 5
+
+
+ Slopy areas between 500 and 1000m and all the areas over
+ 1000m.
+
+
+
+
+
+
+
+ INTEGER
+
+
+
+
+
+
+
+
+```
+
+### Feature operation {#iso19110-elem-gfc-FC_FeatureOperation-637b82bc0e9951563005e479a9e1d152}
+
+Name
+
+:
+
+> gfc:FC_FeatureOperation
+
+Description
+
+:
+
+### Attribute table description {#iso19110-elem-gfc-FC_FeatureType-38ad06d5e87d9bf33d5f111e7bca0eb4}
+
+Name
+
+:
+
+> gfc:FC_FeatureType
+
+Description
+
+:
+
+```{=html}
+Attribute table description
+```
+``` xml
+
+
+ Elevation breakdown
+
+
+ The Elevation breakdown is used to allocate Land cover changes into
+ homogeneous areas as function of height, slope and distance to the sea.
+
+
+
+ false
+
+
+
+
+
+ VALUE
+
+
+
+
+
+
+
+
+
+ 1
+
+
+ 1
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Low coasts
+
+
+ 1
+
+
+ Areas within 10km from the coastline and with an elevation
+ below 50m.
+
+
+
+
+
+
+
+ High coasts
+
+
+ 2
+
+
+ Areas within 10km from the coastline and with an elevation
+ above 50m.
+
+
+
+
+
+
+
+ Inlands
+
+
+ 3
+
+
+ Areas between 0 and 200 m outside the coastal strip.
+
+
+
+
+
+
+
+ Uplands
+
+
+ 4
+
+
+ Zones between 200 and 500 m plus the flat areas between 500 and
+ 1000m.
+
+
+
+
+
+
+
+ Mountains
+
+
+ 5
+
+
+ Slopy areas between 500 and 1000m and all the areas over
+ 1000m.
+
+
+
+
+
+
+
+ INTEGER
+
+
+
+
+
+
+```
+
+### Heritance relation {#iso19110-elem-gfc-FC_InheritanceRelation-fe8bfb4f25b16151bf7dc241c0bb800c}
+
+Name
+
+:
+
+> gfc:FC_InheritanceRelation
+
+Description
+
+:
+
+### Codelist {#iso19110-elem-gfc-FC_ListedValue-281cee06b2347acc7c485783eb4cf22f}
+
+Name
+
+:
+
+> gfc:FC_ListedValue
+
+Description
+
+:
+
+### Role type {#iso19110-elem-gfc-FC_RoleType-8f835d500036f8c773643298ee9a1287}
+
+Name
+
+:
+
+> gfc:FC_RoleType
+
+Description
+
+:
+
+### Feature catalogue {#iso19110-elem-gfc-featureCatalogue-747a0827bf295f6d27168cd2b274929b}
+
+Name
+
+:
+
+> gfc:featureCatalogue
+
+Description
+
+:
+
+``` xml
+
+```
+
+### Property description {#iso19110-elem-gfc-featureType-d6099a684b15337451388dd46048c48f}
+
+Name
+
+:
+
+> gfc:featureType
+
+Description
+
+:
+
+```{=html}
+Property description
+```
+### Field of application {#iso19110-elem-gfc-fieldOfApplication-548e0631e3ea92f7dd05ac533b6c14d2}
+
+Name
+
+:
+
+> gfc:fieldOfApplication
+
+Description
+
+:
+
+```{=html}
+Field of application
+```
+### Formal definition {#iso19110-elem-gfc-formalDefinition-61fbbceaf2b0eca25754ba29528ac201}
+
+Name
+
+:
+
+> gfc:formalDefinition
+
+Description
+
+:
+
+### Functional language {#iso19110-elem-gfc-functionalLanguage-7a21d9c35ed9c400c40959ede97b8d76}
+
+Name
+
+:
+
+> gfc:functionalLanguage
+
+Description
+
+:
+
+### Inherits from {#iso19110-elem-gfc-inheritsFrom-d48c2429ef37a9f7001c4c78b3185ad8}
+
+Name
+
+:
+
+> gfc:inheritsFrom
+
+Description
+
+:
+
+### Inherits to {#iso19110-elem-gfc-inheritsTo-21e907a9a6f03374cf39958e940d6c04}
+
+Name
+
+:
+
+> gfc:inheritsTo
+
+Description
+
+:
+
+### Abstract {#iso19110-elem-gfc-isAbstract-108adb5fd93bc80097796cf3e185145e}
+
+Name
+
+:
+
+> gfc:isAbstract
+
+Description
+
+:
+
+```{=html}
+Is this element an abstract element ?
+```
+``` xml
+
+ false
+
+```
+
+### Is navigable {#iso19110-elem-gfc-isNavigable-ee77efa13eb047461f3d1b10eb057ad2}
+
+Name
+
+:
+
+> gfc:isNavigable
+
+Description
+
+:
+
+### Is ordered {#iso19110-elem-gfc-isOrdered-99dd774d6527b2e2a6714029b3d85562}
+
+Name
+
+:
+
+> gfc:isOrdered
+
+Description
+
+:
+
+### Label {#iso19110-elem-gfc-label-f039ffb9cb376d0473d7be6326b20fd7}
+
+Name
+
+:
+
+> gfc:label
+
+Description
+
+:
+
+### Codelist {#iso19110-elem-gfc-listedValue-10921452105d681cb7bcb8c2851416f9}
+
+Name
+
+:
+
+> gfc:listedValue
+
+Description
+
+:
+
+```{=html}
+List of values for this element.
+```
+### Member name {#iso19110-elem-gfc-memberName-3bd14590c8d90557f5d48e886a3ebef7}
+
+Name
+
+:
+
+> gfc:memberName
+
+Description
+
+:
+
+``` xml
+
+ VALUE
+
+```
+
+### Name {#iso19110-elem-gfc-name-134285dc9b9a3268556039e2fe3f370e}
+
+Name
+
+:
+
+> gfc:name
+
+Description
+
+:
+
+```{=html}
+Feature catalogue name
+```
+``` xml
+
+ Elevation breakdown feature catalogue
+
+```
+
+### Observes value of {#iso19110-elem-gfc-observesValueOf-b236ed68892a516373f72b89b397cde4}
+
+Name
+
+:
+
+> gfc:observesValueOf
+
+Description
+
+:
+
+### Catalogue producer {#iso19110-elem-gfc-producer-5a13bfab8b07441bc9f9f71dcfdf7f6c}
+
+Name
+
+:
+
+> gfc:producer
+
+Description
+
+:
+
+```{=html}
+Catalogue responsible
+```
+``` xml
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ mauro.michielon@eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+```
+
+### Relation {#iso19110-elem-gfc-relation-aacba568eb3b35bd7b8432488f11bf69}
+
+Name
+
+:
+
+> gfc:relation
+
+Description
+
+:
+
+### Role name {#iso19110-elem-gfc-roleName-75ef0d862fac206908f78b9ecd526c65}
+
+Name
+
+:
+
+> gfc:roleName
+
+Description
+
+:
+
+### Role type {#iso19110-elem-gfc-roleType-e11e8dd83ce112d38151e4c5d41f5e57}
+
+Name
+
+:
+
+> gfc:roleType
+
+Description
+
+:
+
+### Scope {#iso19110-elem-gfc-scope-4f044fce55b8e0b6dd0d77516ad9e66d}
+
+Name
+
+:
+
+> gfc:scope
+
+Description
+
+:
+
+```{=html}
+Scope definition
+```
+``` xml
+
+ Dataset elevation breakdown (raster 1 km)
+
+```
+
+### Signature {#iso19110-elem-gfc-signature-a322fc9fc498999771ea25d75eeadb92}
+
+Name
+
+:
+
+> gfc:signature
+
+Description
+
+:
+
+### Triggered by value of {#iso19110-elem-gfc-triggeredByValueOf-f9c78e57b38ecbf17a07eae27ddceb25}
+
+Name
+
+:
+
+> gfc:triggeredByValueOf
+
+Description
+
+:
+
+### Type {#iso19110-elem-gfc-type-8d417215d65176688a81728103dee9d4}
+
+Name
+
+:
+
+> gfc:type
+
+Description
+
+:
+
+### Property name {#iso19110-elem-gfc-typeName-5eb6a83793b5f1865c0a10bc6d3cb399}
+
+Name
+
+:
+
+> gfc:typeName
+
+Description
+
+:
+
+``` xml
+
+ Elevation breakdown
+
+```
+
+### Unique instance {#iso19110-elem-gfc-uniqueInstance-b0b6a49f0189dc2499564de5cdfd25a0}
+
+Name
+
+:
+
+> gfc:uniqueInstance
+
+Description
+
+:
+
+### Value measurement unit {#iso19110-elem-gfc-valueMeasurementUnit-3722d826b1a00b71bfae6cd7eefff3cd}
+
+Name
+
+:
+
+> gfc:valueMeasurementUnit
+
+Description
+
+:
+
+``` xml
+
+
+
+
+
+
+```
+
+### Value type {#iso19110-elem-gfc-valueType-faeb30b744a5e7aa19f43cb83bf2a9ab}
+
+Name
+
+:
+
+> gfc:valueType
+
+Description
+
+:
+
+``` xml
+
+
+
+ INTEGER
+
+
+
+```
+
+### Date {#iso19110-elem-gfc-versionDate-536720beffcbb11d9da8bd041ad7a762}
+
+Name
+
+:
+
+> gfc:versionDate
+
+Description
+
+:
+
+```{=html}
+Catalogue date
+```
+``` xml
+
+ 2012-11-05T10:56:11
+
+```
+
+### Version {#iso19110-elem-gfc-versionNumber-d66ec9fd5c22c70a69dd2b759d66cc4f}
+
+Name
+
+:
+
+> gfc:versionNumber
+
+Description
+
+:
+
+```{=html}
+Catalogue version
+```
+``` xml
+
+ 1.0
+
+```
+
+### Responsible party {#iso19110-elem-gmd-CI_ResponsibleParty-f8269ab6464cabb0bc5d4b5d8e2d410c}
+
+Name
+
+:
+
+> gmd:CI_ResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Responsible party
+```
+``` xml
+
+
+ European Environment Agency
+
+
+
+
+
+
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ mauro.michielon@eea.europa.eu
+
+
+
+
+
+
+
+
+
+```
+
+### Responsible party {#iso19110-elem-gmd-responsibleParty-7352aaa3187b52425f19d3f567e8b88a}
+
+Name
+
+:
+
+> gmd:responsibleParty
+
+Description
+
+:
+
+```{=html}
+Responsible party
+```
+### Anchor {#iso19110-elem-gmx-Anchor-4e506485badff59411e1cb2c1f5031e3}
+
+Name
+
+:
+
+> gmx:Anchor
+
+Description
+
+:
+
+### Field of application {#iso19110-elem-gmx-fieldOfApplication-66508d1f139317e01e1decd095915428}
+
+Name
+
+:
+
+> gmx:fieldOfApplication
+
+Description
+
+:
+
+```{=html}
+Field of application
+```
+### File name {#iso19110-elem-gmx-FileName-2a19fe714b24f0a417598321882eef7f}
+
+Name
+
+:
+
+> gmx:FileName
+
+Description
+
+:
+
+### Name {#iso19110-elem-gmx-name-5ec0c4442ad2b94944636103e556d401}
+
+Name
+
+:
+
+> gmx:name
+
+Description
+
+:
+
+```{=html}
+Feature catalogue name
+```
+### Scope {#iso19110-elem-gmx-scope-14efac6982297b09ba1324e80138092f}
+
+Name
+
+:
+
+> gmx:scope
+
+Description
+
+:
+
+```{=html}
+Scope definition
+```
+### Date {#iso19110-elem-gmx-versionDate-6c27e2ee0b2daa4ab1aea9ef374bc08f}
+
+Name
+
+:
+
+> gmx:versionDate
+
+Description
+
+:
+
+```{=html}
+Catalogue date
+```
+### Version {#iso19110-elem-gmx-versionNumber-075201f18225aec432b46c75a93589a2}
+
+Name
+
+:
+
+> gmx:versionNumber
+
+Description
+
+:
+
+```{=html}
+Catalogue version
+```
+## Standard codelists
+
+List of all codelists available in the standard.
+
+### Standard codelists (gmd:CI_RoleCode) {#iso19110-cl-gmd-CI_RoleCode}
+
+| code | label | description |
+|-----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| resourceProvider | Resource provider | Party that supplies the resource |
+| custodian | Custodian | Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource |
+| owner | Owner | Party that owns the resource |
+| user | User | Party who uses the resource |
+| distributor | Distributor | Party who distributes the resource |
+| originator | Originator | Party who created the resource |
+| pointOfContact | Point of contact | Party who can be contacted for acquiring knowledge about or acquisition of the resource |
+| principalInvestigator | Principal investigator | Key party responsible for gathering information and conducting research |
+| processor | Processor | Party that has processed the data in a manner such that the resource has been modified |
+| publisher | Publisher | Party who published the resource |
+| author | Author | Party who authored the resource |
diff --git a/docs/manual/docs/annexes/standards/iso19115-3.2018.md b/docs/manual/docs/annexes/standards/iso19115-3.2018.md
new file mode 100644
index 00000000000..baaabc077f1
--- /dev/null
+++ b/docs/manual/docs/annexes/standards/iso19115-3.2018.md
@@ -0,0 +1,20114 @@
+# Geographic information -- Metadata (iso19115-3.2018) {#iso19115-3.2018}
+
+The objective of ISO 19115 is to provide a model for describing information or resources that can have geographic extents. This part of ISO 19115 is intended to be used by information system analysts, program planners, and developers of information systems, as well as others in order to define basic principles and requirements for standardized description of information resources. This part of ISO 19115 defines metadata elements, their properties, and the relationships between elements, and establishes a common set of metadata terminology, definitions, and extension procedures.
+
+Although the primary purpose of this part of ISO 19115 is to describe digital information that has a geographic extent, it can be used to describe all types of resources including textual documents, initiatives, software, sensors, non-geographic information, product specifications and repositories, i.e. it can be used to describe information resources that do not have geographic extent. Some domains have their own metadata standards, such as the Dublin Core for libraries. If necessary such standards and this part of ISO 19115 could be profiled to create a Community Schema.
+
+This schema also includes:
+
+- Describe imagery data (covered by ISO19115-2)
+- Embed data model (feature catalogue) in the dataset record (covered by ISO19110)
+- Data quality described using ISO19157
+
+More information:
+
+- [Using the latest ISO Standard for Geographic Information (ISO19115-1) for an INSPIRE Discovery Service](https://www.iso.org/standard/53798.html)
+
+This standard is maintained on and is available by default in GeoNetwork. The TC211 is maintaining the XSD for this standard on .
+
+Example of catalogues using this standard:
+
+- [Metawal - Catalogue pour l'information géographique de Wallonie](https://metawal.wallonie.be/) is using ISO19115-3 as the default standard for all records. Main advantages are: categorizations of related documents (eg. online sources, DQ reports, GIS styles, Data models), better description of organization / parties and roles, remain compliant to the INSPIRE directive by converting to ISO19139 through CSW.
+
+
+
+- [Sextant - Checkpoints](https://sextant.ifremer.fr/) is using ISO19115-3 for data quality description of Specification / Products and upstream data.
+
+
+
+More details:
+
+## Metadata editor
+
+This standard can be encoded using 3 view(s).
+
+- `iso19115-3.2018-view-default`{.interpreted-text role="ref"}
+- `iso19115-3.2018-view-advanced`{.interpreted-text role="ref"}
+- `iso19115-3.2018-view-xml`{.interpreted-text role="ref"}
+
+### View: Simple (default) {#iso19115-3.2018-view-default}
+
+This view is composed of1tab(s).
+
+- `iso19115-3.2018-tab-default`{.interpreted-text role="ref"}
+
+This view also allows to add the following element even if not in the current record:
+
+- Descriptive keywords (mri:descriptiveKeywords)
+- Processor (mrl:processor)
+- Cited responsible party (cit:citedResponsibleParty)
+- Point of contact (mri:pointOfContact)
+- Contact (mdb:contact)
+- (mcc:processor)
+- Elements (gfc:carrierOfCharacteristics)
+- Party (cit:party)
+- Individual (cit:CI_Individual)
+- Organisation (cit:CI_Organisation)
+- Codelist (gfc:listedValue)
+
+#### Tab: Simple (default) {#iso19115-3.2018-tab-default}
+
+This tab display elements from the XML metadata record.
+
+##### Section: Identification info
+
+```{=html}
+Basic information about the resource(s) to which the metadata applies
+```
+See `iso19115-3.2018-elem-mdb-identificationInfo-7b3f7b7fbb8a986c92658058fe54f876`{.interpreted-text role="ref"}
+
+##### Section: Content Information
+
+```{=html}
+Provides information about the feature catalogue and describes the coverage and image data characteristics
+```
+See `iso19115-3.2018-elem-mdb-contentInfo-477f3b1af76890ee3158c66524002fd8`{.interpreted-text role="ref"}
+
+##### Section: Distribution Information
+
+```{=html}
+Provides information about the distributor of and options for obtaining the resource(s)
+```
+See `iso19115-3.2018-elem-mdb-distributionInfo-26e7e205c5605edb7225b0aa5c3950f1`{.interpreted-text role="ref"}
+
+##### Section: Data quality info
+
+```{=html}
+Provides overall assessment of quality of a resource(s)
+```
+See `iso19115-3.2018-elem-mdb-dataQualityInfo-05c1cd27fb52b7bc5c361a03fb962e72`{.interpreted-text role="ref"}
+
+##### Section: Resource lineage
+
+```{=html}
+Information about the provenance, source(s), and/or the production process(es) applied to the resource
+```
+See `iso19115-3.2018-elem-mdb-resourceLineage-b38f8fe2e0d2dee771b11f2dfcb77937`{.interpreted-text role="ref"}
+
+##### Section: Spatial representation info
+
+```{=html}
+Digital representation of spatial information in the dataset
+```
+See `iso19115-3.2018-elem-mdb-spatialRepresentationInfo-fa98674c3f9afa7324634c07cda62b3b`{.interpreted-text role="ref"}
+
+##### Section: Reference System Information
+
+```{=html}
+Description of the spatial and temporal reference systems used in the dataset
+```
+See `iso19115-3.2018-elem-mdb-referenceSystemInfo-6e40de8cf9dbe75d0601aedf78756344`{.interpreted-text role="ref"}
+
+##### Section: Acquisition information
+
+See `iso19115-3.2018-elem-mdb-acquisitionInformation-ce87174a305975fd6ab50c76fa062e87`{.interpreted-text role="ref"}
+
+##### Section: Portrayal catalogue info
+
+```{=html}
+Provides information about the catalogue of rules defined for the portrayal of a resource(s)
+```
+See `iso19115-3.2018-elem-mdb-portrayalCatalogueInfo-f6c73fdd3d7c18f1e90d4a8853986230`{.interpreted-text role="ref"}
+
+##### Section: Metadata constraints
+
+```{=html}
+Provides restrictions on the access and use of metadata
+```
+See `iso19115-3.2018-elem-mdb-metadataConstraints-cd13aab243e8cf8b0009f3c2cc6288a6`{.interpreted-text role="ref"}
+
+##### Section: Metadata maintenance
+
+```{=html}
+Provides information about the frequency of metadata updates, and the scope of those updates
+```
+See `iso19115-3.2018-elem-mdb-metadataMaintenance-f31a9a9880a6a939b8125c2505a04439`{.interpreted-text role="ref"}
+
+##### Section: Application schema info
+
+```{=html}
+Provides information about the conceptual schema of a dataset
+```
+See `iso19115-3.2018-elem-mdb-applicationSchemaInfo-6e29d5e06caa68d593c2abc867db859e`{.interpreted-text role="ref"}
+
+##### Section: Metadata
+
+##### Metadata identifier
+
+```{=html}
+Unique identifier for this metadata file
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataIdentifier
+
+See `iso19115-3.2018-elem-mdb-metadataIdentifier-a4b2a53a6ba91300cd824aaa32dced12`{.interpreted-text role="ref"}
+
+##### Default locale
+
+```{=html}
+Language and character set used for documenting metadata
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:defaultLocale
+
+See `iso19115-3.2018-elem-mdb-defaultLocale-dd848d0de1837131c70510c4ab1253b4`{.interpreted-text role="ref"}
+
+##### Other locale
+
+```{=html}
+Provides information about alternatively used localised character strings
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:otherLocale
+
+See `iso19115-3.2018-elem-mdb-otherLocale-f4f26265136a3b0812c2ce9d90c0c17f`{.interpreted-text role="ref"}
+
+##### Contact
+
+```{=html}
+Party responsible for the metadata information
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:contact
+
+See `iso19115-3.2018-elem-mdb-contact-bd86ee4331a33e4a09966e9d3837b346`{.interpreted-text role="ref"}
+
+##### Parent metadata
+
+```{=html}
+Identification of the parent metadata record
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:parentMetadata
+
+See `iso19115-3.2018-elem-mdb-parentMetadata-d82be96796ed0eaaa63a697cfec1287a`{.interpreted-text role="ref"}
+
+##### Type of resource
+
+```{=html}
+Type of resource for which metadata is provided
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataScope
+
+See `iso19115-3.2018-elem-mdb-metadataScope-85ce83354003a98ad94f8f749af858f7`{.interpreted-text role="ref"}
+
+##### Alternative metadata reference
+
+```{=html}
+Reference to alternative metadata, e.g Dublin Core, FGDC, or metadata in a non-ISO standard for the same resource
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:alternativeMetadataReference
+
+See `iso19115-3.2018-elem-mdb-alternativeMetadataReference-d658e4e78b4bb85f325070dac38656f2`{.interpreted-text role="ref"}
+
+##### Metadata linkage
+
+```{=html}
+Online location where the metadata is available
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataLinkage
+
+See `iso19115-3.2018-elem-mdb-metadataLinkage-582ff009f1d12392ca0be7e310ace58b`{.interpreted-text role="ref"}
+
+##### Date info
+
+```{=html}
+Date(s) associated with the metadata. NOTE Creation” date must be provided, others can also be provided
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:dateInfo
+
+See `iso19115-3.2018-elem-mdb-dateInfo-74b8e273fbd6b264ff0c70ca542b6fa3`{.interpreted-text role="ref"}
+
+##### Metadata standard
+
+```{=html}
+Citation for the standard to which the metadata conforms. NOTE Metadata standard citations should include an identifier.
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataStandard
+
+See `iso19115-3.2018-elem-mdb-metadataStandard-317906f5ed0893d367c6a78ab2d68812`{.interpreted-text role="ref"}
+
+##### Metadata profile
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataProfile
+
+See `iso19115-3.2018-elem-mdb-metadataProfile-92627fbcc80493116a75b90146bcf055`{.interpreted-text role="ref"}
+
+### View: Full (advanced) {#iso19115-3.2018-view-advanced}
+
+This view is composed of13tab(s).
+
+- `iso19115-3.2018-tab-identificationInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-contentInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-distributionInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-dataQualityInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-resourceLineage`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-spatialRepresentationInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-referenceSystemInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-acquisitionInformation`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-metadata`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-portrayalCatalogueInfo`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-metadataConstraints`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-metadataMaintenance`{.interpreted-text role="ref"}
+- `iso19115-3.2018-tab-applicationSchemaInfo`{.interpreted-text role="ref"}
+
+#### Tab: Identification (identificationInfo) {#iso19115-3.2018-tab-identificationInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Identification info
+
+```{=html}
+Basic information about the resource(s) to which the metadata applies
+```
+See `iso19115-3.2018-elem-mdb-identificationInfo-7b3f7b7fbb8a986c92658058fe54f876`{.interpreted-text role="ref"}
+
+#### Tab: Content (contentInfo) {#iso19115-3.2018-tab-contentInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Content Information
+
+```{=html}
+Provides information about the feature catalogue and describes the coverage and image data characteristics
+```
+See `iso19115-3.2018-elem-mdb-contentInfo-477f3b1af76890ee3158c66524002fd8`{.interpreted-text role="ref"}
+
+#### Tab: Distribution (distributionInfo) {#iso19115-3.2018-tab-distributionInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Distribution Information
+
+```{=html}
+Provides information about the distributor of and options for obtaining the resource(s)
+```
+See `iso19115-3.2018-elem-mdb-distributionInfo-26e7e205c5605edb7225b0aa5c3950f1`{.interpreted-text role="ref"}
+
+#### Tab: Quality (dataQualityInfo) {#iso19115-3.2018-tab-dataQualityInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Data quality info
+
+```{=html}
+Provides overall assessment of quality of a resource(s)
+```
+See `iso19115-3.2018-elem-mdb-dataQualityInfo-05c1cd27fb52b7bc5c361a03fb962e72`{.interpreted-text role="ref"}
+
+#### Tab: Lineage (resourceLineage) {#iso19115-3.2018-tab-resourceLineage}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Resource lineage
+
+```{=html}
+Information about the provenance, source(s), and/or the production process(es) applied to the resource
+```
+See `iso19115-3.2018-elem-mdb-resourceLineage-b38f8fe2e0d2dee771b11f2dfcb77937`{.interpreted-text role="ref"}
+
+#### Tab: Spatial rep. (spatialRepresentationInfo) {#iso19115-3.2018-tab-spatialRepresentationInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Spatial representation info
+
+```{=html}
+Digital representation of spatial information in the dataset
+```
+See `iso19115-3.2018-elem-mdb-spatialRepresentationInfo-fa98674c3f9afa7324634c07cda62b3b`{.interpreted-text role="ref"}
+
+#### Tab: Ref. system (referenceSystemInfo) {#iso19115-3.2018-tab-referenceSystemInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Reference System Information
+
+```{=html}
+Description of the spatial and temporal reference systems used in the dataset
+```
+See `iso19115-3.2018-elem-mdb-referenceSystemInfo-6e40de8cf9dbe75d0601aedf78756344`{.interpreted-text role="ref"}
+
+#### Tab: Acquisition info (acquisitionInformation) {#iso19115-3.2018-tab-acquisitionInformation}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Acquisition information
+
+See `iso19115-3.2018-elem-mdb-acquisitionInformation-ce87174a305975fd6ab50c76fa062e87`{.interpreted-text role="ref"}
+
+#### Tab: Metadata (metadata) {#iso19115-3.2018-tab-metadata}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata
+
+##### Metadata identifier
+
+```{=html}
+Unique identifier for this metadata file
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataIdentifier
+
+See `iso19115-3.2018-elem-mdb-metadataIdentifier-a4b2a53a6ba91300cd824aaa32dced12`{.interpreted-text role="ref"}
+
+##### Default locale
+
+```{=html}
+Language and character set used for documenting metadata
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:defaultLocale
+
+See `iso19115-3.2018-elem-mdb-defaultLocale-dd848d0de1837131c70510c4ab1253b4`{.interpreted-text role="ref"}
+
+##### Other locale
+
+```{=html}
+Provides information about alternatively used localised character strings
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:otherLocale
+
+See `iso19115-3.2018-elem-mdb-otherLocale-f4f26265136a3b0812c2ce9d90c0c17f`{.interpreted-text role="ref"}
+
+##### Contact
+
+```{=html}
+Party responsible for the metadata information
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:contact
+
+See `iso19115-3.2018-elem-mdb-contact-bd86ee4331a33e4a09966e9d3837b346`{.interpreted-text role="ref"}
+
+##### Parent metadata
+
+```{=html}
+Identification of the parent metadata record
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:parentMetadata
+
+See `iso19115-3.2018-elem-mdb-parentMetadata-d82be96796ed0eaaa63a697cfec1287a`{.interpreted-text role="ref"}
+
+##### Type of resource
+
+```{=html}
+Type of resource for which metadata is provided
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataScope
+
+See `iso19115-3.2018-elem-mdb-metadataScope-85ce83354003a98ad94f8f749af858f7`{.interpreted-text role="ref"}
+
+##### Alternative metadata reference
+
+```{=html}
+Reference to alternative metadata, e.g Dublin Core, FGDC, or metadata in a non-ISO standard for the same resource
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:alternativeMetadataReference
+
+See `iso19115-3.2018-elem-mdb-alternativeMetadataReference-d658e4e78b4bb85f325070dac38656f2`{.interpreted-text role="ref"}
+
+##### Metadata linkage
+
+```{=html}
+Online location where the metadata is available
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataLinkage
+
+See `iso19115-3.2018-elem-mdb-metadataLinkage-582ff009f1d12392ca0be7e310ace58b`{.interpreted-text role="ref"}
+
+##### Date info
+
+```{=html}
+Date(s) associated with the metadata. NOTE Creation” date must be provided, others can also be provided
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:dateInfo
+
+See `iso19115-3.2018-elem-mdb-dateInfo-74b8e273fbd6b264ff0c70ca542b6fa3`{.interpreted-text role="ref"}
+
+##### Metadata standard
+
+```{=html}
+Citation for the standard to which the metadata conforms. NOTE Metadata standard citations should include an identifier.
+```
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataStandard
+
+See `iso19115-3.2018-elem-mdb-metadataStandard-317906f5ed0893d367c6a78ab2d68812`{.interpreted-text role="ref"}
+
+##### Metadata profile
+
+XPath
+
+:
+
+> /mdb:MD_Metadata/mdb:metadataProfile
+
+See `iso19115-3.2018-elem-mdb-metadataProfile-92627fbcc80493116a75b90146bcf055`{.interpreted-text role="ref"}
+
+#### Tab: Portrayal (portrayalCatalogueInfo) {#iso19115-3.2018-tab-portrayalCatalogueInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Portrayal catalogue info
+
+```{=html}
+Provides information about the catalogue of rules defined for the portrayal of a resource(s)
+```
+See `iso19115-3.2018-elem-mdb-portrayalCatalogueInfo-f6c73fdd3d7c18f1e90d4a8853986230`{.interpreted-text role="ref"}
+
+#### Tab: Md. constraints (metadataConstraints) {#iso19115-3.2018-tab-metadataConstraints}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata constraints
+
+```{=html}
+Provides restrictions on the access and use of metadata
+```
+See `iso19115-3.2018-elem-mdb-metadataConstraints-cd13aab243e8cf8b0009f3c2cc6288a6`{.interpreted-text role="ref"}
+
+#### Tab: Md. maintenance (metadataMaintenance) {#iso19115-3.2018-tab-metadataMaintenance}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata maintenance
+
+```{=html}
+Provides information about the frequency of metadata updates, and the scope of those updates
+```
+See `iso19115-3.2018-elem-mdb-metadataMaintenance-f31a9a9880a6a939b8125c2505a04439`{.interpreted-text role="ref"}
+
+#### Tab: Schema info (applicationSchemaInfo) {#iso19115-3.2018-tab-applicationSchemaInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Application schema info
+
+```{=html}
+Provides information about the conceptual schema of a dataset
+```
+See `iso19115-3.2018-elem-mdb-applicationSchemaInfo-6e29d5e06caa68d593c2abc867db859e`{.interpreted-text role="ref"}
+
+### View: XML (xml) {#iso19115-3.2018-view-xml}
+
+This view is composed of1tab(s).
+
+- `iso19115-3.2018-tab-xml`{.interpreted-text role="ref"}
+
+#### Tab: XML (xml) {#iso19115-3.2018-tab-xml}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+## Schema technical details
+
+Standard identifier
+
+:
+
+> iso19115-3.2018
+
+Version
+
+:
+
+> 1.0
+
+Schema location
+
+:
+
+>
+
+Schema namespaces
+
+:
+
+-
+-
+-
+-
+-
+-
+-
+-
+-
+-
+-
+
+Schema detection mode
+
+:
+
+> elements (root)
+
+Schema detection elements
+
+:
+
+- cit:CI_Organisation
+- cit:CI_Responsibility
+- mcc:MD_BrowseGraphic
+- mco:MD_Constraints
+- mco:MD_LegalConstraints
+- mco:MD_SecurityConstraints
+- mdb:MD_Metadata
+- mdq:DQ_AbsoluteExternalPositionalAccuracy
+- mdq:DQ_AccuracyOfATimeMeasurement
+- mdq:DQ_CompletenessCommission
+- mdq:DQ_CompletenessOmission
+- mdq:DQ_ConceptualConsistency
+- mdq:DQ_Confidence
+- mdq:DQ_DomainConsistency
+- mdq:DQ_FormatConsistency
+- mdq:DQ_GriddedDataPositionalAccuracy
+- mdq:DQ_Homogeneity
+- mdq:DQ_NonQuantitativeAttributeCorrectness
+- mdq:DQ_QuantitativeAttributeAccuracy
+- mdq:DQ_RelativeInternalPositionalAccuracy
+- mdq:DQ_Representativity
+- mdq:DQ_TemporalConsistency
+- mdq:DQ_TemporalValidity
+- mdq:DQ_ThematicClassificationCorrectness
+- mdq:DQ_TopologicalConsistency
+- mdq:DQ_UsabilityElement
+- mrd:MD_Format
+- mrs:MD_ReferenceSystem
+
+## Standard elements
+
+List of all elements available in the standard.
+
+### Name of the calendar era {#iso19115-3.2018-elem-calendarEraName-ec7b1c5ffbce0e1b8ddb7e74376c0b6e}
+
+Name
+
+:
+
+> calendarEraName
+
+Description
+
+:
+
+### Character set {#iso19115-3.2018-elem-cat-characterSet-52f1baf6f54b3997a8466c8f0bf097be}
+
+Name
+
+:
+
+> cat:characterSet
+
+Description
+
+:
+
+### Field of application {#iso19115-3.2018-elem-cat-fieldOfApplication-5bc58fccff6401611fa893189aceaaba}
+
+Name
+
+:
+
+> cat:fieldOfApplication
+
+Description
+
+:
+
+```{=html}
+Field of application
+```
+### Language {#iso19115-3.2018-elem-cat-language-c1b6596a8773519ed974661112541469}
+
+Name
+
+:
+
+> cat:language
+
+Description
+
+:
+
+### Language (locale) {#iso19115-3.2018-elem-cat-locale-885b210b8fd2b91d64ac8933002875c0}
+
+Name
+
+:
+
+> cat:locale
+
+Description
+
+:
+
+### Name {#iso19115-3.2018-elem-cat-name-1fcd08e54b352d11b28503ec22b0f840}
+
+Name
+
+:
+
+> cat:name
+
+Description
+
+:
+
+```{=html}
+Feature catalogue name
+```
+### Scope {#iso19115-3.2018-elem-cat-scope-ab251abb91bc86162e5e3909c4ea453a}
+
+Name
+
+:
+
+> cat:scope
+
+Description
+
+:
+
+```{=html}
+Scope definition
+```
+### Date {#iso19115-3.2018-elem-cat-versionDate-87cadc81f222434772d4afbc70202647}
+
+Name
+
+:
+
+> cat:versionDate
+
+Description
+
+:
+
+```{=html}
+Catalogue date
+```
+### Version {#iso19115-3.2018-elem-cat-versionNumber-cc9ba326c564cc1cd3dfe1d5f48c56ef}
+
+Name
+
+:
+
+> cat:versionNumber
+
+Description
+
+:
+
+```{=html}
+Catalogue version
+```
+### Address {#iso19115-3.2018-elem-cit-address-CI_Contact-97d82fe84f0b58d25ab4a3bc467b682e}
+
+Name
+
+:
+
+> cit:address
+
+Context
+
+:
+
+> CI_Contact
+
+Description
+
+:
+
+```{=html}
+Physical and email address at which the organization or
+ individual may be
+ contacted
+```
+### Adresse {#iso19115-3.2018-elem-cit-address-855032095c3291ece299ab89936fbd31}
+
+Name
+
+:
+
+> cit:address
+
+Description
+
+:
+
+```{=html}
+Adresse physique et électronique à laquelle la personne ou
+ l'organisation responsable peut être contactée
+```
+```{=html}
+Adresse postale ou électronique d'un premier niveau de contact (par
+ exemple un secrétariat). Ces informations sont du type CI_Address et sont
+ gérées dans la classe du même nom.
+```
+### Administrative area {#iso19115-3.2018-elem-cit-administrativeArea-b8c4ff9a4088ccf36d86a7844f6ee578}
+
+Name
+
+:
+
+> cit:administrativeArea
+
+Description
+
+:
+
+```{=html}
+State, province of the location
+```
+### Alternate title {#iso19115-3.2018-elem-cit-alternateTitle-11081d54ab21175ab27ed26bd70f1318}
+
+Name
+
+:
+
+> cit:alternateTitle
+
+Description
+
+:
+
+```{=html}
+Short name or other language name by which the cited
+ information is known.
+ Example: "DCW" as an alternative title for "Digital Chart of the World
+```
+### Application profile {#iso19115-3.2018-elem-cit-applicationProfile-cc4b32b3780fe5ec9c452cc5cadd0991}
+
+Name
+
+:
+
+> cit:applicationProfile
+
+Description
+
+:
+
+```{=html}
+Name of an application profile that can be used with the online
+ resource
+```
+### Address {#iso19115-3.2018-elem-cit-CI_Address-5ae5f6aeaca8c394467355c580134ce5}
+
+Name
+
+:
+
+> cit:CI_Address
+
+Description
+
+:
+
+```{=html}
+Location of the responsible individual or organization
+```
+### Citation {#iso19115-3.2018-elem-cit-CI_Citation-07ef81205ee846bbc18cc8483d63b488}
+
+Name
+
+:
+
+> cit:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Standardised resource reference
+```
+### Contact {#iso19115-3.2018-elem-cit-CI_Contact-9c64730242278628f7068b237dc2e3ba}
+
+Name
+
+:
+
+> cit:CI_Contact
+
+Description
+
+:
+
+```{=html}
+Information required to enable contact with the responsible
+ person and/or
+ organization
+```
+### Date {#iso19115-3.2018-elem-cit-CI_Date-d1dcaf53cc1f919898b4cb1f2716d465}
+
+Name
+
+:
+
+> cit:CI_Date
+
+Description
+
+:
+
+```{=html}
+Reference date and event used to describe it (YYYY-MM-DD)
+```
+### Individual {#iso19115-3.2018-elem-cit-CI_Individual-f6229448aa872e50835de3e9bf949386}
+
+Name
+
+:
+
+> cit:CI_Individual
+
+Description
+
+:
+
+```{=html}
+Class of information about the party if the party is
+ an individual
+```
+### OnLine resource {#iso19115-3.2018-elem-cit-CI_OnlineResource-44959d6b329db39e0b0fc7fe8776471b}
+
+Name
+
+:
+
+> cit:CI_OnlineResource
+
+Description
+
+:
+
+```{=html}
+Information about on-line sources from which the dataset,
+ specification, or
+ community profile name and extended metadata elements can be obtained
+```
+### Organisation {#iso19115-3.2018-elem-cit-CI_Organisation-053268e94a93caf2bca99e2e34be8ecd}
+
+Name
+
+:
+
+> cit:CI_Organisation
+
+Description
+
+:
+
+```{=html}
+Class of information about the party if the party is
+ an organization
+```
+### Responsibility {#iso19115-3.2018-elem-cit-CI_Responsibility-071c0ed4ea21aca2435009ff6d74ca00}
+
+Name
+
+:
+
+> cit:CI_Responsibility
+
+Description
+
+:
+
+```{=html}
+Class of information about the party and their
+ role
+```
+### Role code {#iso19115-3.2018-elem-cit-CI_RoleCode-4d462a9e57560b8f52a159210fb7a409}
+
+Name
+
+:
+
+> cit:CI_RoleCode
+
+Description
+
+:
+
+### Standard codelists Role code (cit:CI_RoleCode)
+
+| code | label | description |
+|-----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| resourceProvider | Resource provider | Party that supplies the resource |
+| custodian | Custodian | Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource |
+| owner | Owner | Party that owns the resource |
+| user | User | Party who uses the resource |
+| distributor | Distributor | Party who distributes the resource |
+| originator | Originator | Party who created the resource |
+| pointOfContact | Point of contact | Party who can be contacted for acquiring knowledge about or acquisition of the resource |
+| principalInvestigator | Principal investigator | Key party responsible for gathering information and conducting research |
+| processor | Processor | Party that has processed the data in a manner such that the resource has been modified |
+| publisher | Publisher | Party who published the resource |
+| author | Author | Party who authored the resource |
+| sponsor | Sponsor | Party who speaks for the resource |
+| coAuthor | Co-author | Party who jointly authors the resource |
+| collaborator | Collaborator | Party who assists with the generation of the resource other than the principal investigator |
+| editor | Editor | Party who reviewed or modified the resource to improve the content |
+| mediator | Mediator | A class of entity that mediates access to the resource and for whom the resource is intended or useful |
+| rightsHolder | Rights holder | Party owning or managing rights over the resource |
+| contributor | Contributor | Party contributing to the resource |
+| funder | Funder | Party providing monetary support for the resource |
+| stakeholder | Stakeholder | Party who has an interest in the resource or the use of the resource |
+
+### Séries {#iso19115-3.2018-elem-cit-CI_Series-05997b3c9b5a88806c44ec019dd105f6}
+
+Name
+
+:
+
+> cit:CI_Series
+
+Description
+
+:
+
+```{=html}
+Class of information about the series, or aggregate
+ resource, to which a resource belongs
+```
+### Telephone {#iso19115-3.2018-elem-cit-CI_Telephone-57584ba11ae4721360c06e9f1a980082}
+
+Name
+
+:
+
+> cit:CI_Telephone
+
+Description
+
+:
+
+```{=html}
+Telephone numbers for contacting the responsible individual or
+ organization
+```
+### Cited responsible party {#iso19115-3.2018-elem-cit-citedResponsibleParty-12711cd21eb7ccd8be6d15ff06b1fecc}
+
+Name
+
+:
+
+> cit:citedResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Name and position information for an individual or organization
+ that is
+ responsible for the resource
+```
+### City {#iso19115-3.2018-elem-cit-city-64053d57bd74c4e93afb69989ee49cb4}
+
+Name
+
+:
+
+> cit:city
+
+Description
+
+:
+
+```{=html}
+City of the location
+```
+### Contact Information {#iso19115-3.2018-elem-cit-contactInfo-5c594c4932c99a4158471697d7f84f18}
+
+Name
+
+:
+
+> cit:contactInfo
+
+Description
+
+:
+
+```{=html}
+Address of the responsible party
+```
+### Contact instructions {#iso19115-3.2018-elem-cit-contactInstructions-28da1ff5a0492d67e13453f2a39ca9e2}
+
+Name
+
+:
+
+> cit:contactInstructions
+
+Description
+
+:
+
+```{=html}
+Supplemental instructions on how or when to contact the
+ individual or
+ organization
+```
+### Contact type {#iso19115-3.2018-elem-cit-contactType-20fe26a0025843f8389415944deb170c}
+
+Name
+
+:
+
+> cit:contactType
+
+Description
+
+:
+
+```{=html}
+Type of the contact
+```
+### Country {#iso19115-3.2018-elem-cit-country-8569b7d15373c7d51d73fe19899ddc47}
+
+Name
+
+:
+
+> cit:country
+
+Description
+
+:
+
+```{=html}
+Country of the physical address
+```
+### Country {#iso19115-3.2018-elem-cit-country-cit-CI_Address-2e0d29619005dfe74c7a6d24b38058f3}
+
+Name
+
+:
+
+> cit:country
+
+Context
+
+:
+
+> cit:CI_Address
+
+Description
+
+:
+
+```{=html}
+Country of the address
+```
+
+Condition
+
+:
+
+> optional
+
+### Date {#iso19115-3.2018-elem-cit-date-c960311cb0c208a0574cc6c1189e291b}
+
+Name
+
+:
+
+> cit:date
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12 (YYYY-MM-DD)
+```
+```{=html}
+reference date and event used to describe it
+```
+### Date {#iso19115-3.2018-elem-cit-date-cit-CI_Citation-f920bf44c6e3baee883e7de01175e514}
+
+Name
+
+:
+
+> cit:date
+
+Context
+
+:
+
+> cit:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Reference date for the cited resource
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date {#iso19115-3.2018-elem-cit-date-cit-CI_Date-ba0770057c4e9ec8eb2d52e7d0b2c59f}
+
+Name
+
+:
+
+> cit:date
+
+Context
+
+:
+
+> cit:CI_Date
+
+Description
+
+:
+
+```{=html}
+Reference date for the cited resource
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date type {#iso19115-3.2018-elem-cit-dateType-441176555042ce6ede97954a98eb7b83}
+
+Name
+
+:
+
+> cit:dateType
+
+Description
+
+:
+
+```{=html}
+Event used for reference date
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Delivery point {#iso19115-3.2018-elem-cit-deliveryPoint-81ad23bd0554b46cfbd1f7dfa20f81ea}
+
+Name
+
+:
+
+> cit:deliveryPoint
+
+Description
+
+:
+
+```{=html}
+Address line for the location (as described in ISO 11180, annex
+ A)
+```
+```{=html}
+Address line for the location. Example Street number
+ and name, Suite number, etc.
+```
+### Description {#iso19115-3.2018-elem-cit-description-cit-CI_OnlineResource-01ddc3b7f9794277399a2c56f4e7f0aa}
+
+Name
+
+:
+
+> cit:description
+
+Context
+
+:
+
+> cit:CI_OnlineResource
+
+Description
+
+:
+
+```{=html}
+Detailed text description of what the online resource is/does
+```
+``` xml
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+```
+
+### Edition {#iso19115-3.2018-elem-cit-edition-04e1813c8da877a03f60df27a3b69ab2}
+
+Name
+
+:
+
+> cit:edition
+
+Description
+
+:
+
+```{=html}
+Version of the cited resource
+```
+### Edition date {#iso19115-3.2018-elem-cit-editionDate-2fe8af778725aaaa1c77f6f5094c2c27}
+
+Name
+
+:
+
+> cit:editionDate
+
+Description
+
+:
+
+```{=html}
+Date of the edition (YYYY-MM-DD)
+```
+### Electronic mail address {#iso19115-3.2018-elem-cit-electronicMailAddress-8abe82c5c90b49acb18508577ddf6f95}
+
+Name
+
+:
+
+> cit:electronicMailAddress
+
+Description
+
+:
+
+```{=html}
+Address of the electronic mailbox of the responsible
+ organization or
+ individual
+```
+### Extent {#iso19115-3.2018-elem-cit-extent-cit-CI_Responsibility-cafbc635a55f5453157ec2cc54c624f8}
+
+Name
+
+:
+
+> cit:extent
+
+Context
+
+:
+
+> cit:CI_Responsibility
+
+Description
+
+:
+
+```{=html}
+Spatial or temporal extent of the role
+```
+### Function {#iso19115-3.2018-elem-cit-function-d1ccd71b112690a7ae7f187d2b1286b9}
+
+Name
+
+:
+
+> cit:function
+
+Description
+
+:
+
+```{=html}
+Code for function performed by the online resource
+```
+### Graphic {#iso19115-3.2018-elem-cit-graphic-cit-CI_Citation-a71bc47c4468f216fac662acedf06ff2}
+
+Name
+
+:
+
+> cit:graphic
+
+Context
+
+:
+
+> cit:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Citation graphic or logo for the cited resource
+```
+
+Condition
+
+:
+
+> optional
+
+### Hours of service {#iso19115-3.2018-elem-cit-hoursOfService-005f6a6884104abc1caeff5be47c98b8}
+
+Name
+
+:
+
+> cit:hoursOfService
+
+Description
+
+:
+
+```{=html}
+Time period (including time zone) when individuals can contact
+ the organization
+ or individual
+```
+### Citation identifier {#iso19115-3.2018-elem-cit-identifier-cit-CI_Citation-39034d5cd7f284b1b393efdee0580e49}
+
+Name
+
+:
+
+> cit:identifier
+
+Context
+
+:
+
+> cit:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Identifier of the citation
+```
+### Individual {#iso19115-3.2018-elem-cit-individual-55ac5c7a0365c3cc796a297e2f6bdf73}
+
+Name
+
+:
+
+> cit:individual
+
+Description
+
+:
+
+```{=html}
+An individual in the named organization
+```
+### ISBN {#iso19115-3.2018-elem-cit-ISBN-32066ff442c8b0e2dbb3b0885a94976a}
+
+Name
+
+:
+
+> cit:ISBN
+
+Description
+
+:
+
+```{=html}
+International Standard Book Number
+```
+### ISSN {#iso19115-3.2018-elem-cit-ISSN-1e3a944a9bd57fddb021ebdd8d9e882a}
+
+Name
+
+:
+
+> cit:ISSN
+
+Description
+
+:
+
+```{=html}
+International Standard Serial Number
+```
+### Issue identification {#iso19115-3.2018-elem-cit-issueIdentification-d6144f3517e8dca0a71cfcdac7907efa}
+
+Name
+
+:
+
+> cit:issueIdentification
+
+Description
+
+:
+
+```{=html}
+Information identifying the issue of the series
+```
+### Linkage {#iso19115-3.2018-elem-cit-linkage-72b815e56327f02e8c718dfc3c53955c}
+
+Name
+
+:
+
+> cit:linkage
+
+Description
+
+:
+
+```{=html}
+Location (address) for on-line access using a Uniform Resource
+ Locator address
+ or similar addressing scheme such as http://www.statkart.no/isotc211
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Logo {#iso19115-3.2018-elem-cit-logo-aafda1f3a41ecfe3fa4c4dcc6a4f4c34}
+
+Name
+
+:
+
+> cit:logo
+
+Description
+
+:
+
+```{=html}
+Graphic identifying the organization
+```
+### Name of the resource {#iso19115-3.2018-elem-cit-name-cit-CI_OnlineResource-ab7fb0a1840b8534cbf9f4b41530ae35}
+
+Name
+
+:
+
+> cit:name
+
+Context
+
+:
+
+> cit:CI_OnlineResource
+
+Description
+
+:
+
+```{=html}
+Name of the online resource
+```
+### Name {#iso19115-3.2018-elem-cit-name-cit-CI_Series-0266f984b84af8225a054d8f77cbf48a}
+
+Name
+
+:
+
+> cit:name
+
+Context
+
+:
+
+> cit:CI_Series
+
+Description
+
+:
+
+```{=html}
+Name of the series, or aggregate dataset, of which the dataset
+ is a
+ part
+```
+### Organisation name {#iso19115-3.2018-elem-cit-name-cit-CI_Organisation-35d4282d04316174623d834f8a425bba}
+
+Name
+
+:
+
+> cit:name
+
+Context
+
+:
+
+> cit:CI_Organisation
+
+Description
+
+:
+
+```{=html}
+Name of the responsible organization
+```
+
+Condition
+
+:
+
+> conditional
+
+### Individual name {#iso19115-3.2018-elem-cit-name-cit-CI_Individual-652968a35c18c887fd63b5a8f0623dd8}
+
+Name
+
+:
+
+> cit:name
+
+Context
+
+:
+
+> cit:CI_Individual
+
+Description
+
+:
+
+```{=html}
+Name of the responsible person- surname, given name, title
+```
+### Name {#iso19115-3.2018-elem-cit-name-ebbdb582d68421b99463b31059d63b5a}
+
+Name
+
+:
+
+> cit:name
+
+Description
+
+:
+
+### Number {#iso19115-3.2018-elem-cit-number-be212daea0ac64953b2c7b1ef5e8c0d5}
+
+Name
+
+:
+
+> cit:number
+
+Description
+
+:
+
+```{=html}
+Telephone number by which individuals can contact
+ responsible organisation or individual
+```
+### Number type {#iso19115-3.2018-elem-cit-numberType-528a01ad72f823205c2faaeb99a60907}
+
+Name
+
+:
+
+> cit:numberType
+
+Description
+
+:
+
+```{=html}
+Type of telephone number
+```
+### Online resource {#iso19115-3.2018-elem-cit-onlineResource-cit-CI_Contact-1f4b0cbdb455e04f053de4187d716280}
+
+Name
+
+:
+
+> cit:onlineResource
+
+Context
+
+:
+
+> cit:CI_Contact
+
+Description
+
+:
+
+```{=html}
+On-line information that can be used to contact the
+ individual or organisation
+```
+### Website {#iso19115-3.2018-elem-cit-onlineResource-2ed916ad0165783c0e00cd631a2fa9e4}
+
+Name
+
+:
+
+> cit:onlineResource
+
+Description
+
+:
+
+```{=html}
+Define URL to access the website
+```
+```{=html}
+On-line information that can be used to contact the individual
+ or
+ organisation
+```
+### Other citation details {#iso19115-3.2018-elem-cit-otherCitationDetails-12cf58786723aa5bbbb5768a566120b7}
+
+Name
+
+:
+
+> cit:otherCitationDetails
+
+Description
+
+:
+
+```{=html}
+Other information required to complete the citation that is not
+ recorded
+ elsewhere
+```
+### Page {#iso19115-3.2018-elem-cit-page-8f0b8d638ea1b8990cc7a78128a246d1}
+
+Name
+
+:
+
+> cit:page
+
+Description
+
+:
+
+```{=html}
+Details on which pages of the publication the article was
+ published
+```
+### Party {#iso19115-3.2018-elem-cit-party-cit-CI_Responsibility-21218621f3c4fc5f48c55804f5a14d2e}
+
+Name
+
+:
+
+> cit:party
+
+Context
+
+:
+
+> cit:CI_Responsibility
+
+Description
+
+:
+
+```{=html}
+Information about the party
+```
+### Identifier for the party {#iso19115-3.2018-elem-cit-partyIdentifier-cd101436a544472459e8b848a2eb8e56}
+
+Name
+
+:
+
+> cit:partyIdentifier
+
+Description
+
+:
+
+### Telephone {#iso19115-3.2018-elem-cit-phone-29b2e78f752a094113d95c28083ead50}
+
+Name
+
+:
+
+> cit:phone
+
+Description
+
+:
+
+```{=html}
+Telephone numbers at which the organisation or
+ individual may be contacted
+```
+### Position name {#iso19115-3.2018-elem-cit-positionName-77a4db52c54386c39c3267bb69aad17a}
+
+Name
+
+:
+
+> cit:positionName
+
+Description
+
+:
+
+```{=html}
+Role or position of the responsible person
+```
+
+Condition
+
+:
+
+> conditional
+
+### Postal code {#iso19115-3.2018-elem-cit-postalCode-103d77a2e1d3eb6891052449be62520e}
+
+Name
+
+:
+
+> cit:postalCode
+
+Description
+
+:
+
+```{=html}
+ZIP or other postal code
+```
+### Presentation form {#iso19115-3.2018-elem-cit-presentationForm-9b37d87116e709efbd758957d7ddbb34}
+
+Name
+
+:
+
+> cit:presentationForm
+
+Description
+
+:
+
+```{=html}
+Mode in which the resource is represented
+```
+### Protocol {#iso19115-3.2018-elem-cit-protocol-56ba71e5a9e6ae87797545a296a791f2}
+
+Name
+
+:
+
+> cit:protocol
+
+Description
+
+:
+
+```{=html}
+Connection protocol to be used
+```
+Recommended values
+
+| code | label |
+|----------------------------------|------------------------------------------------|
+| OGC API - Coverages | OGC API - Coverages |
+| OGC API - Features | OGC API - Features |
+| OGC API - Maps | OGC API - Maps |
+| OGC API - Records | OGC API - Records |
+| OGC:CSW | OGC-CSW Catalogue Service for the Web |
+| OGC:KML | OGC-KML Keyhole Markup Language |
+| OGC:GML | OGC-GML Geography Markup Language |
+| OGC:ODS | OGC-ODS OpenLS Directory Service |
+| OGC:OGS | OGC-ODS OpenLS Gateway Service |
+| OGC:OUS | OGC-ODS OpenLS Utility Service |
+| OGC:OPS | OGC-ODS OpenLS Presentation Service |
+| OGC:ORS | OGC-ODS OpenLS Route Service |
+| OGC:SOS | OGC-SOS Sensor Observation Service |
+| OGC:SPS | OGC-SPS Sensor Planning Service |
+| OGC:SAS | OGC-SAS Sensor Alert Service |
+| OGC:WCS | OGC-WCS Web Coverage Service |
+| OGC:WCTS | OGC-WCTS Web Coordinate Transformation Service |
+| OGC:WFS | OGC-WFS Web Feature Service |
+| INSPIRE Atom | INSPIRE Atom |
+| OGC:WMS | OGC-WMS Web Map Service |
+| OGC:WMTS | OGC-WMS Web Map Tile Service |
+| OGC:WNS | OGC-WNS Web Notification Service |
+| OGC:WPS | OGC-WPS Web Processing Service |
+| WWW:DOWNLOAD-1.0-ftp--download | File for download through FTP |
+| WWW:DOWNLOAD-1.0-http--download | File for download |
+| ESRI:REST | ESRI REST Service |
+| ESRI:REST-TILED | ESRI REST Tiled Service |
+| | GIS file |
+| | GIS RASTER file |
+| WWW:LINK-1.0-http--link | Web address (URL) |
+| WWW:LINK-1.0-http--rss | RSS News feed (URL) |
+| DB:POSTGIS | PostGIS database table |
+| DB:ORACLE | ORACLE database table |
+| WWW:LINK-1.0-http--opendap | OPeNDAP URL |
+| RBNB:DATATURBINE | Data Turbine |
+| UKST | Unknown Service Type |
+
+``` xml
+
+ atom:feed
+
+```
+
+### Protocol request {#iso19115-3.2018-elem-cit-protocolRequest-e58550e17f9baca9aaa1dc62bec847d1}
+
+Name
+
+:
+
+> cit:protocolRequest
+
+Description
+
+:
+
+```{=html}
+Request used to access the resource depending on the protocol
+ (to be used mainly for POST requests)
+```
+### Role {#iso19115-3.2018-elem-cit-role-8e99af312ea1dbd228b50677ba6b9fd7}
+
+Name
+
+:
+
+> cit:role
+
+Description
+
+:
+
+### Role {#iso19115-3.2018-elem-cit-role-cit-CI_Responsibility-e5aa9d82909db5e5beb67eb483f8bdc4}
+
+Name
+
+:
+
+> cit:role
+
+Context
+
+:
+
+> cit:CI_Responsibility
+
+Description
+
+:
+
+```{=html}
+Function performed by the responsible party
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Role {#iso19115-3.2018-elem-cit-role-mri-MD_Association-9fb15da4e2c1795eed15ad17f6b508bb}
+
+Name
+
+:
+
+> cit:role
+
+Context
+
+:
+
+> mri:MD_Association
+
+Description
+
+:
+
+```{=html}
+Reference to the ends (roles) of a concrete association
+```
+### Series {#iso19115-3.2018-elem-cit-series-33d7a9a9d8aab2b7285884917cc0368c}
+
+Name
+
+:
+
+> cit:series
+
+Description
+
+:
+
+```{=html}
+Information about the series, or aggregate resource,
+ of which the resource is a part
+```
+### Format name {#iso19115-3.2018-elem-cit-title-/mdb-MD_Metadata/mdb-distributionInfo/mrd-MD_Distribution/mrd-distributionFormat/mrd-MD_Format/mrd-formatSpecificationCitation/cit-CI_Citation/cit-title-11140ae1a791f8912ad78af979af4a3a}
+
+Name
+
+:
+
+> cit:title
+
+Context
+
+:
+
+> /mdb:MD_Metadata/mdb:distributionInfo/mrd:MD_Distribution/mrd:distributionFormat/mrd:MD_Format/mrd:formatSpecificationCitation/cit:CI_Citation/cit:title
+
+Description
+
+:
+
+```{=html}
+Name of the data transfer format(s)
+```
+```{=html}
+File or link format name
+```
+Recommended values
+
+| code | label |
+|-----------------|-----------------|
+| Text | Text |
+| XLS | XLS |
+| ESRI Shapefile | ESRI Shapefile |
+| Mapinfo MIF/MID | Mapinfo MIF/MID |
+| Mapinfo TAB | Mapinfo TAB |
+| KML | KML |
+| GML | GML |
+| XYZ Ascii | XYZ Ascii |
+| NetCDF | NetCDF |
+| GeoTIFF | GeoTIFF |
+| TIFF | TIFF |
+| ECW | ECW |
+| JPEG2000 | JPEG2000 |
+| ZIP | ZIP |
+| PDF | PDF |
+| PNG | PNG |
+| JPEG | JPEG |
+| OGC:WMC | OGC:WMC |
+| OGC:OWS-C | OGC OWS Context |
+
+### Specification {#iso19115-3.2018-elem-cit-title-/mdb-MD_Metadata/mdb-dataQualityInfo/mdq-DQ_DataQuality/mdq-report/mdq-DQ_DomainConsistency/mdq-result/mdq-DQ_ConformanceResult/mdq-specification/cit-CI_Citation/cit-title-b03759562aa7906e72e843780b064c77}
+
+Name
+
+:
+
+> cit:title
+
+Context
+
+:
+
+> /mdb:MD_Metadata/mdb:dataQualityInfo/mdq:DQ_DataQuality/mdq:report/mdq:DQ_DomainConsistency/mdq:result/mdq:DQ_ConformanceResult/mdq:specification/cit:CI_Citation/cit:title
+
+Description
+
+:
+
+Recommended values
+
+| code | label |
+|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services | COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services |
+| INSPIRE Data Specification on Administrative Units - Guidelines v3.0.1 | Guide INSPIRE sur les unités administratives |
+| INSPIRE Data Specification on Cadastral Parcels - Guidelines v 3.0.1 | Guide INSPIRE sur les parcelles cadastrales |
+| INSPIRE Data Specification on Geographical Names - Guidelines v 3.0.1 | Guide INSPIRE sur les dénominations géographiques |
+| INSPIRE Data Specification on Hydrography - Guidelines v 3.0.1 | Guide INSPIRE sur l'hydrographie |
+| INSPIRE Data Specification on Protected Sites - Guidelines v 3.1.0 | Guide INSPIRE sur les sites protégés |
+| INSPIRE Data Specification on Transport Networks - Guidelines v 3.1.0 | Guide INSPIRE sur les réseaux de transport |
+| INSPIRE Data Specification on Addresses - Guidelines v 3.0.1 | Guide INSPIRE sur les adresses |
+| INSPIRE Specification on Coordinate Reference Systems - Guidelines v 3.1 | Guide INSPIRE sur les référentiels de coordonnées |
+| INSPIRE Specification on Geographical Grid Systems - Guidelines v 3.0.1 | Guide INSPIRE sur les systèmes de maillage géographique |
+
+Recommended values
+
+| code | label |
+|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|
+| RÈGLEMENT (UE) N° 976/2009 | Règlement service en réseau INSPIRE (service de recherche et de consultation) - RÈGLEMENT (UE) N° 976/2009 |
+| RÈGLEMENT (UE) N° 1088/2010 | Règlement service en réseau INSPIRE (service de téléchargement et de transformation) - RÈGLEMENT (UE) N° 1088/2010 |
+| Technical Guidance for the implementation of INSPIRE Discovery Services -- v.3.1 | Guide INSPIRE sur les services de recherche |
+| Technical Guidance for the implementation of INSPIRE View Services - v3.1 -- part 4 | Guide INSPIRE sur les services de consultation -- profil ISO 19128 (WMS) |
+| Technical Guidance for the implementation of INSPIRE View Services - v3.1 -- part 5 | Guide INSPIRE sur les services de consultation -- profil ISO WMTS 1.0.0 |
+| Technical Guidance for the INSPIRE Schema Transformation Network Service - v3.0 | Guide INSPIRE sur les services de transformation de schéma |
+| Technical Guidance for the implementation of INSPIRE Download Services -- level1 - v3.0 | Guide INSPIRE sur les services de téléchargement -- classe de conformité 1 (ATOM pré-défini) |
+| Technical Guidance for the implementation of INSPIRE Download Services -- level2 - v3.0 | Guide INSPIRE sur les services de téléchargement -- classe de conformité 2 (WFS pré-défini) |
+| Technical Guidance for the implementation of INSPIRE Download Services -- level3 - v3.0 | Guide INSPIRE sur les services de téléchargement -- classe de conformité 3 (WFS direct) |
+
+### Title {#iso19115-3.2018-elem-cit-title-/mdb-MD_Metadata/mdb-identificationInfo/mri-MD_DataIdentification/mri-citation/cit-CI_Citation/cit-title-5084206f0cda801f58faf7204c09b3d1}
+
+Name
+
+:
+
+> cit:title
+
+Context
+
+:
+
+> /mdb:MD_Metadata/mdb:identificationInfo/mri:MD_DataIdentification/mri:citation/cit:CI_Citation/cit:title
+
+Description
+
+:
+
+```{=html}
+Name by which the cited resource is known
+```
+### Title {#iso19115-3.2018-elem-cit-title-7dfafb62cad1555c0ee6d132f1e775fd}
+
+Name
+
+:
+
+> cit:title
+
+Description
+
+:
+
+```{=html}
+Name by which the cited resource is known
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Code {#iso19115-3.2018-elem-code-mri-MD_Identifier-67258785530ff4b1ebf28f28ce66d33b}
+
+Name
+
+:
+
+> code
+
+Context
+
+:
+
+> mri:MD_Identifier
+
+Description
+
+:
+
+```{=html}
+Alphanumeric value identifying an instance in the namespace
+```
+```{=html}
+alphanumeric value identifying an instance in the namespace
+```
+### System code {#iso19115-3.2018-elem-code-5d6344f28f37d0f73c2cb79145f5668d}
+
+Name
+
+:
+
+> code
+
+Description
+
+:
+
+```{=html}
+Code. i.e. EPSG code.
+```
+### Code {#iso19115-3.2018-elem-code-mri-MD_CodeValue-e885cdcb9c42da39e0093542b4865e30}
+
+Name
+
+:
+
+> code
+
+Context
+
+:
+
+> mri:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Value code
+```
+```{=html}
+Value code (i.e. numeric)
+```
+### Reference Authority {#iso19115-3.2018-elem-codeSpace-c90144a092543c4117eb54a71d33ac63}
+
+Name
+
+:
+
+> codeSpace
+
+Description
+
+:
+
+```{=html}
+Authority responsible for codification. i.e. EPSG
+```
+### Date et heure {#iso19115-3.2018-elem-dqc-dateTime-440241ab056365dcafe4e74d8e833374}
+
+Name
+
+:
+
+> dqc:dateTime
+
+Description
+
+:
+
+### Related element {#iso19115-3.2018-elem-dqc-relatedElement-8807300908c0949ebb1329e3e7a3eacc}
+
+Name
+
+:
+
+> dqc:relatedElement
+
+Description
+
+:
+
+### Factor {#iso19115-3.2018-elem-factor-5afe00178e76b0c48a70e7bc76d88080}
+
+Name
+
+:
+
+> factor
+
+Description
+
+:
+
+### Frame {#iso19115-3.2018-elem-frame-495bc4e6402da158707765fec6ad81e3}
+
+Name
+
+:
+
+> frame
+
+Description
+
+:
+
+```{=html}
+Frame attribute provides a URI reference that identifies a
+ description of the reference system
+```
+### Name {#iso19115-3.2018-elem-gco-aName-ec573ab870f9406d1373cd7815dbaf97}
+
+Name
+
+:
+
+> gco:aName
+
+Description
+
+:
+
+### Type name {#iso19115-3.2018-elem-gco-aName-gco-TypeName-9aedcb12c741bbbd96004346261c4dda}
+
+Name
+
+:
+
+> gco:aName
+
+Context
+
+:
+
+> gco:TypeName
+
+Description
+
+:
+
+Recommended values
+
+| code | label |
+|-----------|-----------|
+| BOOLEAN | BOOLEAN |
+| BYTE | BYTE |
+| CHARACTER | CHARACTER |
+| DATE | DATE |
+| DATETIME | DATETIME |
+| DOUBLE | DOUBLE |
+| FLOAT | FLOAT |
+| INTEGER | INTEGER |
+| NUMERIC | NUMERIC |
+| REAL | REAL |
+| SERIAL | SERIAL |
+| VARCHAR | VARCHAR |
+| TEXT | TEXT |
+
+### Angle {#iso19115-3.2018-elem-gco-Angle-7ce2d1a5c0a7c675bf50204696f97212}
+
+Name
+
+:
+
+> gco:Angle
+
+Description
+
+:
+
+```{=html}
+Angle
+```
+### Attribute type {#iso19115-3.2018-elem-gco-attributeType-8d0028999602c0fc0861c3e2cdfd3ba4}
+
+Name
+
+:
+
+> gco:attributeType
+
+Description
+
+:
+
+### Binary {#iso19115-3.2018-elem-gco-Binary-fae8ca1153637dd8df3141b8d77f0b88}
+
+Name
+
+:
+
+> gco:Binary
+
+Description
+
+:
+
+### Text {#iso19115-3.2018-elem-gco-CharacterString-b1698de198f86561c868ca9fb4242d60}
+
+Name
+
+:
+
+> gco:CharacterString
+
+Description
+
+:
+
+### Usage Date / Time {#iso19115-3.2018-elem-gco-DateTime-mri-MD_Usage-354630792f5d24d7c5134ae38f654663}
+
+Name
+
+:
+
+> gco:DateTime
+
+Context
+
+:
+
+> mri:MD_Usage
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+```{=html}
+date and time of the first use or range of uses of the resource and/or
+ resource
+ series
+```
+### Planned Available Date / Time {#iso19115-3.2018-elem-gco-DateTime-mrd-MD_StandardOrderProcess-16e3d91c2572d6377e06810858b43450}
+
+Name
+
+:
+
+> gco:DateTime
+
+Context
+
+:
+
+> mrd:MD_StandardOrderProcess
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+```{=html}
+date and time when theresource will be available
+```
+### Date and time {#iso19115-3.2018-elem-gco-DateTime-e6a33d377eb75a1ef5224b35ce0810da}
+
+Name
+
+:
+
+> gco:DateTime
+
+Description
+
+:
+
+```{=html}
+Date and time or range of date and time on or over which the
+ process step occurred
+ (YYYY-MM-DDThh:mm:ss)
+```
+### Distance {#iso19115-3.2018-elem-gco-Distance-02d18ba9c09dae7b4a4ee648ca1afd68}
+
+Name
+
+:
+
+> gco:Distance
+
+Description
+
+:
+
+```{=html}
+Distance
+```
+### Length {#iso19115-3.2018-elem-gco-Length-fc950d15ea62227f0431a5fe64f47d48}
+
+Name
+
+:
+
+> gco:Length
+
+Description
+
+:
+
+```{=html}
+Length
+```
+### Name {#iso19115-3.2018-elem-gco-localName-7c3666b9b35b4cde01f4a7c8f51c0fb9}
+
+Name
+
+:
+
+> gco:localName
+
+Description
+
+:
+
+### Local name {#iso19115-3.2018-elem-gco-LocalName-08c97bf6632239439f713537c5d5ecda}
+
+Name
+
+:
+
+> gco:LocalName
+
+Description
+
+:
+
+### Lower cardinality {#iso19115-3.2018-elem-gco-lower-aeb71a259de3a9b79e057b2587339450}
+
+Name
+
+:
+
+> gco:lower
+
+Description
+
+:
+
+```{=html}
+Lower cardinality
+```
+### Measure {#iso19115-3.2018-elem-gco-Measure-7fd8ef9f27cda91ac9513456c11a7fef}
+
+Name
+
+:
+
+> gco:Measure
+
+Description
+
+:
+
+```{=html}
+Measure
+```
+### Name of Measure {#iso19115-3.2018-elem-gco-Measure-mri-DQ_Element-9093d47a462e74a70a172237586f2f36}
+
+Name
+
+:
+
+> gco:Measure
+
+Context
+
+:
+
+> mri:DQ_Element
+
+Description
+
+:
+
+```{=html}
+Name of the test applied to the data
+```
+### Unit of Measure {#iso19115-3.2018-elem-gco-Measure-mri-EX_VerticalExtent-11f2ea0a92433742e4b068e8aa6c5e87}
+
+Name
+
+:
+
+> gco:Measure
+
+Context
+
+:
+
+> mri:EX_VerticalExtent
+
+Description
+
+:
+
+```{=html}
+Vertical units used for vertical extent information Examples:
+ metres, feet,
+ millimetres, hectopascals
+```
+### Member name {#iso19115-3.2018-elem-gco-MemberName-029e1a339fbce38a70a42b617c003ece}
+
+Name
+
+:
+
+> gco:MemberName
+
+Description
+
+:
+
+### Multiplicity {#iso19115-3.2018-elem-gco-Multiplicity-0dca80c90498a1272be725fe1b99baba}
+
+Name
+
+:
+
+> gco:Multiplicity
+
+Description
+
+:
+
+### Multiplicity range {#iso19115-3.2018-elem-gco-MultiplicityRange-5d8f76d1c4cd389c59b4d736b2301979}
+
+Name
+
+:
+
+> gco:MultiplicityRange
+
+Description
+
+:
+
+### Nil reason {#iso19115-3.2018-elem-gco-nilReason-69d908b4be9b96c2663ae9726ae2b787}
+
+Name
+
+:
+
+> gco:nilReason
+
+Description
+
+:
+
+### Range {#iso19115-3.2018-elem-gco-range-3b2d2f387c5ecf91d053fa864086b9b4}
+
+Name
+
+:
+
+> gco:range
+
+Description
+
+:
+
+### Record {#iso19115-3.2018-elem-gco-Record-c95feb94990445212e6d0234fdfdb79f}
+
+Name
+
+:
+
+> gco:Record
+
+Description
+
+:
+
+### Record type {#iso19115-3.2018-elem-gco-RecordType-baa419e16ebadaef186f5d1d4378d1db}
+
+Name
+
+:
+
+> gco:RecordType
+
+Description
+
+:
+
+### Scoped name {#iso19115-3.2018-elem-gco-ScopedName-1edc4de3e2fd49cb8bfddd8e85a4a987}
+
+Name
+
+:
+
+> gco:ScopedName
+
+Description
+
+:
+
+### Period duration {#iso19115-3.2018-elem-gco-TM_PeriodDuration-f702b95baf47dfb1a87c02f15a5dd639}
+
+Name
+
+:
+
+> gco:TM_PeriodDuration
+
+Description
+
+:
+
+```{=html}
+The duration data type is used to specify a time interval.
+
+The time interval is specified in the following form "PnYnMnDTnHnMnS"
+where:
+
+* P indicates the period (required)
+* nY indicates the number of years
+* nM indicates the number of months
+* nD indicates the number of days
+* T indicates the start of a time section (required if you are going to
+specify hours, minutes, or seconds)
+* nH indicates the number of hours
+* nM indicates the number of minutes
+* nS indicates the number of seconds
+```
+### Type name {#iso19115-3.2018-elem-gco-TypeName-4009cb017635c2d3ff82934005a4ff9b}
+
+Name
+
+:
+
+> gco:TypeName
+
+Description
+
+:
+
+### Upper cardinality {#iso19115-3.2018-elem-gco-upper-0d20822ffdc1ca6563de53fd87a067c2}
+
+Name
+
+:
+
+> gco:upper
+
+Description
+
+:
+
+```{=html}
+Upper cardinality
+```
+### Anchor {#iso19115-3.2018-elem-gcx-Anchor-064e20d9f65a23dc450f791da24017aa}
+
+Name
+
+:
+
+> gcx:Anchor
+
+Description
+
+:
+
+```{=html}
+Supports hyper-linking capabilities and ensures a web-like
+ implementation of CharacterStrings
+```
+### File name {#iso19115-3.2018-elem-gcx-FileName-0bd7e76cc1295f6aa4aebc92c3448842}
+
+Name
+
+:
+
+> gcx:FileName
+
+Description
+
+:
+
+```{=html}
+File name and source URL.
+```
+### Mime file type {#iso19115-3.2018-elem-gcx-MimeFileType-a1cd8621fdd682eaee51c6582ba01ed4}
+
+Name
+
+:
+
+> gcx:MimeFileType
+
+Description
+
+:
+
+### Description {#iso19115-3.2018-elem-gex-description-gex-EX_Extent-28ac6cc0d81cbece1978a8620e803fad}
+
+Name
+
+:
+
+> gex:description
+
+Context
+
+:
+
+> gex:EX_Extent
+
+Description
+
+:
+
+```{=html}
+Spatial and temporal extent for the referring object
+```
+### Bounding Polygon {#iso19115-3.2018-elem-gex-EX_BoundingPolygon-3014dd690ec865ffc1790c19f4d93efd}
+
+Name
+
+:
+
+> gex:EX_BoundingPolygon
+
+Description
+
+:
+
+```{=html}
+Boundary enclosing the dataset, expressed as the closed set of
+ (x,y)
+ coordinates of the polygon (last point replicates first point)
+```
+### Extent {#iso19115-3.2018-elem-gex-EX_Extent-f2e723e195c26ffd1f6db79524409843}
+
+Name
+
+:
+
+> gex:EX_Extent
+
+Description
+
+:
+
+```{=html}
+Information about spatial, vertical, and temporal extent
+```
+``` xml
+
+
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+
+
+```
+
+### Geographic bounding box {#iso19115-3.2018-elem-gex-EX_GeographicBoundingBox-b271c47a118602d36a5450570a2f6b30}
+
+Name
+
+:
+
+> gex:EX_GeographicBoundingBox
+
+Description
+
+:
+
+```{=html}
+Geographic position of the dataset
+```
+``` xml
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+```
+
+### Geographic description {#iso19115-3.2018-elem-gex-EX_GeographicDescription-1d22aba992d17d899cc84e108455ef36}
+
+Name
+
+:
+
+> gex:EX_GeographicDescription
+
+Description
+
+:
+
+```{=html}
+Description of the geographic area using identifiers
+```
+### Spatial temporal extent {#iso19115-3.2018-elem-gex-EX_SpatialTemporalExtent-95530705e6fbad209cc29205102c0888}
+
+Name
+
+:
+
+> gex:EX_SpatialTemporalExtent
+
+Description
+
+:
+
+```{=html}
+Extent with respect to date/time and spatial boundaries
+```
+### Temporal extent {#iso19115-3.2018-elem-gex-EX_TemporalExtent-d2db3333e80d49d8a458007ff3838015}
+
+Name
+
+:
+
+> gex:EX_TemporalExtent
+
+Description
+
+:
+
+```{=html}
+Time period covered by the content of the dataset
+```
+### Vertical extent {#iso19115-3.2018-elem-gex-EX_VerticalExtent-cbd5924052cb1b8e0bf8f5416ece44a2}
+
+Name
+
+:
+
+> gex:EX_VerticalExtent
+
+Description
+
+:
+
+```{=html}
+Vertical domain of dataset
+```
+### Extent {#iso19115-3.2018-elem-gex-extent-gex-EX_TemporalExtent-eb6cbcb83beb909bff900f1169937ce4}
+
+Name
+
+:
+
+> gex:extent
+
+Context
+
+:
+
+> gex:EX_TemporalExtent
+
+Description
+
+:
+
+```{=html}
+Date and time for the content of the dataset
+```
+### Extent {#iso19115-3.2018-elem-gex-extent-396cb78192c906d06c8014fd67c5a704}
+
+Name
+
+:
+
+> gex:extent
+
+Description
+
+:
+
+```{=html}
+Geographic/Temporal Extent of Service
+```
+### Extent type code {#iso19115-3.2018-elem-gex-extentTypeCode-36b0ae6983fbd52220a364b33650402b}
+
+Name
+
+:
+
+> gex:extentTypeCode
+
+Description
+
+:
+
+```{=html}
+Indication of whether the bounding polygon encompasses an area
+ covered by the data or an area where data is not present. Possible values: '1' for
+ inclusion or '0' for exclusion
+```
+### Geographic element {#iso19115-3.2018-elem-gex-geographicElement-a738fb045db07afd86c8631512cdfcd0}
+
+Name
+
+:
+
+> gex:geographicElement
+
+Description
+
+:
+
+```{=html}
+Provides geographic component of the extent of the referring
+ object
+```
+``` xml
+
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+
+```
+
+### Geographic identifier {#iso19115-3.2018-elem-gex-geographicIdentifier-c6240129281eca8d905c5e34faad841d}
+
+Name
+
+:
+
+> gex:geographicIdentifier
+
+Description
+
+:
+
+```{=html}
+Identifier used to represent a geographic area
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Maximum value {#iso19115-3.2018-elem-gex-maximumValue-afcaee5c22764eaa540b44ed5a0d7662}
+
+Name
+
+:
+
+> gex:maximumValue
+
+Description
+
+:
+
+```{=html}
+Highest vertical extent contained in the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Minimum value {#iso19115-3.2018-elem-gex-minimumValue-83e87d76db1e018a13bb2a6649e2daf0}
+
+Name
+
+:
+
+> gex:minimumValue
+
+Description
+
+:
+
+```{=html}
+Lowest vertical extent contained in the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Polygon {#iso19115-3.2018-elem-gex-polygon-9e8a179ed9d619370d2aa0a543d1d3f9}
+
+Name
+
+:
+
+> gex:polygon
+
+Description
+
+:
+
+```{=html}
+Sets of points defining the bounding polygon
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Spatial extent {#iso19115-3.2018-elem-gex-spatialExtent-26a397b1ac7439d895ca7bfee22eb379}
+
+Name
+
+:
+
+> gex:spatialExtent
+
+Description
+
+:
+
+```{=html}
+Spatial extent component of composite spatial and temporal
+ extent
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Temporal element {#iso19115-3.2018-elem-gex-temporalElement-7a393c950f34c06f559b8d7e9179e623}
+
+Name
+
+:
+
+> gex:temporalElement
+
+Description
+
+:
+
+```{=html}
+Provides temporal component of the extent of the referring
+ object
+```
+
+Condition
+
+:
+
+> conditional
+
+### Vertical CRS {#iso19115-3.2018-elem-gex-verticalCRS-b1977041fc95ed539e434436c2103f79}
+
+Name
+
+:
+
+> gex:verticalCRS
+
+Description
+
+:
+
+```{=html}
+Provides information about the origin from which the maximum
+ and minimum elevation values are measured
+```
+### Vertical CRS identifier {#iso19115-3.2018-elem-gex-verticalCRSId-ed97e16f10262e33a28e43ad10d84eb7}
+
+Name
+
+:
+
+> gex:verticalCRSId
+
+Description
+
+:
+
+```{=html}
+Provides information about the origin from which the maximum
+ and minimum elevation values are measured
+```
+### Vertical element {#iso19115-3.2018-elem-gex-verticalElement-36d7efb1213f5644ea5903878e0c6f91}
+
+Name
+
+:
+
+> gex:verticalElement
+
+Description
+
+:
+
+```{=html}
+Provides vertical component of the extent of the referring
+ object
+```
+
+Condition
+
+:
+
+> conditional
+
+### Vertical extent {#iso19115-3.2018-elem-gex-verticalExtent-2536a2a55f2bab6e63bb5fca185b08a4}
+
+Name
+
+:
+
+> gex:verticalExtent
+
+Description
+
+:
+
+```{=html}
+Vertical extent component
+```
+### Affects value of {#iso19115-3.2018-elem-gfc-affectsValueOf-4e1acc1c69d17604f8ea2ec18fd8aac2}
+
+Name
+
+:
+
+> gfc:affectsValueOf
+
+Description
+
+:
+
+### Aliases {#iso19115-3.2018-elem-gfc-aliases-1f3ecb3fce2e8b73e3b5404492fd5e4e}
+
+Name
+
+:
+
+> gfc:aliases
+
+Description
+
+:
+
+### Cardinalities {#iso19115-3.2018-elem-gfc-cardinality-54aa6718c034715f68366669d9c257df}
+
+Name
+
+:
+
+> gfc:cardinality
+
+Description
+
+:
+
+```{=html}
+Cardinalities
+```
+Recommended values
+
+| code | label |
+|------|-------|
+| 0..1 | 0..1 |
+| 1..n | 0..n |
+| 1..1 | 1..1 |
+| 1..n | 1..n |
+
+### Elements {#iso19115-3.2018-elem-gfc-carrierOfCharacteristics-682149d26e0b5d9590e5d0c646422c67}
+
+Name
+
+:
+
+> gfc:carrierOfCharacteristics
+
+Description
+
+:
+
+```{=html}
+Association, attribute, operation, ...
+```
+### Code {#iso19115-3.2018-elem-gfc-code-1b6f547562a07b95ab72fddc20aca409}
+
+Name
+
+:
+
+> gfc:code
+
+Description
+
+:
+
+### Constrained by {#iso19115-3.2018-elem-gfc-constrainedBy-a7116446b2c586c6d8a70e2cf940932b}
+
+Name
+
+:
+
+> gfc:constrainedBy
+
+Description
+
+:
+
+### Definition {#iso19115-3.2018-elem-gfc-definition-1f7a798ac46834d7201d94001a371a2b}
+
+Name
+
+:
+
+> gfc:definition
+
+Description
+
+:
+
+```{=html}
+Property definition
+```
+### Definition reference {#iso19115-3.2018-elem-gfc-definitionReference-330ee93d4b59935b32ddcf04e41bc6f1}
+
+Name
+
+:
+
+> gfc:definitionReference
+
+Description
+
+:
+
+### Definition source {#iso19115-3.2018-elem-gfc-definitionSource-c33b1dd8d05c8122a1e066717bbe01b5}
+
+Name
+
+:
+
+> gfc:definitionSource
+
+Description
+
+:
+
+### Description {#iso19115-3.2018-elem-gfc-description-76104ba864ae4643a9a538027b8a0704}
+
+Name
+
+:
+
+> gfc:description
+
+Description
+
+:
+
+### Designation {#iso19115-3.2018-elem-gfc-designation-10a4f05fcab681ae1738c886134eb754}
+
+Name
+
+:
+
+> gfc:designation
+
+Description
+
+:
+
+### Association role {#iso19115-3.2018-elem-gfc-FC_AssociationRole-54c0b4b36dcbbbf887cfb6edfdda0582}
+
+Name
+
+:
+
+> gfc:FC_AssociationRole
+
+Description
+
+:
+
+### Binding {#iso19115-3.2018-elem-gfc-FC_Binding-8a7dd41a834377a6bd72a8dbb1f5f350}
+
+Name
+
+:
+
+> gfc:FC_Binding
+
+Description
+
+:
+
+### Bound association role {#iso19115-3.2018-elem-gfc-FC_BoundAssociationRole-b4754a7a6f41689a055280d5d2d05cc5}
+
+Name
+
+:
+
+> gfc:FC_BoundAssociationRole
+
+Description
+
+:
+
+### Bound feature attribute {#iso19115-3.2018-elem-gfc-FC_BoundFeatureAttribute-898e24636ada22d18a56641a7dcabd7a}
+
+Name
+
+:
+
+> gfc:FC_BoundFeatureAttribute
+
+Description
+
+:
+
+### Constraint {#iso19115-3.2018-elem-gfc-FC_Constraint-1d48e37a33b2ef6abacdb535438af2c5}
+
+Name
+
+:
+
+> gfc:FC_Constraint
+
+Description
+
+:
+
+### Definition reference {#iso19115-3.2018-elem-gfc-FC_DefinitionReference-fbb7ecc7c5c5b257ab9491fd4ee28e39}
+
+Name
+
+:
+
+> gfc:FC_DefinitionReference
+
+Description
+
+:
+
+### Definition source {#iso19115-3.2018-elem-gfc-FC_DefinitionSource-14e171ff3f78bdf3d634d1ba925d3d36}
+
+Name
+
+:
+
+> gfc:FC_DefinitionSource
+
+Description
+
+:
+
+### Feature association {#iso19115-3.2018-elem-gfc-FC_FeatureAssociation-baa21e2722e293fddbc3037c64118776}
+
+Name
+
+:
+
+> gfc:FC_FeatureAssociation
+
+Description
+
+:
+
+### Attribute {#iso19115-3.2018-elem-gfc-FC_FeatureAttribute-f9e32c08dc1c646c7b52c4cceec296f5}
+
+Name
+
+:
+
+> gfc:FC_FeatureAttribute
+
+Description
+
+:
+
+### Feature Catalogue description {#iso19115-3.2018-elem-gfc-FC_FeatureCatalogue-a85c1d0f43b46f8451f4c40daf0bc705}
+
+Name
+
+:
+
+> gfc:FC_FeatureCatalogue
+
+Description
+
+:
+
+### Feature operation {#iso19115-3.2018-elem-gfc-FC_FeatureOperation-e6ef41cdc09cdb4283da0094259ca585}
+
+Name
+
+:
+
+> gfc:FC_FeatureOperation
+
+Description
+
+:
+
+### Attribute table description {#iso19115-3.2018-elem-gfc-FC_FeatureType-807cb5c8e0cef875eaeb1111deebb772}
+
+Name
+
+:
+
+> gfc:FC_FeatureType
+
+Description
+
+:
+
+```{=html}
+Attribute table description
+```
+### Heritance relation {#iso19115-3.2018-elem-gfc-FC_InheritanceRelation-7e2a5d36b54c948ee7498bd5d828044f}
+
+Name
+
+:
+
+> gfc:FC_InheritanceRelation
+
+Description
+
+:
+
+### Codelist {#iso19115-3.2018-elem-gfc-FC_ListedValue-167a17d6b51fe41652abde46b836c975}
+
+Name
+
+:
+
+> gfc:FC_ListedValue
+
+Description
+
+:
+
+### Multilingual definition reference {#iso19115-3.2018-elem-gfc-FC_LocalisedDefinitionReference-18e0e9f983507db8496dad6d98da596c}
+
+Name
+
+:
+
+> gfc:FC_LocalisedDefinitionReference
+
+Description
+
+:
+
+### Role type {#iso19115-3.2018-elem-gfc-FC_RoleType-d046a278232203a2c540d3302274ee88}
+
+Name
+
+:
+
+> gfc:FC_RoleType
+
+Description
+
+:
+
+### Standard codelists Role type (gfc:FC_RoleType)
+
+| code | label | description |
+|-------------|-------------|------------------------------------------|
+| ordinary | Ordinary | Indicates an ordinary association. |
+| aggregation | Aggregation | Indicates a UML aggregation (part role). |
+| composition | Composition | Indicates a UML composition (part role). |
+
+### Feature catalogue {#iso19115-3.2018-elem-gfc-featureCatalogue-2b9e65b7ec8057df6a5468181ecbf3a3}
+
+Name
+
+:
+
+> gfc:featureCatalogue
+
+Description
+
+:
+
+### Property description {#iso19115-3.2018-elem-gfc-featureType-a588b6f71d43e8be637aa765477a74d2}
+
+Name
+
+:
+
+> gfc:featureType
+
+Description
+
+:
+
+```{=html}
+Property description
+```
+### Field of application {#iso19115-3.2018-elem-gfc-fieldOfApplication-91b54a5961930c2b79e37217649551b7}
+
+Name
+
+:
+
+> gfc:fieldOfApplication
+
+Description
+
+:
+
+```{=html}
+Field of application
+```
+### Formal definition {#iso19115-3.2018-elem-gfc-formalDefinition-9bfd839d612e02d56624fd469562f8cb}
+
+Name
+
+:
+
+> gfc:formalDefinition
+
+Description
+
+:
+
+### Functional language {#iso19115-3.2018-elem-gfc-functionalLanguage-e4caa81d46aea92c7c5c84574fc281eb}
+
+Name
+
+:
+
+> gfc:functionalLanguage
+
+Description
+
+:
+
+### Global property {#iso19115-3.2018-elem-gfc-globalProperty-2576ecf5bb2d911abe673a5626b23316}
+
+Name
+
+:
+
+> gfc:globalProperty
+
+Description
+
+:
+
+### Identifier {#iso19115-3.2018-elem-gfc-identifier-17f8eb8d6427c71971e22ffdd78ccb9d}
+
+Name
+
+:
+
+> gfc:identifier
+
+Description
+
+:
+
+### Inheritance relation {#iso19115-3.2018-elem-gfc-inheritanceRelation-6d26d325e36d277b7f1d330ac39bfbb9}
+
+Name
+
+:
+
+> gfc:inheritanceRelation
+
+Description
+
+:
+
+### Inherits from {#iso19115-3.2018-elem-gfc-inheritsFrom-18bd2dbc3edecade14d5894004fd60f0}
+
+Name
+
+:
+
+> gfc:inheritsFrom
+
+Description
+
+:
+
+### Inherits to {#iso19115-3.2018-elem-gfc-inheritsTo-a417363112776608dbf84d83d3fb67ef}
+
+Name
+
+:
+
+> gfc:inheritsTo
+
+Description
+
+:
+
+### Abstract {#iso19115-3.2018-elem-gfc-isAbstract-62461dcfba818df55568584e01173415}
+
+Name
+
+:
+
+> gfc:isAbstract
+
+Description
+
+:
+
+```{=html}
+Is this element an abstract element ?
+```
+### Is navigable {#iso19115-3.2018-elem-gfc-isNavigable-a831d2a69ea24f3e933ff219c14aaedf}
+
+Name
+
+:
+
+> gfc:isNavigable
+
+Description
+
+:
+
+### Is ordered {#iso19115-3.2018-elem-gfc-isOrdered-c203a60136a7c3943c35a82e53c031eb}
+
+Name
+
+:
+
+> gfc:isOrdered
+
+Description
+
+:
+
+### Label {#iso19115-3.2018-elem-gfc-label-447cd3024c5921db22777d687b3d4d17}
+
+Name
+
+:
+
+> gfc:label
+
+Description
+
+:
+
+### Codelist {#iso19115-3.2018-elem-gfc-listedValue-4fac52554c89276cf08dc3f966a665cf}
+
+Name
+
+:
+
+> gfc:listedValue
+
+Description
+
+:
+
+```{=html}
+List of values for this element.
+```
+### Member name {#iso19115-3.2018-elem-gfc-memberName-8e8235a1cdd6868a4af054b03fe96350}
+
+Name
+
+:
+
+> gfc:memberName
+
+Description
+
+:
+
+### Name {#iso19115-3.2018-elem-gfc-name-54b5c264e311ea93b097ceebb8b6befa}
+
+Name
+
+:
+
+> gfc:name
+
+Description
+
+:
+
+```{=html}
+Feature catalogue name
+```
+### Observes value of {#iso19115-3.2018-elem-gfc-observesValueOf-a157ab4b39a2131d1b4ec430005d70fc}
+
+Name
+
+:
+
+> gfc:observesValueOf
+
+Description
+
+:
+
+### Catalogue producer {#iso19115-3.2018-elem-gfc-producer-ecb58d02ce17a2079eb9665aa1e9a441}
+
+Name
+
+:
+
+> gfc:producer
+
+Description
+
+:
+
+```{=html}
+Catalogue responsible
+```
+### Relation {#iso19115-3.2018-elem-gfc-relation-ea980be9c74952068db1b1d008ea08df}
+
+Name
+
+:
+
+> gfc:relation
+
+Description
+
+:
+
+### Role name {#iso19115-3.2018-elem-gfc-roleName-ff1b162ef6ce9c374ba1681aa15691f6}
+
+Name
+
+:
+
+> gfc:roleName
+
+Description
+
+:
+
+### Role type {#iso19115-3.2018-elem-gfc-roleType-77146288bea15becb410a880f16d04c3}
+
+Name
+
+:
+
+> gfc:roleType
+
+Description
+
+:
+
+### Scope {#iso19115-3.2018-elem-gfc-scope-92c0cc9eb4b0d3fe850346a9d741c495}
+
+Name
+
+:
+
+> gfc:scope
+
+Description
+
+:
+
+```{=html}
+Scope definition
+```
+### Signature {#iso19115-3.2018-elem-gfc-signature-6d40a2368f5c5b76921d7c51b1b7cb70}
+
+Name
+
+:
+
+> gfc:signature
+
+Description
+
+:
+
+### Source {#iso19115-3.2018-elem-gfc-source-49d8df7454dfdb2caae5ec3f70fed1ee}
+
+Name
+
+:
+
+> gfc:source
+
+Description
+
+:
+
+### Source identifier {#iso19115-3.2018-elem-gfc-sourceIdentifier-69e2dff11c6fe458930d27876a77c6ed}
+
+Name
+
+:
+
+> gfc:sourceIdentifier
+
+Description
+
+:
+
+### Subtype {#iso19115-3.2018-elem-gfc-subtype-947c0bc7e4d45ff82b8afa6c6fdf9132}
+
+Name
+
+:
+
+> gfc:subtype
+
+Description
+
+:
+
+### Supertype {#iso19115-3.2018-elem-gfc-supertype-47d00c276a785fb966b84370e7820d40}
+
+Name
+
+:
+
+> gfc:supertype
+
+Description
+
+:
+
+### Translation {#iso19115-3.2018-elem-gfc-translation-3668f7d14cd3e2fe636e67ced85f40b2}
+
+Name
+
+:
+
+> gfc:translation
+
+Description
+
+:
+
+### Triggered by value of {#iso19115-3.2018-elem-gfc-triggeredByValueOf-f3b11de6224235f1982818f79e33bbb4}
+
+Name
+
+:
+
+> gfc:triggeredByValueOf
+
+Description
+
+:
+
+### Type {#iso19115-3.2018-elem-gfc-type-b70cc9bafe6869c97eef915521895006}
+
+Name
+
+:
+
+> gfc:type
+
+Description
+
+:
+
+### Property name {#iso19115-3.2018-elem-gfc-typeName-b1641f3126adf6d82ee4f50601aeb631}
+
+Name
+
+:
+
+> gfc:typeName
+
+Description
+
+:
+
+### Unique instance {#iso19115-3.2018-elem-gfc-uniqueInstance-3faf7b4ff9a9af53dfd0b6d8b2e95b98}
+
+Name
+
+:
+
+> gfc:uniqueInstance
+
+Description
+
+:
+
+### Value measurement unit {#iso19115-3.2018-elem-gfc-valueMeasurementUnit-2380f4c62edf6c737e875281fb4be44e}
+
+Name
+
+:
+
+> gfc:valueMeasurementUnit
+
+Description
+
+:
+
+### Value type {#iso19115-3.2018-elem-gfc-valueType-9d3e77e2649b5cc3dab7232c7d02d891}
+
+Name
+
+:
+
+> gfc:valueType
+
+Description
+
+:
+
+### Date {#iso19115-3.2018-elem-gfc-versionDate-6bbeb2519dec6ad3b9bb84ea49e53458}
+
+Name
+
+:
+
+> gfc:versionDate
+
+Description
+
+:
+
+```{=html}
+Catalogue date
+```
+### Version {#iso19115-3.2018-elem-gfc-versionNumber-f09ca54eb78c0633a010eefa907291de}
+
+Name
+
+:
+
+> gfc:versionNumber
+
+Description
+
+:
+
+```{=html}
+Catalogue version
+```
+### Axis {#iso19115-3.2018-elem-gml-axis-ee4896c6d7c2f971473c33b8a5bb7364}
+
+Name
+
+:
+
+> gml:axis
+
+Description
+
+:
+
+### Axis abbreviation {#iso19115-3.2018-elem-gml-axisAbbrev-06f07ba235d694508081df9b1f650243}
+
+Name
+
+:
+
+> gml:axisAbbrev
+
+Description
+
+:
+
+### Axis direction {#iso19115-3.2018-elem-gml-axisDirection-9e24abc19c9f9a5de788584d548e728c}
+
+Name
+
+:
+
+> gml:axisDirection
+
+Description
+
+:
+
+### Base unit {#iso19115-3.2018-elem-gml-BaseUnit-6c9bea4b727b4bf13d9cd293271472dd}
+
+Name
+
+:
+
+> gml:BaseUnit
+
+Description
+
+:
+
+### Begin {#iso19115-3.2018-elem-gml-begin-9267d72967877bb18ec2ee804105e8f8}
+
+Name
+
+:
+
+> gml:begin
+
+Description
+
+:
+
+### Begin date {#iso19115-3.2018-elem-gml-beginPosition-f00b219677910b0a7663831bcae4a837}
+
+Name
+
+:
+
+> gml:beginPosition
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+### Catalog symbol {#iso19115-3.2018-elem-gml-catalogSymbol-20debf93163e22b85511488caf7de721}
+
+Name
+
+:
+
+> gml:catalogSymbol
+
+Description
+
+:
+
+### Coordinates {#iso19115-3.2018-elem-gml-coordinates-93bba1ad2afcfd7886ad123ead5134b9}
+
+Name
+
+:
+
+> gml:coordinates
+
+Description
+
+:
+
+```{=html}
+Used to record an array of tuples or coordinates.
+```
+### Coordinate system axis {#iso19115-3.2018-elem-gml-CoordinateSystemAxis-3ad068d898bdac7b95af25206b91e31e}
+
+Name
+
+:
+
+> gml:CoordinateSystemAxis
+
+Description
+
+:
+
+### Description {#iso19115-3.2018-elem-gml-description-2600f7b526a347a9b798b8cce5449036}
+
+Name
+
+:
+
+> gml:description
+
+Description
+
+:
+
+```{=html}
+Text description of the element
+```
+### Description reference {#iso19115-3.2018-elem-gml-descriptionReference-578284e505af5531320c6e14a708a760}
+
+Name
+
+:
+
+> gml:descriptionReference
+
+Description
+
+:
+
+### Domain of validity {#iso19115-3.2018-elem-gml-domainOfValidity-1a276165942a51b46610456025c67328}
+
+Name
+
+:
+
+> gml:domainOfValidity
+
+Description
+
+:
+
+### Duration {#iso19115-3.2018-elem-gml-duration-048a2eb087c6f51866b129ff32bfd626}
+
+Name
+
+:
+
+> gml:duration
+
+Description
+
+:
+
+```{=html}
+Conforms to the ISO 8601 syntax for temporal length as
+ implemented by the XML Schema duration type.
+```
+### End {#iso19115-3.2018-elem-gml-end-52f9f66d3851e2c0326222a2a447ef52}
+
+Name
+
+:
+
+> gml:end
+
+Description
+
+:
+
+### End date {#iso19115-3.2018-elem-gml-endPosition-9f8aaba04b72980299ec61c0b8d2d646}
+
+Name
+
+:
+
+> gml:endPosition
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+### Outer boundary {#iso19115-3.2018-elem-gml-exterior-5721530d7165b757db1c8601fe7a24e6}
+
+Name
+
+:
+
+> gml:exterior
+
+Description
+
+:
+
+```{=html}
+The outer boundary of a solid.
+```
+### Identifier {#iso19115-3.2018-elem-gml-id-42de2c4c8a671cebba710db1b18c0107}
+
+Name
+
+:
+
+> gml:id
+
+Description
+
+:
+
+```{=html}
+Unique identifier
+```
+### Ellipsoid {#iso19115-3.2018-elem-gml-id-mri-MD_CRS-c97605d29328beea996712b90459c4b0}
+
+Name
+
+:
+
+> gml:id
+
+Context
+
+:
+
+> mri:MD_CRS
+
+Description
+
+:
+
+```{=html}
+Identity of the ellipsoid used
+```
+```{=html}
+identity of the ellipsoid used
+```
+### Identifier {#iso19115-3.2018-elem-gml-identifier-ee45781f2ae3fc17f684139652109a84}
+
+Name
+
+:
+
+> gml:identifier
+
+Description
+
+:
+
+### Inner boundary {#iso19115-3.2018-elem-gml-interior-3164a957fa955b24e183bc071bb38263}
+
+Name
+
+:
+
+> gml:interior
+
+Description
+
+:
+
+```{=html}
+The inner boundary of a solid
+```
+### Linear ring {#iso19115-3.2018-elem-gml-LinearRing-ced37e1154857d6ce3d664076659332c}
+
+Name
+
+:
+
+> gml:LinearRing
+
+Description
+
+:
+
+```{=html}
+A gml:LinearRing is defined by four or more coordinate tuples,
+ with linear
+ interpolation between them; the first and last coordinates shall be
+ coincident.
+```
+### Line {#iso19115-3.2018-elem-gml-LineString-600185f9928ea52861bb6db1d8faaaf9}
+
+Name
+
+:
+
+> gml:LineString
+
+Description
+
+:
+
+```{=html}
+A gml:LineString is a special curve that consists of a single
+ segment with
+ linear interpolation. It is defined by two or more coordinate tuples, with
+ linear
+ interpolation between them.
+```
+### Maximum value {#iso19115-3.2018-elem-gml-maximumValue-7f3fca69f6f90158c23b4b8ab4cea8d2}
+
+Name
+
+:
+
+> gml:maximumValue
+
+Description
+
+:
+
+### Metadata property {#iso19115-3.2018-elem-gml-metaDataProperty-d35cc559d1ea5955993b4b1f09eb07d8}
+
+Name
+
+:
+
+> gml:metaDataProperty
+
+Description
+
+:
+
+### Minimum value {#iso19115-3.2018-elem-gml-minimumValue-2b8ffd52e40a4035d7ac9df8ac3c0ff4}
+
+Name
+
+:
+
+> gml:minimumValue
+
+Description
+
+:
+
+### Name {#iso19115-3.2018-elem-gml-name-db4e6ae78001c92be5ac3e74d7ec8d77}
+
+Name
+
+:
+
+> gml:name
+
+Description
+
+:
+
+### Point {#iso19115-3.2018-elem-gml-Point-3d13098ff5d2b030481b094ab9d32184}
+
+Name
+
+:
+
+> gml:Point
+
+Description
+
+:
+
+```{=html}
+A gml:Point is defined by a single coordinate tuple.
+```
+### Point type {#iso19115-3.2018-elem-gml-PointType-060f62970e5ada17f74811359552d183}
+
+Name
+
+:
+
+> gml:PointType
+
+Description
+
+:
+
+### Polygon {#iso19115-3.2018-elem-gml-Polygon-be0aca51ddc0b4e76ab1f54444748cc0}
+
+Name
+
+:
+
+> gml:Polygon
+
+Description
+
+:
+
+```{=html}
+A gml:Polygon is a special surface that is defined by a single
+ surface patch.
+ The boundary of this patch is coplanar and the polygon uses planar
+ interpolation in its
+ interior.
+```
+### Pos {#iso19115-3.2018-elem-gml-pos-4fff453ab55389744543f2df6c5a0e0a}
+
+Name
+
+:
+
+> gml:pos
+
+Description
+
+:
+
+### Projected CRS {#iso19115-3.2018-elem-gml-ProjectedCRS-5d3ed9ff2ace3bd4dc4b6d4a68c24491}
+
+Name
+
+:
+
+> gml:ProjectedCRS
+
+Description
+
+:
+
+### Quantity type {#iso19115-3.2018-elem-gml-quantityType-49cf23ca6944dea5ec8fe2740bd8441e}
+
+Name
+
+:
+
+> gml:quantityType
+
+Description
+
+:
+
+### Quantity type reference {#iso19115-3.2018-elem-gml-quantityTypeReference-7d7da8f239d830b79402c17fbbd8bd34}
+
+Name
+
+:
+
+> gml:quantityTypeReference
+
+Description
+
+:
+
+### Range meaning {#iso19115-3.2018-elem-gml-rangeMeaning-02f759e960e187822ef303d11aaaaee5}
+
+Name
+
+:
+
+> gml:rangeMeaning
+
+Description
+
+:
+
+### Realization epoch {#iso19115-3.2018-elem-gml-realizationEpoch-c07141b4c3761224c67b8ad71596f617}
+
+Name
+
+:
+
+> gml:realizationEpoch
+
+Description
+
+:
+
+### Related time {#iso19115-3.2018-elem-gml-relatedTime-a4c0ec44ce9c5e9404b7a318ea456e82}
+
+Name
+
+:
+
+> gml:relatedTime
+
+Description
+
+:
+
+```{=html}
+Defines the relation of a given time to the object.
+```
+### Remarks {#iso19115-3.2018-elem-gml-remarks-aa7c5b619988014f875df4eb43f8fc20}
+
+Name
+
+:
+
+> gml:remarks
+
+Description
+
+:
+
+### Remote schema {#iso19115-3.2018-elem-gml-remoteSchema-e5c36c448e77fee875f1b4cbd87d5e37}
+
+Name
+
+:
+
+> gml:remoteSchema
+
+Description
+
+:
+
+### Scope {#iso19115-3.2018-elem-gml-scope-0030a4d6fa08ad7c1eb516c1bdf3377b}
+
+Name
+
+:
+
+> gml:scope
+
+Description
+
+:
+
+### Time edge {#iso19115-3.2018-elem-gml-TimeEdge-8de5f2633834b77940206332af02a3f3}
+
+Name
+
+:
+
+> gml:TimeEdge
+
+Description
+
+:
+
+### Time edge type {#iso19115-3.2018-elem-gml-TimeEdgeType-6f3c48eb82089951457a8b6e66376d72}
+
+Name
+
+:
+
+> gml:TimeEdgeType
+
+Description
+
+:
+
+### Time instant {#iso19115-3.2018-elem-gml-TimeInstant-9ed28d4003f6f01dcbb5c2a35eb1b868}
+
+Name
+
+:
+
+> gml:TimeInstant
+
+Description
+
+:
+
+### Time instant type {#iso19115-3.2018-elem-gml-TimeInstantType-3f5810bbca58aa889cce1be23cb8b296}
+
+Name
+
+:
+
+> gml:TimeInstantType
+
+Description
+
+:
+
+### Time interval {#iso19115-3.2018-elem-gml-timeInterval-1e58ea97b2d3c8d2ee8af8fba944525e}
+
+Name
+
+:
+
+> gml:timeInterval
+
+Description
+
+:
+
+```{=html}
+conforms to ISO 11404 which is based on floating point values
+ for temporal length.
+ ISO 11404 syntax specifies the use of a positiveInteger together with
+ appropriate values for radix and factor. The resolution of the time
+ interval is to one radix ^(-factor) of the specified time unit.
+ The value of the unit is either selected from the units for time intervals
+ from ISO 31-1:1992, or is another suitable unit. The encoding is defined
+ for GML in gml:TimeUnitType. The second component of this union type
+ provides a method for indicating time units other than the six standard
+ units given in the enumeration.
+```
+### Time node {#iso19115-3.2018-elem-gml-TimeNode-91dbe7a18704bd38bb78222821f700d4}
+
+Name
+
+:
+
+> gml:TimeNode
+
+Description
+
+:
+
+### Time node type {#iso19115-3.2018-elem-gml-TimeNodeType-8ad896bbeae74ddc6aeccb985219b0c8}
+
+Name
+
+:
+
+> gml:TimeNodeType
+
+Description
+
+:
+
+### Time period {#iso19115-3.2018-elem-gml-TimePeriod-d6dba552b799834fed47973fd4b7cd4f}
+
+Name
+
+:
+
+> gml:TimePeriod
+
+Description
+
+:
+
+### Time period type {#iso19115-3.2018-elem-gml-TimePeriodType-c1129dd5a4a5df9ca9aa3fcd4c8fb9b8}
+
+Name
+
+:
+
+> gml:TimePeriodType
+
+Description
+
+:
+
+### Time position {#iso19115-3.2018-elem-gml-timePosition-6857f16de011b9783e13a5d6d6273486}
+
+Name
+
+:
+
+> gml:timePosition
+
+Description
+
+:
+
+### Time position {#iso19115-3.2018-elem-gml-TimePosition-505d1e7bef8e83fa4766daf84513beff}
+
+Name
+
+:
+
+> gml:TimePosition
+
+Description
+
+:
+
+### Unit definition {#iso19115-3.2018-elem-gml-UnitDefinition-c407f907d054e79a4c4664b4c832b325}
+
+Name
+
+:
+
+> gml:UnitDefinition
+
+Description
+
+:
+
+### Units system {#iso19115-3.2018-elem-gml-unitsSystem-cc71d59e78af646f2d29be97dc8c2212}
+
+Name
+
+:
+
+> gml:unitsSystem
+
+Description
+
+:
+
+### Vertical CRS {#iso19115-3.2018-elem-gml-VerticalCRS-0499658a8cbf1588dc852d46a97208e2}
+
+Name
+
+:
+
+> gml:VerticalCRS
+
+Description
+
+:
+
+### Vertical CS {#iso19115-3.2018-elem-gml-verticalCS-da6818bd5029d419378e56a1452af0c8}
+
+Name
+
+:
+
+> gml:verticalCS
+
+Description
+
+:
+
+### Vertical CS {#iso19115-3.2018-elem-gml-VerticalCS-5b2ac8a91a1b1c96e534eac65bbacf38}
+
+Name
+
+:
+
+> gml:VerticalCS
+
+Description
+
+:
+
+### Vertical datum {#iso19115-3.2018-elem-gml-verticalDatum-b6eee3a14a8b0f1075ae043a034e1f40}
+
+Name
+
+:
+
+> gml:verticalDatum
+
+Description
+
+:
+
+### Vertical datum {#iso19115-3.2018-elem-gml-VerticalDatum-cebbc2196212fde90a395c3c216b36c6}
+
+Name
+
+:
+
+> gml:VerticalDatum
+
+Description
+
+:
+
+### Hidden Elements {#iso19115-3.2018-elem-hidden-elements-c22e8449aff98b154969567fdc5c04f0}
+
+Name
+
+:
+
+> hidden-elements
+
+Description
+
+:
+
+```{=html}
+Child elements and attributes have been hidden because you do
+ no have access to view those elements
+```
+### Identifier {#iso19115-3.2018-elem-id-2345f9dc93f577a30435e73a55c2e3c0}
+
+Name
+
+:
+
+> id
+
+Description
+
+:
+
+```{=html}
+Unique identifier
+```
+### Indeterminate position {#iso19115-3.2018-elem-indeterminatePosition-69ea8df41d40c0c9e8bb430d26bb0d49}
+
+Name
+
+:
+
+> indeterminatePosition
+
+Description
+
+:
+
+### Standard codelists Indeterminate position (indeterminatePosition)
+
+| code | label |
+|---------|---------|
+| after | After |
+| before | Before |
+| now | Now |
+| unknown | Unknown |
+
+### Is infinite {#iso19115-3.2018-elem-isInfinite-f8b250954f378d7fed3f293b112e13c4}
+
+Name
+
+:
+
+> isInfinite
+
+Description
+
+:
+
+### Character encoding {#iso19115-3.2018-elem-lan-characterEncoding-2b6f0a1f954994506c54ac850f001f89}
+
+Name
+
+:
+
+> lan:characterEncoding
+
+Description
+
+:
+
+```{=html}
+CharacterEncoding
+```
+### Country {#iso19115-3.2018-elem-lan-country-da9f45a56a7e3bea3fad555ba7b0e8a6}
+
+Name
+
+:
+
+> lan:country
+
+Description
+
+:
+
+```{=html}
+Designation of the specific country of the locale language
+```
+
+Condition
+
+:
+
+> optional
+
+### Country {#iso19115-3.2018-elem-lan-country-lan-PT_Locale-9ff105f1f19be3b26f3ab04cef7f90f2}
+
+Name
+
+:
+
+> lan:country
+
+Context
+
+:
+
+> lan:PT_Locale
+
+Description
+
+:
+
+```{=html}
+Designation of the specific country of the locale language
+```
+
+Condition
+
+:
+
+> optional
+
+### Date {#iso19115-3.2018-elem-lan-date-lan-PT_LocaleContainer-132a4183d35d301254fb13df2d7d0338}
+
+Name
+
+:
+
+> lan:date
+
+Context
+
+:
+
+> lan:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+Date of creation or revision of the locale
+ container
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Description {#iso19115-3.2018-elem-lan-description-lan-PT_LocaleContainer-1f47795aecc317bde4c9afb79d853eb6}
+
+Name
+
+:
+
+> lan:description
+
+Context
+
+:
+
+> lan:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+Designation of the locale language
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Language {#iso19115-3.2018-elem-lan-language-8a2e23cada8f90f768153cd009dd1421}
+
+Name
+
+:
+
+> lan:language
+
+Description
+
+:
+
+```{=html}
+Designation of the locale language
+```
+### ISO Language code {#iso19115-3.2018-elem-lan-LanguageCode-dbfc1c90b859ca52a01a1f8bafbaf567}
+
+Name
+
+:
+
+> lan:LanguageCode
+
+Description
+
+:
+
+```{=html}
+Language code
+```
+### Locale {#iso19115-3.2018-elem-lan-locale-lan-PT_LocaleContainer-e7de1934cd262890bd1e025b68448154}
+
+Name
+
+:
+
+> lan:locale
+
+Context
+
+:
+
+> lan:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+Locale in which the localised strings of the
+ container are expressed
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Locale {#iso19115-3.2018-elem-lan-locale-lan-LocalisedCharacterString-89a38d8f8dd189b863a75f8a0f74f7ba}
+
+Name
+
+:
+
+> lan:locale
+
+Context
+
+:
+
+> lan:LocalisedCharacterString
+
+Description
+
+:
+
+```{=html}
+defines the locale in which the value (sequence of
+ characters) of the localised character string is expressed
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Localised character string {#iso19115-3.2018-elem-lan-LocalisedCharacterString-901dcad3602cb2b433174b51134a10d7}
+
+Name
+
+:
+
+> lan:LocalisedCharacterString
+
+Description
+
+:
+
+```{=html}
+Expression of a free text in a given locale
+```
+### Localised string {#iso19115-3.2018-elem-lan-localisedString-lan-PT_LocaleContainer-bf9b4b45e7257abd994d0abe61aa8e43}
+
+Name
+
+:
+
+> lan:localisedString
+
+Context
+
+:
+
+> lan:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+Provides the list of localised character string
+ expressing the linguistic translation of a set of textual information in a
+ given locale
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Character set code {#iso19115-3.2018-elem-lan-MD_CharacterSetCode-b9a04835e79ab3aca7ae89608dd5b3b4}
+
+Name
+
+:
+
+> lan:MD_CharacterSetCode
+
+Description
+
+:
+
+```{=html}
+Use IANA Character Set register:
+ http://www.iana.org/assignments/character-sets. These are the official
+ names for character sets that may be used in the Internet and may be
+ referred to in Internet documentation. These names are expressed in
+ ANSI_X3.4-1968 which is commonly called US-ASCII or simply ASCII.
+```
+### Standard codelists Character set code (lan:MD_CharacterSetCode)
+
+| code | label | description |
+|------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| ucs2 | UCS2 | 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| ucs4 | UCS4 | 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| utf7 | UTF7 | 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf8 | UTF8 | 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf16 | UTF16 | 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| 8859part1 | 8859 Part 1 | ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 |
+| 8859part2 | 8859 Part 2 | ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 |
+| 8859part3 | 8859 Part 3 | ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 |
+| 8859part4 | 8859 Part 4 | ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 |
+| 8859part5 | 8859 Part 5 | ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet |
+| 8859part6 | 8859 Part 6 | ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet |
+| 8859part7 | 8859 Part 7 | ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet |
+| 8859part8 | 8859 Part 8 | ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet |
+| 8859part9 | 8859 Part 9 | ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 |
+| 8859part10 | 8859 Part 10 | ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 |
+| 8859part11 | 8859 Part 11 | ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet |
+| 8859part13 | 8859 Part 13 | ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 |
+| 8859part14 | 8859 Part 14 | ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) |
+| 8859part15 | 8859 Part 15 | ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 |
+| 8859part16 | 8859 Part 16 | ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 |
+| jis | JIS | Japanese code set used for electronic transmission |
+| shiftJIS | Shift JIS | Japanese code set used on MS-DOS machines |
+| eucJP | EUC JP | Japanese code set used on UNIX based machines |
+| usAscii | US ASCII | United States ASCII code set (ISO 646 US) |
+| ebcdic | EBCDIC | IBM mainframe code set |
+| eucKR | EUC KR | Korean code set |
+| big5 | Big 5 | Traditional Chinese code set used in Taiwan, Hong Kong of China and other areas |
+| GB2312 | GB2312 | Simplified Chinese code set |
+
+### Locale {#iso19115-3.2018-elem-lan-PT_Locale-c8a7a406cec8fd65657ae57ca0af6974}
+
+Name
+
+:
+
+> lan:PT_Locale
+
+Description
+
+:
+
+```{=html}
+Locale
+```
+### Container of localised character strings {#iso19115-3.2018-elem-lan-PT_LocaleContainer-117d7bd7272ea9abb9365a5aeb6e9bbc}
+
+Name
+
+:
+
+> lan:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+Container of localised character strings. NOTE It provides a
+ means to isolate the localised strings related to a given locale.
+```
+### Party responsible {#iso19115-3.2018-elem-lan-responsibleParty-lan-PT_LocaleContainer-0877d1ab157089bc69c5a6c64e7d8256}
+
+Name
+
+:
+
+> lan:responsibleParty
+
+Context
+
+:
+
+> lan:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+Responsible parties of the locale container
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Acquisition plan {#iso19115-3.2018-elem-mac-acquisitionPlan-4c8c1de47fbe550f3ccd431aa4a29724}
+
+Name
+
+:
+
+> mac:acquisitionPlan
+
+Description
+
+:
+
+### Acquisition requirement {#iso19115-3.2018-elem-mac-acquisitionRequirement-e37fc1c473395ccb539432ef3f950800}
+
+Name
+
+:
+
+> mac:acquisitionRequirement
+
+Description
+
+:
+
+### Author {#iso19115-3.2018-elem-mac-author-32773deaf9e82a5689b4e658e4bd0470}
+
+Name
+
+:
+
+> mac:author
+
+Description
+
+:
+
+### Air temperature average {#iso19115-3.2018-elem-mac-averageAirTemperature-d2e612416638d6ffbb455c9c9ab8cbbc}
+
+Name
+
+:
+
+> mac:averageAirTemperature
+
+Description
+
+:
+
+```{=html}
+Average air temperature along the flight pass during the photo flight.
+```
+### Child operation {#iso19115-3.2018-elem-mac-childOperation-ebec2a49b25229de0983dcc2e1235f3d}
+
+Name
+
+:
+
+> mac:childOperation
+
+Description
+
+:
+
+### Citation {#iso19115-3.2018-elem-mac-citation-9bf03298a3d41fa91feea2e4ccd51310}
+
+Name
+
+:
+
+> mac:citation
+
+Description
+
+:
+
+### Content {#iso19115-3.2018-elem-mac-content-f214d41a1c2135aaca4c17c657d771a0}
+
+Name
+
+:
+
+> mac:content
+
+Description
+
+:
+
+### Context {#iso19115-3.2018-elem-mac-context-7feab93bc0b7c188e27294530aeb9bf9}
+
+Name
+
+:
+
+> mac:context
+
+Description
+
+:
+
+```{=html}
+Meaning of the event
+```
+### Description {#iso19115-3.2018-elem-mac-description-3b10ebf848544f1783a7a05fa206e323}
+
+Name
+
+:
+
+> mac:description
+
+Description
+
+:
+
+### Environmental conditions {#iso19115-3.2018-elem-mac-environmentalConditions-b48e662a6b728e9481ee8de2f5f562be}
+
+Name
+
+:
+
+> mac:environmentalConditions
+
+Description
+
+:
+
+### Expected objective {#iso19115-3.2018-elem-mac-expectedObjective-1515a363116cec7e226709b5e3a29df5}
+
+Name
+
+:
+
+> mac:expectedObjective
+
+Description
+
+:
+
+### Expiry date {#iso19115-3.2018-elem-mac-expiryDate-67127493055f27d7a84c5d6c33dad0f3}
+
+Name
+
+:
+
+> mac:expiryDate
+
+Description
+
+:
+
+### Extent {#iso19115-3.2018-elem-mac-extent-32bca388546aa036836a0999d4a0985f}
+
+Name
+
+:
+
+> mac:extent
+
+Description
+
+:
+
+### Function {#iso19115-3.2018-elem-mac-function-43a516d7a5a9d330dfbca44dee9e7805}
+
+Name
+
+:
+
+> mac:function
+
+Description
+
+:
+
+### History {#iso19115-3.2018-elem-mac-history-2863203dec4254489da43424346c292a}
+
+Name
+
+:
+
+> mac:history
+
+Description
+
+:
+
+### Hosted {#iso19115-3.2018-elem-mac-hosted-a93658bd768bab76294623bdc03a7f46}
+
+Name
+
+:
+
+> mac:hosted
+
+Description
+
+:
+
+### Identifier {#iso19115-3.2018-elem-mac-identifier-81da0e180981d90216072a56b23a8aac}
+
+Name
+
+:
+
+> mac:identifier
+
+Description
+
+:
+
+### Instrument {#iso19115-3.2018-elem-mac-instrument-e2f3702c569b7cc4ec779f6747ddf617}
+
+Name
+
+:
+
+> mac:instrument
+
+Description
+
+:
+
+### Instrumentation event {#iso19115-3.2018-elem-mac-instrumentationEvent-4578f8e6e9f5bd9e5f143d95dcd6e551}
+
+Name
+
+:
+
+> mac:instrumentationEvent
+
+Description
+
+:
+
+```{=html}
+An event related to a platform/instrument/sensor
+```
+### Latest acceptable date {#iso19115-3.2018-elem-mac-latestAcceptableDate-4898adac6a40ba5ac94a923f11ee7df5}
+
+Name
+
+:
+
+> mac:latestAcceptableDate
+
+Description
+
+:
+
+### Language (locale) {#iso19115-3.2018-elem-mac-locale-1f9333f7305eb86aca37ce9b26daa454}
+
+Name
+
+:
+
+> mac:locale
+
+Description
+
+:
+
+### Maximum altitude {#iso19115-3.2018-elem-mac-maxAltitude-e09b6ad8e0fc72eece1045c524609e34}
+
+Name
+
+:
+
+> mac:maxAltitude
+
+Description
+
+:
+
+```{=html}
+Maximum altitude during the photo flight.
+```
+### Maximum of relative humidity {#iso19115-3.2018-elem-mac-maxRelativeHumidity-b6e9aa984f7a6d9c47d5f1ed397ff185}
+
+Name
+
+:
+
+> mac:maxRelativeHumidity
+
+Description
+
+:
+
+```{=html}
+Maximum relative humidity along the flight pass during the photo flight.
+```
+### Metadata constraints {#iso19115-3.2018-elem-mac-metadataConstraints-2b5dd2d8c580cbf6942d2aca1a24b252}
+
+Name
+
+:
+
+> mac:metadataConstraints
+
+Description
+
+:
+
+### Meterological conditions {#iso19115-3.2018-elem-mac-meterologicalConditions-d1a103da456e4ddb5ac84a6c34645147}
+
+Name
+
+:
+
+> mac:meterologicalConditions
+
+Description
+
+:
+
+```{=html}
+Meteorological conditions in the photo flight area, in particular clouds, snow and wind.
+```
+### Acquisition information {#iso19115-3.2018-elem-mac-MI_AcquisitionInformation-6dc340212b25f0c014271a29f5dd08ad}
+
+Name
+
+:
+
+> mac:MI_AcquisitionInformation
+
+Description
+
+:
+
+### Environmental record {#iso19115-3.2018-elem-mac-MI_EnvironmentalRecord-7f442841494df00f426bcc2b0851325f}
+
+Name
+
+:
+
+> mac:MI_EnvironmentalRecord
+
+Description
+
+:
+
+```{=html}
+Information about the environmental conditions during the acquisition
+```
+### Event {#iso19115-3.2018-elem-mac-MI_Event-ebe92cdc7725c63f0eff85b23d2f32c1}
+
+Name
+
+:
+
+> mac:MI_Event
+
+Description
+
+:
+
+```{=html}
+Identification of a significant collection point within an operation
+```
+### Instrument {#iso19115-3.2018-elem-mac-MI_Instrument-6eacc5914df11972c7d81a384ec2a3ce}
+
+Name
+
+:
+
+> mac:MI_Instrument
+
+Description
+
+:
+
+```{=html}
+Characteristics of the measuring instrument
+```
+### Instrumentation event {#iso19115-3.2018-elem-mac-MI_InstrumentationEvent-edc1ed671f48408d806ee8b24cba3472}
+
+Name
+
+:
+
+> mac:MI_InstrumentationEvent
+
+Description
+
+:
+
+### Instrumentation event list {#iso19115-3.2018-elem-mac-MI_InstrumentationEventList-ea0c6f932372328f403129acf99234e2}
+
+Name
+
+:
+
+> mac:MI_InstrumentationEventList
+
+Description
+
+:
+
+```{=html}
+List of events related to platform/ instrument/sensor
+```
+### Objective {#iso19115-3.2018-elem-mac-MI_Objective-26ac604605f8af66cb893cef57b01e4f}
+
+Name
+
+:
+
+> mac:MI_Objective
+
+Description
+
+:
+
+```{=html}
+Describes the characteristics, spatial and temporal extent of the intended object to be observed
+```
+### Operation {#iso19115-3.2018-elem-mac-MI_Operation-98933bc74bcfaf78c957c2b0a95acb1b}
+
+Name
+
+:
+
+> mac:MI_Operation
+
+Description
+
+:
+
+```{=html}
+Designations for the operation used to acquire the dataset
+```
+### Plan {#iso19115-3.2018-elem-mac-MI_Plan-ef5177b27b97b5ec45c6d82aebce6725}
+
+Name
+
+:
+
+> mac:MI_Plan
+
+Description
+
+:
+
+```{=html}
+Designations for the planning information related to meeting the data acquisition requirements
+```
+### Platform {#iso19115-3.2018-elem-mac-MI_Platform-7e4bdeefe1bc78a5f0dca2cb685eda26}
+
+Name
+
+:
+
+> mac:MI_Platform
+
+Description
+
+:
+
+```{=html}
+Designations for the platform used to acquire the dataset
+```
+### Platform pass {#iso19115-3.2018-elem-mac-MI_PlatformPass-4d1995d96efd13f5b1244545b89da350}
+
+Name
+
+:
+
+> mac:MI_PlatformPass
+
+Description
+
+:
+
+```{=html}
+Identification of collection coverage.
+```
+### Requested date {#iso19115-3.2018-elem-mac-MI_RequestedDate-9ad587a48505fdbd81772da036ccf318}
+
+Name
+
+:
+
+> mac:MI_RequestedDate
+
+Description
+
+:
+
+### Requirement {#iso19115-3.2018-elem-mac-MI_Requirement-3b49f0fe913e6addc285b9b9e670e5f3}
+
+Name
+
+:
+
+> mac:MI_Requirement
+
+Description
+
+:
+
+```{=html}
+Requirement to be satisfied by the planned data acquisition
+```
+### Revision {#iso19115-3.2018-elem-mac-MI_Revision-aa242ad86f140c920e8f3f10ce3873aa}
+
+Name
+
+:
+
+> mac:MI_Revision
+
+Description
+
+:
+
+```{=html}
+History of the revision of an event
+```
+### Sensor {#iso19115-3.2018-elem-mac-MI_Sensor-1213e290019529db22e20c83052b64db}
+
+Name
+
+:
+
+> mac:MI_Sensor
+
+Description
+
+:
+
+```{=html}
+Specific type of instrument
+```
+### Mounted on {#iso19115-3.2018-elem-mac-mountedOn-18c62cdc237e376b21d0e74d2c3b2391}
+
+Name
+
+:
+
+> mac:mountedOn
+
+Description
+
+:
+
+### Objective {#iso19115-3.2018-elem-mac-objective-f6969734c75afde5ff62a2397caef765}
+
+Name
+
+:
+
+> mac:objective
+
+Description
+
+:
+
+### Objective occurrence {#iso19115-3.2018-elem-mac-objectiveOccurence-a37834ed908ca4ee9d177d34dffff8c8}
+
+Name
+
+:
+
+> mac:objectiveOccurence
+
+Description
+
+:
+
+### Operation {#iso19115-3.2018-elem-mac-operation-33100585e6aa7f87c9f4adc93a740f1e}
+
+Name
+
+:
+
+> mac:operation
+
+Description
+
+:
+
+### Other property {#iso19115-3.2018-elem-mac-otherProperty-9c092131f6ca89ea73c6807fd14c2b31}
+
+Name
+
+:
+
+> mac:otherProperty
+
+Description
+
+:
+
+### Other property type {#iso19115-3.2018-elem-mac-otherPropertyType-f33fc4918fb4268f0073efc189ff4919}
+
+Name
+
+:
+
+> mac:otherPropertyType
+
+Description
+
+:
+
+### Parent operation {#iso19115-3.2018-elem-mac-parentOperation-c561a03420b95045a67c77bb7dd2af62}
+
+Name
+
+:
+
+> mac:parentOperation
+
+Description
+
+:
+
+### Pass {#iso19115-3.2018-elem-mac-pass-1f75aaf313f44ae7d58fe1b4f8c448e7}
+
+Name
+
+:
+
+> mac:pass
+
+Description
+
+:
+
+### Plan {#iso19115-3.2018-elem-mac-plan-9166bddcc181db05999aeedc97b54cda}
+
+Name
+
+:
+
+> mac:plan
+
+Description
+
+:
+
+### Platform {#iso19115-3.2018-elem-mac-platform-865e14036ff1d013e11fd2afd0108d6a}
+
+Name
+
+:
+
+> mac:platform
+
+Description
+
+:
+
+### Priority {#iso19115-3.2018-elem-mac-priority-52f9057ea4ae961125cb328b36d968db}
+
+Name
+
+:
+
+> mac:priority
+
+Description
+
+:
+
+```{=html}
+Priority applied to the target
+```
+### Recipient {#iso19115-3.2018-elem-mac-recipient-6b1a56cb60ca97365b1ececa8473c112}
+
+Name
+
+:
+
+> mac:recipient
+
+Description
+
+:
+
+### Related event {#iso19115-3.2018-elem-mac-relatedEvent-c343b731477ef2687d01751e388e8209}
+
+Name
+
+:
+
+> mac:relatedEvent
+
+Description
+
+:
+
+### Related pass {#iso19115-3.2018-elem-mac-relatedPass-913feab1c6f4fac31d46edf22de3eef7}
+
+Name
+
+:
+
+> mac:relatedPass
+
+Description
+
+:
+
+### Related sensor {#iso19115-3.2018-elem-mac-relatedSensor-b22fab77d761aa9e6046faa7581e68bb}
+
+Name
+
+:
+
+> mac:relatedSensor
+
+Description
+
+:
+
+### Requested date {#iso19115-3.2018-elem-mac-requestedDate-d38587d25a59a1a223f730353f102c82}
+
+Name
+
+:
+
+> mac:requestedDate
+
+Description
+
+:
+
+```{=html}
+Range of date validity
+```
+### Requested date of collection {#iso19115-3.2018-elem-mac-requestedDateOfCollection-76623dcb1fe75b01f587722ad3168472}
+
+Name
+
+:
+
+> mac:requestedDateOfCollection
+
+Description
+
+:
+
+### Requestor {#iso19115-3.2018-elem-mac-requestor-d769b574f6987630916fdd7c0995838c}
+
+Name
+
+:
+
+> mac:requestor
+
+Description
+
+:
+
+### Revision history {#iso19115-3.2018-elem-mac-revisionHistory-2e83384a42f16c9b91738b749272cfd1}
+
+Name
+
+:
+
+> mac:revisionHistory
+
+Description
+
+:
+
+### Satisfied requirement {#iso19115-3.2018-elem-mac-satisfiedRequirement-f9bf2f69059992413e902d634b40662d}
+
+Name
+
+:
+
+> mac:satisfiedRequirement
+
+Description
+
+:
+
+### Satisfied plan {#iso19115-3.2018-elem-mac-satisifiedPlan-fcbae74a0125ba3d459ccb25f56ee57c}
+
+Name
+
+:
+
+> mac:satisifiedPlan
+
+Description
+
+:
+
+### Scope {#iso19115-3.2018-elem-mac-scope-b02c43f01a8862e3af90a0e7ea66dcab}
+
+Name
+
+:
+
+> mac:scope
+
+Description
+
+:
+
+```{=html}
+The specific data to which the acquisition information applies
+```
+### Sensing instrument {#iso19115-3.2018-elem-mac-sensingInstrument-86ced1fab519e44c3fcd7325f491ed88}
+
+Name
+
+:
+
+> mac:sensingInstrument
+
+Description
+
+:
+
+### Sensor {#iso19115-3.2018-elem-mac-sensor-147aa2dffb67eddc2fa663e4c90b9f11}
+
+Name
+
+:
+
+> mac:sensor
+
+Description
+
+:
+
+### Sequence {#iso19115-3.2018-elem-mac-sequence-cacb52f654bf50348861ff06567e0bfd}
+
+Name
+
+:
+
+> mac:sequence
+
+Description
+
+:
+
+```{=html}
+Relative time ordering of the event
+```
+### Significant event {#iso19115-3.2018-elem-mac-significantEvent-290296da36d2627f560e1627fbfda7dc}
+
+Name
+
+:
+
+> mac:significantEvent
+
+Description
+
+:
+
+### Solar azimuth {#iso19115-3.2018-elem-mac-solarAzimuth-4bcda66fb83091bd3da326421c027203}
+
+Name
+
+:
+
+> mac:solarAzimuth
+
+Description
+
+:
+
+```{=html}
+Clockwise angle in degrees from north to the centre of the sun’s disc.
+ Note: This angle is calculated from the nadir point of the sensor, not at the centre point of the image
+```
+### Solar elevation {#iso19115-3.2018-elem-mac-solarElevation-af60e0eceb072b322b47c7d7a52421ba}
+
+Name
+
+:
+
+> mac:solarElevation
+
+Description
+
+:
+
+```{=html}
+Angle between the horizon and the centre of the Sun’s disk
+```
+### Sponsor {#iso19115-3.2018-elem-mac-sponsor-6bc390be3142f1f2b7ef936b3f677d2d}
+
+Name
+
+:
+
+> mac:sponsor
+
+Description
+
+:
+
+### Status {#iso19115-3.2018-elem-mac-status-32c22a9cae01134bd1520ed5116bc066}
+
+Name
+
+:
+
+> mac:status
+
+Description
+
+:
+
+### Time {#iso19115-3.2018-elem-mac-time-d7340d3c53dd6d1afac0240f87395978}
+
+Name
+
+:
+
+> mac:time
+
+Description
+
+:
+
+### Trigger {#iso19115-3.2018-elem-mac-trigger-622d8aa6e371df3f548306153c8ed493}
+
+Name
+
+:
+
+> mac:trigger
+
+Description
+
+:
+
+### Type {#iso19115-3.2018-elem-mac-type-2ac10a6cc42a333f605f86a2d5dd90c6}
+
+Name
+
+:
+
+> mac:type
+
+Description
+
+:
+
+### Constraint language {#iso19115-3.2018-elem-mas-constraintLanguage-6714589d416dbd712eacbe4f41b27057}
+
+Name
+
+:
+
+> mas:constraintLanguage
+
+Description
+
+:
+
+```{=html}
+Formal language used in Application Schema
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Graphics file {#iso19115-3.2018-elem-mas-graphicsFile-c3962cc9dc571ea941923664d931e386}
+
+Name
+
+:
+
+> mas:graphicsFile
+
+Description
+
+:
+
+```{=html}
+Full application schema given as a graphics file
+```
+### Application Schema Information {#iso19115-3.2018-elem-mas-MD_ApplicationSchemaInformation-239070d65d62849e45f86b052fc4b371}
+
+Name
+
+:
+
+> mas:MD_ApplicationSchemaInformation
+
+Description
+
+:
+
+```{=html}
+Information about the application schema used to build the
+ dataset
+```
+### Name {#iso19115-3.2018-elem-mas-name-mas-MD_ApplicationSchemaInformation-286a47b5c1b4cb4c26a6c502e81eab33}
+
+Name
+
+:
+
+> mas:name
+
+Context
+
+:
+
+> mas:MD_ApplicationSchemaInformation
+
+Description
+
+:
+
+```{=html}
+Name of the application schema used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Schema ASCII {#iso19115-3.2018-elem-mas-schemaAscii-6a6918c5cca40db84b935a30a162f1fa}
+
+Name
+
+:
+
+> mas:schemaAscii
+
+Description
+
+:
+
+```{=html}
+Full application schema given as an ASCII file
+```
+### Schema language {#iso19115-3.2018-elem-mas-schemaLanguage-b9f9ab982f3e38f3100229b3919c7fe6}
+
+Name
+
+:
+
+> mas:schemaLanguage
+
+Description
+
+:
+
+```{=html}
+Identification of the schema language used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Software development file {#iso19115-3.2018-elem-mas-softwareDevelopmentFile-9ba5d58b0408fa64717c4af73681252e}
+
+Name
+
+:
+
+> mas:softwareDevelopmentFile
+
+Description
+
+:
+
+```{=html}
+Full application schema given as a software development file
+```
+### Software development file format {#iso19115-3.2018-elem-mas-softwareDevelopmentFileFormat-921ba1f4eea12ce9cfb2f5a735b547a8}
+
+Name
+
+:
+
+> mas:softwareDevelopmentFileFormat
+
+Description
+
+:
+
+```{=html}
+Software dependent format used for the application schema
+ software dependent
+ file
+```
+### Attribute instances {#iso19115-3.2018-elem-mcc-attributeInstances-c2c72bc14be935621cb9c3906b18aa81}
+
+Name
+
+:
+
+> mcc:attributeInstances
+
+Description
+
+:
+
+```{=html}
+Attribute instances to which the information applies
+```
+### Attributes {#iso19115-3.2018-elem-mcc-attributes-1b6aa85965648de38efe03ea2375ae57}
+
+Name
+
+:
+
+> mcc:attributes
+
+Description
+
+:
+
+```{=html}
+Attributes to which the information applies
+```
+### Authority {#iso19115-3.2018-elem-mcc-authority-7e7bc76f9f5323599c8181b4bc336579}
+
+Name
+
+:
+
+> mcc:authority
+
+Description
+
+:
+
+```{=html}
+Person or party responsible for maintenance of the namespace
+```
+### Code {#iso19115-3.2018-elem-mcc-code-2dc2af7f022e459d364d671a8820be3f}
+
+Name
+
+:
+
+> mcc:code
+
+Description
+
+:
+
+```{=html}
+Alphanumeric value identifying an instance in the namespace
+```
+```{=html}
+Alphanumeric value identifying an instance in the
+ namespace. NOTE Avoid characters that are not legal in URLs. EXAMPLE
+ EPSG::4326
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Codespace {#iso19115-3.2018-elem-mcc-codeSpace-1d595727b533966b906de29071e58024}
+
+Name
+
+:
+
+> mcc:codeSpace
+
+Description
+
+:
+
+```{=html}
+Name or identifier of the person or organization responsible
+ for
+ namespace
+```
+```{=html}
+Identifier or namespace in which the code is valid
+```
+Recommended values
+
+| code | label |
+|------|-------|
+| EPSG | EPSG |
+
+### Dataset {#iso19115-3.2018-elem-mcc-dataset-761bde17236898889de12474f6474d19}
+
+Name
+
+:
+
+> mcc:dataset
+
+Description
+
+:
+
+```{=html}
+Dataset to which the information applies
+```
+### Description {#iso19115-3.2018-elem-mcc-description-0a923100b3a1e6ae550b85f0a01ae8d7}
+
+Name
+
+:
+
+> mcc:description
+
+Description
+
+:
+
+```{=html}
+natural language description of the meaning of the
+ code value. EXAMPLE For codeSpace = EPSG, code= 4326, description =
+ WGS-84.
+```
+### Extent {#iso19115-3.2018-elem-mcc-extent-mcc-MD_Scope-9e1c7fbcc9cf379619506e011c40f92f}
+
+Name
+
+:
+
+> mcc:extent
+
+Context
+
+:
+
+> mcc:MD_Scope
+
+Description
+
+:
+
+```{=html}
+Information about the horizontal, vertical and temporal extent
+ of the data specified by the scope
+```
+### Feature instances {#iso19115-3.2018-elem-mcc-featureInstances-17bff6871ce84163c48f358d231b0856}
+
+Name
+
+:
+
+> mcc:featureInstances
+
+Description
+
+:
+
+```{=html}
+Feature instances to which the information applies
+```
+### Features {#iso19115-3.2018-elem-mcc-features-cd1d3790286adbd6dc53f82c201f23c1}
+
+Name
+
+:
+
+> mcc:features
+
+Description
+
+:
+
+```{=html}
+Features to which the information applies
+```
+### File description {#iso19115-3.2018-elem-mcc-fileDescription-b4c8b6a2ce9129eb824c8e8ed9463435}
+
+Name
+
+:
+
+> mcc:fileDescription
+
+Description
+
+:
+
+```{=html}
+Text description of the illustration
+```
+### File name {#iso19115-3.2018-elem-mcc-fileName-286b40df4c38bcadc32de27920d0ce50}
+
+Name
+
+:
+
+> mcc:fileName
+
+Description
+
+:
+
+```{=html}
+Name of the file that contains a graphic that provides an
+ illustration of the
+ dataset. It could be a public image document URL.
+```
+
+Condition
+
+:
+
+> mandatory
+
+### File type {#iso19115-3.2018-elem-mcc-fileType-f47a2fb159012c382d43688a0c9cca21}
+
+Name
+
+:
+
+> mcc:fileType
+
+Description
+
+:
+
+```{=html}
+Format in which the illustration is encoded
+```
+```{=html}
+Format in which the illustration is encoded Examples: EPS, GIF, JPEG,
+ PBM, PS,
+ TIFF, PDF
+```
+Recommended values
+
+| code | label |
+|------|-------|
+| EPS | EPS |
+| GIF | GIF |
+| JPEG | JPEG |
+| PNG | PNG |
+| PBM | PBM |
+| PS | PS |
+| TIFF | TIFF |
+| PDF | PDF |
+
+### Image constraints {#iso19115-3.2018-elem-mcc-imageConstraints-2d7c5a019e2366e90316111db4ab52dc}
+
+Name
+
+:
+
+> mcc:imageConstraints
+
+Description
+
+:
+
+```{=html}
+restriction on access and/or use of browse graphic
+```
+### Hierarchy level {#iso19115-3.2018-elem-mcc-level-7824a07e81fe2c038930823b13560140}
+
+Name
+
+:
+
+> mcc:level
+
+Description
+
+:
+
+```{=html}
+Hierarchical level of the data specified by the scope
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Level description {#iso19115-3.2018-elem-mcc-levelDescription-a3e2988d868514fc0ee95ad80a3c9cc0}
+
+Name
+
+:
+
+> mcc:levelDescription
+
+Description
+
+:
+
+```{=html}
+Detailed description about the level of the data specified by
+ the
+ scope
+```
+### Linkage {#iso19115-3.2018-elem-mcc-linkage-mcc-MD_BrowseGraphic-e51921d09bbc809d8d87caeaba6938f9}
+
+Name
+
+:
+
+> mcc:linkage
+
+Context
+
+:
+
+> mcc:MD_BrowseGraphic
+
+Description
+
+:
+
+```{=html}
+link to browse graphic
+```
+### Browse Graphic {#iso19115-3.2018-elem-mcc-MD_BrowseGraphic-5fedaf89e0cf7c798b88be661c7870a3}
+
+Name
+
+:
+
+> mcc:MD_BrowseGraphic
+
+Description
+
+:
+
+```{=html}
+Graphic that provides an illustration of the dataset (should
+ include a legend for the graphic)
+```
+```{=html}
+Graphic that provides an illustration of a resource
+ NOTE Should include a legend for the graphic, if applicable. EXAMPLE A
+ dataset, an organisation logo, security constraint or citation graphic.
+```
+### Identifier {#iso19115-3.2018-elem-mcc-MD_Identifier-f39fe5214b22e40dfa250c2d1c95eae0}
+
+Name
+
+:
+
+> mcc:MD_Identifier
+
+Description
+
+:
+
+```{=html}
+Value uniquely identifying an object within a namespace
+```
+### Status {#iso19115-3.2018-elem-mcc-MD_ProgressCode-27457369101e4cc3540e5d9cc6d5aa8f}
+
+Name
+
+:
+
+> mcc:MD_ProgressCode
+
+Description
+
+:
+
+### Standard codelists Status (mcc:MD_ProgressCode)
+
+| code | label | description |
+|-------------------|--------------------|--------------------------------------------------------------------------------------|
+| completed | Completed | Production of the data has been completed |
+| historicalArchive | Historical archive | Data has been stored in an offline storage facility |
+| obsolete | Obsolete | Data is no longer relevant |
+| onGoing | On going | Data is continually being updated |
+| planned | Planned | Fixed date has been established upon or by which the data will be created or updated |
+| required | Required | Data needs to be generated or updated |
+| underDevelopment | Under development | Data is currently in the process of being created |
+| final | Final | Progress concluded and no changes will be accepted |
+| pending | Pending | Committed to, but not yet addressed |
+| retired | Retired | Item is no longer recommended for use. It has not been superseded by another item |
+| superseded | Superseded | Replaced by new item |
+| tentative | Tentative | Provisional changes likely before resource becomes final or complete |
+| valid | Valid | Acceptable under specific conditions |
+| accepted | Accepted | Agreed to by sponsor |
+| notAccepted | Not Accepted | Rejected by sponsor |
+| withdrawn | Withdrawn | Withdrawn |
+| proposed | Proposed | Suggested that development needs to be undertaken |
+| deprecated | Deprecated | Resource superseded and will become obsolete, use only for historical purposes |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|-------------|--------------|-------------|
+| notobsolete | Not obsolete | |
+
+``` xml
+
+```
+
+### Scope {#iso19115-3.2018-elem-mcc-MD_Scope-3a2e1c3040c7203740b3178b8d9370b3}
+
+Name
+
+:
+
+> mcc:MD_Scope
+
+Description
+
+:
+
+```{=html}
+Class of information about the target resource and
+ physical extent for which information is reported
+```
+### Scope code {#iso19115-3.2018-elem-mcc-MD_ScopeCode-2f9ce057ea5e2205c2adee8624bac996}
+
+Name
+
+:
+
+> mcc:MD_ScopeCode
+
+Description
+
+:
+
+```{=html}
+Class of information to which the referencing entity applies
+```
+### Standard codelists Scope code (mcc:MD_ScopeCode)
+
+| code | label | description |
+|----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| attribute | Attribute | Information applies to the attribute class |
+| attributeType | Attribute type | Information applies to the characteristic of a feature |
+| collectionHardware | Collection hardware | Information applies to the collection hardware class |
+| collectionSession | Collection session | Information applies to the collection session |
+| dataset | Dataset | Information applies to the dataset |
+| series | Series | Information applies to the series |
+| nonGeographicDataset | Non geographic dataset | Information applies to non-geographic data |
+| dimensionGroup | Dimension group | Information applies to a dimension group |
+| feature | Feature | Information applies to a feature |
+| featureType | Feature type | Information applies to a feature type |
+| propertyType | Property type | Information applies to a property type |
+| fieldSession | Field session | Information applies to a field session |
+| software | Software | Information applies to a computer program or routine |
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+| model | Model | Information applies to a copy or imitation of an existing or hypothetical object |
+| tile | Tile | Information applies to a tile, a spatial subset of geographic data |
+| metadata | Metadata | Information applies to metadata |
+| initiative | Initiative | Information applies to an initiative |
+| sample | Sample | Information applies to a sample |
+| document | Document | Information applies to a document |
+| repository | Repository | Information applies to a repository |
+| aggregate | Aggregate | Information applies to an aggregate resource |
+| product | Product | Metadata describing an ISO 19131 data product specification |
+| collection | Collection | Information applies to an unstructured set |
+| coverage | Coverage | Information applies to a coverage |
+| application | Application | Information resource hosted on a specific set of hardware and accessible over a network |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|------------------------------|--------------------------------|-------------|
+| map staticMap interactiveMap | Map Static map Interactive map | |
+
+### Scope description {#iso19115-3.2018-elem-mcc-MD_ScopeDescription-7995800501eaf72f941d8e81542f8e98}
+
+Name
+
+:
+
+> mcc:MD_ScopeDescription
+
+Description
+
+:
+
+```{=html}
+Description of the class of information covered by the
+ information
+```
+
+Condition
+
+:
+
+> Either attributes, features, featureInstances, attributeInstnaces, dataset or other must be provided
+
+### Scope description {#iso19115-3.2018-elem-mcc-MD_ScopeDescription_Type-e5f6e8be7b7d7e196f4bbdfbb3c51a9c}
+
+Name
+
+:
+
+> mcc:MD_ScopeDescription_Type
+
+Description
+
+:
+
+```{=html}
+Description of the class of information covered by the
+ information
+```
+
+Condition
+
+:
+
+> Either attributes, features, featureInstances, attributeInstnaces, dataset or other must be provided
+
+### Spatial Representation Type {#iso19115-3.2018-elem-mcc-MD_SpatialRepresentationTypeCode-31b02e6b3fa659af6d7f3bae53ccb6a2}
+
+Name
+
+:
+
+> mcc:MD_SpatialRepresentationTypeCode
+
+Description
+
+:
+
+### Standard codelists Spatial Representation Type (mcc:MD_SpatialRepresentationTypeCode)
+
+| code | label | description |
+|-------------|--------------|----------------------------------------------------------------------------------------------------|
+| vector | Vector | Vector data is used to represent geographic data |
+| grid | Grid | Grid data is used to represent geographic data |
+| textTable | Text, table | Textual or tabular data is used to represent geographic data |
+| tin | TIN | Triangulated irregular network |
+| stereoModel | Stereo model | Three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images |
+| video | Video | Scene from a video recording |
+
+``` xml
+
+```
+
+### Other {#iso19115-3.2018-elem-mcc-other-0d4f5c50da1b8c13a103dc016e5c4255}
+
+Name
+
+:
+
+> mcc:other
+
+Description
+
+:
+
+```{=html}
+Class of information that does not fall into the other
+ categories to which the
+ information applies
+```
+### URI {#iso19115-3.2018-elem-mcc-URI-c4a96ada6291119a71dedb4fa821fe83}
+
+Name
+
+:
+
+> mcc:URI
+
+Description
+
+:
+
+### Version {#iso19115-3.2018-elem-mcc-version-mcc-MD_Identifier-e51f35d9b386584a92603051050142b7}
+
+Name
+
+:
+
+> mcc:version
+
+Context
+
+:
+
+> mcc:MD_Identifier
+
+Description
+
+:
+
+```{=html}
+version identifier for the namespace
+```
+### Access constraints {#iso19115-3.2018-elem-mco-accessConstraints-4434175ab3a8a6536daed140ccea3129}
+
+Name
+
+:
+
+> mco:accessConstraints
+
+Description
+
+:
+
+```{=html}
+Access constraints applied to assure the protection of privacy
+ or intellectual
+ property, and any special restrictions or limitations on obtaining the
+ resource
+```
+``` xml
+
+
+
+```
+
+### Addressee {#iso19115-3.2018-elem-mco-addressee-mco-MD_Releasability-6b109e079fa7b6014b3d6746221d694b}
+
+Name
+
+:
+
+> mco:addressee
+
+Context
+
+:
+
+> mco:MD_Releasability
+
+Description
+
+:
+
+```{=html}
+party to which the release statement applies
+```
+### Classification {#iso19115-3.2018-elem-mco-classification-e17c62f61fd7efcb2183fbbb83922018}
+
+Name
+
+:
+
+> mco:classification
+
+Description
+
+:
+
+```{=html}
+Name of the handling restrictions on the resource or metadata
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Classification system {#iso19115-3.2018-elem-mco-classificationSystem-16a2730ef6db9ca4295ef332b221b3c4}
+
+Name
+
+:
+
+> mco:classificationSystem
+
+Description
+
+:
+
+```{=html}
+Name of the classification system
+```
+### Constraint application scope {#iso19115-3.2018-elem-mco-constraintApplicationScope-f10f04ce2d0209c0bab3f67d865cb084}
+
+Name
+
+:
+
+> mco:constraintApplicationScope
+
+Description
+
+:
+
+```{=html}
+Spatial and/or temporal extent and or level of the application
+ of the constraint restrictions
+```
+### Constraints of dissemination {#iso19115-3.2018-elem-mco-disseminationConstraints-mco-MD_Releasability-5c7a4a52cd05e52596ded12c6b653cb4}
+
+Name
+
+:
+
+> mco:disseminationConstraints
+
+Context
+
+:
+
+> mco:MD_Releasability
+
+Description
+
+:
+
+```{=html}
+Component in determining releasability
+```
+### Graphic {#iso19115-3.2018-elem-mco-graphic-787e1689b35d8928184c1b5bbd16ed01}
+
+Name
+
+:
+
+> mco:graphic
+
+Description
+
+:
+
+```{=html}
+Graphic /symbol indicating the constraint
+```
+### Handling description {#iso19115-3.2018-elem-mco-handlingDescription-7fba7a0ac032339d0c1b1886a1389060}
+
+Name
+
+:
+
+> mco:handlingDescription
+
+Description
+
+:
+
+```{=html}
+Additional information about the restrictions on handling the
+ resource
+```
+### Constraints {#iso19115-3.2018-elem-mco-MD_Constraints-33996fc2b6dc952cdf62806ef26202c2}
+
+Name
+
+:
+
+> mco:MD_Constraints
+
+Description
+
+:
+
+```{=html}
+Restrictions on the access and use of a resource or metadata
+```
+### Legal constraints {#iso19115-3.2018-elem-mco-MD_LegalConstraints-238a415897a1738a0d8b0e2e3c9bfd96}
+
+Name
+
+:
+
+> mco:MD_LegalConstraints
+
+Description
+
+:
+
+```{=html}
+Restrictions and legal prerequisites for accessing and using
+ the resource or
+ metadata
+```
+### Releasability {#iso19115-3.2018-elem-mco-MD_Releasability-88ac438bcff297d513b5fd666d45c824}
+
+Name
+
+:
+
+> mco:MD_Releasability
+
+Description
+
+:
+
+```{=html}
+information about resource release constraints
+```
+### Access constraints {#iso19115-3.2018-elem-mco-MD_RestrictionCode-mco-accessConstraints-060503bb481a7679abdc9347b485cd8a}
+
+Name
+
+:
+
+> mco:MD_RestrictionCode
+
+Context
+
+:
+
+> mco:accessConstraints
+
+Description
+
+:
+
+### Standard codelists Access constraints (mco:MD_RestrictionCode)
+
+| code | label | description |
+|----------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| copyright | Copyright | Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor |
+| patent | Patent | Government has granted exclusive right to make, sell, use or license an invention or discovery |
+| patentPending | Pending patent | Produced or sold information awaiting a patent |
+| trademark | Trademark | A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer |
+| license | License | Formal permission to do something |
+| intellectualPropertyRights | Intellectual property rights | Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity |
+| restricted | Restricted | Withheld from general circulation or disclosure |
+| otherRestrictions | Other restrictions | Limitation not listed |
+| unrestricted | Unrestricted | No constraints exist |
+| licenceUnrestricted | Licence Unrestricted | formal permission not required to use the resource |
+| licenceEndUser | Licence End User | Formal permission required for a person or an entity to use the resource and that may differ from the person that orders or purchases it |
+| licenceDistributor | Licence Distributor | Formal permission required for a person or an entity to commercialize or distribute the resource |
+| private | Private | Protects rights of individual or organisations from observation, intrusion, or attention of others |
+| statutory | Statutory | Prescribed by law |
+| confidential | Confidential | Not available to the public. NOTE: Contains information that could be prejudicial to a commercial, industrial, or national interest |
+| SBU | Sensitive But Unclassified | Although unclassified, requires strict controls over its distribution |
+| in-confidence | In-Confidence | With trust |
+
+### Security constraints {#iso19115-3.2018-elem-mco-MD_SecurityConstraints-efee55f2eb2d70f01eed428298e807ca}
+
+Name
+
+:
+
+> mco:MD_SecurityConstraints
+
+Description
+
+:
+
+```{=html}
+Handling restrictions imposed on the resource or metadata for
+ national security
+ or similar security concerns
+```
+### Other constraints {#iso19115-3.2018-elem-mco-otherConstraints-ee6f8fc54e0aa9767312008217583cec}
+
+Name
+
+:
+
+> mco:otherConstraints
+
+Description
+
+:
+
+```{=html}
+Other restrictions and legal prerequisites for accessing and using the
+ resource
+```
+
+Condition
+
+:
+
+> conditional
+
+### Référence {#iso19115-3.2018-elem-mco-reference-be92d9dc3eac6458ea063c8b4e4d16e0}
+
+Name
+
+:
+
+> mco:reference
+
+Description
+
+:
+
+```{=html}
+citation for the limitation or constraint EXAMPLE
+ Copyright statement,licence agreement, etc.
+```
+### Releasability {#iso19115-3.2018-elem-mco-releasability-45662b1e4d3b7b93ffac2cacd9e20d8f}
+
+Name
+
+:
+
+> mco:releasability
+
+Description
+
+:
+
+```{=html}
+information concerning the parties to whom the
+ resource can or cannot be released
+```
+### Party responsible {#iso19115-3.2018-elem-mco-responsibleParty-47b9fb4016b7f424d783277a602b5819}
+
+Name
+
+:
+
+> mco:responsibleParty
+
+Description
+
+:
+
+```{=html}
+Party responsible for the resource constraints
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Statement {#iso19115-3.2018-elem-mco-statement-mco-MD_Releasability-7986cf3965f16774710c30022ed20228}
+
+Name
+
+:
+
+> mco:statement
+
+Context
+
+:
+
+> mco:MD_Releasability
+
+Description
+
+:
+
+```{=html}
+Release statement
+```
+### Use constraints {#iso19115-3.2018-elem-mco-useConstraints-a78891e6df6724f942e929e70f301fa3}
+
+Name
+
+:
+
+> mco:useConstraints
+
+Description
+
+:
+
+```{=html}
+Constraints applied to assure the protection of privacy or
+ intellectual
+ property, and any special restrictions or limitations or warnings on using
+ the
+ resource
+```
+``` xml
+
+
+
+```
+
+### Use limitation {#iso19115-3.2018-elem-mco-useLimitation-40f33cf5aed3dcaded9c6b9b6893a17a}
+
+Name
+
+:
+
+> mco:useLimitation
+
+Description
+
+:
+
+```{=html}
+Limitation affecting the fitness for use of the resource. Example, _not to be
+ used for navigation_
+```
+``` xml
+
+ Conditions d'accès et d'utilisation
+
+```
+
+### User note {#iso19115-3.2018-elem-mco-userNote-e0170adc40a3e38bc167e63c55773149}
+
+Name
+
+:
+
+> mco:userNote
+
+Description
+
+:
+
+```{=html}
+Explanation of the application of the legal constraints or
+ other restrictions
+ and legal prerequisites for obtaining and using the resource or metadata
+```
+### Acquisition information {#iso19115-3.2018-elem-mdb-acquisitionInformation-ce87174a305975fd6ab50c76fa062e87}
+
+Name
+
+:
+
+> mdb:acquisitionInformation
+
+Description
+
+:
+
+### Alternative metadata reference {#iso19115-3.2018-elem-mdb-alternativeMetadataReference-d658e4e78b4bb85f325070dac38656f2}
+
+Name
+
+:
+
+> mdb:alternativeMetadataReference
+
+Description
+
+:
+
+```{=html}
+Reference to alternative metadata, e.g Dublin Core,
+ FGDC, or metadata in a non-ISO standard for the same resource
+```
+### Application schema info {#iso19115-3.2018-elem-mdb-applicationSchemaInfo-6e29d5e06caa68d593c2abc867db859e}
+
+Name
+
+:
+
+> mdb:applicationSchemaInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the conceptual schema of a dataset
+```
+### Contact {#iso19115-3.2018-elem-mdb-contact-bd86ee4331a33e4a09966e9d3837b346}
+
+Name
+
+:
+
+> mdb:contact
+
+Description
+
+:
+
+```{=html}
+Party responsible for the metadata information
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+
+
+
+
+
+ Organisation
+
+
+
+
+
+
+ mail@organisation.org
+
+
+
+
+
+
+
+
+
+```
+
+### Content Information {#iso19115-3.2018-elem-mdb-contentInfo-477f3b1af76890ee3158c66524002fd8}
+
+Name
+
+:
+
+> mdb:contentInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the feature catalogue and describes
+ the coverage and
+ image data characteristics
+```
+### Data quality info {#iso19115-3.2018-elem-mdb-dataQualityInfo-05c1cd27fb52b7bc5c361a03fb962e72}
+
+Name
+
+:
+
+> mdb:dataQualityInfo
+
+Description
+
+:
+
+```{=html}
+Provides overall assessment of quality of a resource(s)
+```
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+
+
+
+
+
+```
+
+### Date info {#iso19115-3.2018-elem-mdb-dateInfo-74b8e273fbd6b264ff0c70ca542b6fa3}
+
+Name
+
+:
+
+> mdb:dateInfo
+
+Description
+
+:
+
+```{=html}
+Date(s) associated with the metadata. NOTE Creation”
+ date must be provided, others can also be provided
+```
+### Default locale {#iso19115-3.2018-elem-mdb-defaultLocale-dd848d0de1837131c70510c4ab1253b4}
+
+Name
+
+:
+
+> mdb:defaultLocale
+
+Description
+
+:
+
+```{=html}
+Language and character set used for documenting
+ metadata
+```
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+### Distribution Information {#iso19115-3.2018-elem-mdb-distributionInfo-26e7e205c5605edb7225b0aa5c3950f1}
+
+Name
+
+:
+
+> mdb:distributionInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the distributor of and options for
+ obtaining the
+ resource(s)
+```
+``` xml
+
+
+
+
+
+
+
+ ESRI Shapefile
+
+
+
+ 1.0
+
+
+
+
+
+
+
+
+
+
+ https://geoservices.wallonie.be/inspire/atom/PS_Service.xml
+
+
+ atom:feed
+
+
+ Service de téléchargement ATOM Feed - Inspire
+
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+
+
+
+
+
+
+
+
+
+```
+
+### Identification info {#iso19115-3.2018-elem-mdb-identificationInfo-7b3f7b7fbb8a986c92658058fe54f876}
+
+Name
+
+:
+
+> mdb:identificationInfo
+
+Description
+
+:
+
+```{=html}
+Basic information about the resource(s) to which the metadata
+ applies
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+
+ Description du jeu de données
+
+
+
+
+
+
+
+
+
+
+
+
+ Organisation
+
+
+
+
+
+
+ mail@organisation.org
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 25000
+
+
+
+
+
+
+ biota
+
+
+ environment
+
+
+
+
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Protected site
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ GEMET themes
+
+
+
+
+ 2009-09-22
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Natura 2000 sites (Birds Directive)
+
+
+
+
+
+
+
+ INSPIRE priority data set
+
+
+
+
+ 2018-04-24
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ No
+ limitations to public access
+
+
+
+
+
+
+ Conditions d'accès et d'utilisation
+
+
+
+
+
+ Description des autres contraintes (eg. CGI, Licence)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### Metadata {#iso19115-3.2018-elem-mdb-MD_Metadata-2a52ffbcceba76f90e734fdd465035a1}
+
+Name
+
+:
+
+> mdb:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Root entity which defines metadata about a resource or
+ resources
+```
+``` xml
+
+
+
+
+ 6d50311c-3ffd-4c09-aa0b-fe9ab1bb93fa
+
+
+ urn:uuid
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Organisation
+
+
+
+
+
+
+ mail@organisation.org
+
+
+
+
+
+
+
+
+
+
+
+
+ 2019-10-07T13:35:35
+
+
+
+
+
+
+
+
+
+ 2019-09-20T15:52:19
+
+
+ creation
+
+
+
+
+
+
+ ISO 19115
+
+
+ 2003/Cor 1:2006
+
+
+
+
+
+
+ http://localhost:8080/geonetwork/srv/eng//metadata/6d50311c-3ffd-4c09-aa0b-fe9ab1bb93fa
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3035
+
+
+
+
+
+
+
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+
+ Description du jeu de données
+
+
+
+
+
+
+
+
+
+
+
+
+ Organisation
+
+
+
+
+
+
+ mail@organisation.org
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 25000
+
+
+
+
+
+
+ biota
+
+
+ environment
+
+
+
+
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Protected site
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ GEMET themes
+
+
+
+
+ 2009-09-22
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Natura 2000 sites (Birds Directive)
+
+
+
+
+
+
+
+ INSPIRE priority data set
+
+
+
+
+ 2018-04-24
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ No
+ limitations to public access
+
+
+
+
+
+
+ Conditions d'accès et d'utilisation
+
+
+
+
+
+ Description des autres contraintes (eg. CGI, Licence)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ESRI Shapefile
+
+
+
+ 1.0
+
+
+
+
+
+
+
+
+
+
+ https://geoservices.wallonie.be/inspire/atom/PS_Service.xml
+
+
+ atom:feed
+
+
+ Service de téléchargement ATOM Feed - Inspire
+
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+
+
+
+
+
+
+
+
+ Généalogie du jeu de données
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### Hierarchy level {#iso19115-3.2018-elem-mdb-MD_MetadataScope-51fe8da3ee06d996c5cb057ea86d4341}
+
+Name
+
+:
+
+> mdb:MD_MetadataScope
+
+Description
+
+:
+
+```{=html}
+Scope to which the metadata applies (see annex H for more
+ information about
+ metadata hierarchy levels)
+```
+``` xml
+
+
+
+
+
+```
+
+### Resource scope {#iso19115-3.2018-elem-mdb-MD_MetadataScoperd-a377c6e12454a013ffc0c05045d2ff20}
+
+Name
+
+:
+
+> mdb:MD_MetadataScoperd
+
+Description
+
+:
+
+```{=html}
+Information about the scope of the resource.
+```
+### Metadata constraints {#iso19115-3.2018-elem-mdb-metadataConstraints-cd13aab243e8cf8b0009f3c2cc6288a6}
+
+Name
+
+:
+
+> mdb:metadataConstraints
+
+Description
+
+:
+
+```{=html}
+Provides restrictions on the access and use of metadata
+```
+### Metadata Extension Information {#iso19115-3.2018-elem-mdb-metadataExtensionInfo-04e7d4f2e4caa82c3ee3957e01387b10}
+
+Name
+
+:
+
+> mdb:metadataExtensionInfo
+
+Description
+
+:
+
+```{=html}
+Information describing metadata extensions
+```
+### Metadata identifier {#iso19115-3.2018-elem-mdb-metadataIdentifier-a4b2a53a6ba91300cd824aaa32dced12}
+
+Name
+
+:
+
+> mdb:metadataIdentifier
+
+Description
+
+:
+
+```{=html}
+Unique identifier for this metadata file
+```
+``` xml
+
+
+
+ 6d50311c-3ffd-4c09-aa0b-fe9ab1bb93fa
+
+
+ urn:uuid
+
+
+
+```
+
+### Metadata linkage {#iso19115-3.2018-elem-mdb-metadataLinkage-582ff009f1d12392ca0be7e310ace58b}
+
+Name
+
+:
+
+> mdb:metadataLinkage
+
+Description
+
+:
+
+```{=html}
+Online location where the metadata is available
+```
+``` xml
+
+
+
+ http://localhost:8080/geonetwork/srv/eng//metadata/6d50311c-3ffd-4c09-aa0b-fe9ab1bb93fa
+
+
+
+
+
+
+```
+
+### Metadata maintenance {#iso19115-3.2018-elem-mdb-metadataMaintenance-f31a9a9880a6a939b8125c2505a04439}
+
+Name
+
+:
+
+> mdb:metadataMaintenance
+
+Description
+
+:
+
+```{=html}
+Provides information about the frequency of metadata updates,
+ and the scope of
+ those updates
+```
+### Metadata profile {#iso19115-3.2018-elem-mdb-metadataProfile-92627fbcc80493116a75b90146bcf055}
+
+Name
+
+:
+
+> mdb:metadataProfile
+
+Description
+
+:
+
+### Type of resource {#iso19115-3.2018-elem-mdb-metadataScope-85ce83354003a98ad94f8f749af858f7}
+
+Name
+
+:
+
+> mdb:metadataScope
+
+Description
+
+:
+
+```{=html}
+Type of resource for which metadata is provided
+```
+``` xml
+
+
+
+
+
+
+
+```
+
+### Metadata standard {#iso19115-3.2018-elem-mdb-metadataStandard-317906f5ed0893d367c6a78ab2d68812}
+
+Name
+
+:
+
+> mdb:metadataStandard
+
+Description
+
+:
+
+```{=html}
+Citation for the standard to which the metadata
+ conforms. NOTE Metadata standard citations should include an identifier.
+```
+``` xml
+
+
+
+ ISO 19115
+
+
+ 2003/Cor 1:2006
+
+
+
+```
+
+### Name {#iso19115-3.2018-elem-mdb-name-66f58b43b2635c779b3af02b3a9748e5}
+
+Name
+
+:
+
+> mdb:name
+
+Description
+
+:
+
+```{=html}
+Description of the scope.
+```
+
+Condition
+
+:
+
+> optional
+
+### Other locale {#iso19115-3.2018-elem-mdb-otherLocale-f4f26265136a3b0812c2ce9d90c0c17f}
+
+Name
+
+:
+
+> mdb:otherLocale
+
+Description
+
+:
+
+```{=html}
+Provides information about alternatively used
+ localised character strings
+```
+### Parent metadata {#iso19115-3.2018-elem-mdb-parentMetadata-d82be96796ed0eaaa63a697cfec1287a}
+
+Name
+
+:
+
+> mdb:parentMetadata
+
+Description
+
+:
+
+```{=html}
+Identification of the parent metadata record
+```
+### Portrayal catalogue info {#iso19115-3.2018-elem-mdb-portrayalCatalogueInfo-f6c73fdd3d7c18f1e90d4a8853986230}
+
+Name
+
+:
+
+> mdb:portrayalCatalogueInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the catalogue of rules defined for
+ the portrayal of
+ a resource(s)
+```
+### Reference System Information {#iso19115-3.2018-elem-mdb-referenceSystemInfo-6e40de8cf9dbe75d0601aedf78756344}
+
+Name
+
+:
+
+> mdb:referenceSystemInfo
+
+Description
+
+:
+
+```{=html}
+Description of the spatial and temporal reference systems used
+ in the
+ dataset
+```
+``` xml
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3035
+
+
+
+
+
+```
+
+### Resource lineage {#iso19115-3.2018-elem-mdb-resourceLineage-b38f8fe2e0d2dee771b11f2dfcb77937}
+
+Name
+
+:
+
+> mdb:resourceLineage
+
+Description
+
+:
+
+```{=html}
+Information about the provenance, source(s), and/or
+ the production process(es) applied to the resource
+```
+``` xml
+
+
+
+ Généalogie du jeu de données
+
+
+
+
+
+
+
+
+
+
+```
+
+### Resource scope {#iso19115-3.2018-elem-mdb-resourceScope-4c3f10bfb66b2ced01f50b3f1f71d4dc}
+
+Name
+
+:
+
+> mdb:resourceScope
+
+Description
+
+:
+
+```{=html}
+Code for the scope.
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+```
+
+### Spatial representation info {#iso19115-3.2018-elem-mdb-spatialRepresentationInfo-fa98674c3f9afa7324634c07cda62b3b}
+
+Name
+
+:
+
+> mdb:spatialRepresentationInfo
+
+Description
+
+:
+
+```{=html}
+Digital representation of spatial information in the dataset
+```
+### Abstract {#iso19115-3.2018-elem-mdq-abstract-fca818cec40fe2f6148cf5424c4a90c6}
+
+Name
+
+:
+
+> mdq:abstract
+
+Description
+
+:
+
+### Date time {#iso19115-3.2018-elem-mdq-dateTime-e5096902a7314e76382ac0f08d866277}
+
+Name
+
+:
+
+> mdq:dateTime
+
+Description
+
+:
+
+### Deductive source {#iso19115-3.2018-elem-mdq-deductiveSource-5831020c420d98cef9262f352dbfcd50}
+
+Name
+
+:
+
+> mdq:deductiveSource
+
+Description
+
+:
+
+```{=html}
+Information on which data are used as
+ sources in deductive evaluation method
+```
+### Derived element {#iso19115-3.2018-elem-mdq-derivedElement-f4c2ee6a8acedce6cfb84f98ec17f06e}
+
+Name
+
+:
+
+> mdq:derivedElement
+
+Description
+
+:
+
+### Absolute external positional accuracy {#iso19115-3.2018-elem-mdq-DQ_AbsoluteExternalPositionalAccuracy-8bcd872552f871a19dce36d6bc7e8700}
+
+Name
+
+:
+
+> mdq:DQ_AbsoluteExternalPositionalAccuracy
+
+Description
+
+:
+
+```{=html}
+Closeness of reported coordinate values to values accepted as
+ or being
+ true
+```
+### Accuracy of time measurement {#iso19115-3.2018-elem-mdq-DQ_AccuracyOfATimeMeasurement-8d3752286366dd7dff87ad296ad7c413}
+
+Name
+
+:
+
+> mdq:DQ_AccuracyOfATimeMeasurement
+
+Description
+
+:
+
+```{=html}
+Correctness of the temporal references of an item (reporting of
+ error in time
+ measurement)
+```
+### Aggregation derivation {#iso19115-3.2018-elem-mdq-DQ_AggregationDerivation-ec544a1c126234ec85e6650ee644a702}
+
+Name
+
+:
+
+> mdq:DQ_AggregationDerivation
+
+Description
+
+:
+
+### Completeness commission {#iso19115-3.2018-elem-mdq-DQ_CompletenessCommission-0dd42a0ab10753452a3199c28fc5599c}
+
+Name
+
+:
+
+> mdq:DQ_CompletenessCommission
+
+Description
+
+:
+
+```{=html}
+Excess data present in the dataset, as described by the scope
+```
+### Completeness omission {#iso19115-3.2018-elem-mdq-DQ_CompletenessOmission-9f6df725bfe69d1f3664bdde5916ea83}
+
+Name
+
+:
+
+> mdq:DQ_CompletenessOmission
+
+Description
+
+:
+
+```{=html}
+Data absent from the dataset, as described by the scope
+```
+### Conceptual consistency {#iso19115-3.2018-elem-mdq-DQ_ConceptualConsistency-eb99a1efe55b65f59083813a036e4ecf}
+
+Name
+
+:
+
+> mdq:DQ_ConceptualConsistency
+
+Description
+
+:
+
+```{=html}
+Adherence to rules of the conceptual schema
+```
+### Metaquality / Confidence {#iso19115-3.2018-elem-mdq-DQ_Confidence-00d5fd5323b9dff53e6e4d6613946c29}
+
+Name
+
+:
+
+> mdq:DQ_Confidence
+
+Description
+
+:
+
+```{=html}
+Trustworthiness of a data quality result.
+```
+### Conformance result {#iso19115-3.2018-elem-mdq-DQ_ConformanceResult-070bb6852050a16c31715ecb6aa09f84}
+
+Name
+
+:
+
+> mdq:DQ_ConformanceResult
+
+Description
+
+:
+
+```{=html}
+Information about the outcome of evaluating
+ the obtained value (or set of values) against a
+ specified acceptable conformance quality
+ level
+```
+``` xml
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+```
+
+### Data inspection {#iso19115-3.2018-elem-mdq-DQ_DataInspection-f2e9ffb22ebdaddde326ffa11dac81ef}
+
+Name
+
+:
+
+> mdq:DQ_DataInspection
+
+Description
+
+:
+
+### Data quality {#iso19115-3.2018-elem-mdq-DQ_DataQuality-b969b0659a4303d9c1d35e4757ac62b3}
+
+Name
+
+:
+
+> mdq:DQ_DataQuality
+
+Description
+
+:
+
+```{=html}
+Quality information for the data specified by a data quality
+ scope
+```
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+
+
+
+
+```
+
+### Descriptive result {#iso19115-3.2018-elem-mdq-DQ_DescriptiveResult-0191aad06a8d885f697f59296d80b017}
+
+Name
+
+:
+
+> mdq:DQ_DescriptiveResult
+
+Description
+
+:
+
+```{=html}
+Data quality descriptive result
+```
+### Domain consistency {#iso19115-3.2018-elem-mdq-DQ_DomainConsistency-c1ef69d6172610098aba6ed8e5b38a88}
+
+Name
+
+:
+
+> mdq:DQ_DomainConsistency
+
+Description
+
+:
+
+```{=html}
+Adherence of values to the value domains
+```
+``` xml
+
+
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+
+
+```
+
+### Evaluation method {#iso19115-3.2018-elem-mdq-DQ_EvaluationMethod-53191928f6b3e447e7e5200f6f9faf7b}
+
+Name
+
+:
+
+> mdq:DQ_EvaluationMethod
+
+Description
+
+:
+
+### Format consistency {#iso19115-3.2018-elem-mdq-DQ_FormatConsistency-8b5f34fa2b437f53829de2f084c0d3e8}
+
+Name
+
+:
+
+> mdq:DQ_FormatConsistency
+
+Description
+
+:
+
+```{=html}
+Degree to which data is stored in accordance with the physical
+ structure of the
+ dataset, as described by the scope
+```
+### Full inspection {#iso19115-3.2018-elem-mdq-DQ_FullInspection-de21b3a5be286e24d1fdec85ffb1b319}
+
+Name
+
+:
+
+> mdq:DQ_FullInspection
+
+Description
+
+:
+
+### Gridded data positional accuracy {#iso19115-3.2018-elem-mdq-DQ_GriddedDataPositionalAccuracy-6d18be23581ad90ef59f83b6bf5a4cf5}
+
+Name
+
+:
+
+> mdq:DQ_GriddedDataPositionalAccuracy
+
+Description
+
+:
+
+```{=html}
+Closeness of gridded data position values to values accepted as
+ or being
+ true
+```
+### Metaquality / Homogeneity {#iso19115-3.2018-elem-mdq-DQ_Homogeneity-180b944deee523419756c21b2194bb4d}
+
+Name
+
+:
+
+> mdq:DQ_Homogeneity
+
+Description
+
+:
+
+```{=html}
+Expected or tested uniformity of the results obtained for a
+ data quality evaluation.
+```
+### Indirect evaluation {#iso19115-3.2018-elem-mdq-DQ_IndirectEvaluation-e1a02547fc4a7b62e5408257b4a9a33d}
+
+Name
+
+:
+
+> mdq:DQ_IndirectEvaluation
+
+Description
+
+:
+
+### Measure reference {#iso19115-3.2018-elem-mdq-DQ_MeasureReference-b2f194226c538d01f7e1336f76fc0b24}
+
+Name
+
+:
+
+> mdq:DQ_MeasureReference
+
+Description
+
+:
+
+### Non quantitative attribute accuracy {#iso19115-3.2018-elem-mdq-DQ_NonQuantitativeAttributeAccuracy-a6eb7ec155510e83e271bb09695d3e4f}
+
+Name
+
+:
+
+> mdq:DQ_NonQuantitativeAttributeAccuracy
+
+Description
+
+:
+
+```{=html}
+Correctness of non-quantitative attributes
+```
+### Non quantitative attribute correctness {#iso19115-3.2018-elem-mdq-DQ_NonQuantitativeAttributeCorrectness-e1763f4a806bc415f75649d03e74e3bc}
+
+Name
+
+:
+
+> mdq:DQ_NonQuantitativeAttributeCorrectness
+
+Description
+
+:
+
+### Quantitative attribute accuracy {#iso19115-3.2018-elem-mdq-DQ_QuantitativeAttributeAccuracy-239216433c75c857c4138b0b58c352ab}
+
+Name
+
+:
+
+> mdq:DQ_QuantitativeAttributeAccuracy
+
+Description
+
+:
+
+```{=html}
+Accuracy of quantitative attributes
+```
+### Quantitative result {#iso19115-3.2018-elem-mdq-DQ_QuantitativeResult-e4aa4d6aa466082557a0e3ffcc2c9a57}
+
+Name
+
+:
+
+> mdq:DQ_QuantitativeResult
+
+Description
+
+:
+
+```{=html}
+The values or information about the value(s) (or set of values)
+ obtained from
+ applying a data quality measure
+```
+### Relative internal positional accuracy {#iso19115-3.2018-elem-mdq-DQ_RelativeInternalPositionalAccuracy-e4a653fe1414c1411957fc3952382400}
+
+Name
+
+:
+
+> mdq:DQ_RelativeInternalPositionalAccuracy
+
+Description
+
+:
+
+```{=html}
+Closeness of the relative positions of features in the scope to
+ their
+ respective relative positions accepted as or being true
+```
+### Metaquality / Representativity {#iso19115-3.2018-elem-mdq-DQ_Representativity-10240a1df9c53d02ddecae55fbafdbed}
+
+Name
+
+:
+
+> mdq:DQ_Representativity
+
+Description
+
+:
+
+```{=html}
+Degree to which the sample used has produced a result which is
+ representative of the
+ data within the data quality scope
+```
+### Sample based inspection {#iso19115-3.2018-elem-mdq-DQ_SampleBasedInspection-c33d13f764fa09dfb5a475d6e7195bdf}
+
+Name
+
+:
+
+> mdq:DQ_SampleBasedInspection
+
+Description
+
+:
+
+### Standalone quality report information {#iso19115-3.2018-elem-mdq-DQ_StandaloneQualityReportInformation-b121dac5f5592e3a9bb1a99b3a062d8d}
+
+Name
+
+:
+
+> mdq:DQ_StandaloneQualityReportInformation
+
+Description
+
+:
+
+### Temporal consistency {#iso19115-3.2018-elem-mdq-DQ_TemporalConsistency-0d4957b3d0b9c0dd8cca38734eb41fdf}
+
+Name
+
+:
+
+> mdq:DQ_TemporalConsistency
+
+Description
+
+:
+
+```{=html}
+Correctness of ordered events or sequences, if reported
+```
+### Temporal validity {#iso19115-3.2018-elem-mdq-DQ_TemporalValidity-99a32e6469000326870fa96cdada6a0d}
+
+Name
+
+:
+
+> mdq:DQ_TemporalValidity
+
+Description
+
+:
+
+```{=html}
+Validity of data specified by the scope with respect to time
+```
+### Thematic classification correctness {#iso19115-3.2018-elem-mdq-DQ_ThematicClassificationCorrectness-918c902da0e32c6f77178fcd97d60564}
+
+Name
+
+:
+
+> mdq:DQ_ThematicClassificationCorrectness
+
+Description
+
+:
+
+```{=html}
+Comparison of the classes assigned to features or their
+ attributes to a
+ universe of discourse
+```
+### Topological consistency {#iso19115-3.2018-elem-mdq-DQ_TopologicalConsistency-fa568b7fed7969dafdabfbcbdcfe0232}
+
+Name
+
+:
+
+> mdq:DQ_TopologicalConsistency
+
+Description
+
+:
+
+```{=html}
+Correctness of the explicitly encoded topological
+ characteristics of the
+ dataset as described by the scope
+```
+### Usability element {#iso19115-3.2018-elem-mdq-DQ_UsabilityElement-595e258aadfc90d614ad2b18937f035f}
+
+Name
+
+:
+
+> mdq:DQ_UsabilityElement
+
+Description
+
+:
+
+### Element report {#iso19115-3.2018-elem-mdq-elementReport-3cab2d79e4788afae28f563eb6f2be3a}
+
+Name
+
+:
+
+> mdq:elementReport
+
+Description
+
+:
+
+### Evaluation method {#iso19115-3.2018-elem-mdq-evaluationMethod-7861233af309ce32dbd0720123144e93}
+
+Name
+
+:
+
+> mdq:evaluationMethod
+
+Description
+
+:
+
+### Evaluation method description {#iso19115-3.2018-elem-mdq-evaluationMethodDescription-8d6e04e7fe7c9f9d3bce27ee81f522cf}
+
+Name
+
+:
+
+> mdq:evaluationMethodDescription
+
+Description
+
+:
+
+### Evaluation method type {#iso19115-3.2018-elem-mdq-evaluationMethodType-aedca134bbad262feabe9ace78c65b95}
+
+Name
+
+:
+
+> mdq:evaluationMethodType
+
+Description
+
+:
+
+### Evaluation procedure {#iso19115-3.2018-elem-mdq-evaluationProcedure-7e7c31ff40c9145381585833a674ca58}
+
+Name
+
+:
+
+> mdq:evaluationProcedure
+
+Description
+
+:
+
+### Explanation {#iso19115-3.2018-elem-mdq-explanation-cb1e2747d00884eed567257f6159357a}
+
+Name
+
+:
+
+> mdq:explanation
+
+Description
+
+:
+
+``` xml
+
+ Voir la spécification référencée
+
+```
+
+### File description {#iso19115-3.2018-elem-mdq-fileDescription-5d8d5370baa1113d804263b54d2a7068}
+
+Name
+
+:
+
+> mdq:fileDescription
+
+Description
+
+:
+
+### File format {#iso19115-3.2018-elem-mdq-fileFormat-9db9383f8fdb906cbec0c9aecc6283a3}
+
+Name
+
+:
+
+> mdq:fileFormat
+
+Description
+
+:
+
+### Result file name {#iso19115-3.2018-elem-mdq-fileName-a1158f7c0bf6be8f9584593a47af5977}
+
+Name
+
+:
+
+> mdq:fileName
+
+Description
+
+:
+
+### File type {#iso19115-3.2018-elem-mdq-fileType-c856d12e8ac8fd38d94e53cd6685a205}
+
+Name
+
+:
+
+> mdq:fileType
+
+Description
+
+:
+
+### Measure {#iso19115-3.2018-elem-mdq-measure-6de6f9f0d8d88ce71be56b93112a0ab7}
+
+Name
+
+:
+
+> mdq:measure
+
+Description
+
+:
+
+### Measure description {#iso19115-3.2018-elem-mdq-measureDescription-c54ad7c4f745a142d2f4a5a0569d174f}
+
+Name
+
+:
+
+> mdq:measureDescription
+
+Description
+
+:
+
+### Measure identification {#iso19115-3.2018-elem-mdq-measureIdentification-8a53966de7a9af0351fc36cc6563d9b8}
+
+Name
+
+:
+
+> mdq:measureIdentification
+
+Description
+
+:
+
+### Name of measure {#iso19115-3.2018-elem-mdq-nameOfMeasure-6d30a22ce349987e83351f36f006edeb}
+
+Name
+
+:
+
+> mdq:nameOfMeasure
+
+Description
+
+:
+
+### Pass {#iso19115-3.2018-elem-mdq-pass-81090ac8a72d22f1cb603c4d5d8c6a69}
+
+Name
+
+:
+
+> mdq:pass
+
+Description
+
+:
+
+``` xml
+
+```
+
+### Coverage result {#iso19115-3.2018-elem-mdq-QE_CoverageResult-f8dae57f155420ec0fcaf24a2c89f826}
+
+Name
+
+:
+
+> mdq:QE_CoverageResult
+
+Description
+
+:
+
+```{=html}
+Result of a data quality measure organising the measured values
+ as a coverage
+```
+### Quality result file {#iso19115-3.2018-elem-mdq-QualityResultFile-f109f1bd9f2a7613c2240692764c6a67}
+
+Name
+
+:
+
+> mdq:QualityResultFile
+
+Description
+
+:
+
+### Reference doc {#iso19115-3.2018-elem-mdq-referenceDoc-0c442bf28823c9941c64476828a3aa8d}
+
+Name
+
+:
+
+> mdq:referenceDoc
+
+Description
+
+:
+
+### Related quality element {#iso19115-3.2018-elem-mdq-relatedElement-6cb5c2f116627d3ffebd1a44e60c6db6}
+
+Name
+
+:
+
+> mdq:relatedElement
+
+Description
+
+:
+
+### Report {#iso19115-3.2018-elem-mdq-report-3f560e7342c96a85b285df503914cd24}
+
+Name
+
+:
+
+> mdq:report
+
+Description
+
+:
+
+```{=html}
+Quantitative quality information for the data specified by the
+ scope
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+
+
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+
+
+
+```
+
+### Report reference {#iso19115-3.2018-elem-mdq-reportReference-3fdd5c73d4c70e02ac95dcd1344fdc0c}
+
+Name
+
+:
+
+> mdq:reportReference
+
+Description
+
+:
+
+### Result {#iso19115-3.2018-elem-mdq-result-4b9abc04ab0aa92a7dfd24268ea92451}
+
+Name
+
+:
+
+> mdq:result
+
+Description
+
+:
+
+``` xml
+
+
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+
+ Voir la spécification référencée
+
+
+
+
+```
+
+### Result content description {#iso19115-3.2018-elem-mdq-resultContentDescription-439741e7294de36459a0575d34b1e0d0}
+
+Name
+
+:
+
+> mdq:resultContentDescription
+
+Description
+
+:
+
+### Result file {#iso19115-3.2018-elem-mdq-resultFile-dd9d02421d1a1daac0ab8764cb9460ab}
+
+Name
+
+:
+
+> mdq:resultFile
+
+Description
+
+:
+
+### Result format {#iso19115-3.2018-elem-mdq-resultFormat-ddf9dccddc161522b101561d867e7416}
+
+Name
+
+:
+
+> mdq:resultFormat
+
+Description
+
+:
+
+### Result scope {#iso19115-3.2018-elem-mdq-resultScope-2d26c490e11930de1c49ad7e9dc5bab4}
+
+Name
+
+:
+
+> mdq:resultScope
+
+Description
+
+:
+
+### Result spatial representation {#iso19115-3.2018-elem-mdq-resultSpatialRepresentation-8bb7067999f2aa15977e1691d088afcc}
+
+Name
+
+:
+
+> mdq:resultSpatialRepresentation
+
+Description
+
+:
+
+### Scope {#iso19115-3.2018-elem-mdq-scope-a680ca4acf1fa0c4c2678a51709f9320}
+
+Name
+
+:
+
+> mdq:scope
+
+Description
+
+:
+
+```{=html}
+The specific data to which the data quality information
+ applies
+```
+``` xml
+
+
+
+
+
+
+
+```
+
+### Spatial representation type {#iso19115-3.2018-elem-mdq-spatialRepresentationType-dc1790616f61278197b4dbd1cf1869bc}
+
+Name
+
+:
+
+> mdq:spatialRepresentationType
+
+Description
+
+:
+
+### Specification {#iso19115-3.2018-elem-mdq-specification-17ccfa051d8e7f1a633444b084c1ae5f}
+
+Name
+
+:
+
+> mdq:specification
+
+Description
+
+:
+
+``` xml
+
+
+
+ COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services
+
+
+
+
+ 2010-12-08
+
+
+
+
+
+
+
+
+```
+
+### Standalone quality report {#iso19115-3.2018-elem-mdq-standaloneQualityReport-fd51848c91b175b598e66e34c0a7150c}
+
+Name
+
+:
+
+> mdq:standaloneQualityReport
+
+Description
+
+:
+
+### Standalone quality report details {#iso19115-3.2018-elem-mdq-standaloneQualityReportDetails-6a45bb0b8ba6ca15eda12e640cfa2a59}
+
+Name
+
+:
+
+> mdq:standaloneQualityReportDetails
+
+Description
+
+:
+
+### Statement {#iso19115-3.2018-elem-mdq-statement-66bfc04c451426e281bd6db312d7ff6a}
+
+Name
+
+:
+
+> mdq:statement
+
+Description
+
+:
+
+### Value {#iso19115-3.2018-elem-mdq-value-/mdb-MD_Metadata/mdb-dataQualityInfo/mdq-DQ_DataQuality/mdq-report/mdq-DQ_DomainConsistency/mdq-result/mdq-DQ_QuantitativeResult/mdq-value-dc03de6f70ba85162fea01c985e91d4e}
+
+Name
+
+:
+
+> mdq:value
+
+Context
+
+:
+
+> /mdb:MD_Metadata/mdb:dataQualityInfo/mdq:DQ_DataQuality/mdq:report/mdq:DQ_DomainConsistency/mdq:result/mdq:DQ_QuantitativeResult/mdq:value
+
+Description
+
+:
+
+```{=html}
+Quantitative value or values, content determined by the evaluation procedure
+ used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Value {#iso19115-3.2018-elem-mdq-value-306d79adb03863fa4fe88c5160249035}
+
+Name
+
+:
+
+> mdq:value
+
+Description
+
+:
+
+### Value type {#iso19115-3.2018-elem-mdq-valueRecordType-39d1e11f86d5166ef7e04d464662590c}
+
+Name
+
+:
+
+> mdq:valueRecordType
+
+Description
+
+:
+
+```{=html}
+Quantitative conformance quality level value or range of
+ values
+```
+Recommended values
+
+| code | label |
+|---------------------------------|---------------------------------|
+| Boolean | Boolean |
+| Real | Real |
+| Integer | Integer |
+| Ratio | Ratio |
+| Percentage | Percentage |
+| Measure(s) (value(s) + unit(s)) | Measure(s) (value(s) + unit(s)) |
+
+### Value unit {#iso19115-3.2018-elem-mdq-valueUnit-edcdbdc8d0e58c8764d5e6cd8088857e}
+
+Name
+
+:
+
+> mdq:valueUnit
+
+Description
+
+:
+
+```{=html}
+Value unit for reporting a data quality result
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Contact {#iso19115-3.2018-elem-mmi-contact-mmi-MD_MaintenanceInformation-67461bcb2fdc653d5dfe4b63a3cbdd5e}
+
+Name
+
+:
+
+> mmi:contact
+
+Context
+
+:
+
+> mmi:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s)
+ and
+ organization(s) with responsibility for maintaining the metadata
+```
+### Maintenance and update frequency {#iso19115-3.2018-elem-mmi-maintenanceAndUpdateFrequency-a9f8c3b3ffff1868396b8be05b51b2ed}
+
+Name
+
+:
+
+> mmi:maintenanceAndUpdateFrequency
+
+Description
+
+:
+
+```{=html}
+Frequency with which changes and additions are made to the
+ resource after the
+ initial resource is completed
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+```
+
+### Maintenance date {#iso19115-3.2018-elem-mmi-maintenanceDate-mmi-MD_MaintenanceInformation-f2d466937a8038b63f448b433b6b639a}
+
+Name
+
+:
+
+> mmi:maintenanceDate
+
+Context
+
+:
+
+> mmi:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Date information associated with maintenance of
+ resource
+```
+### Maintenance note {#iso19115-3.2018-elem-mmi-maintenanceNote-c1095367f28dea87bbedf6ac07490607}
+
+Name
+
+:
+
+> mmi:maintenanceNote
+
+Description
+
+:
+
+```{=html}
+Information regarding specific requirements for maintaining the
+ resource
+```
+### Maintenance scopes {#iso19115-3.2018-elem-mmi-maintenanceScope-mmi-MD_MaintenanceInformation-41e944366902a5e666515d56d075014f}
+
+Name
+
+:
+
+> mmi:maintenanceScope
+
+Context
+
+:
+
+> mmi:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Type of resource and/or extent to which the
+ maintenance information applies
+```
+### Maintenance Frequency {#iso19115-3.2018-elem-mmi-MD_MaintenanceFrequencyCode-2d1d3634943b4db7ca283424e745bc0e}
+
+Name
+
+:
+
+> mmi:MD_MaintenanceFrequencyCode
+
+Description
+
+:
+
+### Standard codelists Maintenance Frequency (mmi:MD_MaintenanceFrequencyCode)
+
+| code | label | description |
+|-------------|--------------|----------------------------------------------------------|
+| continual | Continual | Data is repeatedly and frequently updated |
+| daily | Daily | Data is updated each day |
+| weekly | Weekly | Data is updated on a weekly basis |
+| fortnightly | Fortnightly | Data is updated every two weeks |
+| monthly | Monthly | Data is updated each month |
+| quarterly | Quarterly | Data is updated every three months |
+| biannually | Biannually | Data is updated twice each year |
+| annually | Annually | Data is updated every year |
+| asNeeded | As needed | Data is updated as deemed necessary |
+| irregular | Irregular | Data is updated in intervals that are uneven in duration |
+| notPlanned | Not planned | There are no plans to update the data |
+| unknown | Unknown | Frequency of maintenance for the data is not known |
+| periodic | Periodic | Resource is updated at regular intervals |
+| semimonthly | Semi-monthly | Resource updated twice monthly |
+| biennially | Biennially | Resource is updated every 2 years |
+
+``` xml
+
+```
+
+### Maintenance information {#iso19115-3.2018-elem-mmi-MD_MaintenanceInformation-98062b270bf3eb9ad460147bad01d2f7}
+
+Name
+
+:
+
+> mmi:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Information about the scope and frequency of updating
+```
+``` xml
+
+
+
+
+
+```
+
+### User defined maintenance frequency {#iso19115-3.2018-elem-mmi-userDefinedMaintenanceFrequency-cde10206b5d1414f49a995a98246b323}
+
+Name
+
+:
+
+> mmi:userDefinedMaintenanceFrequency
+
+Description
+
+:
+
+```{=html}
+Maintenance period other than those defined
+```
+### Portrayal catalogue reference {#iso19115-3.2018-elem-mpc-MD_PortrayalCatalogueReference-b60bb4ca1d31a379f47c40d06b9454d5}
+
+Name
+
+:
+
+> mpc:MD_PortrayalCatalogueReference
+
+Description
+
+:
+
+```{=html}
+Information identifying the portrayal catalogue used
+```
+### Portrayal catalogue citation {#iso19115-3.2018-elem-mpc-portrayalCatalogueCitation-d3ffb8ae720f87fb4ff0772f33219cfc}
+
+Name
+
+:
+
+> mpc:portrayalCatalogueCitation
+
+Description
+
+:
+
+```{=html}
+Bibliographic reference to the portrayal catalogue cited
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Attribute {#iso19115-3.2018-elem-mrc-attribute-dea7af5d2034cfa9e7a5a77fc87bf546}
+
+Name
+
+:
+
+> mrc:attribute
+
+Description
+
+:
+
+```{=html}
+Information on an attribute of the resource
+```
+
+Condition
+
+:
+
+> optional
+
+### Attribute description {#iso19115-3.2018-elem-mrc-attributeDescription-37aaaca60c0cd43bf62d310ba147ef43}
+
+Name
+
+:
+
+> mrc:attributeDescription
+
+Description
+
+:
+
+```{=html}
+Description of the attribute described by the measurement
+ value
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Attribute group {#iso19115-3.2018-elem-mrc-attributeGroup-488906be5d4ea5fbfe94380ba5371d51}
+
+Name
+
+:
+
+> mrc:attributeGroup
+
+Description
+
+:
+
+```{=html}
+Information on groups(s) of related attributes of
+ the resource with the same type
+```
+### Bits per value {#iso19115-3.2018-elem-mrc-bitsPerValue-ea78a51caceb3feb5a8d573e937f1e26}
+
+Name
+
+:
+
+> mrc:bitsPerValue
+
+Description
+
+:
+
+```{=html}
+Maximum number of significant bits in the uncompressed
+ representation for the
+ value in each band of each pixel
+```
+### Bound max {#iso19115-3.2018-elem-mrc-boundMax-1016b54ba16d0ffde91fc11a1666047d}
+
+Name
+
+:
+
+> mrc:boundMax
+
+Description
+
+:
+
+```{=html}
+Longest wavelength that the sensor is capable of
+ collecting within a designated band
+```
+
+Condition
+
+:
+
+> optional
+
+### Bound min {#iso19115-3.2018-elem-mrc-boundMin-2b69a646b72ab2f1d87f527fed1bcdde}
+
+Name
+
+:
+
+> mrc:boundMin
+
+Description
+
+:
+
+```{=html}
+Shortest wavelength that the sensor is capable of
+ collecting within a designated band
+```
+
+Condition
+
+:
+
+> optional
+
+### Bound unit {#iso19115-3.2018-elem-mrc-boundUnits-4ad2b13f1b186a494053714d4cbc9886}
+
+Name
+
+:
+
+> mrc:boundUnits
+
+Description
+
+:
+
+```{=html}
+Units in which sensor wavelengths are expressed
+```
+
+Condition
+
+:
+
+> optional
+
+### Camera calibration information availability {#iso19115-3.2018-elem-mrc-cameraCalibrationInformationAvailability-bbc9b002677f5c123fd1f9c935bd1d2c}
+
+Name
+
+:
+
+> mrc:cameraCalibrationInformationAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not constants are available which
+ allow for camera
+ calibration corrections
+```
+### Cloud cover percentage {#iso19115-3.2018-elem-mrc-cloudCoverPercentage-703ebfc5d930f35ccecba7d9ba6d983a}
+
+Name
+
+:
+
+> mrc:cloudCoverPercentage
+
+Description
+
+:
+
+```{=html}
+Area of the dataset obscured by clouds, expressed as a
+ percentage of the
+ spatial extent
+```
+### Compliance code {#iso19115-3.2018-elem-mrc-complianceCode-085f3d1351953db360d964bb7bab6366}
+
+Name
+
+:
+
+> mrc:complianceCode
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the cited feature catalogue
+ complies with ISO
+ 19110
+```
+### Content type {#iso19115-3.2018-elem-mrc-contentType-b3b7e695f74a74466893e19a20849596}
+
+Name
+
+:
+
+> mrc:contentType
+
+Description
+
+:
+
+```{=html}
+Type of information represented by the cell value
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Definition {#iso19115-3.2018-elem-mrc-definition-29b676d7a94fb93a2fa58282483a4692}
+
+Name
+
+:
+
+> mrc:definition
+
+Description
+
+:
+
+```{=html}
+Designation associated with a set of range elements. eg. "Indicates the sample storage method used."
+```
+### Description {#iso19115-3.2018-elem-mrc-description-74b8844c2a5832541e186bdf3a41a726}
+
+Name
+
+:
+
+> mrc:description
+
+Description
+
+:
+
+```{=html}
+Description of the attribute
+```
+
+Condition
+
+:
+
+> optional
+
+### Feature catalogue {#iso19115-3.2018-elem-mrc-featureCatalogue-f1f508ee82724f13567d3975f1c70c3e}
+
+Name
+
+:
+
+> mrc:featureCatalogue
+
+Description
+
+:
+
+```{=html}
+The catalogue of feature types, attribution,
+ operations, and relationships used by the resource
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Feature catalogue citation {#iso19115-3.2018-elem-mrc-featureCatalogueCitation-beae05b407350c4ce10932b35a6947cc}
+
+Name
+
+:
+
+> mrc:featureCatalogueCitation
+
+Description
+
+:
+
+```{=html}
+Complete bibliographic reference to one or more external feature catalogues
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Feature instance count {#iso19115-3.2018-elem-mrc-featureInstanceCount-7b2fb0b426132c4080181e86e40321b5}
+
+Name
+
+:
+
+> mrc:featureInstanceCount
+
+Description
+
+:
+
+```{=html}
+Number of occurrence of feature instances for this
+ feature type
+```
+
+Condition
+
+:
+
+> optional
+
+### Feature type name {#iso19115-3.2018-elem-mrc-featureTypeName-acf13aeabc8218359b85e1c5c16d32b9}
+
+Name
+
+:
+
+> mrc:featureTypeName
+
+Description
+
+:
+
+```{=html}
+name of the feature type
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Feature types {#iso19115-3.2018-elem-mrc-featureTypes-13f71555be371c5cc82c6cafa4e33211}
+
+Name
+
+:
+
+> mrc:featureTypes
+
+Description
+
+:
+
+```{=html}
+Subset of feature types from cited feature catalogue occurring
+ in
+ data
+```
+### Film distortion information availability {#iso19115-3.2018-elem-mrc-filmDistortionInformationAvailability-23e3979145822c8293c502656ce444de}
+
+Name
+
+:
+
+> mrc:filmDistortionInformationAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not Calibration Reseau information is
+ available
+```
+### Illumination azimuth angle {#iso19115-3.2018-elem-mrc-illuminationAzimuthAngle-68703c8ec1b434991369ad110842f0d5}
+
+Name
+
+:
+
+> mrc:illuminationAzimuthAngle
+
+Description
+
+:
+
+```{=html}
+Illumination azimuth measured in degrees clockwise from true
+ north at the time
+ the image is taken. For images from a scanning device, refer to the centre
+ pixel of the
+ image
+```
+### Illumination elevation angle {#iso19115-3.2018-elem-mrc-illuminationElevationAngle-4942fcb50fa1ba386468663a170f4515}
+
+Name
+
+:
+
+> mrc:illuminationElevationAngle
+
+Description
+
+:
+
+```{=html}
+Illumination elevation measured in degrees clockwise from the
+ target plane at
+ intersection of the optical line of sight with the Earth_s surface. For
+ images from a
+ scanning device, refer to the centre pixel of the image
+```
+### Image quality code {#iso19115-3.2018-elem-mrc-imageQualityCode-d76c432bcf49e1705efa580424294b6d}
+
+Name
+
+:
+
+> mrc:imageQualityCode
+
+Description
+
+:
+
+```{=html}
+Specifies the image quality
+```
+```{=html}
+specifies the image quality
+```
+### Imaging condition {#iso19115-3.2018-elem-mrc-imagingCondition-138415b371cbe7c705db6c3858d9c19a}
+
+Name
+
+:
+
+> mrc:imagingCondition
+
+Description
+
+:
+
+```{=html}
+Conditions affected the image
+```
+### Included with dataset {#iso19115-3.2018-elem-mrc-includedWithDataset-406a9a329b292776ade8c8b32d3fdfd5}
+
+Name
+
+:
+
+> mrc:includedWithDataset
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the feature catalogue
+ is included with the resource
+```
+### Language {#iso19115-3.2018-elem-mrc-language-mrc-MD_FeatureCatalogueDescription-b823b546a702df52e72c3d763a33a1e0}
+
+Name
+
+:
+
+> mrc:language
+
+Context
+
+:
+
+> mrc:MD_FeatureCatalogueDescription
+
+Description
+
+:
+
+```{=html}
+Language(s) used within the catalogue
+```
+### Lens distortion information availability {#iso19115-3.2018-elem-mrc-lensDistortionInformationAvailability-b4bcaa5a49e2e331bce3130b001528ba}
+
+Name
+
+:
+
+> mrc:lensDistortionInformationAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not lens aberration correction
+ information is
+ available
+```
+### Other language {#iso19115-3.2018-elem-mrc-locale-d66cfb23e274f1b932595edae8291687}
+
+Name
+
+:
+
+> mrc:locale
+
+Description
+
+:
+
+```{=html}
+Use this section to define other metadata language
+ (multilingual metadata).
+```
+### Maximum value {#iso19115-3.2018-elem-mrc-maxValue-f4d6b07e0627d3dad6327a88e0fb7645}
+
+Name
+
+:
+
+> mrc:maxValue
+
+Description
+
+:
+
+```{=html}
+Longest wavelength that the sensor is capable of collecting
+ within a designated
+ band
+```
+### Attribute group {#iso19115-3.2018-elem-mrc-MD_AttributeGroup-fde4af4efe67a27c7eb38f18e55a7bfa}
+
+Name
+
+:
+
+> mrc:MD_AttributeGroup
+
+Description
+
+:
+
+```{=html}
+Class of information about contentType for groups of
+ attributes for a specific MD_RangeDimension
+```
+### Band {#iso19115-3.2018-elem-mrc-MD_Band-b11f77f7425007bf07d4fa479295fc57}
+
+Name
+
+:
+
+> mrc:MD_Band
+
+Description
+
+:
+
+```{=html}
+Range of wavelengths in the electromagnetic spectrum
+```
+```{=html}
+range of wavelengths in the electromagnetic spectrum
+```
+### Coverage content {#iso19115-3.2018-elem-mrc-MD_CoverageContentTypeCode-b7fd2aef2e8871ea509a92f553d14c52}
+
+Name
+
+:
+
+> mrc:MD_CoverageContentTypeCode
+
+Description
+
+:
+
+### Standard codelists Coverage content (mrc:MD_CoverageContentTypeCode)
+
+| code | label | description |
+|------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| image | Image | Meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter |
+| thematicClassification | Thematic classification | Code value with no quantitative meaning, used to represent a physical quantity |
+| physicalMeasurement | Physical measurement | Value in physical units of the quantity being measured |
+| auxillaryInformation | Auxillary Information | Data, usually a physical measurement, used to support the calculation of the primary physicalMeasurement coverages in the dataset. EXAMPLE: Grid of aerosol optical thickness used in the calculation of a sea surface temperature product |
+| qualityInformation | Quality Information | Data used to characterize the quality of the physicalMeasurement coverages in the dataset. NOTE: Typically included in a gmi:QE_CoverageResult |
+| referenceInformation | Reference Information | Data used to characterize the quality of the physicalMeasurement coverages in the dataset. NOTE: Typically included in a gmi:QE_CoverageResult |
+| modelResult | Model Result | Resources with values that are calculated using a model rather than being observed or calculated from observations |
+| coordinate | Coordinate | Data used to provide coordinate axis values |
+
+### Coverage description {#iso19115-3.2018-elem-mrc-MD_CoverageDescription-20da3d15d7d2d5b9fe25c271bf685b2f}
+
+Name
+
+:
+
+> mrc:MD_CoverageDescription
+
+Description
+
+:
+
+```{=html}
+Information about the content of a grid data cell
+```
+### Feature catalogue {#iso19115-3.2018-elem-mrc-MD_FeatureCatalogue-bbbf11cbc612ed2caa46922976d76c6e}
+
+Name
+
+:
+
+> mrc:MD_FeatureCatalogue
+
+Description
+
+:
+
+```{=html}
+A catalogue of feature types
+```
+### Feature catalogue description {#iso19115-3.2018-elem-mrc-MD_FeatureCatalogueDescription-25544385dc037d9d72c849835f4600d9}
+
+Name
+
+:
+
+> mrc:MD_FeatureCatalogueDescription
+
+Description
+
+:
+
+```{=html}
+Information identifying the feature catalogue or the conceptual
+ schema
+```
+### Feature type info {#iso19115-3.2018-elem-mrc-MD_FeatureTypeInfo-62a86318a6a5fa1493616ea4e0703f1b}
+
+Name
+
+:
+
+> mrc:MD_FeatureTypeInfo
+
+Description
+
+:
+
+```{=html}
+Information about the occurring feature type
+```
+### Image description {#iso19115-3.2018-elem-mrc-MD_ImageDescription-593f7c8841d10f6d890cb7c653b68304}
+
+Name
+
+:
+
+> mrc:MD_ImageDescription
+
+Description
+
+:
+
+```{=html}
+Information about an image's suitability for use
+```
+### Range dimension {#iso19115-3.2018-elem-mrc-MD_RangeDimension-5d6ee7c06f95d6a0873f9d3e73f9f806}
+
+Name
+
+:
+
+> mrc:MD_RangeDimension
+
+Description
+
+:
+
+```{=html}
+Information on the range of each dimension of a cell
+ measurement
+ value
+```
+### Sample dimension {#iso19115-3.2018-elem-mrc-MD_SampleDimension-d144bfef885aeb0a9646d264f6bac3a4}
+
+Name
+
+:
+
+> mrc:MD_SampleDimension
+
+Description
+
+:
+
+```{=html}
+Class of information about characteristics of each
+ dimension (layer) included in the resource
+```
+### Mean value {#iso19115-3.2018-elem-mrc-meanValue-dca986b28aac66bb498a06cc8bd63de2}
+
+Name
+
+:
+
+> mrc:meanValue
+
+Description
+
+:
+
+```{=html}
+Mean value of data values in each dimension included
+ in the resource
+```
+
+Condition
+
+:
+
+> optional
+
+### Coverage description (with range elements) {#iso19115-3.2018-elem-mrc-MI_CoverageDescription-f1c665c83cb4c58187c8267e58693137}
+
+Name
+
+:
+
+> mrc:MI_CoverageDescription
+
+Description
+
+:
+
+```{=html}
+information about the content of a coverage, including the description of specific range elements
+```
+### Range element description {#iso19115-3.2018-elem-mrc-MI_RangeElementDescription-3ea08f39e0b95158ed36f0a1d95f32b2}
+
+Name
+
+:
+
+> mrc:MI_RangeElementDescription
+
+Description
+
+:
+
+```{=html}
+eg. storage_meth
+```
+### Minimum value {#iso19115-3.2018-elem-mrc-minValue-6c115fdd9335853f2ed4d501c55d0cd3}
+
+Name
+
+:
+
+> mrc:minValue
+
+Description
+
+:
+
+```{=html}
+Shortest wavelength that the sensor is capable of collecting
+ within a
+ designated band
+```
+### Name {#iso19115-3.2018-elem-mrc-name-b10ecd5c969f4405e4432a10ce4c987a}
+
+Name
+
+:
+
+> mrc:name
+
+Description
+
+:
+
+```{=html}
+Identifiers for each attribute included in the resource. NOTE
+ These identifiers can be used to provide names for the attribute from a
+ standard set of names.
+```
+### Number of values {#iso19115-3.2018-elem-mrc-numberOfValues-7523788807eb16fb4c28f3cc87695fea}
+
+Name
+
+:
+
+> mrc:numberOfValues
+
+Description
+
+:
+
+```{=html}
+The number of values used in a
+ thematic-Classification resource. Example The number of classes in a Land
+ Cover Type coverage or the number of cells with data in other types of
+ coverages.
+```
+
+Condition
+
+:
+
+> optional
+
+### Offset {#iso19115-3.2018-elem-mrc-offset-cbfe08793cf284c302b1a3ff5279fd2b}
+
+Name
+
+:
+
+> mrc:offset
+
+Description
+
+:
+
+```{=html}
+The physical value corresponding to a cell value of zero
+```
+### Other property {#iso19115-3.2018-elem-mrc-otherProperty-2b07e124713e224f44f3f16c558d07a4}
+
+Name
+
+:
+
+> mrc:otherProperty
+
+Description
+
+:
+
+```{=html}
+Instance of otherAttributeType that defines
+ attributes not explicitly included in MD_CoverageType
+```
+
+Condition
+
+:
+
+> optional
+
+### Other property type {#iso19115-3.2018-elem-mrc-otherPropertyType-3c86efa51e730535417cf07c9d0e46b7}
+
+Name
+
+:
+
+> mrc:otherPropertyType
+
+Description
+
+:
+
+```{=html}
+Type of other attribute description (i.e.
+ netcdf/variable in ncml.xsd)
+```
+
+Condition
+
+:
+
+> optional
+
+### Peak response {#iso19115-3.2018-elem-mrc-peakResponse-3de9d3d87866575d11d2843ecfaf3f14}
+
+Name
+
+:
+
+> mrc:peakResponse
+
+Description
+
+:
+
+```{=html}
+Wavelength at which the response is the highest
+```
+### Processing level code {#iso19115-3.2018-elem-mrc-processingLevelCode-6b9cbec9c2e7653417fe4085fa2f518e}
+
+Name
+
+:
+
+> mrc:processingLevelCode
+
+Description
+
+:
+
+```{=html}
+Image distributor_s code that identifies the level of
+ radiometric and geometric
+ processing that has been applied
+```
+### Radiometric calibration data availability {#iso19115-3.2018-elem-mrc-radiometricCalibrationDataAvailability-cd03f7e1aa8805ed7f2629c4d71f9ab0}
+
+Name
+
+:
+
+> mrc:radiometricCalibrationDataAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the radiometric calibration
+ information for
+ generating the radiometrically calibrated standard data product is
+ available
+```
+### Range element {#iso19115-3.2018-elem-mrc-rangeElement-c2ca16217781d20936083b76e758a5b6}
+
+Name
+
+:
+
+> mrc:rangeElement
+
+Description
+
+:
+
+```{=html}
+Specific range elements, i.e. range elements associated with a name and their definition. eg. "frozen: Samples are kept frozen.", "room temperature, dry: Samples are kept at room temperature, unsealed."
+```
+### Range element description {#iso19115-3.2018-elem-mrc-rangeElementDescription-0d1cc78e663f1eccce73c39c905e8606}
+
+Name
+
+:
+
+> mrc:rangeElementDescription
+
+Description
+
+:
+
+### Scale factor {#iso19115-3.2018-elem-mrc-scaleFactor-d0c127708af77d60471931d015e154da}
+
+Name
+
+:
+
+> mrc:scaleFactor
+
+Description
+
+:
+
+```{=html}
+Scale factor which has been applied to the cell value
+```
+### Sequence identifier {#iso19115-3.2018-elem-mrc-sequenceIdentifier-9985f58f70c92c442461a95ff7a2387e}
+
+Name
+
+:
+
+> mrc:sequenceIdentifier
+
+Description
+
+:
+
+```{=html}
+Number that uniquely identifies instances of bands of
+ wavelengths on which a
+ sensor operates
+```
+### Standard deviation {#iso19115-3.2018-elem-mrc-standardDeviation-46d51bf39f4256ce781ba724ce7a4678}
+
+Name
+
+:
+
+> mrc:standardDeviation
+
+Description
+
+:
+
+```{=html}
+Standard deviation of data values in each dimension
+ included in the resource
+```
+
+Condition
+
+:
+
+> optional
+
+### Tone gradation {#iso19115-3.2018-elem-mrc-toneGradation-00522b18a25c437874134ff1507233ee}
+
+Name
+
+:
+
+> mrc:toneGradation
+
+Description
+
+:
+
+```{=html}
+Number of discrete numerical values in the grid data
+```
+### Triangulation indicator {#iso19115-3.2018-elem-mrc-triangulationIndicator-766a13c1a0f5c40aeeea98ea964584ac}
+
+Name
+
+:
+
+> mrc:triangulationIndicator
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not triangulation has been performed
+ upon the
+ image
+```
+### Value unit {#iso19115-3.2018-elem-mrc-units-beb1f3c6a128f74d575f87e6e7ea46b4}
+
+Name
+
+:
+
+> mrc:units
+
+Description
+
+:
+
+```{=html}
+Units in which sensor wavelengths are expressed
+```
+### Amendment number {#iso19115-3.2018-elem-mrd-amendmentNumber-6f1c8cb20613ad2e309e5bb98c2cbdc6}
+
+Name
+
+:
+
+> mrd:amendmentNumber
+
+Description
+
+:
+
+```{=html}
+Amendment number of the format version
+```
+### Density {#iso19115-3.2018-elem-mrd-density-1dd26b1967b18ff25f8427f5ded195b0}
+
+Name
+
+:
+
+> mrd:density
+
+Description
+
+:
+
+```{=html}
+Density at which the data is recorded
+```
+### Density units {#iso19115-3.2018-elem-mrd-densityUnits-e82aa4195b9434d3a68263bcffdba896}
+
+Name
+
+:
+
+> mrd:densityUnits
+
+Description
+
+:
+
+```{=html}
+Units of measure for the recording density
+```
+
+Condition
+
+:
+
+> conditional
+
+### Description {#iso19115-3.2018-elem-mrd-description-mrd-MD_Distribution-4776d7962b0a05ccef02ea6322033b31}
+
+Name
+
+:
+
+> mrd:description
+
+Context
+
+:
+
+> mrd:MD_Distribution
+
+Description
+
+:
+
+```{=html}
+Brief description of a set of distribution options
+```
+
+Condition
+
+:
+
+> optional
+
+### Distribution format {#iso19115-3.2018-elem-mrd-distributionFormat-ab2a7aa7307b337b55fd0813ee4164be}
+
+Name
+
+:
+
+> mrd:distributionFormat
+
+Description
+
+:
+
+```{=html}
+Provides a description of the format of the data to be
+ distributed
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+
+
+ ESRI Shapefile
+
+
+
+ 1.0
+
+
+
+
+
+```
+
+### Distribution / Order Process {#iso19115-3.2018-elem-mrd-distributionOrderProcess-9d9c84da23cda2ebdfd2df84ed8c8238}
+
+Name
+
+:
+
+> mrd:distributionOrderProcess
+
+Description
+
+:
+
+```{=html}
+Provides information about how the resource may be obtained,
+ and related
+ instructions and fee information
+```
+### Distributor {#iso19115-3.2018-elem-mrd-distributor-ded9d0279d2a2b1d04058bcfe0cdadd3}
+
+Name
+
+:
+
+> mrd:distributor
+
+Description
+
+:
+
+```{=html}
+Provides information about the distributor
+```
+### Distributor contact {#iso19115-3.2018-elem-mrd-distributorContact-c291667f416ad3edb6e9ba3c7ce6e6d2}
+
+Name
+
+:
+
+> mrd:distributorContact
+
+Description
+
+:
+
+```{=html}
+Party from whom the resource may be obtained. This list need
+ not be
+ exhaustive
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Distributor format {#iso19115-3.2018-elem-mrd-distributorFormat-385b3a3cdc414ef818b29eead21ed7e6}
+
+Name
+
+:
+
+> mrd:distributorFormat
+
+Description
+
+:
+
+```{=html}
+Provides information about the format used by the distributor
+```
+
+Condition
+
+:
+
+> conditional
+
+### Distributor transfer options {#iso19115-3.2018-elem-mrd-distributorTransferOptions-fed28aa32a0ff7ee645473414c10fd93}
+
+Name
+
+:
+
+> mrd:distributorTransferOptions
+
+Description
+
+:
+
+```{=html}
+Provides information about the technical means and media used
+ by the
+ distributor
+```
+### Fees {#iso19115-3.2018-elem-mrd-fees-a89d56e0d6fad26e33792138077cf724}
+
+Name
+
+:
+
+> mrd:fees
+
+Description
+
+:
+
+```{=html}
+Fees and terms for retrieving the resource. Include monetary
+ units (as
+ specified in ISO 4217)
+```
+### File decompression technique {#iso19115-3.2018-elem-mrd-fileDecompressionTechnique-79a96bbb2fc4a7cfacb6cb50f79ac39a}
+
+Name
+
+:
+
+> mrd:fileDecompressionTechnique
+
+Description
+
+:
+
+```{=html}
+Recommendations of algorithms or processes that can be applied
+ to read or
+ expand resources to which compression techniques have been applied
+```
+### Format distributor {#iso19115-3.2018-elem-mrd-formatDistributor-76fa4371c29fb34aeaa312f75b331eb0}
+
+Name
+
+:
+
+> mrd:formatDistributor
+
+Description
+
+:
+
+```{=html}
+Provides information about the distributor’s format
+```
+### Format specification citation {#iso19115-3.2018-elem-mrd-formatSpecificationCitation-8857c3b7bb4601e89bcc1459881dce96}
+
+Name
+
+:
+
+> mrd:formatSpecificationCitation
+
+Description
+
+:
+
+```{=html}
+citation/URL of the specification for the format
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+ ESRI Shapefile
+
+
+
+ 1.0
+
+
+
+```
+
+### Identifier {#iso19115-3.2018-elem-mrd-identifier-mrd-MD_Medium-b4ad5d7dfbc8331c8b46a58b5e2074f4}
+
+Name
+
+:
+
+> mrd:identifier
+
+Context
+
+:
+
+> mrd:MD_Medium
+
+Description
+
+:
+
+```{=html}
+Unique identifier for an instance of the MD_Medium
+```
+
+Condition
+
+:
+
+> optional
+
+### Digital transfer options {#iso19115-3.2018-elem-mrd-MD_DigitalTransferOptions-c26594fe5b1a54f2778851719f742143}
+
+Name
+
+:
+
+> mrd:MD_DigitalTransferOptions
+
+Description
+
+:
+
+```{=html}
+Technical means and media by which a resource is obtained from
+ the
+ distributor
+```
+``` xml
+
+
+
+
+ https://geoservices.wallonie.be/inspire/atom/PS_Service.xml
+
+
+ atom:feed
+
+
+ Service de téléchargement ATOM Feed - Inspire
+
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+
+
+
+
+
+
+```
+
+### Distribution {#iso19115-3.2018-elem-mrd-MD_Distribution-0aca2560647689db7ebf415baf443815}
+
+Name
+
+:
+
+> mrd:MD_Distribution
+
+Description
+
+:
+
+```{=html}
+Information about the distributor of and options for obtaining
+ the
+ resource
+```
+``` xml
+
+
+
+
+
+
+ ESRI Shapefile
+
+
+
+ 1.0
+
+
+
+
+
+
+
+
+
+
+ https://geoservices.wallonie.be/inspire/atom/PS_Service.xml
+
+
+ atom:feed
+
+
+ Service de téléchargement ATOM Feed - Inspire
+
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+
+
+
+
+
+
+
+
+```
+
+### Distributor {#iso19115-3.2018-elem-mrd-MD_Distributor-d38062afe33f6acc7dd0874610344056}
+
+Name
+
+:
+
+> mrd:MD_Distributor
+
+Description
+
+:
+
+```{=html}
+Information about the distributor
+```
+### Format {#iso19115-3.2018-elem-mrd-MD_Format-cf79bdb2251ece19f8f9a2efa0080e17}
+
+Name
+
+:
+
+> mrd:MD_Format
+
+Description
+
+:
+
+```{=html}
+Description of the computer language construct that specifies
+ the
+ representation of data objects in a record, file, message, storage device
+ or
+ transmission channel
+```
+``` xml
+
+
+
+
+ ESRI Shapefile
+
+
+
+ 1.0
+
+
+
+
+```
+
+### Medium {#iso19115-3.2018-elem-mrd-MD_Medium-47c4ae7fb9c00a03bc19f6684356ccd3}
+
+Name
+
+:
+
+> mrd:MD_Medium
+
+Description
+
+:
+
+```{=html}
+Information about the media on which the resource can be
+ distributed
+```
+### Standard order process {#iso19115-3.2018-elem-mrd-MD_StandardOrderProcess-bbf8a6d49b7ccfe336ae772581224a5c}
+
+Name
+
+:
+
+> mrd:MD_StandardOrderProcess
+
+Description
+
+:
+
+```{=html}
+Common ways in which the resource may be obtained or received,
+ and related
+ instructions and fee information
+```
+### Medium {#iso19115-3.2018-elem-mrd-medium-2da5ffeab982f345f690536effef17c3}
+
+Name
+
+:
+
+> mrd:medium
+
+Description
+
+:
+
+```{=html}
+Medium used by the format
+```
+### Medium format {#iso19115-3.2018-elem-mrd-mediumFormat-ead4f2e742d591857767ef2599762f33}
+
+Name
+
+:
+
+> mrd:mediumFormat
+
+Description
+
+:
+
+```{=html}
+Method used to write to the medium
+```
+### Medium note {#iso19115-3.2018-elem-mrd-mediumNote-18fe569d2e175e458cdba96d642973ed}
+
+Name
+
+:
+
+> mrd:mediumNote
+
+Description
+
+:
+
+```{=html}
+Description of other limitations or requirements for using the
+ medium
+```
+### Name {#iso19115-3.2018-elem-mrd-name-mrd-MD_Medium-6b32246dbc4ce932f20d5faa5622c8cb}
+
+Name
+
+:
+
+> mrd:name
+
+Context
+
+:
+
+> mrd:MD_Medium
+
+Description
+
+:
+
+```{=html}
+Name of the medium on which the resource can be received
+```
+
+Condition
+
+:
+
+> optional
+
+### Offline {#iso19115-3.2018-elem-mrd-offLine-48c66fab18ef14981a5e4fae104c6f97}
+
+Name
+
+:
+
+> mrd:offLine
+
+Description
+
+:
+
+```{=html}
+Information about offline media on which the resource can be
+ obtained
+```
+### OnLine resource {#iso19115-3.2018-elem-mrd-onLine-b258f26a552d7bdb353a9ed8602955f9}
+
+Name
+
+:
+
+> mrd:onLine
+
+Description
+
+:
+
+```{=html}
+Information about online sources from which the resource can be
+ obtained
+```
+``` xml
+
+
+
+ https://geoservices.wallonie.be/inspire/atom/PS_Service.xml
+
+
+ atom:feed
+
+
+ Service de téléchargement ATOM Feed - Inspire
+
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+
+
+
+
+
+```
+
+### Ordering instructions {#iso19115-3.2018-elem-mrd-orderingInstructions-697dea5f51a3bc14b9261c199646b2e5}
+
+Name
+
+:
+
+> mrd:orderingInstructions
+
+Description
+
+:
+
+```{=html}
+General instructions, terms and services provided by the
+ distributor
+```
+### Request/Purchase choices {#iso19115-3.2018-elem-mrd-orderOptions-77c57136b3bbf368b7ce40dc320e0f10}
+
+Name
+
+:
+
+> mrd:orderOptions
+
+Description
+
+:
+
+### Order options type {#iso19115-3.2018-elem-mrd-orderOptionsType-3fa15edfa3acc92ebf7095a49192991f}
+
+Name
+
+:
+
+> mrd:orderOptionsType
+
+Description
+
+:
+
+```{=html}
+Description of the order options record
+```
+### Planned available datetime {#iso19115-3.2018-elem-mrd-plannedAvailableDateTime-58431a14cc32a4038ddbce9871023820}
+
+Name
+
+:
+
+> mrd:plannedAvailableDateTime
+
+Description
+
+:
+
+```{=html}
+Date and time when the dataset will be available
+ (CCYY-MM-DDThh:mm:ss)
+```
+### Transfer frequency {#iso19115-3.2018-elem-mrd-transferFrequency-734c97eb43b31196d37e306d4a55c64f}
+
+Name
+
+:
+
+> mrd:transferFrequency
+
+Description
+
+:
+
+```{=html}
+Rate of occurrence of distribution
+```
+### Transfer options {#iso19115-3.2018-elem-mrd-transferOptions-406dce14c80f3ab2bab25cbcb045148b}
+
+Name
+
+:
+
+> mrd:transferOptions
+
+Description
+
+:
+
+```{=html}
+Provides information about technical means and media by which a
+ resource is
+ obtained from the distributor
+```
+``` xml
+
+
+
+
+
+ https://geoservices.wallonie.be/inspire/atom/PS_Service.xml
+
+
+ atom:feed
+
+
+ Service de téléchargement ATOM Feed - Inspire
+
+
+ Ce service de téléchargement ATOM Feed permet de télécharger la série de couches de
+ données conforme au thème INSPIRE "Sites protégés". Cliquez sur le lien correspondant aux couches de
+ données Natura 2000 pour télécharger les informations relatives à ce mécanisme de désignation.
+
+
+
+
+
+
+
+
+```
+
+### Transfer size {#iso19115-3.2018-elem-mrd-transferSize-18c1e66604b41b220a25872a4e4392b3}
+
+Name
+
+:
+
+> mrd:transferSize
+
+Description
+
+:
+
+```{=html}
+Estimated size of a unit in the specified transfer format,
+ expressed in
+ megabytes. The transfer size is > 0.0
+```
+### Turnaround {#iso19115-3.2018-elem-mrd-turnaround-428b1bfcefbc1a5350d5e910d0a49941}
+
+Name
+
+:
+
+> mrd:turnaround
+
+Description
+
+:
+
+```{=html}
+Typical turnaround time for the filling of an order
+```
+### Units of distribution {#iso19115-3.2018-elem-mrd-unitsOfDistribution-bfd51096d182fdfed936fe30f646b048}
+
+Name
+
+:
+
+> mrd:unitsOfDistribution
+
+Description
+
+:
+
+```{=html}
+Tiles, layers, geographic areas, etc., in which data is
+ available
+```
+### Volumes {#iso19115-3.2018-elem-mrd-volumes-8fbc4cdb71c04f0d9d7a81fd69811a6f}
+
+Name
+
+:
+
+> mrd:volumes
+
+Description
+
+:
+
+```{=html}
+Number of items in the media identified
+```
+### Abstract {#iso19115-3.2018-elem-mri-abstract-b1bed9a6d2c9c70eb6b29dc5f23b5b99}
+
+Name
+
+:
+
+> mri:abstract
+
+Description
+
+:
+
+```{=html}
+Brief narrative summary of the content of the resource(s)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ Description du jeu de données
+
+```
+
+### Additional documentation {#iso19115-3.2018-elem-mri-additionalDocumentation-085f02b75f646444bac3a4e64e1902ab}
+
+Name
+
+:
+
+> mri:additionalDocumentation
+
+Description
+
+:
+
+```{=html}
+Publications that describe usage of data
+```
+### Address {#iso19115-3.2018-elem-mri-address-mri-CI_ResponsibleParty-cdfa0ffe58b9f168d74204ba97e5c255}
+
+Name
+
+:
+
+> mri:address
+
+Context
+
+:
+
+> mri:CI_ResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Address of the responsible party
+```
+### Aggregate Datasetindentifier {#iso19115-3.2018-elem-mri-aggregateDataSetIdentifier-80a8130a9c7c9d5c351a30f6d3b19922}
+
+Name
+
+:
+
+> mri:aggregateDataSetIdentifier
+
+Description
+
+:
+
+```{=html}
+Identification information about aggregate dataset
+```
+### Aggregate Datasetname {#iso19115-3.2018-elem-mri-aggregateDataSetName-008e770be965e057181c9ba67f7744aa}
+
+Name
+
+:
+
+> mri:aggregateDataSetName
+
+Description
+
+:
+
+```{=html}
+Citation information about the aggregate dataset
+```
+### Aggregation Information {#iso19115-3.2018-elem-mri-aggregationInfo-05a21c978da37347b2374194e023b8c3}
+
+Name
+
+:
+
+> mri:aggregationInfo
+
+Description
+
+:
+
+```{=html}
+Provides aggregate dataset information
+```
+### Angular sampling measure {#iso19115-3.2018-elem-mri-angularDistance-ca774f3cfa2db619366fd4746b5feb0b}
+
+Name
+
+:
+
+> mri:angularDistance
+
+Description
+
+:
+
+```{=html}
+Angular sampling measure
+```
+### Associated resource {#iso19115-3.2018-elem-mri-associatedResource-4687e155ff36c1fced9bb0a5a55a34fa}
+
+Name
+
+:
+
+> mri:associatedResource
+
+Description
+
+:
+
+```{=html}
+Associated resource information
+```
+### Association Type {#iso19115-3.2018-elem-mri-associationType-50002af61552cfafa00e8158d1e86dd4}
+
+Name
+
+:
+
+> mri:associationType
+
+Description
+
+:
+
+```{=html}
+Association type of the aggregate dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Axis Dimensions Properties {#iso19115-3.2018-elem-mri-axisDimensionProperties-843437604cfe1e16ceda396764927b8c}
+
+Name
+
+:
+
+> mri:axisDimensionProperties
+
+Description
+
+:
+
+```{=html}
+Information about spatial-temporal axis properties
+```
+### Cell geometry {#iso19115-3.2018-elem-mri-cellGeometry-f970f9e6a0c45f74441de613b704305e}
+
+Name
+
+:
+
+> mri:cellGeometry
+
+Description
+
+:
+
+```{=html}
+Identification of grid data as point or cell
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Center point {#iso19115-3.2018-elem-mri-centerPoint-cb30d24a90d23a1948cd9db74bfe6149}
+
+Name
+
+:
+
+> mri:centerPoint
+
+Description
+
+:
+
+```{=html}
+Earth location in the coordinate system defined by the Spatial
+ Reference System
+ and the grid coordinate of the cell halfway between opposite ends of the
+ grid in the
+ spatial dimensions
+```
+### Character set {#iso19115-3.2018-elem-mri-characterSet-mri-MD_Metadata-fbb8af54487af62f6d4dd9bbcbd5e4ab}
+
+Name
+
+:
+
+> mri:characterSet
+
+Context
+
+:
+
+> mri:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Full name of the character coding standard used for the
+ metadata
+ set
+```
+
+Condition
+
+:
+
+> conditional
+
+### Character set {#iso19115-3.2018-elem-mri-characterSet-mri-MD_DataIdentification-670c14eea2290ec02febe561bb9dc317}
+
+Name
+
+:
+
+> mri:characterSet
+
+Context
+
+:
+
+> mri:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Full name of the character coding standard used for the
+ dataset
+```
+### Character set {#iso19115-3.2018-elem-mri-characterSet-e5dcdb278033ab3d5b29b1d3adffbeeb}
+
+Name
+
+:
+
+> mri:characterSet
+
+Description
+
+:
+
+```{=html}
+Full name of the character coding standard used for the
+ metadata
+ set
+```
+
+Condition
+
+:
+
+> conditional
+
+### Checkpoint Availability {#iso19115-3.2018-elem-mri-checkPointAvailability-0d6de599f9bd32d29175051a4ae24928}
+
+Name
+
+:
+
+> mri:checkPointAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not geographic position points are
+ available to test
+ the accuracy of the georeferenced grid data
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Checkpoint Description {#iso19115-3.2018-elem-mri-checkPointDescription-555aba53a5c04b8cb05befe68bcf8524}
+
+Name
+
+:
+
+> mri:checkPointDescription
+
+Description
+
+:
+
+```{=html}
+Description of geographic position points used to test the
+ accuracy of the
+ georeferenced grid data
+```
+
+Condition
+
+:
+
+> conditional
+
+### Responsible party {#iso19115-3.2018-elem-mri-CI_ResponsibleParty-dc40d258bd15a7fb52433fbb269d409e}
+
+Name
+
+:
+
+> mri:CI_ResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s)
+ and organizations
+ associated with the dataset
+```
+### Role code {#iso19115-3.2018-elem-mri-CI_RoleCode-831e2b39ab9b602c6becdbf79b4f0443}
+
+Name
+
+:
+
+> mri:CI_RoleCode
+
+Description
+
+:
+
+### Series {#iso19115-3.2018-elem-mri-CI_Series-6a7b9c3a3ef0733a8f9b4180070cef1f}
+
+Name
+
+:
+
+> mri:CI_Series
+
+Description
+
+:
+
+```{=html}
+Information about the series, or aggregate dataset, to which a
+ dataset
+ belongs
+```
+### Citation {#iso19115-3.2018-elem-mri-citation-mri-MD_Identification-a2fcf35af33b9a01b7c462115da464dd}
+
+Name
+
+:
+
+> mri:citation
+
+Context
+
+:
+
+> mri:MD_Identification
+
+Description
+
+:
+
+```{=html}
+Citation data for the resource(s)
+```
+``` xml
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+```
+
+### Citation {#iso19115-3.2018-elem-mri-citation-mri-MD_Authority-eaa69cd35eb9afb1096bad7358353672}
+
+Name
+
+:
+
+> mri:citation
+
+Context
+
+:
+
+> mri:MD_Authority
+
+Description
+
+:
+
+```{=html}
+Citation which belongs to the authority
+```
+``` xml
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+```
+
+### Citation {#iso19115-3.2018-elem-mri-citation-mri-MD_Thesaurus-b6bb9eeb1a510d12d52677ed2bc11d8f}
+
+Name
+
+:
+
+> mri:citation
+
+Context
+
+:
+
+> mri:MD_Thesaurus
+
+Description
+
+:
+
+```{=html}
+Citation of the thesaurus
+```
+``` xml
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+```
+
+### Citation {#iso19115-3.2018-elem-mri-citation-c0c64fab562a266e6c2ed433b3aa4648}
+
+Name
+
+:
+
+> mri:citation
+
+Description
+
+:
+
+```{=html}
+Citation data for the resource(s)
+```
+``` xml
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+```
+
+### Class name {#iso19115-3.2018-elem-mri-className-04b5dd0e3097cde916ca0c5a4cfa35e1}
+
+Name
+
+:
+
+> mri:className
+
+Description
+
+:
+
+```{=html}
+Character string to label the keyword category in natural
+ language
+```
+### Unique resource identifier {#iso19115-3.2018-elem-mri-code-mri-RS_Identifier-c455cad07e7765deb05b6635b4fd9690}
+
+Name
+
+:
+
+> mri:code
+
+Context
+
+:
+
+> mri:RS_Identifier
+
+Description
+
+:
+
+```{=html}
+Alphanumeric value identifying an instance in the namespace
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Code {#iso19115-3.2018-elem-mri-code-mri-MD_CodeValue-28d6cd273cf6fbf5bb1aacf1d1a4baa9}
+
+Name
+
+:
+
+> mri:code
+
+Context
+
+:
+
+> mri:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Value code
+```
+```{=html}
+Value code (i.e. numeric)
+```
+### Collective title {#iso19115-3.2018-elem-mri-collectiveTitle-f256578a9a2233009afc61772d6a7f33}
+
+Name
+
+:
+
+> mri:collectiveTitle
+
+Description
+
+:
+
+```{=html}
+Common title with holdings note. NOTE title identifies elements
+ of a series
+ collectively, combined with information about what volumes are available
+ at the source
+ cited
+```
+```{=html}
+This field is used to name the Basic Geodata as defined in the GeoIV
+ Annex I, as it is possible that there are more than 1 "physical" datasets
+ assigned to 1 legal entry. E.g.: Entry no. 47 "Geophysikalisches
+ Kartenwerk" consists of 3 datasets "Geophysikalische Karten 1:500000",
+ "Geophysikalische Spezialkarten" and "Gravimetrischer Atlas 1:100000"
+```
+### ComposedOf {#iso19115-3.2018-elem-mri-composedOf-f92227eb3a814aba43b51e3d34cd42e5}
+
+Name
+
+:
+
+> mri:composedOf
+
+Description
+
+:
+
+```{=html}
+ComposedOf
+```
+### Compression generation quantity {#iso19115-3.2018-elem-mri-compressionGenerationQuantity-d160638acebb019ed7a920807bdbf1ab}
+
+Name
+
+:
+
+> mri:compressionGenerationQuantity
+
+Description
+
+:
+
+```{=html}
+Count of the number of lossy compression cycles
+ performed on the
+ image
+```
+### Concept Identifier {#iso19115-3.2018-elem-mri-conceptIdentifier-b98afc41c1dfd685b2c144a974df26f9}
+
+Name
+
+:
+
+> mri:conceptIdentifier
+
+Description
+
+:
+
+```{=html}
+URI of concept in the ontology specified by the next
+ element (ontology) and labelled by the previous element (className)
+```
+### Condition {#iso19115-3.2018-elem-mri-condition-d09f5c29e8fc98d775e2441859741fcd}
+
+Name
+
+:
+
+> mri:condition
+
+Description
+
+:
+
+```{=html}
+Condition under which the extended element is mandatory
+```
+### Metadata author {#iso19115-3.2018-elem-mri-contact-bacc2742e5169472e4f906ecdbe619aa}
+
+Name
+
+:
+
+> mri:contact
+
+Description
+
+:
+
+```{=html}
+Party responsible for the metadata information
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Controlpoint Availability {#iso19115-3.2018-elem-mri-controlPointAvailability-c8b4921fc9ebea36af87be3c0bf06a4b}
+
+Name
+
+:
+
+> mri:controlPointAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not control point(s) exists
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Corner points {#iso19115-3.2018-elem-mri-cornerPoints-32f0d2d110abed4a81576c25d2428903}
+
+Name
+
+:
+
+> mri:cornerPoints
+
+Description
+
+:
+
+```{=html}
+Earth location in the coordinate system defined by the Spatial
+ Reference System
+ and the grid coordinate of the cells at opposite ends of grid coverage
+ along two
+ diagonals in the grid spatial dimensions. There are four corner points in
+ a georectified
+ grid; at least two corner points along one diagonal are required
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Country {#iso19115-3.2018-elem-mri-country-mri-MD_Legislation-3b41c7104c5243085e9a8075d454b1a6}
+
+Name
+
+:
+
+> mri:country
+
+Context
+
+:
+
+> mri:MD_Legislation
+
+Description
+
+:
+
+```{=html}
+Country in which the law was issued
+```
+### Country {#iso19115-3.2018-elem-mri-country-PT_Group-5cc39a3f362fc6adbbb8ca2cc466b38b}
+
+Name
+
+:
+
+> mri:country
+
+Context
+
+:
+
+> PT_Group
+
+Description
+
+:
+
+```{=html}
+Country of language used for documenting a plain text
+```
+### Credit {#iso19115-3.2018-elem-mri-credit-f6c38ebd90277f0c08097e3db4cd7334}
+
+Name
+
+:
+
+> mri:credit
+
+Description
+
+:
+
+```{=html}
+Recognition of those who contributed to the resource(s)
+```
+### Dataset URI {#iso19115-3.2018-elem-mri-dataSetURI-3094b958d87ee68d3f1eb876b6645c15}
+
+Name
+
+:
+
+> mri:dataSetURI
+
+Description
+
+:
+
+```{=html}
+Uniformed Resource Identifier (URI) of the dataset to which the
+ metadata
+ applies
+```
+```{=html}
+Uniformed Resource Identifier (URI) of the dataset to which the
+ metadata applies. This
+ link refers direct to the machine-readable dataset.
+```
+### Data type {#iso19115-3.2018-elem-mri-dataType-04da587951dce6d554e42c1695bdd525}
+
+Name
+
+:
+
+> mri:dataType
+
+Description
+
+:
+
+```{=html}
+Code which identifies the kind of valueprovidedeprovided in the
+ extended
+ element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date {#iso19115-3.2018-elem-mri-date-6a55cc1dfd056e73aa1b4c012ce4574f}
+
+Name
+
+:
+
+> mri:date
+
+Description
+
+:
+
+```{=html}
+Reference date for the cited resource (YYYY-MM-DD)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date of last update {#iso19115-3.2018-elem-mri-date-mri-MD_Revision-729c81a65123dc90b3a9e9e306ac0694}
+
+Name
+
+:
+
+> mri:date
+
+Context
+
+:
+
+> mri:MD_Revision
+
+Description
+
+:
+
+```{=html}
+Date of last update
+```
+### Date of next update {#iso19115-3.2018-elem-mri-date-mri-MD_MaintenanceInformation-30e9e24621af992aa138556c1736c8a1}
+
+Name
+
+:
+
+> mri:date
+
+Context
+
+:
+
+> mri:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Scheduled revision date for resource
+```
+### Date of next update {#iso19115-3.2018-elem-mri-dateOfNextUpdate-22828f5e6b6f62144cf28bca8e708bb0}
+
+Name
+
+:
+
+> mri:dateOfNextUpdate
+
+Description
+
+:
+
+```{=html}
+Scheduled revision date for resource (YYYY-MM-DD)
+```
+### Date stamp {#iso19115-3.2018-elem-mri-dateStamp-daf76a0c4f3ff93e20644dd6ab31181c}
+
+Name
+
+:
+
+> mri:dateStamp
+
+Description
+
+:
+
+```{=html}
+Date that the metadata was created (YYYY-MM-DDThh:mm:ss)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date / Time {#iso19115-3.2018-elem-mri-dateTime-d2271d115f2a482a92c2e1a1dd3459eb}
+
+Name
+
+:
+
+> mri:dateTime
+
+Description
+
+:
+
+```{=html}
+Date and time or range of date and time on or over which the
+ process step
+ occurred (YYYY-MM-DDThh:mm:ss)
+```
+### Date / Time {#iso19115-3.2018-elem-mri-dateTime-LI_ProcessStep-3ad03f294b10052ffc357100eaa260ae}
+
+Name
+
+:
+
+> mri:dateTime
+
+Context
+
+:
+
+> LI_ProcessStep
+
+Description
+
+:
+
+```{=html}
+Date and time or range of date and time on or over which the
+ process step
+ occurred (YYYY-MM-DDThh:mm:ss)
+```
+### Date / Time {#iso19115-3.2018-elem-mri-dateTime-mri-DQ_Element-ff109aefe881cf309cad57b5773e87a8}
+
+Name
+
+:
+
+> mri:dateTime
+
+Context
+
+:
+
+> mri:DQ_Element
+
+Description
+
+:
+
+```{=html}
+Date or range of dates on which a data quality measure was
+ applied
+```
+### Default locale {#iso19115-3.2018-elem-mri-defaultLocale-354b26c7ab4ca62c4ea66a28a2d85ba7}
+
+Name
+
+:
+
+> mri:defaultLocale
+
+Description
+
+:
+
+```{=html}
+Language and character set used within the
+ resource
+```
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+### Definition {#iso19115-3.2018-elem-mri-definition-bf5edfffdd3034ef755376dafcfb4726}
+
+Name
+
+:
+
+> mri:definition
+
+Description
+
+:
+
+```{=html}
+Definition of the extended element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Denominator {#iso19115-3.2018-elem-mri-denominator-edd990de0c40bd27204fea0f87cb2c83}
+
+Name
+
+:
+
+> mri:denominator
+
+Description
+
+:
+
+```{=html}
+The number below the line in a vulgar fraction
+```
+
+Condition
+
+:
+
+> add either a denominator or a distance
+
+Recommended values
+
+| code | label |
+|---------|-------------|
+| 5000 | 1:5´000 |
+| 10000 | 1:10´000 |
+| 25000 | 1:25´000 |
+| 50000 | 1:50´000 |
+| 100000 | 1:100´000 |
+| 200000 | 1:200´000 |
+| 300000 | 1:300´000 |
+| 500000 | 1:500´000 |
+| 1000000 | 1:1´000´000 |
+
+``` xml
+
+ 25000
+
+```
+
+### Describes {#iso19115-3.2018-elem-mri-describes-47ece431d0767368e0126222741e51e3}
+
+Name
+
+:
+
+> mri:describes
+
+Description
+
+:
+
+```{=html}
+Describes
+```
+### Description {#iso19115-3.2018-elem-mri-description-dae99f8d3d2cea097c94167ab45d1141}
+
+Name
+
+:
+
+> mri:description
+
+Description
+
+:
+
+```{=html}
+Description of the event, including related parameters or
+ tolerances
+```
+### Description {#iso19115-3.2018-elem-mri-description-mri-MD_AbstractClass-4257d154e3ae528bdad656f043f167b3}
+
+Name
+
+:
+
+> mri:description
+
+Context
+
+:
+
+> mri:MD_AbstractClass
+
+Description
+
+:
+
+```{=html}
+Description
+```
+### Description {#iso19115-3.2018-elem-mri-description-LI_ProcessStep-3e394cb8d22507d6341ba875fff94ad5}
+
+Name
+
+:
+
+> mri:description
+
+Context
+
+:
+
+> LI_ProcessStep
+
+Description
+
+:
+
+```{=html}
+Description of the event, including related parameters or
+ tolerances
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Description {#iso19115-3.2018-elem-mri-description-mri-MD_CodeDomain-a073652c24dc830d64f1a571e5a5d398}
+
+Name
+
+:
+
+> mri:description
+
+Context
+
+:
+
+> mri:MD_CodeDomain
+
+Description
+
+:
+
+```{=html}
+Description of the code domain
+```
+### Value description {#iso19115-3.2018-elem-mri-description-mri-MD_CodeValue-c4f9744373b4f7ee492f3e74deec4e90}
+
+Name
+
+:
+
+> mri:description
+
+Context
+
+:
+
+> mri:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Description of the value
+```
+### Description {#iso19115-3.2018-elem-mri-description-mri-MD_Attribute-0cf58a01b569955380601f5c96a58d6f}
+
+Name
+
+:
+
+> mri:description
+
+Context
+
+:
+
+> mri:MD_Attribute
+
+Description
+
+:
+
+```{=html}
+Attribute description
+```
+### Description {#iso19115-3.2018-elem-mri-description-mri-MD_Role-0424c25c947e4c293301c06364d797c2}
+
+Name
+
+:
+
+> mri:description
+
+Context
+
+:
+
+> mri:MD_Role
+
+Description
+
+:
+
+```{=html}
+Role description
+```
+### Descriptive keywords {#iso19115-3.2018-elem-mri-descriptiveKeywords-3bbdaa8489a36cab45781306bdf7418c}
+
+Name
+
+:
+
+> mri:descriptiveKeywords
+
+Description
+
+:
+
+```{=html}
+Provides category keywords, their type, and reference source
+```
+### Descriptor {#iso19115-3.2018-elem-mri-descriptor-d03fecc7145f034b0e41d44613397ed4}
+
+Name
+
+:
+
+> mri:descriptor
+
+Description
+
+:
+
+```{=html}
+Description of the range of a cell measurement value
+```
+### Dimension {#iso19115-3.2018-elem-mri-dimension-53c837bdd73cb3e453d4bd6f3e1055f3}
+
+Name
+
+:
+
+> mri:dimension
+
+Description
+
+:
+
+```{=html}
+Information on the dimensions of the cell measurement value
+```
+### Dimension name {#iso19115-3.2018-elem-mri-dimensionName-3b4bcb3ee8f0f2a3f0a32e19e7932bcc}
+
+Name
+
+:
+
+> mri:dimensionName
+
+Description
+
+:
+
+```{=html}
+Name of the axis
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Dimension size {#iso19115-3.2018-elem-mri-dimensionSize-56ea1ddf2c206136a267554acc5d1c0e}
+
+Name
+
+:
+
+> mri:dimensionSize
+
+Description
+
+:
+
+```{=html}
+Number of elements along the axis
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Spatial resolution {#iso19115-3.2018-elem-mri-distance-3928324dc7cf53182407dbe43a21ccfd}
+
+Name
+
+:
+
+> mri:distance
+
+Description
+
+:
+
+```{=html}
+Ground sample distance
+```
+
+Condition
+
+:
+
+> Provide a distance if no equivalent Scale is documented
+
+Recommended values
+
+| code | label |
+|------|-------|
+| 0.10 | 10 cm |
+| 0.25 | 25 cm |
+| 0.50 | 50 cm |
+| 1 | 1 m |
+| 30 | 30 m |
+| 100 | 100 m |
+
+### Domain code {#iso19115-3.2018-elem-mri-domainCode-04aff018af98f2c97ba5e4889daea229}
+
+Name
+
+:
+
+> mri:domainCode
+
+Description
+
+:
+
+```{=html}
+Three digit code assigned to the extended element
+```
+### Domain of validity {#iso19115-3.2018-elem-mri-domainOfValidity-51dfb463c5bc44fb8ed66fa8bc54c46e}
+
+Name
+
+:
+
+> mri:domainOfValidity
+
+Description
+
+:
+
+```{=html}
+Range which is valid for the referencesystem
+```
+### Domain value {#iso19115-3.2018-elem-mri-domainValue-05bccd10b5fc9843957e6c93022f8e1d}
+
+Name
+
+:
+
+> mri:domainValue
+
+Description
+
+:
+
+```{=html}
+Valid values that can be assigned to the extended element
+```
+### Conformance result {#iso19115-3.2018-elem-mri-DQ_ConformanceResult-6fa2196468e3afbaa5831ce5af398ae6}
+
+Name
+
+:
+
+> mri:DQ_ConformanceResult
+
+Description
+
+:
+
+```{=html}
+Information about the outcome of evaluating the obtained value
+ (or set of
+ values) against a specified acceptable conformance quality level
+```
+### Scope {#iso19115-3.2018-elem-mri-DQ_Scope-5db3160e69e03b2221e538d816192372}
+
+Name
+
+:
+
+> mri:DQ_Scope
+
+Description
+
+:
+
+```{=html}
+Description of the data specified by the scope
+```
+```{=html}
+extent of characteristic(s) of the data for which quality information
+ is
+ reported
+```
+### DS_Association {#iso19115-3.2018-elem-mri-DS_Association-625caa34f37621855b1adc979fdf5ecf}
+
+Name
+
+:
+
+> mri:DS_Association
+
+Description
+
+:
+
+```{=html}
+DS_Association
+```
+### DS_DataSet {#iso19115-3.2018-elem-mri-DS_DataSet-b5e6c1fc90906663f44d86998594b001}
+
+Name
+
+:
+
+> mri:DS_DataSet
+
+Description
+
+:
+
+```{=html}
+DS_DataSet
+```
+### DS_Initiative {#iso19115-3.2018-elem-mri-DS_Initiative-f5b135d1832358421374540b97006ef2}
+
+Name
+
+:
+
+> mri:DS_Initiative
+
+Description
+
+:
+
+```{=html}
+DS_Initiative
+```
+### DS_OtherAggregate {#iso19115-3.2018-elem-mri-DS_OtherAggregate-2d9d8e81109c16a488a15dea67edbe24}
+
+Name
+
+:
+
+> mri:DS_OtherAggregate
+
+Description
+
+:
+
+```{=html}
+DS_OtherAggregate
+```
+### DS_Platform {#iso19115-3.2018-elem-mri-DS_Platform-395f7c4d1717e416dcf564d4062adefe}
+
+Name
+
+:
+
+> mri:DS_Platform
+
+Description
+
+:
+
+```{=html}
+DS_Platform
+```
+### DS_ProductionSeries {#iso19115-3.2018-elem-mri-DS_ProductionSeries-5921b13217f1a54a7fe5be17bb100ba3}
+
+Name
+
+:
+
+> mri:DS_ProductionSeries
+
+Description
+
+:
+
+```{=html}
+DS_ProductionSeries
+```
+### DS_Sensor {#iso19115-3.2018-elem-mri-DS_Sensor-c627d0348b2116c3948d2028e1d7dbe5}
+
+Name
+
+:
+
+> mri:DS_Sensor
+
+Description
+
+:
+
+```{=html}
+DS_Sensor
+```
+### DS_Series {#iso19115-3.2018-elem-mri-DS_Series-c84ca9870459bc2c905b3625036ced17}
+
+Name
+
+:
+
+> mri:DS_Series
+
+Description
+
+:
+
+```{=html}
+DS_Series
+```
+### DS_StereoMate {#iso19115-3.2018-elem-mri-DS_StereoMate-8fc4ee2a9b8c90412129e6a8f0e94931}
+
+Name
+
+:
+
+> mri:DS_StereoMate
+
+Description
+
+:
+
+```{=html}
+DS_StereoMate
+```
+### East bound {#iso19115-3.2018-elem-mri-eastBoundLongitude-1b0c554db3391725ff40fd4b3f7d4d4d}
+
+Name
+
+:
+
+> mri:eastBoundLongitude
+
+Description
+
+:
+
+```{=html}
+Eastern-most coordinate of the limit of the dataset extent,
+ expressed in
+ longitude in decimal degrees (positive east)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Environment description {#iso19115-3.2018-elem-mri-environmentDescription-ac2adb30f1402078f5b6f707c3d9c2f1}
+
+Name
+
+:
+
+> mri:environmentDescription
+
+Description
+
+:
+
+```{=html}
+Description of the dataset in the producer_s processing
+ environment, including
+ items such as the software, the computer operating system, file name, and
+ the dataset
+ size
+```
+### Equivalent scale {#iso19115-3.2018-elem-mri-equivalentScale-2fd017e8c8cd6e6663fe128196d0be07}
+
+Name
+
+:
+
+> mri:equivalentScale
+
+Description
+
+:
+
+```{=html}
+Level of detail expressed as the scale of a comparable hardcopy
+ map or
+ chart
+```
+``` xml
+
+
+
+ 25000
+
+
+
+```
+
+### Error statistic {#iso19115-3.2018-elem-mri-errorStatistic-df112e02728fdfa199b3c136c6ff11fd}
+
+Name
+
+:
+
+> mri:errorStatistic
+
+Description
+
+:
+
+```{=html}
+Statistical method used to determine the value
+```
+### Evaluation method description {#iso19115-3.2018-elem-mri-evaluationMethodDescription-ee3bd83356c3eafce1900c161d09c14a}
+
+Name
+
+:
+
+> mri:evaluationMethodDescription
+
+Description
+
+:
+
+```{=html}
+Description of the evaluation method
+```
+### Evaluation Method {#iso19115-3.2018-elem-mri-evaluationMethodType-ad6e089dfe9c39eaa2e5f6cf3e7dbf9c}
+
+Name
+
+:
+
+> mri:evaluationMethodType
+
+Description
+
+:
+
+```{=html}
+Type of method used to evaluate quality of the dataset
+```
+### Evaluation procedure {#iso19115-3.2018-elem-mri-evaluationProcedure-dd1d15f51eea1fc725ba6dc3dca04024}
+
+Name
+
+:
+
+> mri:evaluationProcedure
+
+Description
+
+:
+
+```{=html}
+Reference to the procedure information
+```
+### Explanation {#iso19115-3.2018-elem-mri-explanation-4a7325eb479000c4bf97ced8d8f40d22}
+
+Name
+
+:
+
+> mri:explanation
+
+Description
+
+:
+
+```{=html}
+Explanation of the meaning of conformance for this result
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Extended element information {#iso19115-3.2018-elem-mri-extendedElementInformation-41146f06b4994ea88616e35991861c17}
+
+Name
+
+:
+
+> mri:extendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Provides information about a new metadata element, not found in
+ ISO 19115, which is required to describe geographic data
+```
+### Extension Online resource {#iso19115-3.2018-elem-mri-extensionOnLineResource-7c1d5fd25b64912f01f87f3b3575b621}
+
+Name
+
+:
+
+> mri:extensionOnLineResource
+
+Description
+
+:
+
+```{=html}
+Information about on-line sources containing the community
+ profile name and the extended metadata elements. Information for all new metadata elements
+```
+### Extent {#iso19115-3.2018-elem-mri-extent-2265c394538ef47049b9d39e1431a5b1}
+
+Name
+
+:
+
+> mri:extent
+
+Description
+
+:
+
+```{=html}
+Extent information including the bounding polygon, vertical,
+ and temporal extent of the dataset
+```
+``` xml
+
+
+
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+
+
+
+```
+
+### Facsimile {#iso19115-3.2018-elem-mri-facsimile-ed44306eda27fbc251eb4cb8d042c12e}
+
+Name
+
+:
+
+> mri:facsimile
+
+Description
+
+:
+
+```{=html}
+Telephone number of a facsimile machine for the responsible organization or individual
+```
+### Feature attribute {#iso19115-3.2018-elem-mri-featureAttribute-c9379b1b5ddea9c2098fb5eb5d473c07}
+
+Name
+
+:
+
+> mri:featureAttribute
+
+Description
+
+:
+
+### Feature type {#iso19115-3.2018-elem-mri-featureType-affc938534ba82ccfad753e3de66f4dc}
+
+Name
+
+:
+
+> mri:featureType
+
+Description
+
+:
+
+```{=html}
+Subset of feature types from cited feature catalogue occurring
+ in
+ data
+```
+### Geometric object count {#iso19115-3.2018-elem-mri-geometricObjectCount-3db26814a8c8452828933028c75dc10b}
+
+Name
+
+:
+
+> mri:geometricObjectCount
+
+Description
+
+:
+
+```{=html}
+Total number of the point or vector object type occurring in
+ the
+ dataset
+```
+### Geometric objects {#iso19115-3.2018-elem-mri-geometricObjects-29d1b872c8bcf5d90e3e3ea7155c59b3}
+
+Name
+
+:
+
+> mri:geometricObjects
+
+Description
+
+:
+
+```{=html}
+Information about the geometric objects used in the dataset
+```
+### Geometric object type {#iso19115-3.2018-elem-mri-geometricObjectType-13b5366ea59d71264a65d4238c788e41}
+
+Name
+
+:
+
+> mri:geometricObjectType
+
+Description
+
+:
+
+```{=html}
+Name of point and vector spatial objects used to locate zero-,
+ one-, and
+ two-dimensional spatial locations in the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### GeoreferencedParameters {#iso19115-3.2018-elem-mri-georeferencedParameters-028b4f1108628c33bb915234d2324ab5}
+
+Name
+
+:
+
+> mri:georeferencedParameters
+
+Description
+
+:
+
+```{=html}
+GeoreferencedParameters
+```
+### Graphic overview {#iso19115-3.2018-elem-mri-graphicOverview-8640aa6248a384d60f83fa2c32942577}
+
+Name
+
+:
+
+> mri:graphicOverview
+
+Description
+
+:
+
+```{=html}
+Provides a graphic that illustrates the resource(s) (should
+ include a legend
+ for the graphic)
+```
+### Has {#iso19115-3.2018-elem-mri-has-a62a70d8d758396c952ad3c7a7090571}
+
+Name
+
+:
+
+> mri:has
+
+Description
+
+:
+
+```{=html}
+Has
+```
+### Hierarchy level {#iso19115-3.2018-elem-mri-hierarchyLevel-1ba3e3235eedebc22f7ff178c66f25c6}
+
+Name
+
+:
+
+> mri:hierarchyLevel
+
+Description
+
+:
+
+```{=html}
+Scope to which the metadata applies (see annex H for more
+ information about
+ metadata hierarchy levels)
+```
+### Hierarchy level name {#iso19115-3.2018-elem-mri-hierarchyLevelName-55cf15d0f210413ac816ec9e8abce9ac}
+
+Name
+
+:
+
+> mri:hierarchyLevelName
+
+Description
+
+:
+
+```{=html}
+Name of the hierarchy levels for which the metadata is
+ provided
+```
+### Identified issues {#iso19115-3.2018-elem-mri-identifiedIssues-ee073e37cce74aaabfd1c7d230c349ab}
+
+Name
+
+:
+
+> mri:identifiedIssues
+
+Description
+
+:
+
+```{=html}
+Citation of a description of known issues associated
+ with the resource along with proposed solutions if available
+```
+### Identifier {#iso19115-3.2018-elem-mri-identifier-a2ed8fa00e68521846e3c515084cb9f9}
+
+Name
+
+:
+
+> mri:identifier
+
+Description
+
+:
+
+```{=html}
+Unique identifier for the resource. EXAMPLE: Universal Product
+ Code (UPC),
+ National Stock Number (NSN)
+```
+### Identifier {#iso19115-3.2018-elem-mri-identifier-mri-MD_Authority-14f0abc5b645685e06a83445d163dfae}
+
+Name
+
+:
+
+> mri:identifier
+
+Context
+
+:
+
+> mri:MD_Authority
+
+Description
+
+:
+
+```{=html}
+Identifier which belongs to the authority
+```
+### Included with dataset {#iso19115-3.2018-elem-mri-includedWithDataset-5f9bc1136b461cdfc172fc42fc0419be}
+
+Name
+
+:
+
+> mri:includedWithDataset
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the feature catalogue is included
+ with the
+ dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Initiative Type {#iso19115-3.2018-elem-mri-initiativeType-1004a8e07ee24afe674aeaa8e59e230e}
+
+Name
+
+:
+
+> mri:initiativeType
+
+Description
+
+:
+
+```{=html}
+Type of initiative under which the aggregate dataset was
+ produced
+```
+### Keyword {#iso19115-3.2018-elem-mri-keyword-71c3570eaf518f78a536bb606c93f359}
+
+Name
+
+:
+
+> mri:keyword
+
+Description
+
+:
+
+```{=html}
+Commonly used word(s) or formalised word(s) or phrase(s) used
+ to describe the
+ subject
+```
+### Keyword class {#iso19115-3.2018-elem-mri-keywordClass-8bcc88fad14d5de58ebe26e47303657a}
+
+Name
+
+:
+
+> mri:keywordClass
+
+Description
+
+:
+
+```{=html}
+association of a MD_Keywords instance with a
+ MD_KeywordClass to provide user-defined categorization of groups of
+ keywords that extend or are orthogonal to the standardized
+ KeywordTypeCodes and are associated with an ontology that allows
+ additional semantic query processing NOTE The thesaurus citation specifies
+ a collection of instances from some ontology, but is not an ontology. It
+ might be a list of places that include rivers, mountains, counties and
+ cities. There might be a Laconte county, the city of Laconte, the Laconte
+ River, and Mt. Laconte; when searching it is useful for the user to be
+ able to restrict the search to only rivers.
+```
+### Metadata language {#iso19115-3.2018-elem-mri-language-mri-MD_Metadata-35e24f579bcdd8eb6b3a4afd1fb07d75}
+
+Name
+
+:
+
+> mri:language
+
+Context
+
+:
+
+> mri:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Language used for documenting metadata
+```
+
+Condition
+
+:
+
+> conditional
+
+### Language {#iso19115-3.2018-elem-mri-language-mri-MD_DataIdentification-1a91b7a90b04ad15f6d973265b70dc48}
+
+Name
+
+:
+
+> mri:language
+
+Context
+
+:
+
+> mri:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Language(s) used within the dataset
+```
+```{=html}
+language(s) used within the dataset
+```
+### Language {#iso19115-3.2018-elem-mri-languageCode-305fbc461b78dd7b5659ea8a28a96cdf}
+
+Name
+
+:
+
+> mri:languageCode
+
+Description
+
+:
+
+```{=html}
+Language code
+```
+### ISO Language code {#iso19115-3.2018-elem-mri-LanguageCode-440e7030d461f7a681b67af921c79bfb}
+
+Name
+
+:
+
+> mri:LanguageCode
+
+Description
+
+:
+
+```{=html}
+Language code
+```
+### Level of detail {#iso19115-3.2018-elem-mri-levelOfDetail-401a945f53a61c9289d6a8e0d372cf99}
+
+Name
+
+:
+
+> mri:levelOfDetail
+
+Description
+
+:
+
+```{=html}
+Brief textual description of the spatial resolution of the
+ resource
+```
+### Process step {#iso19115-3.2018-elem-mri-LI_ProcessStep-2e909c9f21434501914535cfcaf75997}
+
+Name
+
+:
+
+> mri:LI_ProcessStep
+
+Description
+
+:
+
+```{=html}
+Information about an event in the creation process for the data
+ specified by
+ the scope
+```
+```{=html}
+information about an event or transformation in the life of a dataset
+ including the
+ process used to maintain the dataset
+```
+### Source {#iso19115-3.2018-elem-mri-LI_Source-5cd1e641a7cfe7cc97c848bce1a49475}
+
+Name
+
+:
+
+> mri:LI_Source
+
+Description
+
+:
+
+```{=html}
+Information about the source data used in creating the data
+ specified by the
+ scope
+```
+### Lineage {#iso19115-3.2018-elem-mri-lineage-4a5e3f33503eddf336b5c8fb9a0dec13}
+
+Name
+
+:
+
+> mri:lineage
+
+Description
+
+:
+
+```{=html}
+Non-quantitative quality information about the lineage of the
+ data specified by
+ the scope
+```
+### Maximum occurrence {#iso19115-3.2018-elem-mri-maximumOccurrence-08133a89b21a5fea01ca6a8f80fa0386}
+
+Name
+
+:
+
+> mri:maximumOccurrence
+
+Description
+
+:
+
+```{=html}
+Maximum occurrence of the extended element
+```
+### Aggregate Information {#iso19115-3.2018-elem-mri-MD_AggregateInformation-140ed169bbe03a66caa26f1a81cc4dc5}
+
+Name
+
+:
+
+> mri:MD_AggregateInformation
+
+Description
+
+:
+
+```{=html}
+Aggregate dataset information
+```
+### Associated resource {#iso19115-3.2018-elem-mri-MD_AssociatedResource-4741c31756de110640d3751ef259b610}
+
+Name
+
+:
+
+> mri:MD_AssociatedResource
+
+Description
+
+:
+
+```{=html}
+Associated resource information
+```
+### Data identification {#iso19115-3.2018-elem-mri-MD_DataIdentification-45539414c34262f719bd1a9cb65d5c34}
+
+Name
+
+:
+
+> mri:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Information required to identify a dataset
+```
+``` xml
+
+
+
+
+ INSPIRE - TG2 - Template
+
+
+
+
+ 2019-10-01
+
+
+
+
+
+
+
+
+
+ 48c6f2bb-4828-46eb-a2cc-d5bcb94340dc
+
+
+ https://registry.organisation.fr/datasets
+
+
+
+
+
+
+ Description du jeu de données
+
+
+
+
+
+
+
+
+
+
+
+
+ Organisation
+
+
+
+
+
+
+ mail@organisation.org
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 25000
+
+
+
+
+
+
+ biota
+
+
+ environment
+
+
+
+
+
+
+ 2.78
+
+
+ 6.41
+
+
+ 49.46
+
+
+ 50.85
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Protected site
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ GEMET themes
+
+
+
+
+ 2009-09-22
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Natura 2000 sites (Birds Directive)
+
+
+
+
+
+
+
+ INSPIRE priority data set
+
+
+
+
+ 2018-04-24
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ No
+ limitations to public access
+
+
+
+
+
+
+ Conditions d'accès et d'utilisation
+
+
+
+
+
+ Description des autres contraintes (eg. CGI, Licence)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### Dimension {#iso19115-3.2018-elem-mri-MD_Dimension-4247609a5b17f0635f0771ccf8f1d7c6}
+
+Name
+
+:
+
+> mri:MD_Dimension
+
+Description
+
+:
+
+```{=html}
+Axis properties
+```
+### Extended Element Information {#iso19115-3.2018-elem-mri-MD_ExtendedElementInformation-b44873eaadd8ccde9aedba5fb0f6378d}
+
+Name
+
+:
+
+> mri:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+New metadata element, not found in ISO 19115, which is required
+ to describe
+ geographic data
+```
+### Geometric objects {#iso19115-3.2018-elem-mri-MD_GeometricObjects-701be4ade2337a169cdd7437341bdfd8}
+
+Name
+
+:
+
+> mri:MD_GeometricObjects
+
+Description
+
+:
+
+```{=html}
+Number of objects, listed by geometric object type, used in the
+ dataset
+```
+### Georectified {#iso19115-3.2018-elem-mri-MD_Georectified-9cd3df419c9405e05aa22437fd8f44b8}
+
+Name
+
+:
+
+> mri:MD_Georectified
+
+Description
+
+:
+
+```{=html}
+Grid whose cells are regularly spaced in a geographic (i.e.,
+ lat / long) or map
+ coordinate system defined in the Spatial Referencing System (SRS) so that
+ any cell in
+ the grid can be geolocated given its grid coordinate and the grid origin,
+ cell spacing,
+ and orientation
+```
+### Georeferenceable {#iso19115-3.2018-elem-mri-MD_Georeferenceable-6f861dc9dcd05001b271619beb2a0b02}
+
+Name
+
+:
+
+> mri:MD_Georeferenceable
+
+Description
+
+:
+
+```{=html}
+Grid with cells irregularly spaced in any given geographic/map
+ projection
+ coordinate system, whose individual cells can be geolocated using
+ geolocation
+ information supplied with the data but cannot be geolocated from the grid
+ properties
+ alone
+```
+### Grid spatial representation {#iso19115-3.2018-elem-mri-MD_GridSpatialRepresentation-704f579a18d1e383740b32a1c40f4025}
+
+Name
+
+:
+
+> mri:MD_GridSpatialRepresentation
+
+Description
+
+:
+
+```{=html}
+Information about grid spatial objects in the dataset
+```
+### Keyword class {#iso19115-3.2018-elem-mri-MD_KeywordClass-e8da816d8a2be293339b5591c5b31709}
+
+Name
+
+:
+
+> mri:MD_KeywordClass
+
+Description
+
+:
+
+```{=html}
+Specification of a class to categorize keywords in a
+ domain-specific vocabulary that has a binding to a formal ontology
+```
+### Keywords {#iso19115-3.2018-elem-mri-MD_Keywords-c8844255cb6b1346e604a53d830e6697}
+
+Name
+
+:
+
+> mri:MD_Keywords
+
+Description
+
+:
+
+```{=html}
+Keywords, their type and reference source
+```
+### Metadata Extension Information {#iso19115-3.2018-elem-mri-MD_MetadataExtensionInformation-0d852a81587a640b13d910e246bda49f}
+
+Name
+
+:
+
+> mri:MD_MetadataExtensionInformation
+
+Description
+
+:
+
+```{=html}
+Information describing metadata extensions
+```
+### Obligation code {#iso19115-3.2018-elem-mri-MD_ObligationCode-0457c04f99f950848fce2bed3f4ef83b}
+
+Name
+
+:
+
+> mri:MD_ObligationCode
+
+Description
+
+:
+
+```{=html}
+Obligation of the element or entity
+```
+### Representative fraction {#iso19115-3.2018-elem-mri-MD_RepresentativeFraction-af8f6be9f23e0d14630082d51a310384}
+
+Name
+
+:
+
+> mri:MD_RepresentativeFraction
+
+Description
+
+:
+
+```{=html}
+Derived from Scale where MD_RepresentativeFraction.denominator
+ = 1 /
+ Scale.measure And Scale.targetUnits = Scale.sourceUnits
+```
+``` xml
+
+
+ 25000
+
+
+```
+
+### Resolution {#iso19115-3.2018-elem-mri-MD_Resolution-e0b4cae62a188c5bc322edb64b2d26b0}
+
+Name
+
+:
+
+> mri:MD_Resolution
+
+Description
+
+:
+
+```{=html}
+Level of detail expressed as a scale factor or a ground
+ distance
+```
+``` xml
+
+
+
+
+ 25000
+
+
+
+
+```
+
+### Resolution type {#iso19115-3.2018-elem-mri-MD_Resolution_Type-de6a074ca31faa71c5dc3549bb2ade22}
+
+Name
+
+:
+
+> mri:MD_Resolution_Type
+
+Description
+
+:
+
+### Scope code {#iso19115-3.2018-elem-mri-MD_ScopeCode-836acd6fc05e96ec03dca7f9e6cef9e9}
+
+Name
+
+:
+
+> mri:MD_ScopeCode
+
+Description
+
+:
+
+```{=html}
+Class of information to which the referencing entity applies
+```
+### Service Identification {#iso19115-3.2018-elem-mri-MD_ServiceIdentification-ae78ae27b9261dcfde913c0f1780d1fe}
+
+Name
+
+:
+
+> mri:MD_ServiceIdentification
+
+Description
+
+:
+
+```{=html}
+Identification of capabilities which a service provider makes
+ available to a
+ service user through a set of interfaces that define a behaviour - See ISO
+ 19119 -
+ Services for further information
+```
+### Topic category code {#iso19115-3.2018-elem-mri-MD_TopicCategoryCode-809913fe5286f1b06f3cef490e3eb204}
+
+Name
+
+:
+
+> mri:MD_TopicCategoryCode
+
+Description
+
+:
+
+```{=html}
+High-level geographic data thematic classification to assist in
+ the grouping
+ and search of available geographic data sets. Can be used to group
+ keywords as well.
+ Listed examples are not exhaustive. NOTE It is understood there are
+ overlaps between
+ general categories and the user is encouraged to select the one most
+ appropriate.
+```
+### Standard codelists Topic category code (mri:MD_TopicCategoryCode)
+
+| code | label | description |
+|----------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| farming | Farming | Rearing of animals and/or cultivation of plants. Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock |
+| biota | Biota | Flora and/or fauna in natural environment. Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat |
+| boundaries | Boundaries | Legal land descriptions. Examples: political and administrative boundaries |
+| climatologyMeteorologyAtmosphere | Climatology, meteorology, atmosphere | Processes and phenomena of the atmosphere. Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation |
+| economy | Economy | Economic activities, conditions and employment. Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas |
+| elevation | Elevation | Height above or below sea level. Examples: altitude, bathymetry, digital elevation models, slope, derived products |
+| environment | Environment | Environmental resources, protection and conservation. Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape |
+| geoscientificInformation | Geoscientific information | Information pertaining to earth sciences. Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion |
+| health | Health | Health, health services, human ecology, and safety. Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services |
+| imageryBaseMapsEarthCover | Imagery base maps earth cover | Base maps. Examples: land cover, topographic maps, imagery, unclassified images, annotations |
+| intelligenceMilitary | Intelligence military | Military bases, structures, activities. Examples: barracks, training grounds, military transportation, information collection |
+| inlandWaters | Inland waters | Inland water features, drainage systems and their characteristics. Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts |
+| location | Location | Positional information and services. Examples: addresses, geodetic networks, control points, postal zones and services, place names |
+| oceans | Oceans | Features and characteristics of salt water bodies (excluding inland waters). Examples: tides, tidal waves, coastal information, reefs |
+| planningCadastre | Planning cadastre | Information used for appropriate actions for future use of the land. Examples: land use maps, zoning maps, cadastral surveys, land ownership |
+| society | Society | Characteristics of society and cultures. Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information |
+| structure | Structure | Man-made construction. Examples: buildings, museums, churches, factories, housing, monuments, shops, towers |
+| transportation | Transportation | Means and aids for conveying persons and/or goods. Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways |
+| utilitiesCommunication | Utilities communication | Energy, water and waste systems and communications infrastructure andservices. Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks |
+| extraTerrestrial | Extra Terrestrial | Region more than 100 km above the surface of the Earth |
+| disaster | Disaster | Information related to disasters EXAMPLES: Site of the disaster, evacuation zone, disaster-prevention facility, disaster relief activities |
+
+### Usage {#iso19115-3.2018-elem-mri-MD_Usage-28b7ff49f2495cc919db1dfdb5504d4a}
+
+Name
+
+:
+
+> mri:MD_Usage
+
+Description
+
+:
+
+```{=html}
+Brief description of ways in which the resource(s) is/are
+ currently
+ used
+```
+### Vector spatial representation {#iso19115-3.2018-elem-mri-MD_VectorSpatialRepresentation-1fa2cede09489f2fe243fa7e91a26c94}
+
+Name
+
+:
+
+> mri:MD_VectorSpatialRepresentation
+
+Description
+
+:
+
+```{=html}
+Information about the vector spatial objects in the dataset
+```
+### Measure description {#iso19115-3.2018-elem-mri-measureDescription-20a5a3fe84e0b24da0dc627dde2ba323}
+
+Name
+
+:
+
+> mri:measureDescription
+
+Description
+
+:
+
+```{=html}
+Description of the measure being determined
+```
+### Measure identification {#iso19115-3.2018-elem-mri-measureIdentification-5d7fb93ef9082c314e8c8f7245a54d93}
+
+Name
+
+:
+
+> mri:measureIdentification
+
+Description
+
+:
+
+```{=html}
+Code identifying a registered standard procedure
+```
+### Metadata Reference {#iso19115-3.2018-elem-mri-metadataReference-10650eae9154c3c351793de92fffaf31}
+
+Name
+
+:
+
+> mri:metadataReference
+
+Description
+
+:
+
+```{=html}
+Reference to the metadata of the associated
+ resource
+```
+### Metadata standard name {#iso19115-3.2018-elem-mri-metadataStandardName-f03bf900f90b2510635c8fe4b33a13d2}
+
+Name
+
+:
+
+> mri:metadataStandardName
+
+Description
+
+:
+
+```{=html}
+Name of the metadata standard (including profile name) used
+```
+### Metadata standard version {#iso19115-3.2018-elem-mri-metadataStandardVersion-d38c2f3d2a6d13013d6ea511e584b610}
+
+Name
+
+:
+
+> mri:metadataStandardVersion
+
+Description
+
+:
+
+```{=html}
+Version (profile) of the metadata standard used
+```
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_AbstractClass-9877241cc220793ccba8ca14dcc1b384}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_AbstractClass
+
+Description
+
+:
+
+```{=html}
+Name
+```
+### Name {#iso19115-3.2018-elem-mri-name-mri-RS_ReferenceSystem-c677cc018d021b59efd4d4877cc8b127}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:RS_ReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Name of reference system used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_Format-8ba2d3536f54f8f338f96ee1c631fb7a}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_Format
+
+Description
+
+:
+
+```{=html}
+Name of the data transfer format(s)
+```
+```{=html}
+name of the data transfer format(s)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_ExtendedElementInformation-71da9b45b9a805e89bdb4ebb0e589286}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Name of the extended metadata element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_AssociatedResource-592c1a294a5f5e20abb8a2eb4ff9fd5d}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_AssociatedResource
+
+Description
+
+:
+
+```{=html}
+To be provided if no metadata reference provided
+```
+### Name {#iso19115-3.2018-elem-mri-name-4ced2246372284fb55369904f44d6a96}
+
+Name
+
+:
+
+> mri:name
+
+Description
+
+:
+
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_CodeDomain-7e463975608cc25196e1a6e9331330b6}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_CodeDomain
+
+Description
+
+:
+
+```{=html}
+Name of the code domain
+```
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_CodeValue-2e8d7c21f7913f12492cecdfdafd9f87}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Value name
+```
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_Attribute-34776ed0db644231645dbea5da7a6d41}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_Attribute
+
+Description
+
+:
+
+```{=html}
+Attribute name
+```
+### Name {#iso19115-3.2018-elem-mri-name-mri-MD_Role-dbac7d81940bece1b2bd05ee942e0f1a}
+
+Name
+
+:
+
+> mri:name
+
+Context
+
+:
+
+> mri:MD_Role
+
+Description
+
+:
+
+```{=html}
+Role name
+```
+### Name of measure {#iso19115-3.2018-elem-mri-nameOfMeasure-339a7390bc51c94a8cd698950f14e00a}
+
+Name
+
+:
+
+> mri:nameOfMeasure
+
+Description
+
+:
+
+```{=html}
+Name of the test applied to the data
+```
+Recommended values
+
+| code | label |
+|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| | -- Completeness -- |
+| Excess item | Excess item |
+| Number of excess items | Number of excess items |
+| Rate of excess items | Rate of excess items |
+| Number of duplicate feature instances | Number of duplicate feature instances |
+| Missing item | Missing item |
+| Number of missing items | Number of missing items |
+| Rate of missing items | Rate of missing items -- Logical consistency / Conceptual consistency -- |
+| Conceptual schema noncompliance | Conceptual schema noncompliance |
+| Conceptual schema compliance | Conceptual schema compliance |
+| Number of items noncompliant to the rules of the conceptual schema | Number of items noncompliant to the rules of the conceptual schema |
+| Number of invalid overlaps of surfaces | Number of invalid overlaps of surfaces |
+| Non-compliance rate with respect to the rules of the conceptual schema | Non-compliance rate with respect to the rules of the conceptual schema |
+| Compliance rate with the rules of the conceptual schema | Compliance rate with the rules of the conceptual schema -- Logical consistency / Domain consistency -- |
+| Value domain non-conformance | Value domain non-conformance |
+| Value domain conformance | Value domain conformance |
+| Number of items not in conformance with their value domain | Number of items not in conformance with their value domain |
+| Value domain conformance rate | Value domain conformance rate |
+| Value domain non-conformance rate | Value domain non-conformance rate |
+| Physical structure conflicts | Physical structure conflicts |
+| Physical structure conflict rate | Physical structure conflict rate -- Logical consistency / Topological consistency -- |
+| Number of faulty point-curve connections | Number of faulty point-curve connections |
+| Rate of faulty point-curve connections | Rate of faulty point-curve connections |
+| Number of missing connection due to undershoots | Number of missing connection due to undershoots |
+| Number of missing connections due to overshoots | Number of missing connections due to overshoots |
+| Number of invalid slivers | Number of invalid slivers |
+| Number of invalid self intersect errors | Number of invalid self intersect errors |
+| Number of invalid self overlap errors | Number of invalid self overlap errors -- Positional accuracy / Absolute or external accuracy / General measures -- |
+| Mean value of positional uncertainties | Mean value of positional uncertainties |
+| Mean value of positional uncertainties excluding outliers | Mean value of positional uncertainties excluding outliers |
+| Number of positional uncertainties above a given threshold | Number of positional uncertainties above a given threshold |
+| Rate of positional errors above a given threshold | Rate of positional errors above a given threshold |
+| Covariance matrix | Covariance matrix -- Positional accuracy / Absolute or external accuracy / Vertical -- |
+| Linear error probable | Linear error probable |
+| Standard linear error | Standard linear error |
+| Linear map accuracy at 90% significance level | Linear map accuracy at 90% significance level |
+| Linear map accuracy at 95% significance level | Linear map accuracy at 95% significance level |
+| Linear map accuracy at 99% significance level | Linear map accuracy at 99% significance level |
+| Near certainty linear error | Near certainty linear error |
+| Root mean square error | Root mean square error |
+| Absolute linear error at 90% significance level of biased vertical data (Alternative 1) | Absolute linear error at 90% significance level of biased vertical data (Alternative 1) |
+| Absolute linear error at 90% significance level of biased vertical data | Absolute linear error at 90% significance level of biased vertical data -- Positional accuracy / Absolute or external accuracy / Horizontal -- |
+| Circular standard deviation | Circular standard deviation |
+| Circular error probable | Circular error probable |
+| Circular map accuracy standard | Circular map accuracy standard |
+| Circular error at 95% significance level | Circular error at 95% significance level |
+| Circular near certainty error | Circular near certainty error |
+| Root mean square error of planimetry | Root mean square error of planimetry |
+| Absolute circular error at 90% significance level of biased data (Alternative 2) | Absolute circular error at 90% significance level of biased data (Alternative 2) |
+| Absolute circular error at 90% significance level of biased data | Absolute circular error at 90% significance level of biased data |
+| Uncertainty ellipse | Uncertainty ellipse |
+| Confidence ellipse | Confidence ellipse -- Positional accuracy / Relative or internal accuracy -- |
+| Relative vertical error | Relative vertical error |
+| Relative horizontal error | Relative horizontal error -- Temporal accuracy / Accuracy of a time measurement -- |
+| Time accuracy at 68.3% significance level | Time accuracy at 68.3% significance level |
+| Time accuracy at 50% significance level | Time accuracy at 50% significance level |
+| Time accuracy at 90% significance level | Time accuracy at 90% significance level |
+| Time accuracy at 95% significance level | Time accuracy at 95% significance level |
+| Time accuracy at 99% significance level | Time accuracy at 99% significance level |
+| Time accuracy at 99.8% significance level | Time accuracy at 99.8% significance level -- Thematic accuracy / Classification correctness -- |
+| Number of incorrectly classified features | Number of incorrectly classified features |
+| Misclassification rate | Misclassification rate |
+| Misclassification matrix | Misclassification matrix |
+| Relative misclassification matrix | Relative misclassification matrix |
+| Kappa coefficient | Kappa coefficient -- Thematic accuracy / Non-quantitative attribute correctness -- |
+| Number of incorrect attribute values | Number of incorrect attribute values |
+| Rate of correct attribute values | Rate of correct attribute values |
+| Rate of incorrect attribute values | Rate of incorrect attribute values -- Thematic accuracy / Quantitative attribute accuracy -- |
+| Attribute value uncertainty at 68.3% significance level | Attribute value uncertainty at 68.3% significance level |
+| Attribute value uncertainty at 50% significance level | Attribute value uncertainty at 50% significance level |
+| Attribute value uncertainty at 90% significance level | Attribute value uncertainty at 90% significance level |
+| Attribute value uncertainty at 95% significance level | Attribute value uncertainty at 95% significance level |
+| Attribute value uncertainty at 99% significance level | Attribute value uncertainty at 99% significance level |
+| Attribute value uncertainty at 99.8% significance level | Attribute value uncertainty at 99.8% significance level |
+
+### North bound {#iso19115-3.2018-elem-mri-northBoundLatitude-e07339e2d468c1051d7560ef6225ef2e}
+
+Name
+
+:
+
+> mri:northBoundLatitude
+
+Description
+
+:
+
+```{=html}
+Northern-most, coordinate of the limit of the dataset extent
+ expressed in
+ latitude in decimal degrees (positive north)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Number of dimensions {#iso19115-3.2018-elem-mri-numberOfDimensions-cf4fa5a9e3934a3c2c4d4a6b08321edb}
+
+Name
+
+:
+
+> mri:numberOfDimensions
+
+Description
+
+:
+
+```{=html}
+Number of independent spatial-temporal axes
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Obligation {#iso19115-3.2018-elem-mri-obligation-b03e941988d111c06fc0a685a14b79fb}
+
+Name
+
+:
+
+> mri:obligation
+
+Description
+
+:
+
+```{=html}
+Obligation of the extended element
+```
+### Ontology {#iso19115-3.2018-elem-mri-ontology-413f6aac4db11311fc78f9a029912c9a}
+
+Name
+
+:
+
+> mri:ontology
+
+Description
+
+:
+
+```{=html}
+Reference that binds the keyword class to a formal
+ conceptualization of a knowledge domain for use in semantic processing
+ NOTE Keywords in the associated MD_Keywords keyword list must be within
+ the scope of this ontology.
+```
+### Orientation parameter availability {#iso19115-3.2018-elem-mri-orientationParameterAvailability-1d8cbe1a4b5d406ef7721d68bbcec95d}
+
+Name
+
+:
+
+> mri:orientationParameterAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not orientation parameters are
+ available
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Orientation parameter description {#iso19115-3.2018-elem-mri-orientationParameterDescription-fbbc85950d68d2de1919b38ba893120f}
+
+Name
+
+:
+
+> mri:orientationParameterDescription
+
+Description
+
+:
+
+```{=html}
+Description of parameters used to describe sensor orientation
+```
+### Other locale {#iso19115-3.2018-elem-mri-otherLocale-bfdf11aeefc7ffb0ac1f8ae02ae7d875}
+
+Name
+
+:
+
+> mri:otherLocale
+
+Description
+
+:
+
+```{=html}
+Alternate localised language(s) and character set
+ (s) used within the resource
+```
+### Parameter citation {#iso19115-3.2018-elem-mri-parameterCitation-9ef2b2fc7df47c492bb9a19fce4ba6e8}
+
+Name
+
+:
+
+> mri:parameterCitation
+
+Description
+
+:
+
+```{=html}
+Reference providing description of the parameters
+```
+### Parent entity {#iso19115-3.2018-elem-mri-parentEntity-0b202b298ce60d1717e5d04b88c83e4e}
+
+Name
+
+:
+
+> mri:parentEntity
+
+Description
+
+:
+
+```{=html}
+Name of the metadata entity(s) under which this extended
+ metadata element may
+ appear. The name(s) may be standard metadata element(s) or other extended
+ metadata
+ element(s).
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Parent identifier {#iso19115-3.2018-elem-mri-parentIdentifier-5f0e8c7441e5779b27d133eba76fbbad}
+
+Name
+
+:
+
+> mri:parentIdentifier
+
+Description
+
+:
+
+```{=html}
+File identifier of the metadata to which this metadata is a
+ subset
+ (child)
+```
+### PartOf {#iso19115-3.2018-elem-mri-partOf-1567d8c5a5040af4fb70a2a728ec3d00}
+
+Name
+
+:
+
+> mri:partOf
+
+Description
+
+:
+
+```{=html}
+PartOf
+```
+### Pass {#iso19115-3.2018-elem-mri-pass-80f8d49ddc3e9855c783a6eca671a20d}
+
+Name
+
+:
+
+> mri:pass
+
+Description
+
+:
+
+```{=html}
+Indication of the conformance result where 0 = fail and 1 =
+ pass
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Phone {#iso19115-3.2018-elem-mri-phone-60b8622d9cf4ed86cab44b6ec6dda2a5}
+
+Name
+
+:
+
+> mri:phone
+
+Description
+
+:
+
+```{=html}
+Telephone numbers at which the organization or individual may
+ be
+ contacted
+```
+### Point in Pixel {#iso19115-3.2018-elem-mri-pointInPixel-2c8b52f284ca32d399381131e41a4305}
+
+Name
+
+:
+
+> mri:pointInPixel
+
+Description
+
+:
+
+```{=html}
+Point in a pixel corresponding to the Earth location of the
+ pixel
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Point of contact {#iso19115-3.2018-elem-mri-pointOfContact-0a191d0435894206a844cde68a5bc873}
+
+Name
+
+:
+
+> mri:pointOfContact
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s)
+ and
+ organizations(s) associated with the resource(s)
+```
+``` xml
+
+
+
+
+
+
+
+
+ Organisation
+
+
+
+
+
+
+ mail@organisation.org
+
+
+
+
+
+
+
+
+
+```
+
+### Presentation form {#iso19115-3.2018-elem-mri-presentationForm-c60bbfde21396f943e6032fca7b69550}
+
+Name
+
+:
+
+> mri:presentationForm
+
+Description
+
+:
+
+```{=html}
+Mode in which the resource is represented
+```
+### Processing level {#iso19115-3.2018-elem-mri-processingLevel-92beb3a40f398b02520cb6da80890df9}
+
+Name
+
+:
+
+> mri:processingLevel
+
+Description
+
+:
+
+```{=html}
+Code that identifies the level of processing in the
+ producers coding system of a resource. Example NOAA level 1B.
+```
+### PropertyType {#iso19115-3.2018-elem-mri-propertyType-e9212239d95c65d827b824b048de51a6}
+
+Name
+
+:
+
+> mri:propertyType
+
+Description
+
+:
+
+```{=html}
+PropertyType
+```
+### Free text {#iso19115-3.2018-elem-mri-PT_FreeText-6219dda1e26c4d314689c8bc49ddfb63}
+
+Name
+
+:
+
+> mri:PT_FreeText
+
+Description
+
+:
+
+```{=html}
+Description of a multi-language free text metadata element
+```
+### Purpose {#iso19115-3.2018-elem-mri-purpose-f010699f7244e7c9797817d3a9a78c8d}
+
+Name
+
+:
+
+> mri:purpose
+
+Description
+
+:
+
+```{=html}
+Summary of the intentions with which the resource(s) was
+ developed
+```
+### Rationale {#iso19115-3.2018-elem-mri-rationale-mri-MD_ExtendedElementInformation-b1f26013fe0ce1e4f6018873aa1f0e5b}
+
+Name
+
+:
+
+> mri:rationale
+
+Context
+
+:
+
+> mri:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Reason for creating the extended element
+```
+### Resource constraints {#iso19115-3.2018-elem-mri-resourceConstraints-22849b1b8ec64c231cd8eda0547a553a}
+
+Name
+
+:
+
+> mri:resourceConstraints
+
+Description
+
+:
+
+```{=html}
+Provides information about constraints which apply to the
+ resource(s)
+```
+### Resource format {#iso19115-3.2018-elem-mri-resourceFormat-713c10529cd9a1b05d0e0d70cf37fa08}
+
+Name
+
+:
+
+> mri:resourceFormat
+
+Description
+
+:
+
+```{=html}
+Provides a description of the format of the resource(s)
+```
+### Resource maintenance {#iso19115-3.2018-elem-mri-resourceMaintenance-9aabbe5ce70e511c06bf7decde6ba3ac}
+
+Name
+
+:
+
+> mri:resourceMaintenance
+
+Description
+
+:
+
+```{=html}
+Provides information about the frequency of resource updates,
+ and the scope of
+ those updates
+```
+``` xml
+
+
+
+
+
+
+
+```
+
+### Resource specific usage {#iso19115-3.2018-elem-mri-resourceSpecificUsage-16894db96c1cd1836b2b8838b3a7ad30}
+
+Name
+
+:
+
+> mri:resourceSpecificUsage
+
+Description
+
+:
+
+```{=html}
+Provides basic information about specific application(s) for
+ which the
+ resource(s) has/have been or is being used by different users
+```
+### Response {#iso19115-3.2018-elem-mri-response-5c7415e8bb679a4645e53f1bca4888c1}
+
+Name
+
+:
+
+> mri:response
+
+Description
+
+:
+
+```{=html}
+Response to the user-determined limitations. Example
+ “This has been fixed in version x.”
+```
+### Result {#iso19115-3.2018-elem-mri-result-cf813985cacbefc1455b60255c9aacd0}
+
+Name
+
+:
+
+> mri:result
+
+Description
+
+:
+
+```{=html}
+Value (or set of values) obtained from applying a data quality
+ measure or the
+ out come of evaluating the obtained value (or set of values) against a
+ specified
+ acceptable conformance quality level
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Identifier {#iso19115-3.2018-elem-mri-RS_Identifier-0ff1b8f7f7961d3b04637810bc4bbc95}
+
+Name
+
+:
+
+> mri:RS_Identifier
+
+Description
+
+:
+
+```{=html}
+Identifier used for reference systems
+```
+### Rule {#iso19115-3.2018-elem-mri-rule-4724b8d466dc221ef079c5a9c07ad554}
+
+Name
+
+:
+
+> mri:rule
+
+Description
+
+:
+
+```{=html}
+Specifies how the extended element relates to other existing
+ elements and
+ entities
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Scale Denominator {#iso19115-3.2018-elem-mri-scaleDenominator-dac4fe9262fc158c1184fa0969bef7ae}
+
+Name
+
+:
+
+> mri:scaleDenominator
+
+Description
+
+:
+
+```{=html}
+Denominator of the representative fraction on a source map
+```
+### Series {#iso19115-3.2018-elem-mri-series-00c09e9ddd3edc0274c60cf72e66966b}
+
+Name
+
+:
+
+> mri:series
+
+Description
+
+:
+
+```{=html}
+Information about the series, or aggregate dataset, of which
+ the dataset is a
+ part
+```
+### SeriesMetadata {#iso19115-3.2018-elem-mri-seriesMetadata-983451ad1bc581791b639c841965fc41}
+
+Name
+
+:
+
+> mri:seriesMetadata
+
+Description
+
+:
+
+```{=html}
+SeriesMetadata
+```
+### Short name {#iso19115-3.2018-elem-mri-shortName-d6f9ddc078149cfd4ae0fff6efe14041}
+
+Name
+
+:
+
+> mri:shortName
+
+Description
+
+:
+
+```{=html}
+Short form suitable for use in an implementation method such as
+ XML or SGML.
+ NOTE other methods may be used
+```
+### Source {#iso19115-3.2018-elem-mri-source-mri-MD_ExtendedElementInformation-69dc34a4ad2af38b82c4651fed59231c}
+
+Name
+
+:
+
+> mri:source
+
+Context
+
+:
+
+> mri:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Name of the person or organization creating the extended
+ element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Source extent {#iso19115-3.2018-elem-mri-sourceExtent-3c6ed438e292db496d6517c3534f17a7}
+
+Name
+
+:
+
+> mri:sourceExtent
+
+Description
+
+:
+
+```{=html}
+Information about the spatial, vertical and temporal extent of
+ the source
+ data
+```
+
+Condition
+
+:
+
+> conditional
+
+### South bound {#iso19115-3.2018-elem-mri-southBoundLatitude-4ddecaaf6237fcc1c5d40358875edf7c}
+
+Name
+
+:
+
+> mri:southBoundLatitude
+
+Description
+
+:
+
+```{=html}
+Southern-most coordinate of the limit of the dataset extent,
+ expressed in
+ latitude in decimal degrees (positive north)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Spatial representation type {#iso19115-3.2018-elem-mri-spatialRepresentationType-e3208e8cd1381b9fc68b3aeea9b717bc}
+
+Name
+
+:
+
+> mri:spatialRepresentationType
+
+Description
+
+:
+
+```{=html}
+Method used to spatially represent geographic information
+```
+``` xml
+
+
+
+```
+
+### Spatial resolution {#iso19115-3.2018-elem-mri-spatialResolution-21e177ffd817c0d4ab98dbb85f2023f4}
+
+Name
+
+:
+
+> mri:spatialResolution
+
+Description
+
+:
+
+```{=html}
+Factor which provides a general understanding of the density of
+ spatial data in
+ the dataset
+```
+``` xml
+
+
+
+
+
+ 25000
+
+
+
+
+
+```
+
+### Specification {#iso19115-3.2018-elem-mri-specification-mri-DQ_ConformanceResult-b7cc00be1811025bfd6d444339699780}
+
+Name
+
+:
+
+> mri:specification
+
+Context
+
+:
+
+> mri:DQ_ConformanceResult
+
+Description
+
+:
+
+```{=html}
+Citation of product specification or user requirement against
+ which data is
+ being evaluated
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Specification {#iso19115-3.2018-elem-mri-specification-mri-MD_Format-7df5c14f28cb23cf5b04ecb8bc52a50d}
+
+Name
+
+:
+
+> mri:specification
+
+Context
+
+:
+
+> mri:MD_Format
+
+Description
+
+:
+
+```{=html}
+Name of a subset, profile, or product specification of the
+ format
+```
+### Specification {#iso19115-3.2018-elem-mri-specification-da131cbaabfe65e6342437511b16716f}
+
+Name
+
+:
+
+> mri:specification
+
+Description
+
+:
+
+### Specific usage {#iso19115-3.2018-elem-mri-specificUsage-e10bbb146f9122f24b86bd27cd582a0b}
+
+Name
+
+:
+
+> mri:specificUsage
+
+Description
+
+:
+
+```{=html}
+Brief description of the resource and/or resource series
+ usage
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Status {#iso19115-3.2018-elem-mri-status-cc6f58a635c230364c21dcd8822e7ebd}
+
+Name
+
+:
+
+> mri:status
+
+Description
+
+:
+
+```{=html}
+Status of the resource(s)
+```
+``` xml
+
+
+
+```
+
+### Subset {#iso19115-3.2018-elem-mri-subset-e094e68292e2fa9500f0d6380981f185}
+
+Name
+
+:
+
+> mri:subset
+
+Description
+
+:
+
+```{=html}
+Subset
+```
+### Superset {#iso19115-3.2018-elem-mri-superset-786873bc68f8c3a000a3fd54ece6fb6f}
+
+Name
+
+:
+
+> mri:superset
+
+Description
+
+:
+
+```{=html}
+Superset
+```
+### Supplemental Information {#iso19115-3.2018-elem-mri-supplementalInformation-84665de001cb75c50eb593b3a9366f70}
+
+Name
+
+:
+
+> mri:supplementalInformation
+
+Description
+
+:
+
+```{=html}
+Any other descriptive information about the dataset
+```
+### Temporal resolution {#iso19115-3.2018-elem-mri-temporalResolution-50d263b81d8636c123eea3bcb704872d}
+
+Name
+
+:
+
+> mri:temporalResolution
+
+Description
+
+:
+
+```{=html}
+Smallest resolvable temporal period in a resource
+```
+### TextGroup {#iso19115-3.2018-elem-mri-textGroup-f5fee81a35f938add5c2959da2e0944a}
+
+Name
+
+:
+
+> mri:textGroup
+
+Description
+
+:
+
+```{=html}
+TextGroup
+```
+### Thesaurus name {#iso19115-3.2018-elem-mri-thesaurusName-fdfd987e5e74c33c17af7d710026a114}
+
+Name
+
+:
+
+> mri:thesaurusName
+
+Description
+
+:
+
+```{=html}
+Name of the formally registered thesaurus or a similar
+ authoritative source of
+ keywords
+```
+### Title {#iso19115-3.2018-elem-mri-title-mri-MD_Legislation-87bbb0dc3d29b30cec5bdf043159fec3}
+
+Name
+
+:
+
+> mri:title
+
+Context
+
+:
+
+> mri:MD_Legislation
+
+Description
+
+:
+
+```{=html}
+Reference to legal title
+```
+### Topic category {#iso19115-3.2018-elem-mri-topicCategory-3384f3f2b46b6851db1e3c2ac2404477}
+
+Name
+
+:
+
+> mri:topicCategory
+
+Description
+
+:
+
+```{=html}
+Main theme(s) of the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Topology level {#iso19115-3.2018-elem-mri-topologyLevel-c192e149d637dd11a6735e4ab2793cce}
+
+Name
+
+:
+
+> mri:topologyLevel
+
+Description
+
+:
+
+```{=html}
+Code which identifies the degree of complexity of the spatial
+ relationships
+```
+### Transformation dimension description {#iso19115-3.2018-elem-mri-transformationDimensionDescription-7817f43a4aedff49f2770b81155bd879}
+
+Name
+
+:
+
+> mri:transformationDimensionDescription
+
+Description
+
+:
+
+```{=html}
+Description of the information about which grid dimensions are
+ the spatial
+ dimensions
+```
+### Transformation dimension mapping {#iso19115-3.2018-elem-mri-transformationDimensionMapping-af6c96c0b976aae72d391badb572d556}
+
+Name
+
+:
+
+> mri:transformationDimensionMapping
+
+Description
+
+:
+
+```{=html}
+Information about which grid dimensions are the spatial
+ dimensions
+```
+### Transformation parameter availability {#iso19115-3.2018-elem-mri-transformationParameterAvailability-00ae4b9f58a82c8747c05290206e073c}
+
+Name
+
+:
+
+> mri:transformationParameterAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not parameters for transformation
+ between image
+ coordinates and geographic or map coordinates exist (are available)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Type {#iso19115-3.2018-elem-mri-type-c713af5b3e37409f862f317150418a43}
+
+Name
+
+:
+
+> mri:type
+
+Description
+
+:
+
+```{=html}
+Subject matter used to group similar keywords
+```
+### Type {#iso19115-3.2018-elem-mri-type-mri-MD_CodeDomain-f36524bc9b2bcff08dc13b26a6f1c412}
+
+Name
+
+:
+
+> mri:type
+
+Context
+
+:
+
+> mri:MD_CodeDomain
+
+Description
+
+:
+
+```{=html}
+Datatype of the code domain
+```
+### Type definition {#iso19115-3.2018-elem-mri-type-mri-MD_Type-509a3b36cee46d21f76032143452c3df}
+
+Name
+
+:
+
+> mri:type
+
+Context
+
+:
+
+> mri:MD_Type
+
+Description
+
+:
+
+```{=html}
+Data type definition
+```
+```{=html}
+Data type definition, formal of informal (i.e. Text12, Line)
+```
+### Update scope {#iso19115-3.2018-elem-mri-updateScope-2f6505dc9e21679f55889d5d3dab55f0}
+
+Name
+
+:
+
+> mri:updateScope
+
+Description
+
+:
+
+```{=html}
+Scope of data to which maintenance is applied
+```
+### Update scope description {#iso19115-3.2018-elem-mri-updateScopeDescription-4ed2c444d7ad67f7d337a115667d00f4}
+
+Name
+
+:
+
+> mri:updateScopeDescription
+
+Description
+
+:
+
+```{=html}
+Additional information about the range or extent of the
+ resource
+```
+### URL {#iso19115-3.2018-elem-mri-URL-ade84020707f315475cd2242c01dd25a}
+
+Name
+
+:
+
+> mri:URL
+
+Description
+
+:
+
+```{=html}
+URL
+```
+### Usage datetime {#iso19115-3.2018-elem-mri-usageDateTime-cb7d2c81941c09afc3a52bfc79bf71fb}
+
+Name
+
+:
+
+> mri:usageDateTime
+
+Description
+
+:
+
+```{=html}
+Date and time of the first use or range of uses of the resource
+ and/or resource
+ series (YYYY-MM-DDThh:mm:ss)
+```
+### User contact info {#iso19115-3.2018-elem-mri-userContactInfo-a2ba616281c1660c5480ee85e959ee52}
+
+Name
+
+:
+
+> mri:userContactInfo
+
+Description
+
+:
+
+```{=html}
+Identification of and means of communicating with person(s) and
+ organization(s)
+ using the resource(s)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### User determined limitations {#iso19115-3.2018-elem-mri-userDeterminedLimitations-cbd92baf556f2b19980a621ce6c02254}
+
+Name
+
+:
+
+> mri:userDeterminedLimitations
+
+Description
+
+:
+
+```{=html}
+Applications, determined by the user for which the resource
+ and/or resource
+ series is not suitable
+```
+### Version {#iso19115-3.2018-elem-mri-version-mri-RS_Identifier-21131c5f6a0db9532cc8ee120d605769}
+
+Name
+
+:
+
+> mri:version
+
+Context
+
+:
+
+> mri:RS_Identifier
+
+Description
+
+:
+
+```{=html}
+Version identifier for the namespace
+```
+### Version {#iso19115-3.2018-elem-mri-version-37b307063b9e962d1848882bb4e6cfbd}
+
+Name
+
+:
+
+> mri:version
+
+Description
+
+:
+
+```{=html}
+Version of the format (date, number, etc.)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Vertical sampling distance {#iso19115-3.2018-elem-mri-vertical-43bcad35797e8b97a17410d5045328f0}
+
+Name
+
+:
+
+> mri:vertical
+
+Description
+
+:
+
+```{=html}
+Vertical sampling distance
+```
+### Voice {#iso19115-3.2018-elem-mri-voice-8b6d31c838c1369223d55ee98798ca8f}
+
+Name
+
+:
+
+> mri:voice
+
+Description
+
+:
+
+```{=html}
+Telephone number by which individuals can speak to the
+ responsible organization
+ or individual
+```
+### West bound {#iso19115-3.2018-elem-mri-westBoundLongitude-ce82ae6636f5b594044aada5c51913ac}
+
+Name
+
+:
+
+> mri:westBoundLongitude
+
+Description
+
+:
+
+```{=html}
+Western-most coordinate of the limit of the dataset extent,
+ expressed in
+ longitude in decimal degrees (positive east)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Additional doc. {#iso19115-3.2018-elem-mrl-additionalDocumentation-f113e2c0288a07cf4fe6882d11069fad}
+
+Name
+
+:
+
+> mrl:additionalDocumentation
+
+Description
+
+:
+
+### Description {#iso19115-3.2018-elem-mrl-description-a45016f67dc027509d26734d33ba598c}
+
+Name
+
+:
+
+> mrl:description
+
+Description
+
+:
+
+### Description {#iso19115-3.2018-elem-mrl-description-mrl-LI_Source-3f37e9df548dbad7ccfc5a97b569f6bb}
+
+Name
+
+:
+
+> mrl:description
+
+Context
+
+:
+
+> mrl:LI_Source
+
+Description
+
+:
+
+```{=html}
+Detailed description of the level of the source data
+```
+### File type {#iso19115-3.2018-elem-mrl-fileType-34ce7f3d07796298fa2fd3be3ca9f725}
+
+Name
+
+:
+
+> mrl:fileType
+
+Description
+
+:
+
+### Process step {#iso19115-3.2018-elem-mrl-LE_ProcessStep-34c17a1d181ee4939772d7207becf6ee}
+
+Name
+
+:
+
+> mrl:LE_ProcessStep
+
+Description
+
+:
+
+### Process step report {#iso19115-3.2018-elem-mrl-LE_ProcessStepReport-7f36ac19621de69c869f50fffa5888f6}
+
+Name
+
+:
+
+> mrl:LE_ProcessStepReport
+
+Description
+
+:
+
+### Source (imagery) {#iso19115-3.2018-elem-mrl-LE_Source-966e475433745f44485a80b7d3d67a5b}
+
+Name
+
+:
+
+> mrl:LE_Source
+
+Description
+
+:
+
+### Lineage {#iso19115-3.2018-elem-mrl-LI_Lineage-f498f5aafe17748455864fd3fb332568}
+
+Name
+
+:
+
+> mrl:LI_Lineage
+
+Description
+
+:
+
+```{=html}
+Information about the events or source data used in
+ constructing the data
+ specified by the scope or lack of knowledge about lineage
+```
+``` xml
+
+
+ Généalogie du jeu de données
+
+
+
+
+
+
+
+
+
+```
+
+### Process step (imagery) {#iso19115-3.2018-elem-mrl-LI_ProcessStep-523fb797e15543dcd78820cf7da6a353}
+
+Name
+
+:
+
+> mrl:LI_ProcessStep
+
+Description
+
+:
+
+### Source {#iso19115-3.2018-elem-mrl-LI_Source-516cbe9c5aee24a2298148e192b1b430}
+
+Name
+
+:
+
+> mrl:LI_Source
+
+Description
+
+:
+
+### Name {#iso19115-3.2018-elem-mrl-name-c3ddefc350a7df82d699cd21db3265bb}
+
+Name
+
+:
+
+> mrl:name
+
+Description
+
+:
+
+### Output {#iso19115-3.2018-elem-mrl-output-7b92f6eed5c27bf127bcd1b00ba02bd2}
+
+Name
+
+:
+
+> mrl:output
+
+Description
+
+:
+
+### Processed level {#iso19115-3.2018-elem-mrl-processedLevel-a16a0921791d25b12c661d6b523823fd}
+
+Name
+
+:
+
+> mrl:processedLevel
+
+Description
+
+:
+
+### Information sur le processus {#iso19115-3.2018-elem-mrl-processingInformation-43dcf9a95a6b46ecd38081b26ad4405c}
+
+Name
+
+:
+
+> mrl:processingInformation
+
+Description
+
+:
+
+### Processor {#iso19115-3.2018-elem-mrl-processor-d25f51596af7f766fb5e2e2d235b8d38}
+
+Name
+
+:
+
+> mrl:processor
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s)
+ and
+ organization(s) associated with the process step
+```
+### Process step {#iso19115-3.2018-elem-mrl-processStep-b30816d20fac90a8f4714473ce039ab6}
+
+Name
+
+:
+
+> mrl:processStep
+
+Description
+
+:
+
+```{=html}
+Information about an event in the creation process for the data
+ specified by
+ the scope
+```
+
+Condition
+
+:
+
+> conditional
+
+### Rationale {#iso19115-3.2018-elem-mrl-rationale-80f6a85b661cb0e1343a18c85fef1c6a}
+
+Name
+
+:
+
+> mrl:rationale
+
+Description
+
+:
+
+```{=html}
+Requirement or purpose for the process step
+```
+### Reference {#iso19115-3.2018-elem-mrl-reference-f0e0b120539f104664b10ed341d78e1c}
+
+Name
+
+:
+
+> mrl:reference
+
+Description
+
+:
+
+### Report {#iso19115-3.2018-elem-mrl-report-a6ace6224eaf1048b4fa5a64e3ed3c8d}
+
+Name
+
+:
+
+> mrl:report
+
+Description
+
+:
+
+### Resolution {#iso19115-3.2018-elem-mrl-resolution-4a197894c21de3f79a1db7fd8cdef215}
+
+Name
+
+:
+
+> mrl:resolution
+
+Description
+
+:
+
+```{=html}
+Degree of detail in the grid dataset
+```
+### Scope {#iso19115-3.2018-elem-mrl-scope-6d6d5c1accac2c5584b8d24677b8e466}
+
+Name
+
+:
+
+> mrl:scope
+
+Description
+
+:
+
+```{=html}
+Type of resource and/or extent to which the lineage
+ information applies
+```
+``` xml
+
+
+
+
+
+
+
+```
+
+### Source {#iso19115-3.2018-elem-mrl-source-f9e07e326a4d78299bfa20d20350d4e5}
+
+Name
+
+:
+
+> mrl:source
+
+Description
+
+:
+
+```{=html}
+Information about the source data used in creating the data
+ specified by the
+ scope
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Source citation {#iso19115-3.2018-elem-mrl-sourceCitation-493609aa2a1f745385660e829fa9dfb4}
+
+Name
+
+:
+
+> mrl:sourceCitation
+
+Description
+
+:
+
+```{=html}
+Recommended reference to be used for the source data
+```
+### Source Metadata {#iso19115-3.2018-elem-mrl-sourceMetadata-e2c32177f459ed654ad740ae7a82c89a}
+
+Name
+
+:
+
+> mrl:sourceMetadata
+
+Description
+
+:
+
+```{=html}
+Reference to metadata for the source
+```
+
+Condition
+
+:
+
+> optional
+
+### Source reference system {#iso19115-3.2018-elem-mrl-sourceReferenceSystem-1037d7bf6f0b485f262e4322cb9e37cf}
+
+Name
+
+:
+
+> mrl:sourceReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Spatial reference system used by the source data
+```
+### Source spatial resolution {#iso19115-3.2018-elem-mrl-sourceSpatialResolution-cf018c59a91f5566c1b1783f2acbd27d}
+
+Name
+
+:
+
+> mrl:sourceSpatialResolution
+
+Description
+
+:
+
+```{=html}
+spatial resolution expressed as a scale factor, a distance, an
+ angle or a level of detail
+```
+
+Condition
+
+:
+
+> optional
+
+### Source step {#iso19115-3.2018-elem-mrl-sourceStep-mrl-LI_Source-df0d740b9f8a72af86d6f0c7adee8c72}
+
+Name
+
+:
+
+> mrl:sourceStep
+
+Context
+
+:
+
+> mrl:LI_Source
+
+Description
+
+:
+
+```{=html}
+Information about a process step in which this source was
+ used
+```
+
+Condition
+
+:
+
+> optional
+
+### Source step {#iso19115-3.2018-elem-mrl-sourceStep-7a3ac763c9a58974ba992b5b15f42c8e}
+
+Name
+
+:
+
+> mrl:sourceStep
+
+Description
+
+:
+
+```{=html}
+Information about an event in the creation process for the
+ source
+ data
+```
+### Statement {#iso19115-3.2018-elem-mrl-statement-889c16bd4aae51af718de1e5d417231b}
+
+Name
+
+:
+
+> mrl:statement
+
+Description
+
+:
+
+```{=html}
+General explanation of the data producer_s knowledge about the
+ lineage of a
+ dataset
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+ Généalogie du jeu de données
+
+```
+
+### Step date time {#iso19115-3.2018-elem-mrl-stepDateTime-ff4d18ce2643f44151f2edb998f6d42d}
+
+Name
+
+:
+
+> mrl:stepDateTime
+
+Description
+
+:
+
+### Reference system {#iso19115-3.2018-elem-mrs-MD_ReferenceSystem-75f781a6e44f220db44fb9f797143583}
+
+Name
+
+:
+
+> mrs:MD_ReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Information about the reference system.
+```
+```{=html}
+information about the reference system
+```
+``` xml
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3035
+
+
+
+
+```
+
+### Reference system identifier {#iso19115-3.2018-elem-mrs-referenceSystemIdentifier-c940c3e9ba051b44e2041d768ac777c8}
+
+Name
+
+:
+
+> mrs:referenceSystemIdentifier
+
+Description
+
+:
+
+```{=html}
+Name of reference system
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3035
+
+
+
+```
+
+### Reference system type {#iso19115-3.2018-elem-mrs-referenceSystemType-9165956812eecd1c7858dd599ce31ca8}
+
+Name
+
+:
+
+> mrs:referenceSystemType
+
+Description
+
+:
+
+```{=html}
+Type of reference system used Example
+ compoundGeographic2DParametric
+```
+### Axis dimension properties {#iso19115-3.2018-elem-msr-axisDimensionProperties-073ec35418d10c4f0c137378a6134493}
+
+Name
+
+:
+
+> msr:axisDimensionProperties
+
+Description
+
+:
+
+```{=html}
+Information about spatial-temporal axis properties
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Cell geometry {#iso19115-3.2018-elem-msr-cellGeometry-3a6cc41f54ba7d4c75eee03be5598318}
+
+Name
+
+:
+
+> msr:cellGeometry
+
+Description
+
+:
+
+```{=html}
+Identification of grid data as point or cell
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Point central {#iso19115-3.2018-elem-msr-centrePoint-f92f835c824050de5f3fbf6f008870a8}
+
+Name
+
+:
+
+> msr:centrePoint
+
+Description
+
+:
+
+```{=html}
+Position terrestre dans le système de coordonnées
+ définie par le système de références spatiales et la coordonnée dans la
+ grille de la cellule située à mi-chemin entre les extrémités opposées de
+ la grille selon les dimensions spatiales.
+```
+
+Condition
+
+:
+
+> optional
+
+### Check point availability {#iso19115-3.2018-elem-msr-checkPointAvailability-eede9501cd9cc8710550fe01f8fe1cee}
+
+Name
+
+:
+
+> msr:checkPointAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not geographic position
+ points are available to test the accuracy of the georeferenced grid data
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Check point description {#iso19115-3.2018-elem-msr-checkPointDescription-226168985a0798a955267fbc21aacab4}
+
+Name
+
+:
+
+> msr:checkPointDescription
+
+Description
+
+:
+
+```{=html}
+Description of geographic position points used to
+ test the accuracy of the georeferenced grid data
+```
+### Compliance code {#iso19115-3.2018-elem-msr-complianceCode-f13f2f65f47a827bb9bbea5e092edad1}
+
+Name
+
+:
+
+> msr:complianceCode
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the cited feature
+ catalogue complies with ISO 191109110
+```
+
+Condition
+
+:
+
+> optional
+
+### Control point availability {#iso19115-3.2018-elem-msr-controlPointAvailability-c7d5efb26ca7e4ef90f8ad058e99ae88}
+
+Name
+
+:
+
+> msr:controlPointAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not control point(s)
+ existse existent
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Corner points {#iso19115-3.2018-elem-msr-cornerPoints-3c2edbd5ef81dec63afd53ca43db0765}
+
+Name
+
+:
+
+> msr:cornerPoints
+
+Description
+
+:
+
+```{=html}
+Earth location in the coordinate system defined by
+ the Spatial Reference System and the grid coordinate of the cells at
+ opposite ends of grid coverage along two diagonals in the grid spatial
+ dimensions NOTE There are four corner points in a georectified grid; at
+ least two corner points along one diagonal are required. The first corner
+ point corresponds to the origin of the grid..
+```
+
+Condition
+
+:
+
+> optional
+
+### Dimension description {#iso19115-3.2018-elem-msr-dimensionDescription-069e485d9f5957e96240c0b98bc04124}
+
+Name
+
+:
+
+> msr:dimensionDescription
+
+Description
+
+:
+
+```{=html}
+Description of the axis
+```
+
+Condition
+
+:
+
+> optional
+
+### Dimension name {#iso19115-3.2018-elem-msr-dimensionName-c36a4acbeab1e6196344534c31664de1}
+
+Name
+
+:
+
+> msr:dimensionName
+
+Description
+
+:
+
+```{=html}
+Name of the axis
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Dimension size {#iso19115-3.2018-elem-msr-dimensionSize-9f8a6d21785fddccf25ed28f463ff82c}
+
+Name
+
+:
+
+> msr:dimensionSize
+
+Description
+
+:
+
+```{=html}
+Number of elements along the axis
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Dimension title {#iso19115-3.2018-elem-msr-dimensionTitle-cfbbd35244998db6fedc70383d0b1a4f}
+
+Name
+
+:
+
+> msr:dimensionTitle
+
+Description
+
+:
+
+```{=html}
+enhancement/modifier of the dimension name. EXAMPLE
+ dimensionName = “column” dimensionTitle = “Longitude”
+```
+
+Condition
+
+:
+
+> optional
+
+### Feature catalogue citation {#iso19115-3.2018-elem-msr-featureCatalogueCitation-86dcf88571deb3bc83ffd96f17063b0c}
+
+Name
+
+:
+
+> msr:featureCatalogueCitation
+
+Description
+
+:
+
+```{=html}
+complete bibliographic reference to one or more
+ external feature catalogues
+```
+### Feature types {#iso19115-3.2018-elem-msr-featureTypes-4eff89188c1d3db76667047f6cf6badc}
+
+Name
+
+:
+
+> msr:featureTypes
+
+Description
+
+:
+
+```{=html}
+Subset of feature types from cited feature catalogue
+ occurring in resource and count of feature instances
+```
+
+Condition
+
+:
+
+> optional
+
+### Geometric object count {#iso19115-3.2018-elem-msr-geometricObjectCount-c1286bf556b766a23d0f4f8dc8876b1b}
+
+Name
+
+:
+
+> msr:geometricObjectCount
+
+Description
+
+:
+
+```{=html}
+Total number of the point or vector object type
+ occurring in the dataset
+```
+
+Condition
+
+:
+
+> optional
+
+### Geometric objects {#iso19115-3.2018-elem-msr-geometricObjects-a372c8a09516b77dbe0b8670c1022008}
+
+Name
+
+:
+
+> msr:geometricObjects
+
+Description
+
+:
+
+```{=html}
+Information about the geometric objects used in the
+ resource
+```
+
+Condition
+
+:
+
+> optional
+
+### Geometric object type {#iso19115-3.2018-elem-msr-geometricObjectType-c9165f96bf9fa94f81beca9336981531}
+
+Name
+
+:
+
+> msr:geometricObjectType
+
+Description
+
+:
+
+```{=html}
+Name of point or vector objects used to locate
+ zero-, one-, two-, or three-dimensional spatial locations in the resource
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Georeferenced parameters {#iso19115-3.2018-elem-msr-georeferencedParameters-c9d8550ed978763e23072bb01554fefa}
+
+Name
+
+:
+
+> msr:georeferencedParameters
+
+Description
+
+:
+
+```{=html}
+Terms which support grid data georeferencing
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Included with dataset {#iso19115-3.2018-elem-msr-includedWithDataset-595a7c08cab2d676de4bdce06cbac54e}
+
+Name
+
+:
+
+> msr:includedWithDataset
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the feature catalogue
+ is included with the resource
+```
+
+Condition
+
+:
+
+> optional
+
+### Locale {#iso19115-3.2018-elem-msr-locale-f20a8851d10c4ed34e8953c641b28abd}
+
+Name
+
+:
+
+> msr:locale
+
+Description
+
+:
+
+```{=html}
+Language(s) and character set(s) used within the
+ catalogue
+```
+
+Condition
+
+:
+
+> optional
+
+### ContentInformation {#iso19115-3.2018-elem-msr-MD_ContentInformation-dc1f6d0dc9b01792c811602b6b31fd6d}
+
+Name
+
+:
+
+> msr:MD_ContentInformation
+
+Description
+
+:
+
+```{=html}
+description of the content of a resource
+```
+### Dimension {#iso19115-3.2018-elem-msr-MD_Dimension-87ab48f712228b93b6951a4260df02c6}
+
+Name
+
+:
+
+> msr:MD_Dimension
+
+Description
+
+:
+
+```{=html}
+Axis properties
+```
+### Name {#iso19115-3.2018-elem-msr-MD_DimensionNameTypeCode-37d039177e852fd253d6c21c02fe5ae7}
+
+Name
+
+:
+
+> msr:MD_DimensionNameTypeCode
+
+Description
+
+:
+
+### Standard codelists Name (msr:MD_DimensionNameTypeCode)
+
+| code | label | description |
+|------------|-------------|------------------------------------------------------------|
+| row | Row | Ordinate (y) axis |
+| column | Column | Abscissa (x) axis |
+| vertical | Vertical | Vertical (z) axis |
+| track | Track | Along the direction of motion of the scan point |
+| crossTrack | Cross track | Perpendicular to the direction of motion of the scan point |
+| line | Line | Scan line of a sensor |
+| sample | Sample | Element along a scan line |
+| time | Time | Duration |
+
+### Feature catalogue description {#iso19115-3.2018-elem-msr-MD_FeatureCatalogueDescription-19307415e31a221cf4c2a6153a0eb8b8}
+
+Name
+
+:
+
+> msr:MD_FeatureCatalogueDescription
+
+Description
+
+:
+
+```{=html}
+Information identifying the feature catalogue or the
+ conceptual schema
+```
+### Geometric objects {#iso19115-3.2018-elem-msr-MD_GeometricObjects-75921e796523b0c5e9e75e059ce2373d}
+
+Name
+
+:
+
+> msr:MD_GeometricObjects
+
+Description
+
+:
+
+```{=html}
+Number of objects, listed by geometric object type,
+ used in the resource
+```
+### Georectified {#iso19115-3.2018-elem-msr-MD_Georectified-cb54f6a4733d966162a4d43f454cd92b}
+
+Name
+
+:
+
+> msr:MD_Georectified
+
+Description
+
+:
+
+```{=html}
+Grid whose cells are regularly spaced in a
+ geographic (i.e., lat / long) or map coordinate system defined in the
+ Spatial Referencing System (SRS) so that any cell in the grid can be
+ geolocated given its grid coordinate and the grid origin, cell spacing,
+ and orientation
+```
+### Georeferenceable {#iso19115-3.2018-elem-msr-MD_Georeferenceable-858db82597d26c7495c70c557fae1a4a}
+
+Name
+
+:
+
+> msr:MD_Georeferenceable
+
+Description
+
+:
+
+```{=html}
+Grid with cells irregularly spaced in any given
+ geographic/map projection coordinate system, whose individual cells can be
+ eolocated using geolocation information supplied with the data but cannot
+ be geolocated from the grid properties alone
+```
+### Grid spatial representation {#iso19115-3.2018-elem-msr-MD_GridSpatialRepresentation-a05d8ac70cdbde9496a5c63a5dc94f3d}
+
+Name
+
+:
+
+> msr:MD_GridSpatialRepresentation
+
+Description
+
+:
+
+```{=html}
+Information about grid spatial objects in the
+ resource
+```
+### Pixel orientation code {#iso19115-3.2018-elem-msr-MD_PixelOrientationCode-70d12e70676ab7a22eaf4b94d24fdc11}
+
+Name
+
+:
+
+> msr:MD_PixelOrientationCode
+
+Description
+
+:
+
+```{=html}
+Point in a pixel corresponding to the Earth location of the
+ pixel
+```
+### Standard codelists Pixel orientation code (msr:MD_PixelOrientationCode)
+
+| code | label | description |
+|------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| center | Center | Point halfway between the lower left and the upper right of the pixel |
+| lowerLeft | Lower left | The corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value |
+| lowerRight | Lower right | Next corner counterclockwise from the lower left |
+| upperRight | Upper right | Next corner counterclockwise from the lower right |
+| upperLeft | Upper left | Next corner counterclockwise from the upper right |
+
+### Reference system {#iso19115-3.2018-elem-msr-MD_ReferenceSystem-050bc2ad30ca0aa0877ac3c39ead49a6}
+
+Name
+
+:
+
+> msr:MD_ReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Information about the reference system
+```
+### Vector spatial sepresentation {#iso19115-3.2018-elem-msr-MD_VectorSpatialRepresentation-995972e18071d37f9476492d224d6186}
+
+Name
+
+:
+
+> msr:MD_VectorSpatialRepresentation
+
+Description
+
+:
+
+```{=html}
+Information about the vector spatial objects in the
+ resource
+```
+### Number of dimensions {#iso19115-3.2018-elem-msr-numberOfDimensions-e13eac032aba12c4d1306effd633cd91}
+
+Name
+
+:
+
+> msr:numberOfDimensions
+
+Description
+
+:
+
+```{=html}
+Number of independent spatial-temporal axes
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Orientation parameter availability {#iso19115-3.2018-elem-msr-orientationParameterAvailability-69856b25d667d8d93e60b54298dc7321}
+
+Name
+
+:
+
+> msr:orientationParameterAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not orientation parameters
+ are available
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Orientation parameter description {#iso19115-3.2018-elem-msr-orientationParameterDescription-73c93e809e439a9e74b59660193a9e5b}
+
+Name
+
+:
+
+> msr:orientationParameterDescription
+
+Description
+
+:
+
+```{=html}
+Description of parameters used to describe sensor
+ orientation
+```
+
+Condition
+
+:
+
+> optional
+
+### Parameter citation {#iso19115-3.2018-elem-msr-parameterCitation-f73ae3a2b90e81efc9580944ce22b2ac}
+
+Name
+
+:
+
+> msr:parameterCitation
+
+Description
+
+:
+
+```{=html}
+reference providing description of the parameters
+```
+
+Condition
+
+:
+
+> optional
+
+### Point in pixel {#iso19115-3.2018-elem-msr-pointInPixel-0af6deb11128e3f4a2ff8b0977992bfa}
+
+Name
+
+:
+
+> msr:pointInPixel
+
+Description
+
+:
+
+```{=html}
+earth location in the coordinate system defined by
+ the Spatial Reference System and the grid coordinate of the cell halfway
+ between opposite ends of the grid in the spatial dimensions
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Reference system identifier {#iso19115-3.2018-elem-msr-referenceSystemIdentifier-09e68463a6d485661dea8c8ee60f200c}
+
+Name
+
+:
+
+> msr:referenceSystemIdentifier
+
+Description
+
+:
+
+```{=html}
+identifier and codespace for reference system.: NOTE
+ Refer to SC_CRS in ISO 19111 and ISO 19111-2 when coordinate reference
+ system information is not given through reference system identifier.
+ EXAMPLE EPSG::4326
+```
+
+Condition
+
+:
+
+> optional
+
+### Reference system type {#iso19115-3.2018-elem-msr-referenceSystemType-ceb046628f892e9275b16576075da590}
+
+Name
+
+:
+
+> msr:referenceSystemType
+
+Description
+
+:
+
+```{=html}
+Type of reference system used. EXAMPLE
+ compoundGeographic2DParametric
+```
+
+Condition
+
+:
+
+> optional
+
+### Resolution {#iso19115-3.2018-elem-msr-resolution-8c31d92119d27e90a500ba143ebba523}
+
+Name
+
+:
+
+> msr:resolution
+
+Description
+
+:
+
+```{=html}
+Degree of detail in the grid dataset
+```
+
+Condition
+
+:
+
+> optional
+
+Recommended values
+
+| code | label |
+|------|---------|
+| 1 | seconds |
+| 1 | minutes |
+| 1 | hours |
+| 1 | days |
+| 1 | months |
+| 1 | years |
+
+### Scope {#iso19115-3.2018-elem-msr-scope-09241cd1dbd4fe44de5bfc2286fbf809}
+
+Name
+
+:
+
+> msr:scope
+
+Description
+
+:
+
+### Topology level {#iso19115-3.2018-elem-msr-topologyLevel-be67871bdfef340e4c64d23ce720309f}
+
+Name
+
+:
+
+> msr:topologyLevel
+
+Description
+
+:
+
+```{=html}
+Code which identifies the degree of complexity of
+ the spatial relationships
+```
+
+Condition
+
+:
+
+> optional
+
+### Transformation dimension description {#iso19115-3.2018-elem-msr-transformationDimensionDescription-d8267d48e06a28d23995f4d15632df06}
+
+Name
+
+:
+
+> msr:transformationDimensionDescription
+
+Description
+
+:
+
+```{=html}
+General description of the transformation
+```
+
+Condition
+
+:
+
+> optional
+
+### Transformation dimension mapping {#iso19115-3.2018-elem-msr-transformationDimensionMapping-096dd7aa9d987551a7fc05916ab175e5}
+
+Name
+
+:
+
+> msr:transformationDimensionMapping
+
+Description
+
+:
+
+```{=html}
+information about which grid axes are the spatial
+ (map) axes
+```
+
+Condition
+
+:
+
+> optional
+
+### Transformation parameter availability {#iso19115-3.2018-elem-msr-transformationParameterAvailability-6b1938c019c8c19dfd766adb28ac8ad2}
+
+Name
+
+:
+
+> msr:transformationParameterAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not parameters for
+ transformation between image coordinates and geographic or map coordinates
+ exist (are available)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Owns {#iso19115-3.2018-elem-owns-07532653d8de43dc6b0895600811d193}
+
+Name
+
+:
+
+> owns
+
+Description
+
+:
+
+### Radix {#iso19115-3.2018-elem-radix-d838eab62c3144df803ddaa55d6095bc}
+
+Name
+
+:
+
+> radix
+
+Description
+
+:
+
+### Amendment Type {#iso19115-3.2018-elem-reg-RE_AmendmentType-bc6ddbef5ca2d044bee06fd1e05fb752}
+
+Name
+
+:
+
+> reg:RE_AmendmentType
+
+Description
+
+:
+
+### Standard codelists Amendment Type (reg:RE_AmendmentType)
+
+| code | label | description |
+|-------------------------|-------------------------|-------------|
+| supersession retirement | Supersession Retirement | |
+
+### Decision status {#iso19115-3.2018-elem-reg-RE_DecisionStatus-66fa1c01ac218aa9877e8385d9191958}
+
+Name
+
+:
+
+> reg:RE_DecisionStatus
+
+Description
+
+:
+
+### Standard codelists Decision status (reg:RE_DecisionStatus)
+
+| code | label | description |
+|-------------------------|-------------------------|-------------|
+| pending tentative final | Pending Tentative Final | |
+
+### Disposition {#iso19115-3.2018-elem-reg-RE_Disposition-a0b74f296840fca012ef83c90e5652f1}
+
+Name
+
+:
+
+> reg:RE_Disposition
+
+Description
+
+:
+
+### Standard codelists Disposition (reg:RE_Disposition)
+
+| code | label | description |
+|--------------------------------|---------------------------------|-------------|
+| withdrawn accepted notAccepted | Withdrawn Accepted Not Accepted | |
+
+### Item status {#iso19115-3.2018-elem-reg-RE_ItemStatus-89ad94dd47ec1c6aee8e600828b872d9}
+
+Name
+
+:
+
+> reg:RE_ItemStatus
+
+Description
+
+:
+
+### Standard codelists Item status (reg:RE_ItemStatus)
+
+| code | label | description |
+|-----------------------------------|------------------------------------|-------------|
+| notValid valid superseded retired | Not Valid Valid Superseded Retired | |
+
+### Relative position {#iso19115-3.2018-elem-relativePosition-9b7022d59a1a04be5c97e5183ed0dad1}
+
+Name
+
+:
+
+> relativePosition
+
+Description
+
+:
+
+### Source URL {#iso19115-3.2018-elem-src-3f3e4b17ba622503c28a6c57e4bf00ed}
+
+Name
+
+:
+
+> src
+
+Description
+
+:
+
+```{=html}
+URL of the document.
+```
+### Access Properties {#iso19115-3.2018-elem-srv-accessProperties-1dcd3beb74b9676cd785381643761876}
+
+Name
+
+:
+
+> srv:accessProperties
+
+Description
+
+:
+
+```{=html}
+Information about the availability of the service eg. fees,
+ availability,
+ oredering instructions
+```
+### Connect Point {#iso19115-3.2018-elem-srv-connectPoint-7c5cf627952a324e2bfe7d4b61a8ad43}
+
+Name
+
+:
+
+> srv:connectPoint
+
+Description
+
+:
+
+```{=html}
+Handle for accessing the service interface
+```
+### Contains chain {#iso19115-3.2018-elem-srv-containsChain-27a1d0df5e650777f8e743e2f2467942}
+
+Name
+
+:
+
+> srv:containsChain
+
+Description
+
+:
+
+```{=html}
+Provide information about the chain applied by the service
+```
+### Contains Operations {#iso19115-3.2018-elem-srv-containsOperations-2eecc0ef056aa77980cf2310cbbf0c61}
+
+Name
+
+:
+
+> srv:containsOperations
+
+Description
+
+:
+
+```{=html}
+Provides information about the operations that comprise the
+ service
+```
+### Coupled Resource {#iso19115-3.2018-elem-srv-coupledResource-100ccf0b66cb2f607621adb7e3fc9faa}
+
+Name
+
+:
+
+> srv:coupledResource
+
+Description
+
+:
+
+```{=html}
+Details of services coupled with this one
+```
+### Coupling Type {#iso19115-3.2018-elem-srv-couplingType-d0122b98967eda4ad7f6dc04f2696288}
+
+Name
+
+:
+
+> srv:couplingType
+
+Description
+
+:
+
+```{=html}
+Type of Coupling
+```
+### Distributed Computing Platforms {#iso19115-3.2018-elem-srv-DCP-998f113aa8f9c2233a5eaabf47816383}
+
+Name
+
+:
+
+> srv:DCP
+
+Description
+
+:
+
+```{=html}
+Distributed computing platforms on which the operation has been
+ implemented
+```
+### Distributed Computing Platforms list {#iso19115-3.2018-elem-srv-DCPList-c62e5d011b03b39b745537e308630f03}
+
+Name
+
+:
+
+> srv:DCPList
+
+Description
+
+:
+
+### Standard codelists Distributed Computing Platforms list (srv:DCPList)
+
++-------------+-------------+--------------------+
+| code | label | description |
++=============+=============+====================+
+| XML | XML | DCP is XML |
++-------------+-------------+--------------------+
+| CORBA | CORBA | DCP is CORBA |
++-------------+-------------+--------------------+
+| JAVA | JAVA | DCP is JAVA |
++-------------+-------------+--------------------+
+| COM | COM | DCP is COM |
++-------------+-------------+--------------------+
+| SQL | DCP is SQL | > SQL |
++-------------+-------------+--------------------+
+| SOAP | SOAP | DCP is SOAP |
++-------------+-------------+--------------------+
+| Z3950 | Z3950 | DCP is Z3950 |
++-------------+-------------+--------------------+
+| HTTP | HTTP | DCP is HTTP |
++-------------+-------------+--------------------+
+| FTP | FTP | DCP is FTP |
++-------------+-------------+--------------------+
+| WebServices | WebServices | DCP is WebServices |
++-------------+-------------+--------------------+
+
+### Depends On {#iso19115-3.2018-elem-srv-dependsOn-1332fa3f646ce374f71ce340e90a89c8}
+
+Name
+
+:
+
+> srv:dependsOn
+
+Description
+
+:
+
+```{=html}
+List of operations that must be completed immediately before
+ current operation
+ is invoked, structured as a list for capturing alternate predecessor paths
+ and sets for
+ capturing parallel predecessor paths
+```
+### Description {#iso19115-3.2018-elem-srv-description-89c6b5fc52f0f104cffb29ff89a72125}
+
+Name
+
+:
+
+> srv:description
+
+Description
+
+:
+
+```{=html}
+Narrative explanation of the services in the chain and
+ resulting output or role
+ of the parameter
+```
+### Direction {#iso19115-3.2018-elem-srv-direction-56def65b903590f672385be14b20d5fd}
+
+Name
+
+:
+
+> srv:direction
+
+Description
+
+:
+
+### Distributed computing platform (DCP) {#iso19115-3.2018-elem-srv-distributedComputingPlatform-2d5874d202fafb73f06538a78607a586}
+
+Name
+
+:
+
+> srv:distributedComputingPlatform
+
+Description
+
+:
+
+```{=html}
+DCP on which the operation has been implemented
+```
+### Identifier {#iso19115-3.2018-elem-srv-identifier-cb2268470326162da9519dae784ee639}
+
+Name
+
+:
+
+> srv:identifier
+
+Description
+
+:
+
+```{=html}
+Identifier of resource to which the operation applies
+```
+### Invocation Name {#iso19115-3.2018-elem-srv-invocationName-f632c6f1011da90346f900f7839a33a8}
+
+Name
+
+:
+
+> srv:invocationName
+
+Description
+
+:
+
+```{=html}
+The name used to invoke this interface within the context of
+ the DCP. The name
+ is identical for all DCPs
+```
+### Keywords {#iso19115-3.2018-elem-srv-keywords-cb9fb095a7a8472109439348ed146d7f}
+
+Name
+
+:
+
+> srv:keywords
+
+Description
+
+:
+
+```{=html}
+Keywords describing service
+```
+### Name {#iso19115-3.2018-elem-srv-name-8213033a4a5d36c4b7a7a21e51058844}
+
+Name
+
+:
+
+> srv:name
+
+Description
+
+:
+
+```{=html}
+The name, as used by the service for this chain or parameter
+```
+### Operated dataset {#iso19115-3.2018-elem-srv-operatedDataset-feeb6f24e1ef2b2c5f23d1aaaa1ac0d1}
+
+Name
+
+:
+
+> srv:operatedDataset
+
+Description
+
+:
+
+```{=html}
+Provides a reference to the resource on which the service operates. Note: For one resource either operated dataset or operates on may be used (not both).
+```
+### Operates On {#iso19115-3.2018-elem-srv-operatesOn-2690cd62eaa299d9d24d44103a7c6f1d}
+
+Name
+
+:
+
+> srv:operatesOn
+
+Description
+
+:
+
+```{=html}
+Provides information on the datasets that the service operates
+ on
+```
+### Operation Description {#iso19115-3.2018-elem-srv-operationDescription-4bf280cc494e9e2d0ccbbcc1e6213185}
+
+Name
+
+:
+
+> srv:operationDescription
+
+Description
+
+:
+
+```{=html}
+Free text description of the intent of the operation and the
+ results of the
+ operation
+```
+### Operation Name {#iso19115-3.2018-elem-srv-operationName-ae64b692aa02e2fccc8081aae5d6fd08}
+
+Name
+
+:
+
+> srv:operationName
+
+Description
+
+:
+
+```{=html}
+A unique identifier for this interface
+```
+### Optionality {#iso19115-3.2018-elem-srv-optionality-62aca8e868833c95f16a1c5d9fc41ce8}
+
+Name
+
+:
+
+> srv:optionality
+
+Description
+
+:
+
+```{=html}
+Indication if the parameter is required
+```
+### Parameter {#iso19115-3.2018-elem-srv-parameter-efeaa89fa390b7c869522baf94cb3421}
+
+Name
+
+:
+
+> srv:parameter
+
+Description
+
+:
+
+### Parameters {#iso19115-3.2018-elem-srv-parameters-2b38d36e3a0bef6c49fff8b983deb47e}
+
+Name
+
+:
+
+> srv:parameters
+
+Description
+
+:
+
+```{=html}
+The parameters that are required for this interface
+```
+### Profile {#iso19115-3.2018-elem-srv-profile-8a095529da8795ed9becd1b15d1cdb6d}
+
+Name
+
+:
+
+> srv:profile
+
+Description
+
+:
+
+```{=html}
+Profile to which the service adheres
+```
+### Provider Name {#iso19115-3.2018-elem-srv-providerName-30341d7e33c9b0622f5fe1c7e33bf449}
+
+Name
+
+:
+
+> srv:providerName
+
+Description
+
+:
+
+```{=html}
+A unique identifier for this organization
+```
+### Repeatability {#iso19115-3.2018-elem-srv-repeatability-88dc3b9d192faab07e37d1aaf1b98440}
+
+Name
+
+:
+
+> srv:repeatability
+
+Description
+
+:
+
+```{=html}
+Indication if more than one value of the parameter may be
+ provided
+```
+### Restrictions {#iso19115-3.2018-elem-srv-restrictions-640e586d60c54c786ca65fa870eb7e46}
+
+Name
+
+:
+
+> srv:restrictions
+
+Description
+
+:
+
+```{=html}
+Legal and security constraints on accessing the service and
+ distributing data
+ generated by the service
+```
+### Service Contact {#iso19115-3.2018-elem-srv-serviceContact-ec85c67af1aecbd4739b76567523edb1}
+
+Name
+
+:
+
+> srv:serviceContact
+
+Description
+
+:
+
+```{=html}
+Information for contacting the service provider
+```
+### Service standard {#iso19115-3.2018-elem-srv-serviceStandard-97e92f2223295fea76badfd3355952c9}
+
+Name
+
+:
+
+> srv:serviceStandard
+
+Description
+
+:
+
+```{=html}
+Standard to which the service adheres
+```
+### Service Type {#iso19115-3.2018-elem-srv-serviceType-2234736c4656254dd3186e40b24d9acf}
+
+Name
+
+:
+
+> srv:serviceType
+
+Description
+
+:
+
+```{=html}
+Service type name from a registry of services. For example, the
+ values of the
+ nameSpace and name attributes of GeneralName may be 'OGC' and 'catalogue'
+```
+Recommended values
+
+| code | label |
+|-----------|----------------------------|
+| OGC:WMS | OGC Web Map Service |
+| OGC:WMTS | OGC Web Map Tile Service |
+| OGC:WFS | OGC Web Feature Service |
+| OGC:WCS | OGC Web Coverage Service |
+| OGC:WPS | OGC Web Processing Service |
+| atom:feed | ATOM feed |
+
+### Service Version {#iso19115-3.2018-elem-srv-serviceTypeVersion-d13d77b6c3c1085c84121099f3e977b9}
+
+Name
+
+:
+
+> srv:serviceTypeVersion
+
+Description
+
+:
+
+```{=html}
+Provides for searching based on the version of serviceType. For
+ example, we may
+ only be interested in OGC Catalogue V1.1 services. If version is
+ maintained as a
+ separate attribute, users can easily search for all services of a type
+ regardless of the
+ version
+```
+### Coupled Resource {#iso19115-3.2018-elem-srv-SV_CoupledResource-58b1bb08fb2ff8e0c70e6ee5f9b5a151}
+
+Name
+
+:
+
+> srv:SV_CoupledResource
+
+Description
+
+:
+
+```{=html}
+Details of services coupled with this one
+```
+### Operation {#iso19115-3.2018-elem-srv-SV_OperationMetadata-3267aa3513feb299599031dd1cf78c96}
+
+Name
+
+:
+
+> srv:SV_OperationMetadata
+
+Description
+
+:
+
+```{=html}
+Operation Metadata
+```
+### Parameter {#iso19115-3.2018-elem-srv-SV_Parameter-6f238c83d2a447d7ff4fc3f2e7af0e88}
+
+Name
+
+:
+
+> srv:SV_Parameter
+
+Description
+
+:
+
+```{=html}
+The parameters that are required for this interface
+```
+### Parameter direction {#iso19115-3.2018-elem-srv-SV_ParameterDirection-7bd1f85c0b44fa0fee670d93cc089089}
+
+Name
+
+:
+
+> srv:SV_ParameterDirection
+
+Description
+
+:
+
+### Standard codelists Parameter direction (srv:SV_ParameterDirection)
+
+| code | label | description |
+|--------|--------------|-----------------------------------------------------------------------------|
+| in | Input | The parameter is an input parameter to the service instance |
+| out | Output | The parameter is an output parameter to the service instance |
+| in/out | Input/output | The parameter is both an input and output parameter to the service instance |
+
+### Service Identification {#iso19115-3.2018-elem-srv-SV_ServiceIdentification-fc7ece2ea3d136f031fb0392e774dee6}
+
+Name
+
+:
+
+> srv:SV_ServiceIdentification
+
+Description
+
+:
+
+```{=html}
+Service identification section
+```
+### Value type {#iso19115-3.2018-elem-srv-valueType-e15acf0ffbb059ee6c8bd9516d8d4b0c}
+
+Name
+
+:
+
+> srv:valueType
+
+Description
+
+:
+
+### Unit {#iso19115-3.2018-elem-unit-272387d5556a648743e54ae5e2dba3af}
+
+Name
+
+:
+
+> unit
+
+Description
+
+:
+
+### Units of measure {#iso19115-3.2018-elem-uom-e10669ccd649478676b9c5fafba3f843}
+
+Name
+
+:
+
+> uom
+
+Description
+
+:
+
+Recommended values
+
+| code | label |
+|------|--------|
+| m | meters |
+
+### Metadata uuid {#iso19115-3.2018-elem-uuidref-11480fcd74a341f26892dff0229f85c3}
+
+Name
+
+:
+
+> uuidref
+
+Description
+
+:
+
+```{=html}
+Unique identifier
+```
+### Link href {#iso19115-3.2018-elem-xlink-href-3546192ce8d22ae0019a3b6c851328e5}
+
+Name
+
+:
+
+> xlink:href
+
+Description
+
+:
+
+```{=html}
+Supplies the data that allows an XLink application to find a
+ remote resource (or resource fragment) [W3C XLINK]
+```
+### Type of link {#iso19115-3.2018-elem-xlink-type-bb34ecc5adb016fbd170f488e20511ca}
+
+Name
+
+:
+
+> xlink:type
+
+Description
+
+:
+
+### Nil {#iso19115-3.2018-elem-xsi-nil-6e33165974e6ce03896d82c4465e9a29}
+
+Name
+
+:
+
+> xsi:nil
+
+Description
+
+:
+
+```{=html}
+Indicates that a certain element does not have a value or that the value is unknown.
+```
+## Standard codelists
+
+List of all codelists available in the standard.
+
+### Standard codelists (cit:CI_TelephoneTypeCode) {#iso19115-3.2018-cl-cit-CI_TelephoneTypeCode}
+
+| code | label | description |
+|------------|-----------|--------------------------------------|
+| voice | Voice | Telephone provides voice service |
+| facsimilie | Facsimile | Telephone provides facsimile service |
+| sms | SMS | Telephone provides sms service |
+
+### Standard codelists (cit:CI_DateTypeCode) {#iso19115-3.2018-cl-cit-CI_DateTypeCode}
+
+| code | label | description |
+|-----------------|------------------|---------------------------------------------------------------------------------------|
+| creation | Creation | Date identifies when the resource was brought into existence |
+| publication | Publication | Date identifies when the resource was issued |
+| revision | Revision | Date identifies when the resource was examined or re-examined and improved or amended |
+| expiry | Expiry | Date identifies when the resource expires |
+| lastUpdate | Last Update | Date identifies when the resource was last updated |
+| lastRevision | Last Revision | Date identifies when the resource was last reviewed |
+| nextUpdate | Next Update | Date identifies when the resource will be next updated |
+| unavailable | Unavailable | Date identifies when the resource became not available or obtainable |
+| inForce | In Force | Date identifies when the resource became in force |
+| adopted | Adopted | Date identifies when the resource was adopted |
+| deprecated | Deprecated | Date identifies when the resource was deprecated |
+| superseded | Superseded | Date identifies when the resource was superseded or replaced by another resource |
+| validityBegins | Validity Begins | Date identifies when the resource is considered to be valid |
+| validityExpires | Validity Expires | Date identifies when the resource is no longer considered to be valid |
+| released | Released | Date identifies when the resource shall be released for public access |
+| distribution | Distribution | Date identifies when an instance of the resource was distributed |
+
+### Standard codelists (cit:CI_OnLineFunctionCode) {#iso19115-3.2018-cl-cit-CI_OnLineFunctionCode}
+
+| code | label | description |
+|----------------------|---------------------------------------------------|----------------------------------------------------------------------------------------|
+| download | Download | Online instructions for transferring data from one storage device or system to another |
+| information | Information | Online information about the resource |
+| offlineAccess | Offline access | Online instructions for requesting the resource from the provider |
+| order | Order | Online order process for obtening the resource |
+| search | Search | Online search interface for seeking out information about the resource |
+| completeMetadata doi | Complete Metadata Digital Object Identifier (DOI) | Complete metadata provided |
+| browseGraphic | Browse Graphic | Browse Graphic provided |
+| upload | Upload | Upload service provided |
+| emailService | Email Service | Email service provided |
+| browsing | Browsing | Online browsing provided |
+| fileAccess | Access File | Online file access provided |
+
+### Standard codelists (cit:CI_PresentationFormCode) {#iso19115-3.2018-cl-cit-CI_PresentationFormCode}
+
+| code | label | description |
+|--------------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| documentDigital | Digital document | Digital representation of a primarily textual item (can contain illustrations also) |
+| imageDigital | Digital image | Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format |
+| documentHardcopy | Hardcopy document | Representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media |
+| imageHardcopy | Hardcopy image | Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user |
+| mapDigital | Digital map | Map represented in raster or vector form |
+| mapHardcopy | Hardcopy map | Map printed on paper, photographic material, or other media for use directly by the human user |
+| modelDigital | Digital model | Multi-dimensional digital representation of a feature, process, etc. |
+| modelHardcopy | Hardcopy model | 3-dimensional, physical model |
+| profileDigital | Digital profile | Vertical cross-section in digital form |
+| profileHardcopy | Hardcopy profile | Vertical cross-section printed on paper, etc. |
+| tableDigital | Digital table | Digital representation of facts or figures systematically displayed, especially in columns |
+| tableHardcopy | Hardcopy table | Representation of facts or figures systematically displayed, especially in columns, printed onpapers, photographic material, or other media |
+| videoDigital | Digital video | Digital video recording |
+| videoHardcopy | Hardcopy video | Video recording on film |
+| audioDigital | Digital audio | Digital audio recording |
+| audioHardcopy | Hardcopy audio | Audio recording delivered by analog media, such as magnetic tape |
+| multimediaDigital | Multimedia digital | Information representation using simultaneously various digital modes for text, sound and image |
+| multimediaHardcopy | Multimedia hardcopy | Information representation using simultaneously various analog modes for text, sound and image |
+| physicalObject | Physical object | A physical object eg. rock or mineral sample, microscope slide |
+| diagramDigital | Digital diagram | Information represented graphically by charts such as pie chart, bar chart and other type of diagrams and recorded in digital format |
+| diagramHardcopy | Hardcopy diagram | Information represented graphically by charts such as pie chart, bar chart and other type of diagrams and printed on paper, photographic material, or other media |
+
+### Standard codelists Role code (cit:CI_RoleCode) {#iso19115-3.2018-cl-cit-CI_RoleCode}
+
+| code | label | description |
+|-----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| resourceProvider | Resource provider | Party that supplies the resource |
+| custodian | Custodian | Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource |
+| owner | Owner | Party that owns the resource |
+| user | User | Party who uses the resource |
+| distributor | Distributor | Party who distributes the resource |
+| originator | Originator | Party who created the resource |
+| pointOfContact | Point of contact | Party who can be contacted for acquiring knowledge about or acquisition of the resource |
+| principalInvestigator | Principal investigator | Key party responsible for gathering information and conducting research |
+| processor | Processor | Party that has processed the data in a manner such that the resource has been modified |
+| publisher | Publisher | Party who published the resource |
+| author | Author | Party who authored the resource |
+| sponsor | Sponsor | Party who speaks for the resource |
+| coAuthor | Co-author | Party who jointly authors the resource |
+| collaborator | Collaborator | Party who assists with the generation of the resource other than the principal investigator |
+| editor | Editor | Party who reviewed or modified the resource to improve the content |
+| mediator | Mediator | A class of entity that mediates access to the resource and for whom the resource is intended or useful |
+| rightsHolder | Rights holder | Party owning or managing rights over the resource |
+| contributor | Contributor | Party contributing to the resource |
+| funder | Funder | Party providing monetary support for the resource |
+| stakeholder | Stakeholder | Party who has an interest in the resource or the use of the resource |
+
+### Standard codelists (mdq:DQ_EvaluationMethodTypeCode) {#iso19115-3.2018-cl-mdq-DQ_EvaluationMethodTypeCode}
+
+| code | label | description |
+|----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| directInternal | Direct internal | Method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated |
+| directExternal | Direct external | Method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data external to the dataset being evaluated is required |
+| indirect | Indirect | Method of evaluating the quality of a dataset based on external knowledge |
+
+### Standard codelists (mri:DS_AssociationTypeCode) {#iso19115-3.2018-cl-mri-DS_AssociationTypeCode}
+
+| code | label | description |
+|------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| crossReference | Cross reference | Reference from one dataset to another |
+| largerWorkCitation | Larger work citation | Reference to a master dataset of which this one is a part |
+| partOfSeamlessDatabase | Part of seamless database | Part of the same structured set of data held in a computer |
+| stereoMate | Stereo mate | Part of a set of imagery that when used together, provides three-dimensional images |
+| isComposedOf | Is composed of | Reference to resources that are parts of this resource |
+| collectiveTitle | Collective Title | Common title for a collection of resources. NOTE Title identifies elements of a series collectively, combined with information about what volumes are available at the source cite |
+| series | Series | Associated through a common heritage such as produced to a common product specification |
+| dependency | Dependency | Associated through a dependency |
+| revisionOf | Revision Of | Resource is a revision of associated resource |
+
+### Standard codelists (mri:DS_InitiativeTypeCode) {#iso19115-3.2018-cl-mri-DS_InitiativeTypeCode}
+
+| code | label | description |
+|---------------|---------------|-------------------------------------------------------------|
+| campaign | Campaign | Series of organized planned actions |
+| collection | Collection | Accumulation of datasets assembled for a specific purpose |
+| exercise | Exercise | Specific performance of a function or group of functions |
+| experiment | Experiment | Process designed to find if something is effective or valid |
+| investigation | Investigation | Search or systematic inquiry |
+| mission | Mission | Specific operation of a data collection system |
+| sensor | Sensor | Device or piece of equipment which detects or records |
+| operation | Operation | Action that is part of a series of actions |
+| platform | Platform | Vehicle or other support base that holds a sensor |
+| process | Process | Method of doing something involving a number of steps |
+| program | Program | Specific planned activity |
+| project | Project | Organized undertaking, research, or development |
+| study | Study | Examination or investigation |
+| task | Task | Piece of work |
+| trial | Trial | Process of testing to discover or demonstrate something |
+
+### Standard codelists Role type (gfc:FC_RoleType) {#iso19115-3.2018-cl-gfc-FC_RoleType}
+
+| code | label | description |
+|-------------|-------------|------------------------------------------|
+| ordinary | Ordinary | Indicates an ordinary association. |
+| aggregation | Aggregation | Indicates a UML aggregation (part role). |
+| composition | Composition | Indicates a UML composition (part role). |
+
+### Standard codelists (mco:MD_ClassificationCode) {#iso19115-3.2018-cl-mco-MD_ClassificationCode}
+
+| code | label | description |
+|---------------------|----------------------------|-----------------------------------------------------------------------------------------------------------|
+| unclassified | Unclassified | Available for general disclosure |
+| restricted | Restricted | Not for general disclosure |
+| confidential | Confidential | Available for someone who can be entrusted with information |
+| secret | Secret | Kept or meant to be kept private, unknown, or hidden from all but a select group of people |
+| topSecret | Top secret | Of the highest secrecy |
+| SBU | Sensitive But Unclassified | Although unclassified, requires strict controls over its distribution |
+| forOfficialUseOnly | For Official Use Only | Unclassified information that is to be used only for official purposes determined by the designating body |
+| protected | Protected | Compromise of the information could cause damage |
+| limitedDistribution | Limited Distribution | Dissemination limited by designating body |
+
+### Standard codelists Coverage content (mrc:MD_CoverageContentTypeCode) {#iso19115-3.2018-cl-mrc-MD_CoverageContentTypeCode}
+
+| code | label | description |
+|------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| image | Image | Meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter |
+| thematicClassification | Thematic classification | Code value with no quantitative meaning, used to represent a physical quantity |
+| physicalMeasurement | Physical measurement | Value in physical units of the quantity being measured |
+| auxillaryInformation | Auxillary Information | Data, usually a physical measurement, used to support the calculation of the primary physicalMeasurement coverages in the dataset. EXAMPLE: Grid of aerosol optical thickness used in the calculation of a sea surface temperature product |
+| qualityInformation | Quality Information | Data used to characterize the quality of the physicalMeasurement coverages in the dataset. NOTE: Typically included in a gmi:QE_CoverageResult |
+| referenceInformation | Reference Information | Data used to characterize the quality of the physicalMeasurement coverages in the dataset. NOTE: Typically included in a gmi:QE_CoverageResult |
+| modelResult | Model Result | Resources with values that are calculated using a model rather than being observed or calculated from observations |
+| coordinate | Coordinate | Data used to provide coordinate axis values |
+
+### Standard codelists (mex:MD_DatatypeCode) {#iso19115-3.2018-cl-mex-MD_DatatypeCode}
+
+| code | label | description |
+|-----------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| class | Class | Descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior |
+| codelist | Codelist | Descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior |
+| enumeration | Enumeration | Data type whose instances form a list of named literal values, not extendable |
+| codelistElement | Codelist element | Permissible value for a codelist or enumeration |
+| abstractClass | Abstract class | Class that cannot be directly instantiated |
+| aggregateClass | Aggregate class | Class that is composed of classes it is connected to by an aggregate relationship |
+| specifiedClass | Specified class | Subclass that may be substituted for its superclass |
+| datatypeClass | Datatype class | Class with few or no operations whose primary purpose is to hold the abstract state of another class for transmittal, storage, encoding or persistent storage |
+| interfaceClass | Interface class | Named set of operations that characterize the behavior of an element |
+| unionClass | Union class | Class describing a selection of one of the specified types |
+| metaClass | Meta class | Class whose instances are classes |
+| typeClass | Type class | Class used for specification of a domain of instances (objects), together with the operations applicable to the objects. A type may have attributes and associations |
+| characterString | Character string | Free text field |
+| integer | Integer | Numerical field |
+| association | Association | Semantic relationship between two classes that involves connections among their instances |
+
+### Standard codelists Name (msr:MD_DimensionNameTypeCode) {#iso19115-3.2018-cl-msr-MD_DimensionNameTypeCode}
+
+| code | label | description |
+|------------|-------------|------------------------------------------------------------|
+| row | Row | Ordinate (y) axis |
+| column | Column | Abscissa (x) axis |
+| vertical | Vertical | Vertical (z) axis |
+| track | Track | Along the direction of motion of the scan point |
+| crossTrack | Cross track | Perpendicular to the direction of motion of the scan point |
+| line | Line | Scan line of a sensor |
+| sample | Sample | Element along a scan line |
+| time | Time | Duration |
+
+### Standard codelists (msr:MD_GeometricObjectTypeCode) {#iso19115-3.2018-cl-msr-MD_GeometricObjectTypeCode}
+
+| code | label | description |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------|
+| complex | Complex | Set of geometric primitives such that their boundaries can be represented as an union of other primitives |
+| composite | Composite | Connected set of curves, solids or surfaces |
+| curve | Curve | Bounded, 1-dimensional geometric primitive, representing the continuous image of a line |
+| point | Point | Zero-dimensional geometric primitive, representing a position but not having an extent |
+| solid | Solid | Bounded, connected 3-dimensional geometric primitive, representing the continuous image of a region of space |
+| surface | Surface | Bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane |
+
+### Standard codelists (mrc:MD_ImagingConditionCode) {#iso19115-3.2018-cl-mrc-MD_ImagingConditionCode}
+
+| code | label | description |
+|--------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| blurredImage | Blurred image | Portion of the image is blurred |
+| cloud | Cloud | Portion of the image is partially obscured by cloud cover |
+| degradingObliquity | Degrading obliquity | Acute angle between the plane of the ecliptic (the plane of the Earth s orbit) and the plane of the celestial equator |
+| fog | Fog | Portion of the image is partially obscured by fog |
+| heavySmokeOrDust | Heavy smoke or dust | Portion of the image is partially obscured by heavy smoke or dust |
+| night | Night | Image was taken at night |
+| rain | Rain | Image was taken during rainfall |
+| semiDarkness | Semi darkness | Image was taken during semi-dark conditions -- twilight conditions |
+| shadow | Shadow | Portion of the image is obscured by shadow |
+| snow | Snow | Portion of the image is obscured by snow |
+| terrainMasking | Terrain masking | The absence of collection data of a given point or area caused by the relative location of topographic features which obstruct the collection path between the collector(s) and the subject(s) of interest |
+
+### Standard codelists (mri:MD_KeywordTypeCode) {#iso19115-3.2018-cl-mri-MD_KeywordTypeCode}
+
+| code | label | description |
+|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------|
+| discipline | Discipline | Keyword identifies a branch of instruction or specialized learning |
+| place | Place | Keyword identifies a location |
+| stratum | Stratum | Keyword identifies the layer(s) of any deposited substance |
+| temporal | Temporal | Keyword identifies a time period related to the dataset |
+| theme | Theme | Keyword identifies a particular subject or topic |
+| dataCentre | Data centre | Keyword identifies a repository or archive that manages and distributes data |
+| featureType | Feature type | Keyword identifies a resource containing or about a collection of feature instances with common characteristics |
+| instrument | Instrument | Keyword identifies a device used to measure or compare physical properties |
+| platform | Platform | Keyword identifies a structure upon which an instrument is mounted |
+| process | Process | Keyword identifies a series of actions or natural occurrences |
+| project | Project | Keyword identifies an endeavour undertaken to create or modify a product or service |
+| service | Service | Keyword identifies an activity carried out by one party for the benefit of another |
+| product | Product | Keyword identifies a type of product |
+| subTopicCategory | Sub-Topic Category | Refinement of a topic category for the purpose of geographic data classification |
+| taxon | Taxon | Keyword identifies a taxonomy of the resource |
+
+### Standard codelists Maintenance Frequency (mmi:MD_MaintenanceFrequencyCode) {#iso19115-3.2018-cl-mmi-MD_MaintenanceFrequencyCode}
+
+| code | label | description |
+|-------------|--------------|----------------------------------------------------------|
+| continual | Continual | Data is repeatedly and frequently updated |
+| daily | Daily | Data is updated each day |
+| weekly | Weekly | Data is updated on a weekly basis |
+| fortnightly | Fortnightly | Data is updated every two weeks |
+| monthly | Monthly | Data is updated each month |
+| quarterly | Quarterly | Data is updated every three months |
+| biannually | Biannually | Data is updated twice each year |
+| annually | Annually | Data is updated every year |
+| asNeeded | As needed | Data is updated as deemed necessary |
+| irregular | Irregular | Data is updated in intervals that are uneven in duration |
+| notPlanned | Not planned | There are no plans to update the data |
+| unknown | Unknown | Frequency of maintenance for the data is not known |
+| periodic | Periodic | Resource is updated at regular intervals |
+| semimonthly | Semi-monthly | Resource updated twice monthly |
+| biennially | Biennially | Resource is updated every 2 years |
+
+### Standard codelists (mrd:MD_MediumFormatCode) {#iso19115-3.2018-cl-mrd-MD_MediumFormatCode}
+
+| code | label | description |
+|------------------|--------------------|------------------------------------------------------------|
+| cpio | CPIO | CoPy In / Out (UNIX file format and command) |
+| tar | TAR | Tape ARchive |
+| highSierra | High sierra | High sierra file system |
+| iso9660 | ISO9660 | Information processing volume and file structure of CD-ROM |
+| iso9660RockRidge | ISO9660 Rock Ridge | Rock ridge interchange protocol (UNIX) |
+| iso9660AppleHFS | ISO9660 Apple HFS | Hierarchical file system (Macintosh) |
+| udf | UDF | Universal Disk Format |
+
+### Standard codelists (mex:MD_ObligationCode) {#iso19115-3.2018-cl-mex-MD_ObligationCode}
+
+| code | label | description |
+|-------------|-------------|------------------------------------------------------|
+| mandatory | Mandatory | Element is always required |
+| optional | Optional | Element is not required |
+| conditional | Conditional | Element is required when a specific condition is met |
+
+### Standard codelists Pixel orientation code (msr:MD_PixelOrientationCode) {#iso19115-3.2018-cl-msr-MD_PixelOrientationCode}
+
+| code | label | description |
+|------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| center | Center | Point halfway between the lower left and the upper right of the pixel |
+| lowerLeft | Lower left | The corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value |
+| lowerRight | Lower right | Next corner counterclockwise from the lower left |
+| upperRight | Upper right | Next corner counterclockwise from the lower right |
+| upperLeft | Upper left | Next corner counterclockwise from the upper right |
+
+### Standard codelists Status (mcc:MD_ProgressCode) {#iso19115-3.2018-cl-mcc-MD_ProgressCode}
+
+| code | label | description |
+|-------------------|--------------------|--------------------------------------------------------------------------------------|
+| completed | Completed | Production of the data has been completed |
+| historicalArchive | Historical archive | Data has been stored in an offline storage facility |
+| obsolete | Obsolete | Data is no longer relevant |
+| onGoing | On going | Data is continually being updated |
+| planned | Planned | Fixed date has been established upon or by which the data will be created or updated |
+| required | Required | Data needs to be generated or updated |
+| underDevelopment | Under development | Data is currently in the process of being created |
+| final | Final | Progress concluded and no changes will be accepted |
+| pending | Pending | Committed to, but not yet addressed |
+| retired | Retired | Item is no longer recommended for use. It has not been superseded by another item |
+| superseded | Superseded | Replaced by new item |
+| tentative | Tentative | Provisional changes likely before resource becomes final or complete |
+| valid | Valid | Acceptable under specific conditions |
+| accepted | Accepted | Agreed to by sponsor |
+| notAccepted | Not Accepted | Rejected by sponsor |
+| withdrawn | Withdrawn | Withdrawn |
+| proposed | Proposed | Suggested that development needs to be undertaken |
+| deprecated | Deprecated | Resource superseded and will become obsolete, use only for historical purposes |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|-------------|--------------|-------------|
+| notobsolete | Not obsolete | |
+
+### Standard codelists Access constraints (mco:MD_RestrictionCode) {#iso19115-3.2018-cl-mco-MD_RestrictionCode}
+
+| code | label | description |
+|----------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| copyright | Copyright | Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor |
+| patent | Patent | Government has granted exclusive right to make, sell, use or license an invention or discovery |
+| patentPending | Pending patent | Produced or sold information awaiting a patent |
+| trademark | Trademark | A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer |
+| license | License | Formal permission to do something |
+| intellectualPropertyRights | Intellectual property rights | Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity |
+| restricted | Restricted | Withheld from general circulation or disclosure |
+| otherRestrictions | Other restrictions | Limitation not listed |
+| unrestricted | Unrestricted | No constraints exist |
+| licenceUnrestricted | Licence Unrestricted | formal permission not required to use the resource |
+| licenceEndUser | Licence End User | Formal permission required for a person or an entity to use the resource and that may differ from the person that orders or purchases it |
+| licenceDistributor | Licence Distributor | Formal permission required for a person or an entity to commercialize or distribute the resource |
+| private | Private | Protects rights of individual or organisations from observation, intrusion, or attention of others |
+| statutory | Statutory | Prescribed by law |
+| confidential | Confidential | Not available to the public. NOTE: Contains information that could be prejudicial to a commercial, industrial, or national interest |
+| SBU | Sensitive But Unclassified | Although unclassified, requires strict controls over its distribution |
+| in-confidence | In-Confidence | With trust |
+
+### Standard codelists Scope code (mcc:MD_ScopeCode) {#iso19115-3.2018-cl-mcc-MD_ScopeCode}
+
+| code | label | description |
+|----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| attribute | Attribute | Information applies to the attribute class |
+| attributeType | Attribute type | Information applies to the characteristic of a feature |
+| collectionHardware | Collection hardware | Information applies to the collection hardware class |
+| collectionSession | Collection session | Information applies to the collection session |
+| dataset | Dataset | Information applies to the dataset |
+| series | Series | Information applies to the series |
+| nonGeographicDataset | Non geographic dataset | Information applies to non-geographic data |
+| dimensionGroup | Dimension group | Information applies to a dimension group |
+| feature | Feature | Information applies to a feature |
+| featureType | Feature type | Information applies to a feature type |
+| propertyType | Property type | Information applies to a property type |
+| fieldSession | Field session | Information applies to a field session |
+| software | Software | Information applies to a computer program or routine |
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+| model | Model | Information applies to a copy or imitation of an existing or hypothetical object |
+| tile | Tile | Information applies to a tile, a spatial subset of geographic data |
+| metadata | Metadata | Information applies to metadata |
+| initiative | Initiative | Information applies to an initiative |
+| sample | Sample | Information applies to a sample |
+| document | Document | Information applies to a document |
+| repository | Repository | Information applies to a repository |
+| aggregate | Aggregate | Information applies to an aggregate resource |
+| product | Product | Metadata describing an ISO 19131 data product specification |
+| collection | Collection | Information applies to an unstructured set |
+| coverage | Coverage | Information applies to a coverage |
+| application | Application | Information resource hosted on a specific set of hardware and accessible over a network |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|------------------------------|--------------------------------|-------------|
+| map staticMap interactiveMap | Map Static map Interactive map | |
+
+### Standard codelists Spatial Representation Type (mcc:MD_SpatialRepresentationTypeCode) {#iso19115-3.2018-cl-mcc-MD_SpatialRepresentationTypeCode}
+
+| code | label | description |
+|-------------|--------------|----------------------------------------------------------------------------------------------------|
+| vector | Vector | Vector data is used to represent geographic data |
+| grid | Grid | Grid data is used to represent geographic data |
+| textTable | Text, table | Textual or tabular data is used to represent geographic data |
+| tin | TIN | Triangulated irregular network |
+| stereoModel | Stereo model | Three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images |
+| video | Video | Scene from a video recording |
+
+### Standard codelists Topic category code (mri:MD_TopicCategoryCode) {#iso19115-3.2018-cl-mri-MD_TopicCategoryCode}
+
+| code | label | description |
+|----------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| farming | Farming | Rearing of animals and/or cultivation of plants. Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock |
+| biota | Biota | Flora and/or fauna in natural environment. Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat |
+| boundaries | Boundaries | Legal land descriptions. Examples: political and administrative boundaries |
+| climatologyMeteorologyAtmosphere | Climatology, meteorology, atmosphere | Processes and phenomena of the atmosphere. Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation |
+| economy | Economy | Economic activities, conditions and employment. Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas |
+| elevation | Elevation | Height above or below sea level. Examples: altitude, bathymetry, digital elevation models, slope, derived products |
+| environment | Environment | Environmental resources, protection and conservation. Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape |
+| geoscientificInformation | Geoscientific information | Information pertaining to earth sciences. Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion |
+| health | Health | Health, health services, human ecology, and safety. Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services |
+| imageryBaseMapsEarthCover | Imagery base maps earth cover | Base maps. Examples: land cover, topographic maps, imagery, unclassified images, annotations |
+| intelligenceMilitary | Intelligence military | Military bases, structures, activities. Examples: barracks, training grounds, military transportation, information collection |
+| inlandWaters | Inland waters | Inland water features, drainage systems and their characteristics. Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts |
+| location | Location | Positional information and services. Examples: addresses, geodetic networks, control points, postal zones and services, place names |
+| oceans | Oceans | Features and characteristics of salt water bodies (excluding inland waters). Examples: tides, tidal waves, coastal information, reefs |
+| planningCadastre | Planning cadastre | Information used for appropriate actions for future use of the land. Examples: land use maps, zoning maps, cadastral surveys, land ownership |
+| society | Society | Characteristics of society and cultures. Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information |
+| structure | Structure | Man-made construction. Examples: buildings, museums, churches, factories, housing, monuments, shops, towers |
+| transportation | Transportation | Means and aids for conveying persons and/or goods. Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways |
+| utilitiesCommunication | Utilities communication | Energy, water and waste systems and communications infrastructure andservices. Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks |
+| extraTerrestrial | Extra Terrestrial | Region more than 100 km above the surface of the Earth |
+| disaster | Disaster | Information related to disasters EXAMPLES: Site of the disaster, evacuation zone, disaster-prevention facility, disaster relief activities |
+
+### Standard codelists (msr:MD_TopologyLevelCode) {#iso19115-3.2018-cl-msr-MD_TopologyLevelCode}
+
+| code | label | description |
+|------------------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| geometryOnly | Geometry only | Geometry objects without any additional structure which describes topology |
+| topology1D | Topology 1D | 1-dimensional topological complex -- commonly called chain-node topology |
+| planarGraph | Planar graph | 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.) |
+| fullPlanarGraph | Full planar graph | 2-dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called full topology in a cartographic 2D environment.) |
+| surfaceGraph | Surface graph | 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.) |
+| fullSurfaceGraph | Full surface graph | 2-dimensional topological complex that is isomorphic to a subset of a surface |
+| topology3D | Topology 3D | 3-dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.) |
+| fullTopology3D | Full topology 3D | Complete coverage of a 3D Euclidean coordinate space |
+| abstract | Abstract | Topological complex without any specified geometric realisation |
+
+### Standard codelists (mrc:MI_BandDefinition) {#iso19115-3.2018-cl-mrc-MI_BandDefinition}
+
+| code | label | description |
+|-----------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3db | 3db | TBD |
+| halfMaximum | Half Maximum | Description: width of a distribution equal to the distance between the outer two points on the distribution having power level half of that at the peak |
+| fiftyPercent | Fifty Percent | Description: wavelength difference between the upper and lower bounds at the 50% (-3db) points of the sensor spectral response |
+| oneOverE | One Over E | TBD |
+| equivalentWidth | Equivalent Width | TBD |
+
+### Standard codelists (mac:MI_ContextCode) {#iso19115-3.2018-cl-mac-MI_ContextCode}
+
+| code | label | description |
+|-------------|-------------|----------------------------------------|
+| acquisition | Acquisition | Event related to a specific collection |
+| pass | Pass | Event related to general collection |
+| wayPoint | Way Point | Event related to general collection |
+
+### Standard codelists (mac:MI_GeometryTypeCode) {#iso19115-3.2018-cl-mac-MI_GeometryTypeCode}
+
+| code | label | description |
+|--------------------|--------------------|-----------------------------------------------------------------|
+| areal | Areal | Collection of a geographic area defined by a polygon (coverage) |
+| strip linear point | Strip Linear Point | Series of linear collections grouped by way points |
+
+### Standard codelists (mac:MI_ObjectiveTypeCode) {#iso19115-3.2018-cl-mac-MI_ObjectiveTypeCode}
+
+| code | label | description |
+|-------------------------|--------------------------|----------------------------------|
+| instantaneousCollection | Instantaneous Collection | Single instance of collection |
+| persistentView | Persistent View | Multiple instances of collection |
+| survey | Survey | Comparative collection |
+
+### Standard codelists (mac:MI_OperationTypeCode) {#iso19115-3.2018-cl-mac-MI_OperationTypeCode}
+
+| code | label | description |
+|--------------------------|--------------------------|-------------|
+| real simulated synthetic | Real Simulated Synthetic | |
+
+### Standard codelists (mrc:MI_PolarisationOrientationCode) {#iso19115-3.2018-cl-mrc-MI_PolarisationOrientationCode}
+
+| code | label | description |
+|----------------------------------------------------------|------------------------------------------------------------|-------------|
+| horizontal vertical leftCircular rightCircular theta phi | Horizontal Vertical Left Circular Right Circular Theta Phi | |
+
+### Standard codelists (mac:MI_PriorityCode) {#iso19115-3.2018-cl-mac-MI_PriorityCode}
+
+| code | label | description |
+|-------------------------|--------------------------|----------------------------------------------|
+| critical | Critical | Decisive importance |
+| highImportance | High Importance | Requires resources to be made available |
+| mediumImportance | Medium Importance | Normal operation priority |
+| lowImportance theta phi | Low Importance theta phi | To be completed when resources are available |
+
+### Standard codelists (mac:MI_SequenceCode) {#iso19115-3.2018-cl-mac-MI_SequenceCode}
+
+| code | label | description |
+|---------------|---------------|-------------------------------------------|
+| start | Start | Beginning of a collection |
+| end | End | End of a collection |
+| instantaneous | Instantaneous | Collection without a significant duration |
+
+### Standard codelists (mrc:MI_TransferFunctionTypeCode) {#iso19115-3.2018-cl-mrc-MI_TransferFunctionTypeCode}
+
+| code | label | description |
+|--------------------------------|--------------------------------|-------------|
+| linear logarithmic exponential | Linear Logarithmic Exponential | |
+
+### Standard codelists (mac:MI_TriggerCode) {#iso19115-3.2018-cl-mac-MI_TriggerCode}
+
+| code | label | description |
+|---------------|---------------|-------------------------------------|
+| automatic | Automatic | Event due to external stimuli |
+| manual | Manual | Event manually instigated |
+| preProgrammed | PreProgrammed | Event instigated by planned stimuli |
+
+### Standard codelists Amendment Type (reg:RE_AmendmentType) {#iso19115-3.2018-cl-reg-RE_AmendmentType}
+
+| code | label | description |
+|-------------------------|-------------------------|-------------|
+| supersession retirement | Supersession Retirement | |
+
+### Standard codelists Decision status (reg:RE_DecisionStatus) {#iso19115-3.2018-cl-reg-RE_DecisionStatus}
+
+| code | label | description |
+|-------------------------|-------------------------|-------------|
+| pending tentative final | Pending Tentative Final | |
+
+### Standard codelists Disposition (reg:RE_Disposition) {#iso19115-3.2018-cl-reg-RE_Disposition}
+
+| code | label | description |
+|--------------------------------|---------------------------------|-------------|
+| withdrawn accepted notAccepted | Withdrawn Accepted Not Accepted | |
+
+### Standard codelists Item status (reg:RE_ItemStatus) {#iso19115-3.2018-cl-reg-RE_ItemStatus}
+
+| code | label | description |
+|-----------------------------------|------------------------------------|-------------|
+| notValid valid superseded retired | Not Valid Valid Superseded Retired | |
+
+### Standard codelists Parameter direction (srv:SV_ParameterDirection) {#iso19115-3.2018-cl-srv-SV_ParameterDirection}
+
+| code | label | description |
+|--------|--------------|-----------------------------------------------------------------------------|
+| in | Input | The parameter is an input parameter to the service instance |
+| out | Output | The parameter is an output parameter to the service instance |
+| in/out | Input/output | The parameter is both an input and output parameter to the service instance |
+
+### Standard codelists (mrs:MD_ReferenceSystemTypeCode) {#iso19115-3.2018-cl-mrs-MD_ReferenceSystemTypeCode}
+
+| code | label | description |
+|----------------------------------------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| compoundEngineeringParametric | Compound Engineering Parametric | Compound spatio-parametric coordinate reference system containing an engineering coordinate reference system and a parametric reference system EXAMPLE: [local] x, y, pressure |
+| compoundEngineeringParametricTemporal | Compound Engineering Parametric Temporal | Compound spatio-parametric-temporal coordinate reference system containing an engineering, a parametric, and a temporal coordinate reference system EXAMPLE: [local] x, y, pressure, time |
+| compoundEngineeringTemporal | Compound Engineering Temporal | Compound spatio-temporal coordinate reference system containing an engineering and a temporal coordinate reference system EXAMPLE: [local] x, y, time |
+| compoundEngineeringVertical | Compound Engineering Vertical | Compound spatial reference system containing a horizontal engineering coordinate reference system and a vertical coordinate reference system EXAMPLE: [local] x, y, height |
+| compoundEngineeringVerticalTemporal | Compound Engineering Vertical Temporal | Compound spatio-temporal coordinate reference system containing an engineering, a vertical, and a temporal coordinate reference system EXAMPLE: [local] x, y, height, time |
+| compoundGeographic2DParametric | Compound Geographic 2D Parametric | Compound spatio-parametric coordinate reference system containing a 2 dimensional geographic horizontal coordinate reference system and a parametric reference system EXAMPLE: latitude, longitude, pressure |
+| compoundGeographic2DParametricTemporal | Compound Geographic 2D Parametric Temporal | Compound spatio-parametric-temporal coordinate reference system containing a 2 dimensional geographic horizontal, a parametric and a temporal coordinate reference system EXAMPLE: latitude, longitude, pressure, time |
+| compoundGeographic2DTemporal | Compound Geographic 2D Temporal | Compound spatio-temporal coordinate reference system containing a 2 dimensional geographic horizontal coordinate reference system and a temporal reference system EXAMPLE: latitude, longitude, time |
+| compoundGeographic2DVertical | Compound Geographic 2D Vertical | Compound coordinate reference system in which one constituent coordinate reference system is a horizontal geodetic coordinate reference system and one is a vertical coordinate reference system EXAMPLE: latitude, longitude, [gravity-related] height or depth |
+| compoundGeographic2DVerticalTemporal | Compound Geographic 2D Vertical Temporal | Compound spatio-temporal coordinate reference system containing a 2 dimensional geographic horizontal, a vertical, and a temporal coordinate reference system EXAMPLE: latitude, longitude, height, time |
+| compoundGeographic3DTemporal | Compound Geographic 3D Temporal | Compound spatio-temporal coordinate reference system containing a 3 dimensional geographic and a temporal coordinate reference system EXAMPLE latitude, longitude, ellipsoidal height, time |
+| compoundProjected2DParametric | Compound Projected 2D Parametric | Compound spatio-parametric coordinate reference system containing a projected horizontal coordinate reference system and a parametric reference system EXAMPLE: easting, northing, density |
+| compoundProjected2DParametricTemporal | Compound Projected 2D Parametric Temporal | Compound spatio-parametric-temporal coordinate reference system containing a projected horizontal, a parametric, and a temporal coordinate reference system EXAMPLE: easting, northing, density, time |
+| compoundProjectedTemporal | Compound Projected Temporal | Compound spatio-temporal coordinate reference system containing a projected horizontal and a temporal coordinate reference system EXAMPLE: easting, northing, time |
+| compoundProjectedVertical | Compound Projected Vertical | Compound spatial reference system containing a horizontal projected coordinate reference system and a vertical coordinate reference system EXAMPLE easting, northing, [gravity-related] height or depth |
+| compoundProjectedVerticalTemporal | Compound Projected Vertical Temporal | Compound spatio-temporal coordinate reference system containing a projected horizontal, a vertical, and a temporal coordinate reference system EXAMPLE: easting, northing, height, time |
+| engineering | Engineering | Coordinate reference system based on an engineering datum (datum describing the relationship of a coordinate system to a local reference) EXAMPLE: [local] x,y |
+| engineeringDesign | Engineering Design | Engineering coordinate reference system in which the base representation of a moving object is specified EXAMPLE: [local] x,y |
+| engineeringImage | Engineering Image | Coordinate reference system based on an image datum (engineering datum which defines the relationship of a coordinate system to an image) EXAMPLE: row, column |
+| geodeticGeocentric | Geodetic Geocentric | Geodetic CRS having a Cartesian 3D coordinate system EXAMPLE: [geocentric] X,Y,Z |
+| geodeticGeographic2D | Geodetic Geographic 2D | Geodetic CRS having an ellipsoidal 2D coordinate system EXAMPLE: latitude, longitude |
+| geodeticGeographic3D | Geodetic Geographic 3D | Geodetic CRS having an ellipsoidal 3D coordinate system EXAMPLE: latitude, longitude, ellipsoidal height |
+| geographicIdentifier | Geographic Identifier | Spatial reference in the form of a label or code that identifies a location EXAMPLE: post code |
+| linear | Linear | Reference system that identifies a location by reference to a segment of a linear geographic feature and distance along that segment from a given point EXAMPLE: x km along road |
+| parametric | Parametric | Coordinate reference system based on a parametric datum (datum describing the relationship of a parametric coordinate system to an object) EXAMPLE: pressure |
+| projected | Projected | Coordinate reference system derived from a two-dimensional geodetic coordinate reference system by applying a map projection EXAMPLE: easting, northing |
+| temporal | Temporal | Reference system against which time is measured EXAMPLE: time |
+| vertical | Vertical | One-dimensional coordinate reference system based on a vertical datum (datum describing the relation of gravity-related heights or depths to the Earth) EXAMPLE: [gravity-related] height or depth |
+
+### Standard codelists (msr:MD_CellGeometryCode) {#iso19115-3.2018-cl-msr-MD_CellGeometryCode}
+
+| code | label | description |
+|---------|---------|--------------------------------------------------------------------------------------------|
+| point | Point | Each cell represents a point |
+| area | Area | Each cell represents an area |
+| voxel | Voxel | Each cell represents a volumetric measurement on a regular grid in three dimensional space |
+| stratum | Stratum | Height range for a single point vertical profile |
+
+### Standard codelists Character set code (lan:MD_CharacterSetCode) {#iso19115-3.2018-cl-lan-MD_CharacterSetCode}
+
+| code | label | description |
+|------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| ucs2 | UCS2 | 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| ucs4 | UCS4 | 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| utf7 | UTF7 | 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf8 | UTF8 | 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf16 | UTF16 | 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| 8859part1 | 8859 Part 1 | ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 |
+| 8859part2 | 8859 Part 2 | ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 |
+| 8859part3 | 8859 Part 3 | ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 |
+| 8859part4 | 8859 Part 4 | ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 |
+| 8859part5 | 8859 Part 5 | ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet |
+| 8859part6 | 8859 Part 6 | ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet |
+| 8859part7 | 8859 Part 7 | ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet |
+| 8859part8 | 8859 Part 8 | ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet |
+| 8859part9 | 8859 Part 9 | ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 |
+| 8859part10 | 8859 Part 10 | ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 |
+| 8859part11 | 8859 Part 11 | ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet |
+| 8859part13 | 8859 Part 13 | ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 |
+| 8859part14 | 8859 Part 14 | ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) |
+| 8859part15 | 8859 Part 15 | ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 |
+| 8859part16 | 8859 Part 16 | ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 |
+| jis | JIS | Japanese code set used for electronic transmission |
+| shiftJIS | Shift JIS | Japanese code set used on MS-DOS machines |
+| eucJP | EUC JP | Japanese code set used on UNIX based machines |
+| usAscii | US ASCII | United States ASCII code set (ISO 646 US) |
+| ebcdic | EBCDIC | IBM mainframe code set |
+| eucKR | EUC KR | Korean code set |
+| big5 | Big 5 | Traditional Chinese code set used in Taiwan, Hong Kong of China and other areas |
+| GB2312 | GB2312 | Simplified Chinese code set |
+
+### Standard codelists (mrd:MD_MediumNameCode) {#iso19115-3.2018-cl-mrd-MD_MediumNameCode}
+
+| code | label | description |
+|---------------------------|-------------------------------|----------------------------------------------------|
+| cdRom | CDROM | Read-only optical disk |
+| dvd | DVD | Digital versatile disk |
+| dvdRom | DVDROM | Digital versatile disk, read only |
+| 3halfInchFloppy | 3 Half Inch Floppy | 3,5 inch magnetic disk |
+| 5quarterInchFloppy | 5 Quarter Inch Floppy | 5,25 inch magnetic disk |
+| 7trackTape | 7 Track tape | 7 track magnetic tape |
+| 9trackTape | 9 track tape | 9 track magnetic tape |
+| 3480Cartridge | 3480 Cartridge | 3480 cartridge tape drive |
+| 3490Cartridge | 3490 Cartridge | 3490 cartridge tape drive |
+| 3580Cartridge | 3580 Cartridge | 3580 cartridge tape drive |
+| 4mmCartridgeTape | 4 mm Cartridge tape | 4 millimetre magnetic tape |
+| 8mmCartridgeTape | 8 mm Cartridge tape | 8 millimetre magnetic tape |
+| 1quarterInchCartridgeTape | 1 Quarter inch cartridge tape | 0,25 inch magnetic tape |
+| digitalLinearTap | Digital linear tape | Half inch cartridge streaming tape drive |
+| onLine | Online | Direct computer linkage |
+| satellite | Satellite | Linkage through a satellite communication system |
+| telephoneLink | Telephone link | Communication through a telephone network |
+| hardcopy | Hardcopy | Pamphlet or leaflet giving descriptive information |
+
+### Standard codelists Distributed Computing Platforms list (srv:DCPList) {#iso19115-3.2018-cl-srv-DCPList}
+
++-------------+-------------+--------------------+
+| code | label | description |
++=============+=============+====================+
+| XML | XML | DCP is XML |
++-------------+-------------+--------------------+
+| CORBA | CORBA | DCP is CORBA |
++-------------+-------------+--------------------+
+| JAVA | JAVA | DCP is JAVA |
++-------------+-------------+--------------------+
+| COM | COM | DCP is COM |
++-------------+-------------+--------------------+
+| SQL | DCP is SQL | > SQL |
++-------------+-------------+--------------------+
+| SOAP | SOAP | DCP is SOAP |
++-------------+-------------+--------------------+
+| Z3950 | Z3950 | DCP is Z3950 |
++-------------+-------------+--------------------+
+| HTTP | HTTP | DCP is HTTP |
++-------------+-------------+--------------------+
+| FTP | FTP | DCP is FTP |
++-------------+-------------+--------------------+
+| WebServices | WebServices | DCP is WebServices |
++-------------+-------------+--------------------+
+
+### Standard codelists (srv:SV_CouplingType) {#iso19115-3.2018-cl-srv-SV_CouplingType}
+
+| code | label | description |
+|-------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| loose | Loose | service instance is loosely coupled with a data instance, i.e. no MD_DataIdentification class has to be described |
+| mixed | Mixed | Service instance is mixed coupled with a data instance, i.e. MD_DataIdentification describes the associated data instance and additionally the service instance might work with other external data instances |
+| tight | Tight | Service instance is tightly coupled with a data instance, i.e. MD_DataIdentification class MUST be described |
+
+### Standard codelists Indeterminate position (indeterminatePosition) {#iso19115-3.2018-cl-indeterminatePosition}
+
+| code | label |
+|---------|---------|
+| after | After |
+| before | Before |
+| now | Now |
+| unknown | Unknown |
diff --git a/docs/manual/docs/annexes/standards/iso19139.md b/docs/manual/docs/annexes/standards/iso19139.md
new file mode 100644
index 00000000000..ceb1ef656c9
--- /dev/null
+++ b/docs/manual/docs/annexes/standards/iso19139.md
@@ -0,0 +1,17594 @@
+# Geographic information -- Metadata (iso19139:2007) (iso19139) {#iso19139}
+
+ISO 19115 defines the schema required for describing geographic information and services by means of metadata. It provides information about the identification, the extent, the quality, the spatial and temporal aspects, the content, the spatial reference, the portrayal, distribution, and other properties of digital geographic data and services.
+
+ISO 19115 is applicable to:
+
+- the cataloguing of all types of resources, clearinghouse activities, and the full description of datasets and services;
+- geographic services, geographic datasets, dataset series, and individual geographic features and feature properties.
+
+ISO 19115 defines:
+
+- mandatory and conditional metadata sections, metadata entities, and metadata elements;
+- the minimum set of metadata required to serve most metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data and services);
+- optional metadata elements to allow for a more extensive standard description of resources, if required;
+- a method for extending metadata to fit specialized needs.
+
+Though ISO 19115 is applicable to digital data and services, its principles can be extended to many other types of resources such as maps, charts, and textual documents as well as non-geographic data. Certain conditional metadata elements might not apply to these other forms of data.
+
+More details:
+
+## Metadata editor
+
+This standard can be encoded using 4 view(s).
+
+- [View: INSPIRE (inspire)](iso19139.md#iso19139-view-inspire)
+- [View: Simple (default)](iso19139.md#iso19139-view-default)
+- [View: Full (advanced)](iso19139.md#iso19139-view-advanced)
+- [View: XML (xml)](iso19139.md#iso19139-view-xml)
+
+### View: INSPIRE (inspire) {#iso19139-view-inspire}
+
+This view is composed of2tab(s).
+
+- [Tab: INSPIRE (inspire)](iso19139.md#iso19139-tab-inspire)
+- [Tab: SDS (inspire_sds)](iso19139.md#iso19139-tab-inspire_sds)
+
+This view also allows to add the following element even if not in the current record:
+
+- Contains Operations (srv:containsOperations)
+- Operation (srv:SV_OperationMetadata)
+- Parameters (srv:parameters)
+
+#### Tab: INSPIRE (inspire) {#iso19139-tab-inspire}
+
+
+
+This tab display elements from the XML metadata record.
+
+##### Section: Identification
+
+##### File identifier
+
+```{=html}
+Unique identifier for this metadata file
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:fileIdentifier
+
+See [File identifier](iso19139.md#iso19139-elem-gmd-fileIdentifier-353be7794d17e5435ce2fe57d91966ba)
+
+##### Title
+
+```{=html}
+Name by which the cited resource is known
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/*/gmd:citation/gmd:CI_Citation/gmd:title
+
+See [Title](iso19139.md#iso19139-elem-gmd-title-cc3002a2d81bcdbc5bf4c8735faf6980)
+
+##### Abstract
+
+```{=html}
+Brief narrative summary of the content of the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:abstract
+
+See [Abstract](iso19139.md#iso19139-elem-gmd-abstract-cacfcd3bd6bbd44733f828dd2903ecd8)
+
+##### Abstract
+
+```{=html}
+Brief narrative summary of the content of the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:abstract
+
+See [Abstract](iso19139.md#iso19139-elem-gmd-abstract-cacfcd3bd6bbd44733f828dd2903ecd8)
+
+##### Hierarchy level
+
+```{=html}
+Scope to which the metadata applies (see annex H for more information about metadata hierarchy levels)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:hierarchyLevel
+
+See [Hierarchy level](iso19139.md#iso19139-elem-gmd-hierarchyLevel-2b6d53b433d8f9c0cc58606d27eecc17)
+
+Name
+
+:
+
+> Hierarchy level
+
+Name
+
+:
+
+> Hierarchy level
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) = 0
+
+``` xml
+
+
+
+```
+
+Name
+
+:
+
+> Hierarchy level
+
+Name
+
+:
+
+> Hierarchy level
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+
+
+```
+
+##### Online resource
+
+##### OnLine resource
+
+```{=html}
+Information about online sources from which the resource can be obtained
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:transferOptions /gmd:MD_DigitalTransferOptions/gmd:onLine
+
+See [OnLine resource](iso19139.md#iso19139-elem-gmd-onLine-c0b191c96e7e4d7dfc2a4ba2fd8946f4)
+
+Name
+
+:
+
+> Online resource
+
+Name
+
+:
+
+> Online resource
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Resource identifier
+
+##### Citation identifier
+
+```{=html}
+Identifier of the citation
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/gmd:identifier
+
+See [Identifier](iso19139.md#iso19139-elem-gmd-identifier-c4f31fd808ee0eaa1e5525c5ff0edd23)
+
+Name
+
+:
+
+> Resource identifier
+
+Name
+
+:
+
+> Resource identifier
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+```
+
+Type
+
+:
+
+> process
+
+Displayed only if
+
+:
+
+> (count(gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification) + count(gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:citation/gmd:CI_Citation/ gmd:identifier[ends-with(gmd:MD_Identifier/gmd:code/gco:CharacterString, //gmd:MD_Metadata/gmd:fileIdentifier/gco:CharacterString)])) = 1
+
+##### Language
+
+```{=html}
+Language(s) used within the dataset
+```
+```{=html}
+language(s) used within the dataset
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:language
+
+See [Metadata language](iso19139.md#iso19139-elem-gmd-language-98a1fec5ea30c100ef63f1ca4bd6dbdb)
+
+##### Spatial representation type
+
+```{=html}
+Method used to spatially represent geographic information
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:spatialRepresentationType
+
+See [Spatial representation type](iso19139.md#iso19139-elem-gmd-spatialRepresentationType-1617a07231ac2246d0844778962d4ca0)
+
+Name
+
+:
+
+> Spatial representation type
+
+Name
+
+:
+
+> Spatial representation type
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+```
+
+##### Encoding
+
+##### Distribution format
+
+```{=html}
+Provides a description of the format of the data to be distributed
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution/gmd:distributionFormat
+
+See [Distribution format](iso19139.md#iso19139-elem-gmd-distributionFormat-5cad81c9a7af3991db918a5e8fc0c596)
+
+Name
+
+:
+
+> Encoding
+
+Name
+
+:
+
+> Encoding
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Projection
+
+##### Reference system identifier
+
+```{=html}
+Name of reference system
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier
+
+See [Reference system identifier](iso19139.md#iso19139-elem-gmd-referenceSystemIdentifier-5393a29789a4b6def1795d5a9e70f665)
+
+Name
+
+:
+
+> Projection
+
+Name
+
+:
+
+> Ref. system
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/4936
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/4937
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/4258
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3035
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3034
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3038
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3039
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3040
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3041
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3042
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3043
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3044
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3045
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3046
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3047
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3048
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3049
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3050
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/3051
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/5730
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.opengis.net/def/crs/EPSG/0/7409
+
+
+
+
+
+```
+
+##### Section: Classification of data and services
+
+##### Topic category
+
+```{=html}
+Main theme(s) of the dataset
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:topicCategory
+
+See [Topic category](iso19139.md#iso19139-elem-gmd-topicCategory-beb19f9aa38425d24bc8c438657fff74)
+
+Name
+
+:
+
+> Topic category code
+
+Name
+
+:
+
+> Topic category code
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+```
+
+##### Section: Classification of data and services
+
+##### Service Type
+
+```{=html}
+Service type name from a registry of services. For example, the values of the nameSpace and name attributes of GeneralName may be 'OGC' and 'catalogue'
+```
+Recommended values
+
+| code | label |
+|-------------------|-------------------------------------------------|
+| OGC:WMS | OGC Web Map Service (OGC:WMS) |
+| OGC:WFS | OGC Web Feature Service (OGC:WFS) |
+| OGC:WCS | OGC Web Coverage Service (OGC:WCS) |
+| W3C:HTML:DOWNLOAD | Download (W3C:HTML:DOWNLOAD) |
+| W3C:HTML:LINK | Information (W3C:HTML:LINK) |
+| discovery | INSPIRE Discovery Service (discovery) |
+| view | INSPIRE View Service (view) |
+| download | INSPIRE Download Service (download) |
+| transformation | INSPIRE Transformation Service (transformation) |
+| other | INSPIRE Other Services (other) |
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:serviceType
+
+See [Service Type](iso19139.md#iso19139-elem-srv-serviceType-31230933e2a7436c80955195b74bc0a0)
+
+##### Coupling Type
+
+```{=html}
+Type of Coupling
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:couplingType
+
+See [Coupling Type](iso19139.md#iso19139-elem-srv-couplingType-bc1606dff717a83807e97a1a3789e30a)
+
+##### Section: Coupled resource
+
+##### Coupled resource
+
+##### Operates On
+
+```{=html}
+Provides information on the datasets that the service operates on
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:operatesOn
+
+See [Operates On](iso19139.md#iso19139-elem-srv-operatesOn-fc0165e60dcb452c05c9f1d95416b89a)
+
+Name
+
+:
+
+> Coupled resource
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+```
+
+##### Section: Coupled resource
+
+##### Coupled resource
+
+##### Operates On
+
+```{=html}
+Provides information on the datasets that the service operates on
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:operatesOn
+
+See [Operates On](iso19139.md#iso19139-elem-srv-operatesOn-fc0165e60dcb452c05c9f1d95416b89a)
+
+Name
+
+:
+
+> Coupled resource
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+```
+
+##### Section: Classification of data and services
+
+##### Service Type
+
+```{=html}
+Service type name from a registry of services. For example, the values of the nameSpace and name attributes of GeneralName may be 'OGC' and 'catalogue'
+```
+Recommended values
+
+| code | label |
+|-------------------|-------------------------------------------------|
+| OGC:WMS | OGC Web Map Service (OGC:WMS) |
+| OGC:WFS | OGC Web Feature Service (OGC:WFS) |
+| OGC:WCS | OGC Web Coverage Service (OGC:WCS) |
+| W3C:HTML:DOWNLOAD | Download (W3C:HTML:DOWNLOAD) |
+| W3C:HTML:LINK | Information (W3C:HTML:LINK) |
+| discovery | INSPIRE Discovery Service (discovery) |
+| view | INSPIRE View Service (view) |
+| download | INSPIRE Download Service (download) |
+| transformation | INSPIRE Transformation Service (transformation) |
+| other | INSPIRE Other Services (other) |
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:serviceType
+
+See [Service Type](iso19139.md#iso19139-elem-srv-serviceType-31230933e2a7436c80955195b74bc0a0)
+
+##### Coupling Type
+
+```{=html}
+Type of Coupling
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:couplingType
+
+See [Coupling Type](iso19139.md#iso19139-elem-srv-couplingType-bc1606dff717a83807e97a1a3789e30a)
+
+##### Section: Coupled resource
+
+##### Coupled resource
+
+##### Operates On
+
+```{=html}
+Provides information on the datasets that the service operates on
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:operatesOn
+
+See [Operates On](iso19139.md#iso19139-elem-srv-operatesOn-fc0165e60dcb452c05c9f1d95416b89a)
+
+Name
+
+:
+
+> Coupled resource
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+```
+
+##### Section: Coupled resource
+
+##### Coupled resource
+
+##### Operates On
+
+```{=html}
+Provides information on the datasets that the service operates on
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:operatesOn
+
+See [Operates On](iso19139.md#iso19139-elem-srv-operatesOn-fc0165e60dcb452c05c9f1d95416b89a)
+
+Name
+
+:
+
+> Coupled resource
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+```
+
+##### Section: Keywords
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ gmd:descriptiveKeywords [gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/gco:CharacterString = 'INSPIRE Service taxonomy']
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+Name
+
+:
+
+> INSPIRE Service Taxonomy
+
+Name
+
+:
+
+> INSPIRE Service Taxonomy
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> (count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ gmd:descriptiveKeywords[ contains(gmd:MD_Keywords/gmd:thesaurusName/ gmd:CI_Citation/gmd:title/gco:CharacterString, 'INSPIRE Service taxonomy')]) + count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification)) = 1
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+ INSPIRE Service taxonomy
+
+
+
+
+ 2010-04-22
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.inspire-service-taxonomy
+
+
+
+
+
+
+
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/*/ gmd:descriptiveKeywords [contains(gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/*[name() = 'gco:CharacterString' or name() = 'gmx:Anchor']/text(), 'INSPIRE themes')]
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+Name
+
+:
+
+> INSPIRE themes
+
+Name
+
+:
+
+> INSPIRE themes
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/*/ gmd:descriptiveKeywords[ contains(gmd:MD_Keywords/gmd:thesaurusName/ gmd:CI_Citation/gmd:title/*[name() = 'gco:CharacterString' or name() = 'gmx:Anchor']/text(), 'INSPIRE themes')]) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.httpinspireeceuropaeutheme-theme
+
+
+
+
+
+
+
+
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/*/ gmd:descriptiveKeywords [count(gmd:MD_Keywords/gmd:thesaurusName) > 0 and not(contains(gmd:MD_Keywords/gmd:thesaurusName/gmd:CI_Citation/gmd:title/*[name() = 'gco:CharacterString' or name() = 'gmx:Anchor']/text(), 'INSPIRE themes'))]
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+##### Section: Other keywords
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ gmd:descriptiveKeywords[not(gmd:MD_Keywords/gmd:thesaurusName)]
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:descriptiveKeywords[not(gmd:MD_Keywords/gmd:thesaurusName)]
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+##### Section: Other keywords
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ gmd:descriptiveKeywords[not(gmd:MD_Keywords/gmd:thesaurusName)]
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:descriptiveKeywords[not(gmd:MD_Keywords/gmd:thesaurusName)]
+
+See [Descriptive keywords](iso19139.md#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3)
+
+##### Section: Geographic coverage
+
+##### Geographic bounding box
+
+```{=html}
+Geographic position of the dataset
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ srv:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox
+
+See [Geographic bounding box](iso19139.md#iso19139-elem-gmd-EX_GeographicBoundingBox-317fd5425b55f40c235ada8a89ee0519)
+
+##### Geographic bounding box
+
+```{=html}
+Geographic position of the dataset
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:extent/gmd:EX_Extent/gmd:geographicElement/gmd:EX_GeographicBoundingBox
+
+See [Geographic bounding box](iso19139.md#iso19139-elem-gmd-EX_GeographicBoundingBox-317fd5425b55f40c235ada8a89ee0519)
+
+Name
+
+:
+
+> Geographic bounding box
+
+Name
+
+:
+
+> Geographic bounding box
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+Name
+
+:
+
+> Geographic bounding box
+
+Name
+
+:
+
+> Geographic bounding box
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Temporal reference
+
+##### Temporal extent
+
+##### Temporal element
+
+```{=html}
+Provides temporal component of the extent of the referring object
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement
+
+See [Temporal element](iso19139.md#iso19139-elem-gmd-temporalElement-98c13f1732cd7f7c06320d907eec27ce)
+
+Name
+
+:
+
+> Geographic bounding box
+
+Name
+
+:
+
+> Temporal extent
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Temporal extent
+
+##### Temporal element
+
+```{=html}
+Provides temporal component of the extent of the referring object
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:extent/gmd:EX_Extent/gmd:temporalElement
+
+See [Temporal element](iso19139.md#iso19139-elem-gmd-temporalElement-98c13f1732cd7f7c06320d907eec27ce)
+
+Name
+
+:
+
+> Geographic bounding box
+
+Name
+
+:
+
+> Temporal extent
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:extent/gmd:EX_Extent/gmd:temporalElement) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/*/gmd:citation/gmd:CI_Citation/ gmd:date
+
+See [Date](iso19139.md#iso19139-elem-gmd-date-ebb509445b6cf496cbf813a8b01a2362)
+
+Name
+
+:
+
+> Temporal information
+
+Name
+
+:
+
+> Temporal information
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Quality and validity
+
+##### Lineage
+
+##### Statement
+
+```{=html}
+General explanation of the data producer_s knowledge about the lineage of a dataset
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:lineage/gmd:LI_Lineage/gmd:statement
+
+See [Statement](iso19139.md#iso19139-elem-gmd-statement-593ac58687a7831e3112879ec00a306e)
+
+Name
+
+:
+
+> Lineage
+
+Name
+
+:
+
+> Lineage
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+```
+
+Name
+
+:
+
+> Lineage
+
+Name
+
+:
+
+> Lineage
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+```
+
+##### Denominator
+
+```{=html}
+The number below the line in a vulgar fraction
+```
+Recommended values
+
+| code | label |
+|---------|-------------|
+| 5000 | 1:5´000 |
+| 10000 | 1:10´000 |
+| 25000 | 1:25´000 |
+| 50000 | 1:50´000 |
+| 100000 | 1:100´000 |
+| 200000 | 1:200´000 |
+| 300000 | 1:300´000 |
+| 500000 | 1:500´000 |
+| 1000000 | 1:1´000´000 |
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/ */gmd:spatialResolution/ */gmd:equivalentScale/*/gmd:denominator
+
+See [Denominator](iso19139.md#iso19139-elem-gmd-denominator-e807028ba183b3decd6aa631d0ca1ca3)
+
+Name
+
+:
+
+> Spatial resolution (scale)
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Distance
+
+```{=html}
+Ground sample distance
+```
+Recommended values
+
+| code | label |
+|------|-------|
+| 0.10 | 10 cm |
+| 0.25 | 25 cm |
+| 0.50 | 50 cm |
+| 1 | 1 m |
+| 30 | 30 m |
+| 100 | 100 m |
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/ */gmd:spatialResolution/*/gmd:distance
+
+See [Distance](iso19139.md#iso19139-elem-gmd-distance-7b7fc9e19c5ebb9644dc51880d95a12d)
+
+Name
+
+:
+
+> Spatial resolution (distance)
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+```
+
+##### Section: Conformity
+
+##### Conformity
+
+##### Result
+
+```{=html}
+Value (or set of values) obtained from applying a data quality measure or the out come of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/ gmd:report/gmd:DQ_DomainConsistency/gmd:result[count(gmd:DQ_ConformanceResult/gmd:specification/ gmd:CI_Citation/gmd:title/gmx:Anchor) > 0]
+
+See [Result](iso19139.md#iso19139-elem-gmd-result-83539788e54d2fc7d166ac779dc43f0b)
+
+##### Conformity
+
+##### Result
+
+```{=html}
+Value (or set of values) obtained from applying a data quality measure or the out come of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/ gmd:report/gmd:DQ_DomainConsistency/gmd:result[count(gmd:DQ_ConformanceResult/gmd:specification/ gmd:CI_Citation/gmd:title/gco:CharacterString) > 0]
+
+See [Result](iso19139.md#iso19139-elem-gmd-result-83539788e54d2fc7d166ac779dc43f0b)
+
+Name
+
+:
+
+> Conformity
+
+Name
+
+:
+
+> Conformity
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ true
+
+
+
+
+
+```
+
+##### Section: Conformity
+
+##### Conformity
+
+##### Result
+
+```{=html}
+Value (or set of values) obtained from applying a data quality measure or the out come of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/ gmd:report/gmd:DQ_DomainConsistency/gmd:result[count(gmd:DQ_ConformanceResult/gmd:specification/ gmd:CI_Citation/gmd:title/gmx:Anchor) > 0]
+
+See [Result](iso19139.md#iso19139-elem-gmd-result-83539788e54d2fc7d166ac779dc43f0b)
+
+##### Conformity
+
+##### Result
+
+```{=html}
+Value (or set of values) obtained from applying a data quality measure or the out come of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/ gmd:report/gmd:DQ_DomainConsistency/gmd:result[count(gmd:DQ_ConformanceResult/gmd:specification/ gmd:CI_Citation/gmd:title/gco:CharacterString) > 0]
+
+See [Result](iso19139.md#iso19139-elem-gmd-result-83539788e54d2fc7d166ac779dc43f0b)
+
+Name
+
+:
+
+> Conformity
+
+Name
+
+:
+
+> Conformity
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ true
+
+
+
+
+
+```
+
+##### Section: Restrictions on access and use
+
+##### Use limitation
+
+```{=html}
+Limitation affecting the fitness for use of the resource. Example, _not to be used for navigation_
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:resourceConstraints/gmd:MD_Constraints/gmd:useLimitation
+
+See [Use limitation](iso19139.md#iso19139-elem-gmd-useLimitation-07252e81be8d86aea4553aa3df807d8b)
+
+Name
+
+:
+
+> Use limitation
+
+Name
+
+:
+
+> Use limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification) > 0
+
+``` xml
+
+
+
+
+
+
+
+```
+
+##### Access constraints
+
+##### Other constraints
+
+```{=html}
+Other restrictions and legal prerequisites for accessing and using the resource
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/ gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints
+
+See [Other constraints](iso19139.md#iso19139-elem-gmd-otherConstraints-696de5ef421a230cf560f7566a3c5028)
+
+Name
+
+:
+
+> Access constraints
+
+Name
+
+:
+
+> Access constraints
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification) > 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Restrictions on access and use
+
+##### Use limitation
+
+```{=html}
+Limitation affecting the fitness for use of the resource. Example, _not to be used for navigation_
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ gmd:resourceConstraints/gmd:MD_Constraints/gmd:useLimitation
+
+See [Use limitation](iso19139.md#iso19139-elem-gmd-useLimitation-07252e81be8d86aea4553aa3df807d8b)
+
+Name
+
+:
+
+> Use limitation
+
+Name
+
+:
+
+> Use limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+
+
+
+
+
+
+```
+
+##### Access constraints
+
+##### Other constraints
+
+```{=html}
+Other restrictions and legal prerequisites for accessing and using the resource
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/ gmd:resourceConstraints/gmd:MD_LegalConstraints/gmd:otherConstraints
+
+See [Other constraints](iso19139.md#iso19139-elem-gmd-otherConstraints-696de5ef421a230cf560f7566a3c5028)
+
+Name
+
+:
+
+> Other constraints
+
+Name
+
+:
+
+> Access constraints
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Responsible organization (s)
+
+##### Contact for the resource
+
+##### Point of contact
+
+```{=html}
+Identification of, and means of communication with, person(s) and organizations(s) associated with the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/*/gmd:pointOfContact
+
+See [Point of contact](iso19139.md#iso19139-elem-gmd-pointOfContact-2a38035f4c8b63a35a4e6c44e6f4b624)
+
+Name
+
+:
+
+> Contact for the resource
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Responsible organization (s)
+
+##### Contact for the resource
+
+##### Point of contact
+
+```{=html}
+Identification of, and means of communication with, person(s) and organizations(s) associated with the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/*/gmd:pointOfContact
+
+See [Point of contact](iso19139.md#iso19139-elem-gmd-pointOfContact-2a38035f4c8b63a35a4e6c44e6f4b624)
+
+Name
+
+:
+
+> Contact for the resource
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Metadata information
+
+##### Contact for the metadata
+
+##### Contact
+
+```{=html}
+Party responsible for the metadata information
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:contact
+
+See [Metadata author](iso19139.md#iso19139-elem-gmd-contact-1a17bee429a4ae3c87f4026bd2da8005)
+
+Name
+
+:
+
+> Contact for the metadata
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Date stamp
+
+```{=html}
+Date that the metadata was created (YYYY-MM-DDThh:mm:ss)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dateStamp
+
+See [Date stamp](iso19139.md#iso19139-elem-gmd-dateStamp-ee89eb65741d89aef14d153887f60948)
+
+##### Metadata language
+
+```{=html}
+Language used for documenting metadata
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:language
+
+See [Metadata language](iso19139.md#iso19139-elem-gmd-language-98a1fec5ea30c100ef63f1ca4bd6dbdb)
+
+Name
+
+:
+
+> Metadata language
+
+Name
+
+:
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+```
+
+##### Character set
+
+```{=html}
+Full name of the character coding standard used for the dataset
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:characterSet
+
+See [Character set](iso19139.md#iso19139-elem-gmd-characterSet-351330c9787387f916fed1143727215b)
+
+#### Tab: SDS (inspire_sds) {#iso19139-tab-inspire_sds}
+
+This tab display elements from the XML metadata record.
+
+##### Section: Conformance class 1: invocable
+
+Type
+
+:
+
+> process
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service'])=0
+
+Type
+
+:
+
+> process
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:DQ_ConformanceResult/gmd:specification/gmd:CI_Citation/gmd:title/gco:CharacterString)>0
+
+##### Category
+
+##### Data quality
+
+```{=html}
+Quality information for the data specified by a data quality scope
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:DQ_ConformanceResult/gmd:specification/gmd:CI_Citation/gmd:title
+
+See [Data quality](iso19139.md#iso19139-elem-gmd-DQ_DataQuality-16d17a37284f157b42d492a5960b5171)
+
+##### Data quality
+
+```{=html}
+Quality information for the data specified by a data quality scope
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_DomainConsistency/gmd:result/gmd:DQ_ConformanceResult/gmd:pass
+
+See [Data quality](iso19139.md#iso19139-elem-gmd-DQ_DataQuality-16d17a37284f157b42d492a5960b5171)
+
+Name
+
+:
+
+> Add pass element
+
+Type
+
+:
+
+> add
+
+``` xml
+
+ true
+
+```
+
+##### Access Point URL
+
+##### OnLine resource
+
+```{=html}
+Information about online sources from which the resource can be obtained
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution//gmd:transferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine[gmd:CI_OnlineResource/gmd:description/gmx:Anchor/text() = 'accessPoint']
+
+See [OnLine resource](iso19139.md#iso19139-elem-gmd-onLine-c0b191c96e7e4d7dfc2a4ba2fd8946f4)
+
+Name
+
+:
+
+> Add Access Point
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+ http://accesspoint.url
+
+
+
+ accessPoint
+
+
+
+
+
+
+
+```
+
+##### Endpoint URL
+
+##### OnLine resource
+
+```{=html}
+Information about online sources from which the resource can be obtained
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:distributionInfo/gmd:MD_Distribution//gmd:transferOptions/gmd:MD_DigitalTransferOptions/gmd:onLine[gmd:CI_OnlineResource/gmd:description/gmx:Anchor/text() = 'endPoint']
+
+See [OnLine resource](iso19139.md#iso19139-elem-gmd-onLine-c0b191c96e7e4d7dfc2a4ba2fd8946f4)
+
+Name
+
+:
+
+> Add Endpoint
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+ http://endpoint.url
+
+
+
+ endPoint
+
+
+
+
+
+
+
+```
+
+##### Technical specification
+
+##### Data quality
+
+```{=html}
+Quality information for the data specified by a data quality scope
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_DomainConsistency/gmd:result
+
+See [Data quality](iso19139.md#iso19139-elem-gmd-DQ_DataQuality-16d17a37284f157b42d492a5960b5171)
+
+Name
+
+:
+
+> Add a technical specification
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+
+
+
+ Description of technical specification
+
+
+
+
+
+ 2014-12-11
+
+
+
+
+
+
+
+
+
+ Conformant to the cited specifications.
+
+
+
+ true
+
+
+
+
+
+```
+
+##### Section: Conformance class 2: interoperable
+
+##### Section: Coordinate reference system
+
+##### Anchor
+
+```{=html}
+Supports hyper-linking capabilities and ensures a web-like implementation of CharacterStrings
+```
+
+XPath
+
+:
+
+> gmd:MD_Metadata/gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code/gmx:Anchor
+
+See [Anchor](iso19139.md#iso19139-elem-gmx-Anchor-d0ccf7ef89bd129a31fe766fae38f1df)
+
+Name
+
+:
+
+> Projection
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+ {{code}}
+
+
+
+
+
+
+```
+
+##### Section: Quality of Service
+
+Type
+
+:
+
+> process
+
+Displayed only if
+
+:
+
+> (count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service'])>0 and (count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_ConceptualConsistency/gmd:nameOfMeasure/gmx:Anchor[text()='availability'])=0 or count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_ConceptualConsistency/gmd:nameOfMeasure/gmx:Anchor[text()='performance'])=0 or count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_ConceptualConsistency/gmd:nameOfMeasure/gmx:Anchor[text()='capacity'])=0 ))
+
+##### Conceptual consistency
+
+```{=html}
+Adherence to rules of the conceptual schema
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:report/gmd:DQ_ConceptualConsistency
+
+See [Conceptual consistency](iso19139.md#iso19139-elem-gmd-DQ_ConceptualConsistency-d42ad4a3a30578c7431606e8c1df4df8)
+
+##### Section: Access constraints
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:accessConstraints]/gmd:otherConstraints/gmx:Anchor]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+##### Limitation
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:accessConstraints]/gmd:otherConstraints[gco:CharacterString]]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+Name
+
+:
+
+> No Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:accessConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ No Conditions Apply
+
+
+
+
+```
+
+Name
+
+:
+
+> Unknown Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:accessConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ Conditions Unknown
+
+
+
+
+```
+
+Name
+
+:
+
+> Customizable constraints
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:accessConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Use constraints
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:useConstraints]/gmd:otherConstraints/gmx:Anchor]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+##### Limitation
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:useConstraints]/gmd:otherConstraints[gco:CharacterString]]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+Name
+
+:
+
+> No Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:useConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ No Conditions Apply
+
+
+
+
+```
+
+Name
+
+:
+
+> Unknown Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:useConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ Conditions Unknown
+
+
+
+
+```
+
+Name
+
+:
+
+> Customizable constraints
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:useConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Responsible custodian
+
+##### Contact for the resource
+
+##### Point of contact
+
+```{=html}
+Identification of, and means of communication with, person(s) and organizations(s) associated with the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:pointOfContact[gmd:CI_ResponsibleParty/gmd:role/gmd:='custodian']
+
+See [Point of contact](iso19139.md#iso19139-elem-gmd-pointOfContact-2a38035f4c8b63a35a4e6c44e6f4b624)
+
+Name
+
+:
+
+> Contact for the resource
+
+Type
+
+:
+
+> add
+
+##### Section: Coordinate reference system
+
+##### Anchor
+
+```{=html}
+Supports hyper-linking capabilities and ensures a web-like implementation of CharacterStrings
+```
+
+XPath
+
+:
+
+> gmd:MD_Metadata/gmd:referenceSystemInfo/gmd:MD_ReferenceSystem/gmd:referenceSystemIdentifier/gmd:RS_Identifier/gmd:code/gmx:Anchor
+
+See [Anchor](iso19139.md#iso19139-elem-gmx-Anchor-d0ccf7ef89bd129a31fe766fae38f1df)
+
+Name
+
+:
+
+> Projection
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+
+
+ {{code}}
+
+
+
+
+
+
+```
+
+##### Section: Quality of Service
+
+Type
+
+:
+
+> process
+
+Displayed only if
+
+:
+
+> (count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service'])>0 and (count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_ConceptualConsistency/gmd:nameOfMeasure/gmx:Anchor[text()='availability'])=0 or count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_ConceptualConsistency/gmd:nameOfMeasure/gmx:Anchor[text()='performance'])=0 or count(gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality[gmd:scope/gmd:DQ_Scope/gmd:level/gmd:='service']/gmd:report/gmd:DQ_ConceptualConsistency/gmd:nameOfMeasure/gmx:Anchor[text()='capacity'])=0 ))
+
+##### Conceptual consistency
+
+```{=html}
+Adherence to rules of the conceptual schema
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataQualityInfo/gmd:DQ_DataQuality/gmd:report/gmd:DQ_ConceptualConsistency
+
+See [Conceptual consistency](iso19139.md#iso19139-elem-gmd-DQ_ConceptualConsistency-d42ad4a3a30578c7431606e8c1df4df8)
+
+##### Section: Access constraints
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:accessConstraints]/gmd:otherConstraints/gmx:Anchor]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+##### Limitation
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:accessConstraints]/gmd:otherConstraints[gco:CharacterString]]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+Name
+
+:
+
+> No Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:accessConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ No Conditions Apply
+
+
+
+
+```
+
+Name
+
+:
+
+> Unknown Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:accessConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ Conditions Unknown
+
+
+
+
+```
+
+Name
+
+:
+
+> Customizable constraints
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:accessConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Use constraints
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:useConstraints]/gmd:otherConstraints/gmx:Anchor]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+##### Limitation
+
+##### Resource constraints
+
+```{=html}
+Provides information about constraints which apply to the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints[gmd:MD_LegalConstraints[gmd:useConstraints]/gmd:otherConstraints[gco:CharacterString]]
+
+See [Resource constraints](iso19139.md#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad)
+
+Name
+
+:
+
+> No Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:useConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ No Conditions Apply
+
+
+
+
+```
+
+Name
+
+:
+
+> Unknown Limitation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:useConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+ Conditions Unknown
+
+
+
+
+```
+
+Name
+
+:
+
+> Customizable constraints
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:resourceConstraints/gmd:MD_LegalConstraints[gmd:useConstraints]) = 0
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+##### Section: Responsible custodian
+
+##### Contact for the resource
+
+##### Point of contact
+
+```{=html}
+Identification of, and means of communication with, person(s) and organizations(s) associated with the resource(s)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/gmd:pointOfContact[gmd:CI_ResponsibleParty/gmd:role/gmd:='custodian']
+
+See [Point of contact](iso19139.md#iso19139-elem-gmd-pointOfContact-2a38035f4c8b63a35a4e6c44e6f4b624)
+
+Name
+
+:
+
+> Contact for the resource
+
+Type
+
+:
+
+> add
+
+##### Section: Conformance class 3: harmonized
+
+##### Contains Operations
+
+```{=html}
+Provides information about the operations that comprise the service
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification/srv:containsOperations
+
+See [Contains Operations](iso19139.md#iso19139-elem-srv-containsOperations-5765a967aadd33b5ba92cde03c9ce30e)
+
+Name
+
+:
+
+> Add Operation
+
+Type
+
+:
+
+> add
+
+Displayed only if
+
+:
+
+> count(gmd:MD_Metadata/gmd:identificationInfo/srv:SV_ServiceIdentification) > 0
+
+``` xml
+
+
+
+
+
+
+ Web services
+
+
+
+
+
+ http://
+
+
+
+
+
+```
+
+### View: Simple (default) {#iso19139-view-default}
+
+This view is composed of1tab(s).
+
+- [Tab: Simple (default)](iso19139.md#iso19139-tab-default)
+
+This view also allows to add the following element even if not in the current record:
+
+- Descriptive keywords (gmd:descriptiveKeywords)
+- Keyword (gmd:keyword)
+- Name (gmd:name)
+- Spatial resolution (gmd:spatialResolution)
+- Point of contact (gmd:pointOfContact)
+- Distributor (gmd:distributor)
+- Distribution format (gmd:distributionFormat)
+- Contact (gmd:contact)
+- Processor (gmd:processor)
+- Topic category (gmd:topicCategory)
+- Parameters (srv:parameters)
+
+#### Tab: Simple (default) {#iso19139-tab-default}
+
+
+
+This tab display elements from the XML metadata record.
+
+Instruction
+
+:
+
+##### Linkage
+
+```{=html}
+Location (address) for on-line access using a Uniform Resource Locator address or similar addressing scheme such as http://www.statkart.no/isotc211
+```
+
+XPath
+
+:
+
+> */gmd:linkage
+
+See [Linkage](iso19139.md#iso19139-elem-gmd-linkage-ddec55285da8318007d8ba8df6febcb5)
+
+##### Name
+
+XPath
+
+:
+
+> */gmd:name
+
+See [Name](iso19139.md#iso19139-elem-gmd-name-9796db4d1cab411f64fa97871fd1dd7e)
+
+Instruction
+
+:
+
+##### Linkage
+
+```{=html}
+Location (address) for on-line access using a Uniform Resource Locator address or similar addressing scheme such as http://www.statkart.no/isotc211
+```
+
+XPath
+
+:
+
+> */gmd:linkage
+
+See [Linkage](iso19139.md#iso19139-elem-gmd-linkage-ddec55285da8318007d8ba8df6febcb5)
+
+##### Name
+
+XPath
+
+:
+
+> */gmd:name
+
+See [Name](iso19139.md#iso19139-elem-gmd-name-9796db4d1cab411f64fa97871fd1dd7e)
+
+##### Section: Content Information
+
+```{=html}
+Provides information about the feature catalogue and describes the coverage and image data characteristics
+```
+See [Content Information](iso19139.md#iso19139-elem-gmd-contentInfo-da18cd6a5e91bae67187adc15ff47622)
+
+##### Included with dataset
+
+```{=html}
+Indication of whether or not the feature catalogue is included with the dataset
+```
+
+XPath
+
+:
+
+> gmd:MD_FeatureCatalogueDescription/gmd:includedWithDataset
+
+See [Included with dataset](iso19139.md#iso19139-elem-gmd-includedWithDataset-0148507e25f25653e843ec66cf6cb878)
+
+##### Feature catalogue citation
+
+```{=html}
+Complete bibliographic reference to one or more external feature catalogues
+```
+See [Feature catalogue citation](iso19139.md#iso19139-elem-gmd-featureCatalogueCitation-0d490aca236a02c867c265dc0656143b)
+
+XPath
+
+:
+
+> .
+
+##### Feature catalogue citation
+
+```{=html}
+Complete bibliographic reference to one or more external feature catalogues
+```
+See [Feature catalogue citation](iso19139.md#iso19139-elem-gmd-featureCatalogueCitation-0d490aca236a02c867c265dc0656143b)
+
+XPath
+
+:
+
+> .
+
+Name
+
+:
+
+Type
+
+:
+
+> add
+
+``` xml
+
+
+
+ true
+
+
+
+
+```
+
+### View: Full (advanced) {#iso19139-view-advanced}
+
+This view is composed of11tab(s).
+
+- [Tab: Identification (identificationInfo)](iso19139.md#iso19139-tab-identificationInfo)
+- [Tab: Distribution (distributionInfo)](iso19139.md#iso19139-tab-distributionInfo)
+- [Tab: Quality (dataQualityInfo)](iso19139.md#iso19139-tab-dataQualityInfo)
+- [Tab: Spatial rep. (spatialRepresentationInfo)](iso19139.md#iso19139-tab-spatialRepresentationInfo)
+- [Tab: Ref. system (referenceSystemInfo)](iso19139.md#iso19139-tab-referenceSystemInfo)
+- [Tab: Content (contentInfo)](iso19139.md#iso19139-tab-contentInfo)
+- [Tab: Portrayal (portrayalCatalogueInfo)](iso19139.md#iso19139-tab-portrayalCatalogueInfo)
+- [Tab: Metadata (metadata)](iso19139.md#iso19139-tab-metadata)
+- [Tab: Md. constraints (metadataConstraints)](iso19139.md#iso19139-tab-metadataConstraints)
+- [Tab: Md. maintenance (metadataMaintenance)](iso19139.md#iso19139-tab-metadataMaintenance)
+- [Tab: Schema info (applicationSchemaInfo)](iso19139.md#iso19139-tab-applicationSchemaInfo)
+
+#### Tab: Identification (identificationInfo) {#iso19139-tab-identificationInfo}
+
+
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Identification info
+
+```{=html}
+Basic information about the resource(s) to which the metadata applies
+```
+See [Identification info](iso19139.md#iso19139-elem-gmd-identificationInfo-4fe68a205ff13feeccf0b58e08f39472)
+
+#### Tab: Distribution (distributionInfo) {#iso19139-tab-distributionInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Distribution Information
+
+```{=html}
+Provides information about the distributor of and options for obtaining the resource(s)
+```
+See [Distribution Information](iso19139.md#iso19139-elem-gmd-distributionInfo-3bddab6fda29c9ebd6f0ece68843fcff)
+
+#### Tab: Quality (dataQualityInfo) {#iso19139-tab-dataQualityInfo}
+
+
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Data quality info
+
+```{=html}
+Provides overall assessment of quality of a resource(s)
+```
+See [Data quality info](iso19139.md#iso19139-elem-gmd-dataQualityInfo-9a53c25e2dacf5a7ab0aa1d155efc3dc)
+
+#### Tab: Spatial rep. (spatialRepresentationInfo) {#iso19139-tab-spatialRepresentationInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Spatial representation info
+
+```{=html}
+Digital representation of spatial information in the dataset
+```
+See [Spatial representation info](iso19139.md#iso19139-elem-gmd-spatialRepresentationInfo-f93705d4877ccd4c41819cc79677d6f2)
+
+#### Tab: Ref. system (referenceSystemInfo) {#iso19139-tab-referenceSystemInfo}
+
+
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Reference System Information
+
+```{=html}
+Description of the spatial and temporal reference systems used in the dataset
+```
+See [Reference System Information](iso19139.md#iso19139-elem-gmd-referenceSystemInfo-c7702a2e8ac03097e306ab3a02406765)
+
+#### Tab: Content (contentInfo) {#iso19139-tab-contentInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Content Information
+
+```{=html}
+Provides information about the feature catalogue and describes the coverage and image data characteristics
+```
+See [Content Information](iso19139.md#iso19139-elem-gmd-contentInfo-da18cd6a5e91bae67187adc15ff47622)
+
+#### Tab: Portrayal (portrayalCatalogueInfo) {#iso19139-tab-portrayalCatalogueInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Portrayal catalogue info
+
+```{=html}
+Provides information about the catalogue of rules defined for the portrayal of a resource(s)
+```
+See [Portrayal catalogue info](iso19139.md#iso19139-elem-gmd-portrayalCatalogueInfo-0a09defe8c7ca8431460b5690da9a52d)
+
+#### Tab: Metadata (metadata) {#iso19139-tab-metadata}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata
+
+##### File identifier
+
+```{=html}
+Unique identifier for this metadata file
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:fileIdentifier
+
+See [File identifier](iso19139.md#iso19139-elem-gmd-fileIdentifier-353be7794d17e5435ce2fe57d91966ba)
+
+##### Metadata language
+
+```{=html}
+Language used for documenting metadata
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:language
+
+See [Metadata language](iso19139.md#iso19139-elem-gmd-language-98a1fec5ea30c100ef63f1ca4bd6dbdb)
+
+##### Other language
+
+```{=html}
+Use this section to define other metadata language (multilingual metadata).
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:locale
+
+See [Other language](iso19139.md#iso19139-elem-gmd-locale-826113f1d130f65f95c78f6b16227c4b)
+
+##### Character set
+
+```{=html}
+Full name of the character coding standard used for the metadata set
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:characterSet
+
+See [Character set](iso19139.md#iso19139-elem-gmd-characterSet-351330c9787387f916fed1143727215b)
+
+##### Parent identifier
+
+```{=html}
+File identifier of the metadata to which this metadata is a subset (child)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:parentIdentifier
+
+See [Parent identifier](iso19139.md#iso19139-elem-gmd-parentIdentifier-e660d48fcd79782e330d99a6eee272bc)
+
+##### Hierarchy level
+
+```{=html}
+Scope to which the metadata applies (see annex H for more information about metadata hierarchy levels)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:hierarchyLevel
+
+See [Hierarchy level](iso19139.md#iso19139-elem-gmd-hierarchyLevel-2b6d53b433d8f9c0cc58606d27eecc17)
+
+##### Hierarchy level name
+
+```{=html}
+Name of the hierarchy levels for which the metadata is provided
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:hierarchyLevelName
+
+See [Hierarchy level name](iso19139.md#iso19139-elem-gmd-hierarchyLevelName-1c79276b0501d07055d7480b292899f0)
+
+##### Date stamp
+
+```{=html}
+Date that the metadata was created (YYYY-MM-DDThh:mm:ss)
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dateStamp
+
+See [Date stamp](iso19139.md#iso19139-elem-gmd-dateStamp-ee89eb65741d89aef14d153887f60948)
+
+##### Metadata standard name
+
+```{=html}
+Name of the metadata standard (including profile name) used
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:metadataStandardName
+
+See [Metadata standard name](iso19139.md#iso19139-elem-gmd-metadataStandardName-1e8d324f913f2da08b656d26e73e994d)
+
+##### Metadata standard version
+
+```{=html}
+Version (profile) of the metadata standard used
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:metadataStandardVersion
+
+See [Metadata standard version](iso19139.md#iso19139-elem-gmd-metadataStandardVersion-ab0dd515a6ca9c890bc32d3615cd427f)
+
+##### Contact
+
+```{=html}
+Party responsible for the metadata information
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:contact
+
+See [Metadata author](iso19139.md#iso19139-elem-gmd-contact-1a17bee429a4ae3c87f4026bd2da8005)
+
+##### Dataset URI
+
+```{=html}
+Uniformed Resource Identifier (URI) of the dataset to which the metadata applies
+```
+```{=html}
+Uniformed Resource Identifier (URI) of the dataset to which the metadata applies. This link refers direct to the machine-readable dataset.
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:dataSetURI
+
+See [Dataset URI](iso19139.md#iso19139-elem-gmd-dataSetURI-8e14b3e6d98f92a9356ba2f3ba1ee982)
+
+##### Series
+
+```{=html}
+Information about the series, or aggregate dataset, of which the dataset is a part
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:series
+
+See [Series](iso19139.md#iso19139-elem-gmd-series-98524248b047e1a31966f4fc05c765fb)
+
+##### Describes
+
+```{=html}
+Describes
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:describes
+
+See [Describes](iso19139.md#iso19139-elem-gmd-describes-ea7ef755fceda2ec8b1bf4486f5572bf)
+
+##### PropertyType
+
+```{=html}
+PropertyType
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:propertyType
+
+See [PropertyType](iso19139.md#iso19139-elem-gmd-propertyType-12fff0b8b43529f0300c32a5e13c9f89)
+
+##### Feature type
+
+```{=html}
+Subset of feature types from cited feature catalogue occurring in data
+```
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:featureType
+
+See [Feature type](iso19139.md#iso19139-elem-gmd-featureType-1a7ddaf6d70b2bca513bbb097769f7a5)
+
+##### Feature attribute
+
+XPath
+
+:
+
+> /gmd:MD_Metadata/gmd:featureAttribute
+
+See [Feature attribute](iso19139.md#iso19139-elem-gmd-featureAttribute-ed65880b0d966b5862d0d434b26fd36b)
+
+#### Tab: Md. constraints (metadataConstraints) {#iso19139-tab-metadataConstraints}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata constraints
+
+```{=html}
+Provides restrictions on the access and use of metadata
+```
+See [Metadata constraints](iso19139.md#iso19139-elem-gmd-metadataConstraints-0547cb4265a8d2f9663d558a9ac72d43)
+
+#### Tab: Md. maintenance (metadataMaintenance) {#iso19139-tab-metadataMaintenance}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Metadata maintenance
+
+```{=html}
+Provides information about the frequency of metadata updates, and the scope of those updates
+```
+See [Metadata maintenance](iso19139.md#iso19139-elem-gmd-metadataMaintenance-2af9bf1fc8f71819e7361e5d6987358c)
+
+#### Tab: Schema info (applicationSchemaInfo) {#iso19139-tab-applicationSchemaInfo}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+##### Section: Application schema info
+
+```{=html}
+Provides information about the conceptual schema of a dataset
+```
+See [Application schema info](iso19139.md#iso19139-elem-gmd-applicationSchemaInfo-45e55618bc13cc73f4ede49af591b9cb)
+
+### View: XML (xml) {#iso19139-view-xml}
+
+This view is composed of1tab(s).
+
+- [Tab: XML (xml)](iso19139.md#iso19139-tab-xml)
+
+#### Tab: XML (xml) {#iso19139-tab-xml}
+
+This tab display elements from the XML metadata record and also provide controls to add all elements defined in the schema (XSD).
+
+## Schema technical details
+
+Standard identifier
+
+:
+
+> iso19139
+
+Version
+
+:
+
+> 1.0
+
+Schema location
+
+:
+
+>
+
+Schema namespaces
+
+:
+
+-
+-
+-
+-
+-
+
+Schema detection mode
+
+:
+
+> elements (root)
+
+Schema detection elements
+
+:
+
+- gmd:CI_ResponsibleParty
+- gmd:DQ_DomainConsistency
+- gmd:EX_Extent
+- gmd:MD_Format
+- gmd:MD_Metadata
+
+## Standard elements
+
+List of all elements available in the standard.
+
+### Name of the calendar era {#iso19139-elem-calendarEraName-f6992f57e0b42d0d298ceab6163baa24}
+
+Name
+
+:
+
+> calendarEraName
+
+Description
+
+:
+
+### Code {#iso19139-elem-code-gmd-MD_Identifier-b9e23155977b220811ee241a27dec71c}
+
+Name
+
+:
+
+> code
+
+Context
+
+:
+
+> gmd:MD_Identifier
+
+Description
+
+:
+
+```{=html}
+Alphanumeric value identifying an instance in the namespace
+```
+```{=html}
+alphanumeric value identifying an instance in the namespace
+```
+### System code {#iso19139-elem-code-34002ba7723581d2ef06d2611cab31af}
+
+Name
+
+:
+
+> code
+
+Description
+
+:
+
+```{=html}
+Code. i.e. EPSG code.
+```
+### Code {#iso19139-elem-code-gmd-MD_CodeValue-1315454a3efd07503687cfc5628f2cf1}
+
+Name
+
+:
+
+> code
+
+Context
+
+:
+
+> gmd:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Value code
+```
+```{=html}
+Value code (i.e. numeric)
+```
+### Reference Authority {#iso19139-elem-codeSpace-0e8f09aab4d7c2a27305e0cc2a489acc}
+
+Name
+
+:
+
+> codeSpace
+
+Description
+
+:
+
+```{=html}
+Authority responsible for codification. i.e. EPSG
+```
+### Direct projection system (for geographical resources) {#iso19139-elem-DirectReferenceSystem-d28cd37e0c2b9a86305c20c194bf5f79}
+
+Name
+
+:
+
+> DirectReferenceSystem
+
+Description
+
+:
+
+```{=html}
+ReferenceSystem derived / specify that it is a direct
+ reference
+```
+### Factor {#iso19139-elem-factor-7e34666ca11658e04e31d3a614685b15}
+
+Name
+
+:
+
+> factor
+
+Description
+
+:
+
+### Frame {#iso19139-elem-frame-4aefbf304b03d93af57daba6b7c1fa8d}
+
+Name
+
+:
+
+> frame
+
+Description
+
+:
+
+```{=html}
+Frame attribute provides a URI reference that identifies a description of the
+ reference system
+```
+### Name {#iso19139-elem-gco-aName-39d38a0515ba733c328d5bd1c57e7e5e}
+
+Name
+
+:
+
+> gco:aName
+
+Description
+
+:
+
+### Type name {#iso19139-elem-gco-aName-gco-TypeName-b5751c296623f4c8529273aaf3caa587}
+
+Name
+
+:
+
+> gco:aName
+
+Context
+
+:
+
+> gco:TypeName
+
+Description
+
+:
+
+Recommended values
+
+| code | label |
+|-----------|-----------|
+| BOOLEAN | BOOLEAN |
+| BYTE | BYTE |
+| CHARACTER | CHARACTER |
+| DATE | DATE |
+| DATETIME | DATETIME |
+| DOUBLE | DOUBLE |
+| FLOAT | FLOAT |
+| INTEGER | INTEGER |
+| NUMERIC | NUMERIC |
+| REAL | REAL |
+| SERIAL | SERIAL |
+| VARCHAR | VARCHAR |
+| TEXT | TEXT |
+
+### Angle {#iso19139-elem-gco-Angle-3593960aae71b8b1bdfe5ebf0f35d2c9}
+
+Name
+
+:
+
+> gco:Angle
+
+Description
+
+:
+
+### Attribute type {#iso19139-elem-gco-attributeType-0b903ede9f187704365df4f997921127}
+
+Name
+
+:
+
+> gco:attributeType
+
+Description
+
+:
+
+### Binary {#iso19139-elem-gco-Binary-a22b5d55570c2130700e110981a19fc0}
+
+Name
+
+:
+
+> gco:Binary
+
+Description
+
+:
+
+### Text {#iso19139-elem-gco-CharacterString-3c4a83cea72b8088a49c2cdafdcaf1c1}
+
+Name
+
+:
+
+> gco:CharacterString
+
+Description
+
+:
+
+### Edition Date {#iso19139-elem-gco-Date-gmd-CI_Citation-ca5259e4b2838d1c0558671de588f0df}
+
+Name
+
+:
+
+> gco:Date
+
+Context
+
+:
+
+> gmd:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Date of the edition
+```
+### Date {#iso19139-elem-gco-Date-c5ab2c208539dd2f12e12861e602dc91}
+
+Name
+
+:
+
+> gco:Date
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12 (YYYY-MM-DD)
+```
+```{=html}
+reference date and event used to describe it
+```
+### Usage Date / Time {#iso19139-elem-gco-DateTime-gmd-MD_Usage-5932999d2f9d3461e5820eade7175b5b}
+
+Name
+
+:
+
+> gco:DateTime
+
+Context
+
+:
+
+> gmd:MD_Usage
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+```{=html}
+date and time of the first use or range of uses of the resource and/or resource
+ series
+```
+``` xml
+2016-01-15T16:57:35
+```
+
+### Planned Available Date / Time {#iso19139-elem-gco-DateTime-gmd-MD_StandardOrderProcess-c7c418ca6afb419b0c0f7978f0f70bd5}
+
+Name
+
+:
+
+> gco:DateTime
+
+Context
+
+:
+
+> gmd:MD_StandardOrderProcess
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+```{=html}
+date and time when theresource will be available
+```
+``` xml
+2016-01-15T16:57:35
+```
+
+### Date and time {#iso19139-elem-gco-DateTime-32c0a3056194945a06e26342a31c4abe}
+
+Name
+
+:
+
+> gco:DateTime
+
+Description
+
+:
+
+```{=html}
+Date and time or range of date and time on or over which the process step occurred
+ (YYYY-MM-DDThh:mm:ss)
+```
+``` xml
+2016-01-15T16:57:35
+```
+
+### Distance {#iso19139-elem-gco-Distance-97e7c5e41f65464cfde4bdcbd0987611}
+
+Name
+
+:
+
+> gco:Distance
+
+Description
+
+:
+
+``` xml
+100
+```
+
+### Length {#iso19139-elem-gco-Length-caf3c113efd04589ae6f255714b3cfb5}
+
+Name
+
+:
+
+> gco:Length
+
+Description
+
+:
+
+### Name {#iso19139-elem-gco-localName-d5d8fd10758516aba7e3e61dca6a3d06}
+
+Name
+
+:
+
+> gco:localName
+
+Description
+
+:
+
+### Local name {#iso19139-elem-gco-LocalName-eab12ae644d752a8b1eff54b0477039a}
+
+Name
+
+:
+
+> gco:LocalName
+
+Description
+
+:
+
+### Lower cardinality {#iso19139-elem-gco-lower-2cae58bb16663bb430a5756705195313}
+
+Name
+
+:
+
+> gco:lower
+
+Description
+
+:
+
+```{=html}
+Lower cardinality
+```
+### Name of Measure {#iso19139-elem-gco-Measure-gmd-DQ_Element-6560606f315eea7246848f93ddc3d967}
+
+Name
+
+:
+
+> gco:Measure
+
+Context
+
+:
+
+> gmd:DQ_Element
+
+Description
+
+:
+
+```{=html}
+Name of the test applied to the data
+```
+### Unit of Measure {#iso19139-elem-gco-Measure-gmd-EX_VerticalExtent-89983ecdbd1cba38f291e34bee6c223f}
+
+Name
+
+:
+
+> gco:Measure
+
+Context
+
+:
+
+> gmd:EX_VerticalExtent
+
+Description
+
+:
+
+```{=html}
+Vertical units used for vertical extent information Examples: metres, feet,
+ millimetres, hectopascals
+```
+### Measure {#iso19139-elem-gco-Measure-462aeec614da812d758659486be00b47}
+
+Name
+
+:
+
+> gco:Measure
+
+Description
+
+:
+
+### Member name {#iso19139-elem-gco-MemberName-b60b50f5b87b148b6615393b823e6a3b}
+
+Name
+
+:
+
+> gco:MemberName
+
+Description
+
+:
+
+### Nil reason {#iso19139-elem-gco-nilReason-fab8a57f0e69d3ca1699fa818c483698}
+
+Name
+
+:
+
+> gco:nilReason
+
+Description
+
+:
+
+### Standard codelists Nil reason (gco:nilReason)
+
+| code | label |
+|--------------|--------------|
+| missing | Missing |
+| inapplicable | Inapplicable |
+| template | Template |
+| unknown | Unknown |
+| withheld | Withheld |
+
+### Record {#iso19139-elem-gco-Record-6d9e28990789e830931b4d2ba9766597}
+
+Name
+
+:
+
+> gco:Record
+
+Description
+
+:
+
+### Scale {#iso19139-elem-gco-Scale-be644ab22ff8340a59eb1ea346d70bae}
+
+Name
+
+:
+
+> gco:Scale
+
+Description
+
+:
+
+### Scoped name {#iso19139-elem-gco-ScopedName-fa518f7fd322d0dc580364a3bdd0d0ba}
+
+Name
+
+:
+
+> gco:ScopedName
+
+Description
+
+:
+
+### Type name {#iso19139-elem-gco-TypeName-ca6ce43198031eafc2870fd56a3cca80}
+
+Name
+
+:
+
+> gco:TypeName
+
+Description
+
+:
+
+### Upper cardinality {#iso19139-elem-gco-upper-bb37e0d692d0d0dd4557b3b31c16d35c}
+
+Name
+
+:
+
+> gco:upper
+
+Description
+
+:
+
+```{=html}
+Upper cardinality
+```
+### Abstract {#iso19139-elem-gmd-abstract-cacfcd3bd6bbd44733f828dd2903ecd8}
+
+Name
+
+:
+
+> gmd:abstract
+
+Description
+
+:
+
+```{=html}
+Brief narrative summary of the content of the resource(s)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ The data set combines the Corine based MAES (Mapping and Assessment of
+ Ecosystems and their Services) ecosystem classes with the non-spatial EUNIS habitat
+ classification (LEVEL 1) for a better biological characterization of ecosystems across
+ Europe (EEA-39). As such it represents probabilities of EUNIS habitat presence for each
+ MAES ecosystem type.
+
+ The data set aims to combine spatially explicit land cover information with non-spatially
+ referenced habitat information to improve our knowledge about ecosystems and their
+ distribution across Europe. The work supports the MAES process, Target 2 Action 5 of the
+ implementation of the EU Biodiversity Strategy to 2020, established to achieve the Aichi
+ targets of the Convention of Biological Diversity (CBD).
+
+ The objective of the ecosystem data set produced by EEA and its Topic Centre ETC/SIA was
+ to improve the biological description of land cover based ecosystem types. It represents
+ probabilities of EUNIS habitat presence in ecosystem types at European level. Since it is
+ not based on spatial explicit mapping the spatial and thematic accuracy is not of same
+ quality as delineated maps.
+
+ The MAES ecosystem typology differentiates three levels: whereas the level 2 of the MAES
+ proposal follows closely the EUNIS level 1, the third level of the MAES typology
+ corresponds to the EUNIS level 2. This level will be the base for the mapping approach.
+
+
+```
+
+### Access constraints {#iso19139-elem-gmd-accessConstraints-37a2c49e23691aae70811fa8493a9501}
+
+Name
+
+:
+
+> gmd:accessConstraints
+
+Description
+
+:
+
+```{=html}
+Access constraints applied to assure the protection of privacy or intellectual
+ property, and any special restrictions or limitations on obtaining the
+ resource
+```
+``` xml
+
+
+
+```
+
+### Address {#iso19139-elem-gmd-address-gmd-CI_ResponsibleParty-f03654d869b99fc91ee4abcff33fd45a}
+
+Name
+
+:
+
+> gmd:address
+
+Context
+
+:
+
+> gmd:CI_ResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Address of the responsible party
+```
+### Address {#iso19139-elem-gmd-address-7526bc750039dec29eb9d0d886b5b895}
+
+Name
+
+:
+
+> gmd:address
+
+Description
+
+:
+
+```{=html}
+Physical and email address at which the organization or individual may be
+ contacted
+```
+### Administrative area {#iso19139-elem-gmd-administrativeArea-7e04a671c8b9220833d4bf8cbdc92040}
+
+Name
+
+:
+
+> gmd:administrativeArea
+
+Description
+
+:
+
+```{=html}
+State, province of the location
+```
+### Aggregate Datasetindentifier {#iso19139-elem-gmd-aggregateDataSetIdentifier-f9f0932f51fb5f976d14dc7a9b9d27eb}
+
+Name
+
+:
+
+> gmd:aggregateDataSetIdentifier
+
+Description
+
+:
+
+```{=html}
+Identification information about aggregate dataset
+```
+### Aggregate Datasetname {#iso19139-elem-gmd-aggregateDataSetName-59f3c71bb683851f84e8495e4cbf6753}
+
+Name
+
+:
+
+> gmd:aggregateDataSetName
+
+Description
+
+:
+
+```{=html}
+Citation information about the aggregate dataset
+```
+### Aggregation Information {#iso19139-elem-gmd-aggregationInfo-5f7895f7021de881e9a8eeb5f3cf954f}
+
+Name
+
+:
+
+> gmd:aggregationInfo
+
+Description
+
+:
+
+```{=html}
+Provides aggregate dataset information
+```
+### Alternate title {#iso19139-elem-gmd-alternateTitle-a6ad7cbd770ba390dd40d40adc3767f7}
+
+Name
+
+:
+
+> gmd:alternateTitle
+
+Description
+
+:
+
+```{=html}
+Short name or other language name by which the cited information is known.
+ Example: "DCW" as an alternative title for "Digital Chart of the World
+```
+### Amendment number {#iso19139-elem-gmd-amendmentNumber-9baa9c155f39c7359de9d01c15841366}
+
+Name
+
+:
+
+> gmd:amendmentNumber
+
+Description
+
+:
+
+```{=html}
+Amendment number of the format version
+```
+### Application profile {#iso19139-elem-gmd-applicationProfile-5705b47df6b8e82c11958958b15914a1}
+
+Name
+
+:
+
+> gmd:applicationProfile
+
+Description
+
+:
+
+```{=html}
+Name of an application profile that can be used with the online
+ resource
+```
+### Application schema info {#iso19139-elem-gmd-applicationSchemaInfo-45e55618bc13cc73f4ede49af591b9cb}
+
+Name
+
+:
+
+> gmd:applicationSchemaInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the conceptual schema of a dataset
+```
+### Association Type {#iso19139-elem-gmd-associationType-e943c0b17dfbb55713da9617c4b8f82d}
+
+Name
+
+:
+
+> gmd:associationType
+
+Description
+
+:
+
+```{=html}
+Association type of the aggregate dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Attribute description {#iso19139-elem-gmd-attributeDescription-00769a0e138b43e364425bc2024f59a7}
+
+Name
+
+:
+
+> gmd:attributeDescription
+
+Description
+
+:
+
+```{=html}
+Description of the attribute described by the measurement value
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Attribute instances {#iso19139-elem-gmd-attributeInstances-d2471a047af6b59087ff645bd19192cf}
+
+Name
+
+:
+
+> gmd:attributeInstances
+
+Description
+
+:
+
+```{=html}
+Attribute instances to which the information applies
+```
+### Attributes {#iso19139-elem-gmd-attributes-649c8af5decae1033a93a033cc949221}
+
+Name
+
+:
+
+> gmd:attributes
+
+Description
+
+:
+
+```{=html}
+Attributes to which the information applies
+```
+### Authority {#iso19139-elem-gmd-authority-8906bfad81e05c31f72e1ea5fc426c79}
+
+Name
+
+:
+
+> gmd:authority
+
+Description
+
+:
+
+```{=html}
+Person or party responsible for maintenance of the namespace
+```
+### Axis Dimensions Properties {#iso19139-elem-gmd-axisDimensionProperties-0bb4895a894113bc668ea60ab4d65b7b}
+
+Name
+
+:
+
+> gmd:axisDimensionProperties
+
+Description
+
+:
+
+```{=html}
+Information about spatial-temporal axis properties
+```
+### Bits per value {#iso19139-elem-gmd-bitsPerValue-c821e4cbb21edf31325b2502030f1b4a}
+
+Name
+
+:
+
+> gmd:bitsPerValue
+
+Description
+
+:
+
+```{=html}
+Maximum number of significant bits in the uncompressed representation for the
+ value in each band of each pixel
+```
+### Camera calibration information availability {#iso19139-elem-gmd-cameraCalibrationInformationAvailability-a7b5dfec3c788d338536cb889d5a9aea}
+
+Name
+
+:
+
+> gmd:cameraCalibrationInformationAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not constants are available which allow for camera
+ calibration corrections
+```
+### Cell geometry {#iso19139-elem-gmd-cellGeometry-890a25e7df81597ba59f0485b15e434f}
+
+Name
+
+:
+
+> gmd:cellGeometry
+
+Description
+
+:
+
+```{=html}
+Identification of grid data as point or cell
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Center point {#iso19139-elem-gmd-centerPoint-c69510c5e9aaea576a6ec9a4d2216a1d}
+
+Name
+
+:
+
+> gmd:centerPoint
+
+Description
+
+:
+
+```{=html}
+Earth location in the coordinate system defined by the Spatial Reference System
+ and the grid coordinate of the cell halfway between opposite ends of the grid in the
+ spatial dimensions
+```
+### Character encoding {#iso19139-elem-gmd-characterEncoding-7c26199d236a428b73baf1a730615e56}
+
+Name
+
+:
+
+> gmd:characterEncoding
+
+Description
+
+:
+
+```{=html}
+CharacterEncoding
+```
+### Character set {#iso19139-elem-gmd-characterSet-gmd-MD_Metadata-754de1196395a6e9833e813ecf4adaa3}
+
+Name
+
+:
+
+> gmd:characterSet
+
+Context
+
+:
+
+> gmd:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Full name of the character coding standard used for the metadata
+ set
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+
+
+```
+
+### Character set {#iso19139-elem-gmd-characterSet-gmd-MD_DataIdentification-bcb6931cff8dcf767968cfa67fd83a88}
+
+Name
+
+:
+
+> gmd:characterSet
+
+Context
+
+:
+
+> gmd:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Full name of the character coding standard used for the dataset
+```
+``` xml
+
+
+
+```
+
+### Character set {#iso19139-elem-gmd-characterSet-351330c9787387f916fed1143727215b}
+
+Name
+
+:
+
+> gmd:characterSet
+
+Description
+
+:
+
+```{=html}
+Full name of the character coding standard used for the metadata
+ set
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+
+
+```
+
+### Checkpoint Availability {#iso19139-elem-gmd-checkPointAvailability-72ce5f12e30b81e5dc63f0585a98bd8a}
+
+Name
+
+:
+
+> gmd:checkPointAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not geographic position points are available to test
+ the accuracy of the georeferenced grid data
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Checkpoint Description {#iso19139-elem-gmd-checkPointDescription-cdfe4f08433f7ba8c78498f65aec1099}
+
+Name
+
+:
+
+> gmd:checkPointDescription
+
+Description
+
+:
+
+```{=html}
+Description of geographic position points used to test the accuracy of the
+ georeferenced grid data
+```
+
+Condition
+
+:
+
+> conditional
+
+### Address {#iso19139-elem-gmd-CI_Address-1d6106250b28fc5d97a0cf1a34c00ef8}
+
+Name
+
+:
+
+> gmd:CI_Address
+
+Description
+
+:
+
+```{=html}
+Location of the responsible individual or organization
+```
+### Citation {#iso19139-elem-gmd-CI_Citation-1b27899fdd70634298035b26812c0e67}
+
+Name
+
+:
+
+> gmd:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Standardised resource reference
+```
+### Contact {#iso19139-elem-gmd-CI_Contact-087be944cc5050234e102c0d8eb3cc3d}
+
+Name
+
+:
+
+> gmd:CI_Contact
+
+Description
+
+:
+
+```{=html}
+Information required to enable contact with the responsible person and/or
+ organization
+```
+### Date {#iso19139-elem-gmd-CI_Date-7703f686b3d66a527500403e9e888c5d}
+
+Name
+
+:
+
+> gmd:CI_Date
+
+Description
+
+:
+
+```{=html}
+Reference date and event used to describe it (YYYY-MM-DD)
+```
+### Date type code {#iso19139-elem-gmd-CI_DateTypeCode-beb19798d5fb72e1e08905a0196a7d1a}
+
+Name
+
+:
+
+> gmd:CI_DateTypeCode
+
+Description
+
+:
+
+### Standard codelists Date type code (gmd:CI_DateTypeCode)
+
+| code | label | description |
+|-------------|-------------|---------------------------------------------------------------------------------------|
+| creation | Creation | Date identifies when the resource was brought into existence |
+| publication | Publication | Date identifies when the resource was issued |
+| revision | Revision | Date identifies when the resource was examined or re-examined and improved or amended |
+
+### OnLine function code {#iso19139-elem-gmd-CI_OnLineFunctionCode-6fe7732b8773444ae385d33f3e3e7ce0}
+
+Name
+
+:
+
+> gmd:CI_OnLineFunctionCode
+
+Description
+
+:
+
+### Standard codelists OnLine function code (gmd:CI_OnLineFunctionCode)
+
+| code | label | description |
+|---------------|----------------|----------------------------------------------------------------------------------------|
+| download | Download | Online instructions for transferring data from one storage device or system to another |
+| information | Information | Online information about the resource |
+| offlineAccess | Offline access | Online instructions for requesting the resource from the provider |
+| order | Order | Online order process for obtening the resource |
+| search | Search | Online search interface for seeking out information about the resource |
+
+### OnLine resource {#iso19139-elem-gmd-CI_OnlineResource-213bee17108ab0feab5f62eb0cb7d7ae}
+
+Name
+
+:
+
+> gmd:CI_OnlineResource
+
+Description
+
+:
+
+```{=html}
+Information about on-line sources from which the dataset, specification, or
+ community profile name and extended metadata elements can be obtained
+```
+### Presentatiewijze code {#iso19139-elem-gmd-CI_PresentationFormCode-65627a7048d5ce0c224f1836c65ea95f}
+
+Name
+
+:
+
+> gmd:CI_PresentationFormCode
+
+Description
+
+:
+
+### Standard codelists Presentatiewijze code (gmd:CI_PresentationFormCode)
+
+| code | label | description |
+|------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| documentDigital | Digital document | Digital representation of a primarily textual item (can contain illustrations also) |
+| imageDigital | Digital image | Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format |
+| documentHardcopy | Hardcopy document | Representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media |
+| imageHardcopy | Hardcopy image | Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user |
+| mapDigital | Digital map | Map represented in raster or vector form |
+| mapHardcopy | Hardcopy map | Map printed on paper, photographic material, or other media for use directly by the human user |
+| modelDigital | Digital model | Multi-dimensional digital representation of a feature, process, etc. |
+| modelHardcopy | Hardcopy model | 3-dimensional, physical model |
+| profileDigital | Digital profile | Vertical cross-section in digital form |
+| profileHardcopy | Hardcopy profile | Vertical cross-section printed on paper, etc. |
+| tableDigital | Digital table | Digital representation of facts or figures systematically displayed, especially in columns |
+| tableHardcopy | Hardcopy table | Representation of facts or figures systematically displayed, especially in columns, printed onpapers, photographic material, or other media |
+| videoDigital | Digital video | Digital video recording |
+| videoHardcopy | Hardcopy video | Video recording on film |
+
+### Responsible party {#iso19139-elem-gmd-CI_ResponsibleParty-3c64649ce322328d00e5c999aeceef06}
+
+Name
+
+:
+
+> gmd:CI_ResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s) and organizations
+ associated with the dataset
+```
+### Role code {#iso19139-elem-gmd-CI_RoleCode-5979017c743ab287cf7d4188dc561d4e}
+
+Name
+
+:
+
+> gmd:CI_RoleCode
+
+Description
+
+:
+
+### Standard codelists Role code (gmd:CI_RoleCode)
+
+| code | label | description |
+|-----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| resourceProvider | Resource provider | Party that supplies the resource |
+| custodian | Custodian | Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource |
+| owner | Owner | Party that owns the resource |
+| user | User | Party who uses the resource |
+| distributor | Distributor | Party who distributes the resource |
+| originator | Originator | Party who created the resource |
+| pointOfContact | Point of contact | Party who can be contacted for acquiring knowledge about or acquisition of the resource |
+| principalInvestigator | Principal investigator | Key party responsible for gathering information and conducting research |
+| processor | Processor | Party that has processed the data in a manner such that the resource has been modified |
+| publisher | Publisher | Party who published the resource |
+| author | Author | Party who authored the resource |
+
+### Series {#iso19139-elem-gmd-CI_Series-ceedc6d470330f24379e7dd4263132c9}
+
+Name
+
+:
+
+> gmd:CI_Series
+
+Description
+
+:
+
+```{=html}
+Information about the series, or aggregate dataset, to which a dataset
+ belongs
+```
+### Telephone {#iso19139-elem-gmd-CI_Telephone-a8a5286743a9be34bb502ffd91756c35}
+
+Name
+
+:
+
+> gmd:CI_Telephone
+
+Description
+
+:
+
+```{=html}
+Telephone numbers for contacting the responsible individual or
+ organization
+```
+### Citation {#iso19139-elem-gmd-citation-gmd-MD_Identification-4d43482062eba4f4d96d8c274ebd935c}
+
+Name
+
+:
+
+> gmd:citation
+
+Context
+
+:
+
+> gmd:MD_Identification
+
+Description
+
+:
+
+```{=html}
+Citation data for the resource(s)
+```
+``` xml
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+```
+
+### Citation {#iso19139-elem-gmd-citation-gmd-MD_Authority-c23fa4c41db4a321e376f2625a5b0bf9}
+
+Name
+
+:
+
+> gmd:citation
+
+Context
+
+:
+
+> gmd:MD_Authority
+
+Description
+
+:
+
+```{=html}
+Citation which belongs to the authority
+```
+``` xml
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+```
+
+### Citation {#iso19139-elem-gmd-citation-gmd-MD_Thesaurus-2de9a1c0b4ce344cc8452dceb1eb1f6d}
+
+Name
+
+:
+
+> gmd:citation
+
+Context
+
+:
+
+> gmd:MD_Thesaurus
+
+Description
+
+:
+
+```{=html}
+Citation of the thesaurus
+```
+``` xml
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+```
+
+### Citation {#iso19139-elem-gmd-citation-db812fc78bb9e3e6e756d4aeeed129fa}
+
+Name
+
+:
+
+> gmd:citation
+
+Description
+
+:
+
+```{=html}
+Citation data for the resource(s)
+```
+``` xml
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+```
+
+### Cited responsible party {#iso19139-elem-gmd-citedResponsibleParty-4995fda6b735448d4aaae3ba4568cd90}
+
+Name
+
+:
+
+> gmd:citedResponsibleParty
+
+Description
+
+:
+
+```{=html}
+Name and position information for an individual or organization that is
+ responsible for the resource
+```
+### City {#iso19139-elem-gmd-city-f40cb44555bb1278990e5f3799435366}
+
+Name
+
+:
+
+> gmd:city
+
+Description
+
+:
+
+```{=html}
+City of the location
+```
+### Classification {#iso19139-elem-gmd-classification-6718026907e4b1aead3cfd241f9b4d50}
+
+Name
+
+:
+
+> gmd:classification
+
+Description
+
+:
+
+```{=html}
+Name of the handling restrictions on the resource or metadata
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Classification system {#iso19139-elem-gmd-classificationSystem-010b22c4ad8a62f8521acbbbe6ff3398}
+
+Name
+
+:
+
+> gmd:classificationSystem
+
+Description
+
+:
+
+```{=html}
+Name of the classification system
+```
+### Cloud cover percentage {#iso19139-elem-gmd-cloudCoverPercentage-413e7fc75782e9add871c76f54773c87}
+
+Name
+
+:
+
+> gmd:cloudCoverPercentage
+
+Description
+
+:
+
+```{=html}
+Area of the dataset obscured by clouds, expressed as a percentage of the
+ spatial extent
+```
+### Unique resource identifier {#iso19139-elem-gmd-code-gmd-RS_Identifier-02da3b1f8d1566c861440d9a19132ad6}
+
+Name
+
+:
+
+> gmd:code
+
+Context
+
+:
+
+> gmd:RS_Identifier
+
+Description
+
+:
+
+```{=html}
+Alphanumeric value identifying an instance in the namespace
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Code {#iso19139-elem-gmd-code-gmd-MD_Identifier-41ff66cafe2cad1503b9d38a2447d249}
+
+Name
+
+:
+
+> gmd:code
+
+Context
+
+:
+
+> gmd:MD_Identifier
+
+Description
+
+:
+
+```{=html}
+Alphanumeric value identifying an instance in the namespace
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Code {#iso19139-elem-gmd-code-gmd-MD_CodeValue-d16c67ed008c738facc264888ac97356}
+
+Name
+
+:
+
+> gmd:code
+
+Context
+
+:
+
+> gmd:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Value code
+```
+```{=html}
+Value code (i.e. numeric)
+```
+### Codespace {#iso19139-elem-gmd-codeSpace-02f6245083ede2af10bb3e9028ca4a7c}
+
+Name
+
+:
+
+> gmd:codeSpace
+
+Description
+
+:
+
+```{=html}
+Name or identifier of the person or organization responsible for
+ namespace
+```
+Recommended values
+
+| code | label |
+|------|-------|
+| EPSG | EPSG |
+
+``` xml
+
+ OGP Surveying & Positioning Committee
+
+```
+
+### Collective title {#iso19139-elem-gmd-collectiveTitle-0bc5974850084906d55ce76bb6787867}
+
+Name
+
+:
+
+> gmd:collectiveTitle
+
+Description
+
+:
+
+```{=html}
+Common title with holdings note. NOTE title identifies elements of a series
+ collectively, combined with information about what volumes are available at the source
+ cited
+```
+```{=html}
+This field is used to name the Basic Geodata as defined in the GeoIV Annex I, as it is
+ possible that there are more than 1 "physical" datasets assigned to 1 legal entry. E.g.: Entry
+ no. 47 "Geophysikalisches Kartenwerk" consists of 3 datasets "Geophysikalische Karten
+ 1:500000", "Geophysikalische Spezialkarten" and "Gravimetrischer Atlas 1:100000"
+```
+### Compliance code {#iso19139-elem-gmd-complianceCode-b796c3767c8744c392e3f2313329b30b}
+
+Name
+
+:
+
+> gmd:complianceCode
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the cited feature catalogue complies with ISO
+ 19110
+```
+### ComposedOf {#iso19139-elem-gmd-composedOf-6f05d3ac23259e9892032b2da31de58c}
+
+Name
+
+:
+
+> gmd:composedOf
+
+Description
+
+:
+
+```{=html}
+ComposedOf
+```
+### Compression generation quantity {#iso19139-elem-gmd-compressionGenerationQuantity-8848b37883d12c673e2e9b280c7991ce}
+
+Name
+
+:
+
+> gmd:compressionGenerationQuantity
+
+Description
+
+:
+
+```{=html}
+Count of the number of lossy compression cycles performed on the
+ image
+```
+### Condition {#iso19139-elem-gmd-condition-9eb82cddebe8042afaa4010e913d0c79}
+
+Name
+
+:
+
+> gmd:condition
+
+Description
+
+:
+
+```{=html}
+Condition under which the extended element is mandatory
+```
+### Constraint language {#iso19139-elem-gmd-constraintLanguage-b9baafd989bb2bd8772ac36dc55e333d}
+
+Name
+
+:
+
+> gmd:constraintLanguage
+
+Description
+
+:
+
+```{=html}
+Formal language used in Application Schema
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Contact {#iso19139-elem-gmd-contact-gmd-MD_Metadata-2294585374798aea84d2876a5e8e7ade}
+
+Name
+
+:
+
+> gmd:contact
+
+Context
+
+:
+
+> gmd:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Party responsible for the metadata information
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+```
+
+### Contact {#iso19139-elem-gmd-contact-gmd-MD_MaintenanceInformation-0e2bd3597e71a41f1f85eed23ebb2005}
+
+Name
+
+:
+
+> gmd:contact
+
+Context
+
+:
+
+> gmd:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s) and
+ organization(s) with responsibility for maintaining the metadata
+```
+``` xml
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+```
+
+### Metadata author {#iso19139-elem-gmd-contact-1a17bee429a4ae3c87f4026bd2da8005}
+
+Name
+
+:
+
+> gmd:contact
+
+Description
+
+:
+
+```{=html}
+Party responsible for the metadata information
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+```
+
+### Contact Information {#iso19139-elem-gmd-contactInfo-3ae0765a28247f062c63bdc8eb973f50}
+
+Name
+
+:
+
+> gmd:contactInfo
+
+Description
+
+:
+
+```{=html}
+Address of the responsible party
+```
+### Contact instructions {#iso19139-elem-gmd-contactInstructions-794f3bd38398fc8ae39cce7c984087f0}
+
+Name
+
+:
+
+> gmd:contactInstructions
+
+Description
+
+:
+
+```{=html}
+Supplemental instructions on how or when to contact the individual or
+ organization
+```
+### Content Information {#iso19139-elem-gmd-contentInfo-da18cd6a5e91bae67187adc15ff47622}
+
+Name
+
+:
+
+> gmd:contentInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the feature catalogue and describes the coverage and
+ image data characteristics
+```
+``` xml
+
+
+
+ false
+
+
+
+
+```
+
+### Content type {#iso19139-elem-gmd-contentType-f9d07b4b0ceec04f18bce420c5291a5e}
+
+Name
+
+:
+
+> gmd:contentType
+
+Description
+
+:
+
+```{=html}
+Type of information represented by the cell value
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Controlpoint Availability {#iso19139-elem-gmd-controlPointAvailability-f87c554dde9c2a5bc1413de637c47e2d}
+
+Name
+
+:
+
+> gmd:controlPointAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not control point(s) exists
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Corner points {#iso19139-elem-gmd-cornerPoints-b92ddc8c05fd3950d850515164e26c5c}
+
+Name
+
+:
+
+> gmd:cornerPoints
+
+Description
+
+:
+
+```{=html}
+Earth location in the coordinate system defined by the Spatial Reference System
+ and the grid coordinate of the cells at opposite ends of grid coverage along two
+ diagonals in the grid spatial dimensions. There are four corner points in a georectified
+ grid; at least two corner points along one diagonal are required
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Country {#iso19139-elem-gmd-country-7819215af574621eb7dd1e63f32e1e19}
+
+Name
+
+:
+
+> gmd:country
+
+Description
+
+:
+
+```{=html}
+Country of the physical address
+```
+### Country {#iso19139-elem-gmd-country-gmd-MD_Legislation-84c810ce3efbda031bc28f55683d23a5}
+
+Name
+
+:
+
+> gmd:country
+
+Context
+
+:
+
+> gmd:MD_Legislation
+
+Description
+
+:
+
+```{=html}
+Country in which the law was issued
+```
+### Country {#iso19139-elem-gmd-country-PT_Group-c87df35752363f7e2f20c8a68953c0a6}
+
+Name
+
+:
+
+> gmd:country
+
+Context
+
+:
+
+> PT_Group
+
+Description
+
+:
+
+```{=html}
+Country of language used for documenting a plain text
+```
+### Credit {#iso19139-elem-gmd-credit-0b272311ef39699d6c413fe246ea5326}
+
+Name
+
+:
+
+> gmd:credit
+
+Description
+
+:
+
+```{=html}
+Recognition of those who contributed to the resource(s)
+```
+### Data quality info {#iso19139-elem-gmd-dataQualityInfo-9a53c25e2dacf5a7ab0aa1d155efc3dc}
+
+Name
+
+:
+
+> gmd:dataQualityInfo
+
+Description
+
+:
+
+```{=html}
+Provides overall assessment of quality of a resource(s)
+```
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+ The data set production implied 2 steps. First re-classification of
+ CORINE Land Cover 2006 and bathymetry data using the 7 terrestrial (urban, cropland,
+ grassland, woodland and forest, heathland and shrub, sparsely vegetated land,
+ wetland), 1 freshwater (river and lakes), and 4 marine (marine inlets and transitional
+ waters, coastal, shelf, open ocean) classes of the MAES ecosystem typology (Maes et
+ al., 2013). The classes also provide links to major policy lines such as agriculture,
+ forestry, territorial cohesion, water and marine related policies. The second step
+ comprised refinement of the ecosystem types by attributing EUNIS habitat information
+ to each ecosystem type (see http://eunis.eea.europa.eu/habitats.jsp). The refinement
+ process used reference data such as potential natural vegetation, elevation, slope,
+ aspect, soil, geology, environmental regions and other spatial referenced information
+ which allowed attribution of the EUNIS habitat characteristics to the spatial mapping
+ units of the MAES ecosystem types. The geometric and thematic accuracy of EUNIS class
+ presence was also estimated and mapped. The method is described in the EEA Technical
+ Report 06/2015: European Ecosystem Assessment – Concept, Data, and Implementation.
+ The basis for the update was CORINE land cover 2006 (CLC 2006). It includes Albania,
+ Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic,
+ Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Kosovo
+ (under UNSCR 1244/99), Latvia, Liechtenstein, Lithuania, Luxembourg, the former
+ Yugoslavian Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland,
+ Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
+ the United Kingdom. For Greece that has not participated in the CLC 2006 activity the
+ CLC 2000 data was used instead.
+
+
+
+
+
+
+
+```
+
+### Dataset {#iso19139-elem-gmd-dataset-5262692d36cca930e0c50a2ae131301a}
+
+Name
+
+:
+
+> gmd:dataset
+
+Description
+
+:
+
+```{=html}
+Dataset to which the information applies
+```
+### Dataset URI {#iso19139-elem-gmd-dataSetURI-8e14b3e6d98f92a9356ba2f3ba1ee982}
+
+Name
+
+:
+
+> gmd:dataSetURI
+
+Description
+
+:
+
+```{=html}
+Uniformed Resource Identifier (URI) of the dataset to which the metadata
+ applies
+```
+```{=html}
+Uniformed Resource Identifier (URI) of the dataset to which the metadata applies. This
+ link refers direct to the machine-readable dataset.
+```
+### Data type {#iso19139-elem-gmd-dataType-8e2f4cdbb24b536e5df6aaee70047601}
+
+Name
+
+:
+
+> gmd:dataType
+
+Description
+
+:
+
+```{=html}
+Code which identifies the kind of valueprovidedeprovided in the extended
+ element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date {#iso19139-elem-gmd-date-ebb509445b6cf496cbf813a8b01a2362}
+
+Name
+
+:
+
+> gmd:date
+
+Description
+
+:
+
+```{=html}
+Reference date for the cited resource (YYYY-MM-DD)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date of last update {#iso19139-elem-gmd-date-gmd-MD_Revision-285564fda444a3437d34594df33c890e}
+
+Name
+
+:
+
+> gmd:date
+
+Context
+
+:
+
+> gmd:MD_Revision
+
+Description
+
+:
+
+```{=html}
+Date of last update
+```
+### Date of next update {#iso19139-elem-gmd-date-gmd-MD_MaintenanceInformation-9a98fdd70f046e77f1556ed865f56d0b}
+
+Name
+
+:
+
+> gmd:date
+
+Context
+
+:
+
+> gmd:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Scheduled revision date for resource
+```
+### Date {#iso19139-elem-gmd-date-gmd-CI_Citation-478aeda64d149a8df6810bf35c93f39f}
+
+Name
+
+:
+
+> gmd:date
+
+Context
+
+:
+
+> gmd:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Reference date for the cited resource
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date {#iso19139-elem-gmd-date-gmd-CI_Date-6c9c8f825ef4f9c73ed94df2741d9ff5}
+
+Name
+
+:
+
+> gmd:date
+
+Context
+
+:
+
+> gmd:CI_Date
+
+Description
+
+:
+
+```{=html}
+Reference date for the cited resource
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Date of next update {#iso19139-elem-gmd-dateOfNextUpdate-efa132e2522617da74a9f2b6cac7f884}
+
+Name
+
+:
+
+> gmd:dateOfNextUpdate
+
+Description
+
+:
+
+```{=html}
+Scheduled revision date for resource (YYYY-MM-DD)
+```
+### Date stamp {#iso19139-elem-gmd-dateStamp-ee89eb65741d89aef14d153887f60948}
+
+Name
+
+:
+
+> gmd:dateStamp
+
+Description
+
+:
+
+```{=html}
+Date that the metadata was created (YYYY-MM-DDThh:mm:ss)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ 2016-01-15T16:57:35
+
+```
+
+### Date / Time {#iso19139-elem-gmd-dateTime-f2e7c016069fc9e8b93cacb30bc5c30f}
+
+Name
+
+:
+
+> gmd:dateTime
+
+Description
+
+:
+
+```{=html}
+Date and time or range of date and time on or over which the process step
+ occurred (YYYY-MM-DDThh:mm:ss)
+```
+### Date / Time {#iso19139-elem-gmd-dateTime-LI_ProcessStep-0aea67a7cf3150b81bec5e552be93a4e}
+
+Name
+
+:
+
+> gmd:dateTime
+
+Context
+
+:
+
+> LI_ProcessStep
+
+Description
+
+:
+
+```{=html}
+Date and time or range of date and time on or over which the process step
+ occurred (YYYY-MM-DDThh:mm:ss)
+```
+### Date / Time {#iso19139-elem-gmd-dateTime-gmd-DQ_Element-a5f46c00ce539dddadc06ba486322a5b}
+
+Name
+
+:
+
+> gmd:dateTime
+
+Context
+
+:
+
+> gmd:DQ_Element
+
+Description
+
+:
+
+```{=html}
+Date or range of dates on which a data quality measure was
+ applied
+```
+### Date type {#iso19139-elem-gmd-dateType-7d228e2ac6b4932f0e011cc2521acccb}
+
+Name
+
+:
+
+> gmd:dateType
+
+Description
+
+:
+
+```{=html}
+Event used for reference date
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Definition {#iso19139-elem-gmd-definition-f8069fba68fd297eeca2c4a772339bab}
+
+Name
+
+:
+
+> gmd:definition
+
+Description
+
+:
+
+```{=html}
+Definition of the extended element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Delivery point {#iso19139-elem-gmd-deliveryPoint-4d1627af441e956ac873875949365c46}
+
+Name
+
+:
+
+> gmd:deliveryPoint
+
+Description
+
+:
+
+```{=html}
+Address line for the location (as described in ISO 11180, annex
+ A)
+```
+### Denominator {#iso19139-elem-gmd-denominator-e807028ba183b3decd6aa631d0ca1ca3}
+
+Name
+
+:
+
+> gmd:denominator
+
+Description
+
+:
+
+```{=html}
+The number below the line in a vulgar fraction
+```
+
+Condition
+
+:
+
+> add either a denominator or a distance
+
+Recommended values
+
+| code | label |
+|---------|-------------|
+| 5000 | 1:5´000 |
+| 10000 | 1:10´000 |
+| 25000 | 1:25´000 |
+| 50000 | 1:50´000 |
+| 100000 | 1:100´000 |
+| 200000 | 1:200´000 |
+| 300000 | 1:300´000 |
+| 500000 | 1:500´000 |
+| 1000000 | 1:1´000´000 |
+
+### Density {#iso19139-elem-gmd-density-91b875707b7dd43cd669efc4974331e4}
+
+Name
+
+:
+
+> gmd:density
+
+Description
+
+:
+
+```{=html}
+Density at which the data is recorded
+```
+### Density units {#iso19139-elem-gmd-densityUnits-8ce9ed433e80ccefc11d3af968194b20}
+
+Name
+
+:
+
+> gmd:densityUnits
+
+Description
+
+:
+
+```{=html}
+Units of measure for the recording density
+```
+
+Condition
+
+:
+
+> conditional
+
+### Describes {#iso19139-elem-gmd-describes-ea7ef755fceda2ec8b1bf4486f5572bf}
+
+Name
+
+:
+
+> gmd:describes
+
+Description
+
+:
+
+```{=html}
+Describes
+```
+### Description {#iso19139-elem-gmd-description-eaa9ebfedd88eeab4424b4a0ede4ce7d}
+
+Name
+
+:
+
+> gmd:description
+
+Description
+
+:
+
+```{=html}
+Description of the event, including related parameters or
+ tolerances
+```
+### Description {#iso19139-elem-gmd-description-gmd-MD_AbstractClass-34fc68cb0bdaee5b3d63b2326c7869b3}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:MD_AbstractClass
+
+Description
+
+:
+
+```{=html}
+Description
+```
+### Description {#iso19139-elem-gmd-description-LI_ProcessStep-f1b053819d7813cf9bd105eadd7570bf}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> LI_ProcessStep
+
+Description
+
+:
+
+```{=html}
+Description of the event, including related parameters or
+ tolerances
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Description {#iso19139-elem-gmd-description-LI_Source-3e33abacd589d6d2d76d05d70e90613b}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> LI_Source
+
+Description
+
+:
+
+```{=html}
+Detailed description of the level of the source data
+```
+### Description {#iso19139-elem-gmd-description-gmd-EX_Extent-5b2d427d98a833b825066fc5d95dbcb9}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:EX_Extent
+
+Description
+
+:
+
+```{=html}
+Spatial and temporal extent for the referring object
+```
+### Description {#iso19139-elem-gmd-description-gmd-CI_OnlineResource-7b3dd389b32eff7af6fc0ce939edd2f7}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:CI_OnlineResource
+
+Description
+
+:
+
+```{=html}
+Detailed text description of what the online resource is/does
+```
+Recommended values
+
+| code | label |
+|-----------------------------------------------|---------------------------------------------------------------------------------|
+| | ETRS89 / LAEA Europe |
+| | Belge 1972 / Belgian Lambert 72 |
+| | ETRS89-XYZ: 3D Cartesian in ETRS89 |
+| | ETRS89-GRS80h: 3D geodetic in ETRS89 on GRS80 |
+| | ETRS89-GRS802D: geodetic in ETRS89 on GRS80 |
+| | ETRS89-LAEA2D: LAEA projection in ETRS89 on GRS80 |
+| | ETRS89-LCC2D: LCC projection in ETRS89 on GRS80 |
+| | ETRS89-TM26N2D: TM projection in ETRS89 on GRS80, zone 26N (30°W to 24°W) |
+| | ETRS89-TM27N2D: TM projection in ETRS89 on GRS80, zone 27N (24°W to 18°W) |
+| | ETRS89-TM28N: 2D TM projection in ETRS89 on GRS80, zone 28N (18°W to 12°W) |
+| | ETRS89-TM29N: 2D TM projection in ETRS89 on GRS80, zone 29N (12°W to 6°W) |
+| | ETRS89-TM30N: 2D TM projection in ETRS89 on GRS80, zone 30N (6°W to 0°) |
+| | ETRS89-TM31N: 2D TM projection in ETRS89 on GRS80, zone 31N (0° to 6°E) |
+| | ETRS89-TM32N: 2D TM projection in ETRS89 on GRS80, zone 32N (6°E to 12°E) |
+| | ETRS89-TM33N: 2D TM projection in ETRS89 on GRS80, zone 33N (12°E to 18°E) |
+| | ETRS89-TM34N: 2D TM projection in ETRS89 on GRS80, zone 34N (18°E to 24°E) |
+| | ETRS89-TM35N: 2D TM projection in ETRS89 on GRS80, zone 35N (24°E to 30°E) |
+| | ETRS89-TM36N: 2D TM projection in ETRS89 on GRS80, zone 36N (30°E to 36°E) |
+| | ETRS89-TM37N: 2D TM projection in ETRS89 on GRS80, zone 37N (36°E to 42°E) |
+| | ETRS89-TM38N: 2D TM projection in ETRS89 on GRS80, zone 38N (42°E to 48°E) |
+| | ETRS89-TM39N: 2D TM projection in ETRS89 on GRS80, zone 39N (48°E to 54°E) |
+| | EVRS: Height in EVRS |
+| | ETRS89-GRS80-EVRS: 3D compound: 2D geodetic in ETRS89 on GRS80, and EVRS height |
+| | RGF93 / Lambert-93 |
+| | WGS 84 / UTM zone 20N |
+| | RGFG95 / UTM zone 22N |
+| | RGR92 / UTM zone 40S |
+| | RGSPM06 / UTM zone 21N |
+| | RGM04 / UTM zone 38S |
+
+### Description {#iso19139-elem-gmd-description-gmd-MD_CodeDomain-8103324c89de45c11315a8d351053359}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:MD_CodeDomain
+
+Description
+
+:
+
+```{=html}
+Description of the code domain
+```
+### Value description {#iso19139-elem-gmd-description-gmd-MD_CodeValue-77dfb024af10e6d862075b803cc20dbf}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Description of the value
+```
+### Description {#iso19139-elem-gmd-description-gmd-MD_Attribute-75d5033891a8a34341d31ef9309f59b4}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:MD_Attribute
+
+Description
+
+:
+
+```{=html}
+Attribute description
+```
+### Description {#iso19139-elem-gmd-description-gmd-MD_Role-c9f409ac11c4188ce914585f8c21e5c9}
+
+Name
+
+:
+
+> gmd:description
+
+Context
+
+:
+
+> gmd:MD_Role
+
+Description
+
+:
+
+```{=html}
+Role description
+```
+### Descriptive keywords {#iso19139-elem-gmd-descriptiveKeywords-d9044aa0856cf55d016da575dc037fa3}
+
+Name
+
+:
+
+> gmd:descriptiveKeywords
+
+Description
+
+:
+
+```{=html}
+Provides category keywords, their type, and reference source
+```
+### Descriptor {#iso19139-elem-gmd-descriptor-3b92c037212e359ee64699ddc5187d64}
+
+Name
+
+:
+
+> gmd:descriptor
+
+Description
+
+:
+
+```{=html}
+Description of the range of a cell measurement value
+```
+### Dimension {#iso19139-elem-gmd-dimension-21ead8c88a2cce69c91c967de032bb13}
+
+Name
+
+:
+
+> gmd:dimension
+
+Description
+
+:
+
+```{=html}
+Information on the dimensions of the cell measurement value
+```
+### Dimension name {#iso19139-elem-gmd-dimensionName-db894579835c31371c0bf5b98ec194dc}
+
+Name
+
+:
+
+> gmd:dimensionName
+
+Description
+
+:
+
+```{=html}
+Name of the axis
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Dimension size {#iso19139-elem-gmd-dimensionSize-6d8bbb1333af97b4020cd56044998ea9}
+
+Name
+
+:
+
+> gmd:dimensionSize
+
+Description
+
+:
+
+```{=html}
+Number of elements along the axis
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Distance {#iso19139-elem-gmd-distance-7b7fc9e19c5ebb9644dc51880d95a12d}
+
+Name
+
+:
+
+> gmd:distance
+
+Description
+
+:
+
+```{=html}
+Ground sample distance
+```
+
+Condition
+
+:
+
+> Provide a distance if no equivalent Scale is documented
+
+Recommended values
+
+| code | label |
+|------|-------|
+| 0.10 | 10 cm |
+| 0.25 | 25 cm |
+| 0.50 | 50 cm |
+| 1 | 1 m |
+| 30 | 30 m |
+| 100 | 100 m |
+
+``` xml
+
+ 100
+
+```
+
+### Distribution format {#iso19139-elem-gmd-distributionFormat-5cad81c9a7af3991db918a5e8fc0c596}
+
+Name
+
+:
+
+> gmd:distributionFormat
+
+Description
+
+:
+
+```{=html}
+Provides a description of the format of the data to be
+ distributed
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+ GTiff
+
+
+
+
+
+
+```
+
+### Distribution Information {#iso19139-elem-gmd-distributionInfo-3bddab6fda29c9ebd6f0ece68843fcff}
+
+Name
+
+:
+
+> gmd:distributionInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the distributor of and options for obtaining the
+ resource(s)
+```
+``` xml
+
+
+
+
+
+ GTiff
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.eea.europa.eu/data-and-maps/data/ds_resolveuid/d851e1b7f678468b8f0b1b98930ba3e1
+
+
+
+ WWW:LINK-1.0-http--link
+
+
+
+
+
+
+
+
+
+
+```
+
+### Distribution / Order Process {#iso19139-elem-gmd-distributionOrderProcess-621478a21f4e3c305dc87af00248e875}
+
+Name
+
+:
+
+> gmd:distributionOrderProcess
+
+Description
+
+:
+
+```{=html}
+Provides information about how the resource may be obtained, and related
+ instructions and fee information
+```
+### Distributor {#iso19139-elem-gmd-distributor-b64067d4aecef8f15cc5a182fd00b195}
+
+Name
+
+:
+
+> gmd:distributor
+
+Description
+
+:
+
+```{=html}
+Provides information about the distributor
+```
+### Distributor contact {#iso19139-elem-gmd-distributorContact-57afbc495ed57e4d90c77442277e6961}
+
+Name
+
+:
+
+> gmd:distributorContact
+
+Description
+
+:
+
+```{=html}
+Party from whom the resource may be obtained. This list need not be
+ exhaustive
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Distributor format {#iso19139-elem-gmd-distributorFormat-d5712aab561d34322dd8328ad9362df6}
+
+Name
+
+:
+
+> gmd:distributorFormat
+
+Description
+
+:
+
+```{=html}
+Provides information about the format used by the distributor
+```
+
+Condition
+
+:
+
+> conditional
+
+### Distributor transfer options {#iso19139-elem-gmd-distributorTransferOptions-6149d8c29d10ec5cf30b596582015a41}
+
+Name
+
+:
+
+> gmd:distributorTransferOptions
+
+Description
+
+:
+
+```{=html}
+Provides information about the technical means and media used by the
+ distributor
+```
+### Domain code {#iso19139-elem-gmd-domainCode-7ab4da558ea7aa9973cc9bb4514b14fe}
+
+Name
+
+:
+
+> gmd:domainCode
+
+Description
+
+:
+
+```{=html}
+Three digit code assigned to the extended element
+```
+### Domain of validity {#iso19139-elem-gmd-domainOfValidity-3b8814768dfd794c8bf6114e32bd5464}
+
+Name
+
+:
+
+> gmd:domainOfValidity
+
+Description
+
+:
+
+```{=html}
+Range which is valid for the referencesystem
+```
+### Domain value {#iso19139-elem-gmd-domainValue-d43089dafdacd9f762bfcebf7d39f850}
+
+Name
+
+:
+
+> gmd:domainValue
+
+Description
+
+:
+
+```{=html}
+Valid values that can be assigned to the extended element
+```
+### Absolute external positional accuracy {#iso19139-elem-gmd-DQ_AbsoluteExternalPositionalAccuracy-2d3004ba04cb5440553a71f72784b835}
+
+Name
+
+:
+
+> gmd:DQ_AbsoluteExternalPositionalAccuracy
+
+Description
+
+:
+
+```{=html}
+Closeness of reported coordinate values to values accepted as or being
+ true
+```
+### Accuracy of time measurement {#iso19139-elem-gmd-DQ_AccuracyOfATimeMeasurement-350c5e543ca98de6c417b2dfcec11ad2}
+
+Name
+
+:
+
+> gmd:DQ_AccuracyOfATimeMeasurement
+
+Description
+
+:
+
+```{=html}
+Correctness of the temporal references of an item (reporting of error in time
+ measurement)
+```
+### Completeness commission {#iso19139-elem-gmd-DQ_CompletenessCommission-3eb2187eca9bc68201978727eda4d550}
+
+Name
+
+:
+
+> gmd:DQ_CompletenessCommission
+
+Description
+
+:
+
+```{=html}
+Excess data present in the dataset, as described by the scope
+```
+### Completeness omission {#iso19139-elem-gmd-DQ_CompletenessOmission-0a19919745deecaf08e057f9d745bf9a}
+
+Name
+
+:
+
+> gmd:DQ_CompletenessOmission
+
+Description
+
+:
+
+```{=html}
+Data absent from the dataset, as described by the scope
+```
+### Conceptual consistency {#iso19139-elem-gmd-DQ_ConceptualConsistency-d42ad4a3a30578c7431606e8c1df4df8}
+
+Name
+
+:
+
+> gmd:DQ_ConceptualConsistency
+
+Description
+
+:
+
+```{=html}
+Adherence to rules of the conceptual schema
+```
+### Conformance result {#iso19139-elem-gmd-DQ_ConformanceResult-58ea50589a06c432ba3c0c1fc40caaf7}
+
+Name
+
+:
+
+> gmd:DQ_ConformanceResult
+
+Description
+
+:
+
+```{=html}
+Information about the outcome of evaluating the obtained value (or set of
+ values) against a specified acceptable conformance quality level
+```
+### Data quality {#iso19139-elem-gmd-DQ_DataQuality-16d17a37284f157b42d492a5960b5171}
+
+Name
+
+:
+
+> gmd:DQ_DataQuality
+
+Description
+
+:
+
+```{=html}
+Quality information for the data specified by a data quality
+ scope
+```
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+ The data set production implied 2 steps. First re-classification of
+ CORINE Land Cover 2006 and bathymetry data using the 7 terrestrial (urban, cropland,
+ grassland, woodland and forest, heathland and shrub, sparsely vegetated land,
+ wetland), 1 freshwater (river and lakes), and 4 marine (marine inlets and transitional
+ waters, coastal, shelf, open ocean) classes of the MAES ecosystem typology (Maes et
+ al., 2013). The classes also provide links to major policy lines such as agriculture,
+ forestry, territorial cohesion, water and marine related policies. The second step
+ comprised refinement of the ecosystem types by attributing EUNIS habitat information
+ to each ecosystem type (see http://eunis.eea.europa.eu/habitats.jsp). The refinement
+ process used reference data such as potential natural vegetation, elevation, slope,
+ aspect, soil, geology, environmental regions and other spatial referenced information
+ which allowed attribution of the EUNIS habitat characteristics to the spatial mapping
+ units of the MAES ecosystem types. The geometric and thematic accuracy of EUNIS class
+ presence was also estimated and mapped. The method is described in the EEA Technical
+ Report 06/2015: European Ecosystem Assessment – Concept, Data, and Implementation.
+ The basis for the update was CORINE land cover 2006 (CLC 2006). It includes Albania,
+ Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic,
+ Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Kosovo
+ (under UNSCR 1244/99), Latvia, Liechtenstein, Lithuania, Luxembourg, the former
+ Yugoslavian Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland,
+ Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
+ the United Kingdom. For Greece that has not participated in the CLC 2006 activity the
+ CLC 2000 data was used instead.
+
+
+
+
+
+
+```
+
+### Domain consistency {#iso19139-elem-gmd-DQ_DomainConsistency-b77b3e42dfbc1799faaf486b19f37274}
+
+Name
+
+:
+
+> gmd:DQ_DomainConsistency
+
+Description
+
+:
+
+```{=html}
+Adherence of values to the value domains
+```
+### Evaluation method type code {#iso19139-elem-gmd-DQ_EvaluationMethodTypeCode-ef1611d0cbbf6e1995668d2724dee5d0}
+
+Name
+
+:
+
+> gmd:DQ_EvaluationMethodTypeCode
+
+Description
+
+:
+
+```{=html}
+type of method for evaluating an identified data quality
+ measure
+```
+### Standard codelists Evaluation method type code (gmd:DQ_EvaluationMethodTypeCode)
+
+| code | label | description |
+|----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| directInternal | Direct internal | Method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated |
+| directExternal | Direct external | Method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data external to the dataset being evaluated is required |
+| indirect | Indirect | Method of evaluating the quality of a dataset based on external knowledge |
+
+### Format consistency {#iso19139-elem-gmd-DQ_FormatConsistency-19459f698decb189aed186574d4e433e}
+
+Name
+
+:
+
+> gmd:DQ_FormatConsistency
+
+Description
+
+:
+
+```{=html}
+Degree to which data is stored in accordance with the physical structure of the
+ dataset, as described by the scope
+```
+### Gridded data positional accuracy {#iso19139-elem-gmd-DQ_GriddedDataPositionalAccuracy-fc226f8ad8fedced9779bffe9d4b6db5}
+
+Name
+
+:
+
+> gmd:DQ_GriddedDataPositionalAccuracy
+
+Description
+
+:
+
+```{=html}
+Closeness of gridded data position values to values accepted as or being
+ true
+```
+### Non quantitative attribute accuracy {#iso19139-elem-gmd-DQ_NonQuantitativeAttributeAccuracy-6dd0c58c687f85dca3f14390846b4519}
+
+Name
+
+:
+
+> gmd:DQ_NonQuantitativeAttributeAccuracy
+
+Description
+
+:
+
+```{=html}
+Correctness of non-quantitative attributes
+```
+### Quantitative attribute accuracy {#iso19139-elem-gmd-DQ_QuantitativeAttributeAccuracy-318f4688c57ecac2edb9e81237c188f7}
+
+Name
+
+:
+
+> gmd:DQ_QuantitativeAttributeAccuracy
+
+Description
+
+:
+
+```{=html}
+Accuracy of quantitative attributes
+```
+### Quantitative result {#iso19139-elem-gmd-DQ_QuantitativeResult-9ff68c61fe2bfe850ba1c5da5f0475f8}
+
+Name
+
+:
+
+> gmd:DQ_QuantitativeResult
+
+Description
+
+:
+
+```{=html}
+The values or information about the value(s) (or set of values) obtained from
+ applying a data quality measure
+```
+### Relative internal positional accuracy {#iso19139-elem-gmd-DQ_RelativeInternalPositionalAccuracy-9d1661d32093ae34be463172ee4171b4}
+
+Name
+
+:
+
+> gmd:DQ_RelativeInternalPositionalAccuracy
+
+Description
+
+:
+
+```{=html}
+Closeness of the relative positions of features in the scope to their
+ respective relative positions accepted as or being true
+```
+### Scope {#iso19139-elem-gmd-DQ_Scope-bd775cb6e23ca10fa168f6837f60f149}
+
+Name
+
+:
+
+> gmd:DQ_Scope
+
+Description
+
+:
+
+```{=html}
+Description of the data specified by the scope
+```
+```{=html}
+extent of characteristic(s) of the data for which quality information is
+ reported
+```
+``` xml
+
+
+
+
+
+```
+
+### Temporal consistency {#iso19139-elem-gmd-DQ_TemporalConsistency-cb9d4597a464c61d15952962479895d0}
+
+Name
+
+:
+
+> gmd:DQ_TemporalConsistency
+
+Description
+
+:
+
+```{=html}
+Correctness of ordered events or sequences, if reported
+```
+### Temporal validity {#iso19139-elem-gmd-DQ_TemporalValidity-fc6776c73908af8274103023abfb106c}
+
+Name
+
+:
+
+> gmd:DQ_TemporalValidity
+
+Description
+
+:
+
+```{=html}
+Validity of data specified by the scope with respect to time
+```
+### Thematic classification correctness {#iso19139-elem-gmd-DQ_ThematicClassificationCorrectness-bacc4f5d13c268c61ce4aaad44eacb00}
+
+Name
+
+:
+
+> gmd:DQ_ThematicClassificationCorrectness
+
+Description
+
+:
+
+```{=html}
+Comparison of the classes assigned to features or their attributes to a
+ universe of discourse
+```
+### Topological consistency {#iso19139-elem-gmd-DQ_TopologicalConsistency-14d0182e0c62de72433c7f3440489d0b}
+
+Name
+
+:
+
+> gmd:DQ_TopologicalConsistency
+
+Description
+
+:
+
+```{=html}
+Correctness of the explicitly encoded topological characteristics of the
+ dataset as described by the scope
+```
+### DS_Association {#iso19139-elem-gmd-DS_Association-ae4acbd2f543a91f8514b07a7f469222}
+
+Name
+
+:
+
+> gmd:DS_Association
+
+Description
+
+:
+
+```{=html}
+DS_Association
+```
+### Association Type {#iso19139-elem-gmd-DS_AssociationTypeCode-7cea96a5925a25c140f30c8577eb6813}
+
+Name
+
+:
+
+> gmd:DS_AssociationTypeCode
+
+Description
+
+:
+
+### Standard codelists Association Type (gmd:DS_AssociationTypeCode)
+
+| code | label | description |
+|------------------------|---------------------------|-------------------------------------------------------------------------------------|
+| crossReference | Cross reference | Reference from one dataset to another |
+| largerWorkCitation | Larger work citation | Reference to a master dataset of which this one is a part |
+| partOfSeamlessDatabase | Part of seamless database | Part of the same structured set of data held in a computer |
+| source | Source | Mapping and charting information from which the dataset content originates |
+| stereoMate | Stereo mate | Part of a set of imagery that when used together, provides three-dimensional images |
+
+### DS_DataSet {#iso19139-elem-gmd-DS_DataSet-197a02789f4acc67db14bbc70bdae13d}
+
+Name
+
+:
+
+> gmd:DS_DataSet
+
+Description
+
+:
+
+```{=html}
+DS_DataSet
+```
+### DS_Initiative {#iso19139-elem-gmd-DS_Initiative-99177f56cdac30c8bf8ae08807759c1e}
+
+Name
+
+:
+
+> gmd:DS_Initiative
+
+Description
+
+:
+
+```{=html}
+DS_Initiative
+```
+### Initiative Type {#iso19139-elem-gmd-DS_InitiativeTypeCode-1c08946c9359924c4e0560505d6ed92d}
+
+Name
+
+:
+
+> gmd:DS_InitiativeTypeCode
+
+Description
+
+:
+
+### Standard codelists Initiative Type (gmd:DS_InitiativeTypeCode)
+
+| code | label | description |
+|---------------|---------------|-------------------------------------------------------------|
+| campaign | Campaign | Series of organized planned actions |
+| collection | Collection | Accumulation of datasets assembled for a specific purpose |
+| exercise | Exercise | Specific performance of a function or group of functions |
+| experiment | Experiment | Process designed to find if something is effective or valid |
+| investigation | Investigation | Search or systematic inquiry |
+| mission | Mission | Specific operation of a data collection system |
+| sensor | Sensor | Device or piece of equipment which detects or records |
+| operation | Operation | Action that is part of a series of actions |
+| platform | Platform | Vehicle or other support base that holds a sensor |
+| process | Process | Method of doing something involving a number of steps |
+| program | Program | Specific planned activity |
+| project | Project | Organized undertaking, research, or development |
+| study | Study | Examination or investigation |
+| task | Task | Piece of work |
+| trial | Trial | Process of testing to discover or demonstrate something |
+
+### DS_OtherAggregate {#iso19139-elem-gmd-DS_OtherAggregate-d75f31e38b2c903fb77bee700fd67738}
+
+Name
+
+:
+
+> gmd:DS_OtherAggregate
+
+Description
+
+:
+
+```{=html}
+DS_OtherAggregate
+```
+### DS_Platform {#iso19139-elem-gmd-DS_Platform-1578fc8a9a6c1b3b001447d56dbf3be4}
+
+Name
+
+:
+
+> gmd:DS_Platform
+
+Description
+
+:
+
+```{=html}
+DS_Platform
+```
+### DS_ProductionSeries {#iso19139-elem-gmd-DS_ProductionSeries-dae0ba6d7c6e0c0774507987df27eddd}
+
+Name
+
+:
+
+> gmd:DS_ProductionSeries
+
+Description
+
+:
+
+```{=html}
+DS_ProductionSeries
+```
+### DS_Sensor {#iso19139-elem-gmd-DS_Sensor-99d8fff6c363ece657f8304d6114ae39}
+
+Name
+
+:
+
+> gmd:DS_Sensor
+
+Description
+
+:
+
+```{=html}
+DS_Sensor
+```
+### DS_Series {#iso19139-elem-gmd-DS_Series-fbba19e3982149ccdcca9e862ff983d3}
+
+Name
+
+:
+
+> gmd:DS_Series
+
+Description
+
+:
+
+```{=html}
+DS_Series
+```
+### DS_StereoMate {#iso19139-elem-gmd-DS_StereoMate-8034b71fd81debf0bc765b669a03d0d9}
+
+Name
+
+:
+
+> gmd:DS_StereoMate
+
+Description
+
+:
+
+```{=html}
+DS_StereoMate
+```
+### East bound {#iso19139-elem-gmd-eastBoundLongitude-d587a010e363b83d226fd0035e83d760}
+
+Name
+
+:
+
+> gmd:eastBoundLongitude
+
+Description
+
+:
+
+```{=html}
+Eastern-most coordinate of the limit of the dataset extent, expressed in
+ longitude in decimal degrees (positive east)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ 38.1471
+
+```
+
+### Edition {#iso19139-elem-gmd-edition-b997ad6c7eb67deed33915d4691b4059}
+
+Name
+
+:
+
+> gmd:edition
+
+Description
+
+:
+
+```{=html}
+Version of the cited resource
+```
+``` xml
+
+ 2.1
+
+```
+
+### Edition date {#iso19139-elem-gmd-editionDate-13359f87b19a72433b15f218e4026ee3}
+
+Name
+
+:
+
+> gmd:editionDate
+
+Description
+
+:
+
+```{=html}
+Date of the edition (YYYY-MM-DD)
+```
+### Electronic mail address {#iso19139-elem-gmd-electronicMailAddress-85d2f0b6b81c17b627c0640f7f49e872}
+
+Name
+
+:
+
+> gmd:electronicMailAddress
+
+Description
+
+:
+
+```{=html}
+Address of the electronic mailbox of the responsible organization or
+ individual
+```
+### Environment description {#iso19139-elem-gmd-environmentDescription-f09bfec0427a8a244e444ee494298c90}
+
+Name
+
+:
+
+> gmd:environmentDescription
+
+Description
+
+:
+
+```{=html}
+Description of the dataset in the producer_s processing environment, including
+ items such as the software, the computer operating system, file name, and the dataset
+ size
+```
+### Equivalent scale {#iso19139-elem-gmd-equivalentScale-450afb02a588e99273c4926c53620fb1}
+
+Name
+
+:
+
+> gmd:equivalentScale
+
+Description
+
+:
+
+```{=html}
+Level of detail expressed as the scale of a comparable hardcopy map or
+ chart
+```
+### Error statistic {#iso19139-elem-gmd-errorStatistic-29cd4bc20d224f1b99cd4cdc5f2afbc6}
+
+Name
+
+:
+
+> gmd:errorStatistic
+
+Description
+
+:
+
+```{=html}
+Statistical method used to determine the value
+```
+### Evaluation method description {#iso19139-elem-gmd-evaluationMethodDescription-cf7b77da8217834dc7e28ec9988dd6f7}
+
+Name
+
+:
+
+> gmd:evaluationMethodDescription
+
+Description
+
+:
+
+```{=html}
+Description of the evaluation method
+```
+### Evaluation Method {#iso19139-elem-gmd-evaluationMethodType-76b556cae8d468e563c04da4e16eaca8}
+
+Name
+
+:
+
+> gmd:evaluationMethodType
+
+Description
+
+:
+
+```{=html}
+Type of method used to evaluate quality of the dataset
+```
+### Evaluation procedure {#iso19139-elem-gmd-evaluationProcedure-2ca21440f6d62173cfe90752b85d2873}
+
+Name
+
+:
+
+> gmd:evaluationProcedure
+
+Description
+
+:
+
+```{=html}
+Reference to the procedure information
+```
+### Bounding Polygon {#iso19139-elem-gmd-EX_BoundingPolygon-59e3cbfd7fafe44aacd4370c5c9abf59}
+
+Name
+
+:
+
+> gmd:EX_BoundingPolygon
+
+Description
+
+:
+
+```{=html}
+Boundary enclosing the dataset, expressed as the closed set of (x,y)
+ coordinates of the polygon (last point replicates first point)
+```
+### Extent {#iso19139-elem-gmd-EX_Extent-d972ff3928d3ae0eb52e4853850e7484}
+
+Name
+
+:
+
+> gmd:EX_Extent
+
+Description
+
+:
+
+```{=html}
+Information about spatial, vertical, and temporal extent
+```
+### Geographic bounding box {#iso19139-elem-gmd-EX_GeographicBoundingBox-317fd5425b55f40c235ada8a89ee0519}
+
+Name
+
+:
+
+> gmd:EX_GeographicBoundingBox
+
+Description
+
+:
+
+```{=html}
+Geographic position of the dataset
+```
+``` xml
+
+
+ -33.90432
+
+
+ 38.1471
+
+
+ 26.988714
+
+
+ 60.57849
+
+
+```
+
+### Geographic description {#iso19139-elem-gmd-EX_GeographicDescription-edd6465b6e6b6a804db315a4f05303fb}
+
+Name
+
+:
+
+> gmd:EX_GeographicDescription
+
+Description
+
+:
+
+```{=html}
+Description of the geographic area using identifiers
+```
+### Spatial Temporal Extent {#iso19139-elem-gmd-EX_SpatialTemporalExtent-fb6c94e1d77ff12c5a4c7eefcca03fd0}
+
+Name
+
+:
+
+> gmd:EX_SpatialTemporalExtent
+
+Description
+
+:
+
+```{=html}
+Extent with respect to date/time and spatial boundaries
+```
+### Temporal Extent {#iso19139-elem-gmd-EX_TemporalExtent-49952a3862db59a39b01a7ad01337eab}
+
+Name
+
+:
+
+> gmd:EX_TemporalExtent
+
+Description
+
+:
+
+```{=html}
+Time period covered by the content of the dataset
+```
+``` xml
+
+
+
+ 2006-01-01
+ 2006-12-31
+
+
+
+```
+
+### Vertical extent {#iso19139-elem-gmd-EX_VerticalExtent-03de82207a2d25d3d8106293de357342}
+
+Name
+
+:
+
+> gmd:EX_VerticalExtent
+
+Description
+
+:
+
+```{=html}
+Vertical domain of dataset
+```
+### Explanation {#iso19139-elem-gmd-explanation-a2ff7a210f7f4e385b3f4bc09536eb0b}
+
+Name
+
+:
+
+> gmd:explanation
+
+Description
+
+:
+
+```{=html}
+Explanation of the meaning of conformance for this result
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Extended element information {#iso19139-elem-gmd-extendedElementInformation-df23e4d221faf1125b8d660000cc942d}
+
+Name
+
+:
+
+> gmd:extendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Provides information about a new metadata element, not found in ISO 19115,
+ which is required to describe geographic data
+```
+### Extension Online resource {#iso19139-elem-gmd-extensionOnLineResource-f12177f44a4f70bde032489efa83c4d5}
+
+Name
+
+:
+
+> gmd:extensionOnLineResource
+
+Description
+
+:
+
+```{=html}
+Information about on-line sources containing the community profile name and the
+ extended metadata elements. Information for all new metadata elements
+```
+### Extent {#iso19139-elem-gmd-extent-gmd-MD_DataIdentification-ef6cafbbcf83a9c5f548fc0e2a6e4a67}
+
+Name
+
+:
+
+> gmd:extent
+
+Context
+
+:
+
+> gmd:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Extent information including the bounding polygon, vertical, and temporal
+ extent of the dataset
+```
+### Extent {#iso19139-elem-gmd-extent-gmd-DQ_Scope-cf877c587ba9ea326503a5f7f10db5b4}
+
+Name
+
+:
+
+> gmd:extent
+
+Context
+
+:
+
+> gmd:DQ_Scope
+
+Description
+
+:
+
+```{=html}
+Information about the horizontal, vertical and temporal extent of the data
+ specified by the scope
+```
+### Extent {#iso19139-elem-gmd-extent-gmd-EX_TemporalExtent-47e5bb94d809c840b870705288059fa9}
+
+Name
+
+:
+
+> gmd:extent
+
+Context
+
+:
+
+> gmd:EX_TemporalExtent
+
+Description
+
+:
+
+```{=html}
+Date and time for the content of the dataset
+```
+### Extent type code {#iso19139-elem-gmd-extentTypeCode-3ff35ceb2d2f687d2c8ce3d323884d96}
+
+Name
+
+:
+
+> gmd:extentTypeCode
+
+Description
+
+:
+
+```{=html}
+Indication of whether the bounding polygon encompasses an area covered by the
+ data or an area where data is not present. Possible values: '1' for inclusion or '0' for
+ exclusion
+```
+### Facsimile {#iso19139-elem-gmd-facsimile-b648543ae1d0726685e437bf567ad655}
+
+Name
+
+:
+
+> gmd:facsimile
+
+Description
+
+:
+
+```{=html}
+Telephone number of a facsimile machine for the responsible organization or
+ individual
+```
+### Feature attribute {#iso19139-elem-gmd-featureAttribute-ed65880b0d966b5862d0d434b26fd36b}
+
+Name
+
+:
+
+> gmd:featureAttribute
+
+Description
+
+:
+
+### Feature catalogue citation {#iso19139-elem-gmd-featureCatalogueCitation-0d490aca236a02c867c265dc0656143b}
+
+Name
+
+:
+
+> gmd:featureCatalogueCitation
+
+Description
+
+:
+
+```{=html}
+Complete bibliographic reference to one or more external feature
+ catalogues
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+```
+
+### Feature instances {#iso19139-elem-gmd-featureInstances-2ec1ea3d86d2e7b1a0438f31d90abe5a}
+
+Name
+
+:
+
+> gmd:featureInstances
+
+Description
+
+:
+
+```{=html}
+Feature instances to which the information applies
+```
+### Features {#iso19139-elem-gmd-features-0649c9efc070f5cf773f06bf959cf517}
+
+Name
+
+:
+
+> gmd:features
+
+Description
+
+:
+
+```{=html}
+Features to which the information applies
+```
+### Feature type {#iso19139-elem-gmd-featureType-1a7ddaf6d70b2bca513bbb097769f7a5}
+
+Name
+
+:
+
+> gmd:featureType
+
+Description
+
+:
+
+```{=html}
+Subset of feature types from cited feature catalogue occurring in
+ data
+```
+### Feature types {#iso19139-elem-gmd-featureTypes-57cc98cc1ff094047cfff115a60c96e3}
+
+Name
+
+:
+
+> gmd:featureTypes
+
+Description
+
+:
+
+```{=html}
+Subset of feature types from cited feature catalogue occurring in
+ data
+```
+### Fees {#iso19139-elem-gmd-fees-f12184afc6c48c767b43b36d9044e1c9}
+
+Name
+
+:
+
+> gmd:fees
+
+Description
+
+:
+
+```{=html}
+Fees and terms for retrieving the resource. Include monetary units (as
+ specified in ISO 4217)
+```
+### File decompression technique {#iso19139-elem-gmd-fileDecompressionTechnique-e3c08caebc6eb48277ca074c5e8e547a}
+
+Name
+
+:
+
+> gmd:fileDecompressionTechnique
+
+Description
+
+:
+
+```{=html}
+Recommendations of algorithms or processes that can be applied to read or
+ expand resources to which compression techniques have been applied
+```
+### File description {#iso19139-elem-gmd-fileDescription-146f4502c53733e708c1bd8a795522d7}
+
+Name
+
+:
+
+> gmd:fileDescription
+
+Description
+
+:
+
+```{=html}
+Text description of the illustration
+```
+### File identifier {#iso19139-elem-gmd-fileIdentifier-353be7794d17e5435ce2fe57d91966ba}
+
+Name
+
+:
+
+> gmd:fileIdentifier
+
+Description
+
+:
+
+```{=html}
+Unique identifier for this metadata file
+```
+``` xml
+
+ e8a366b7-0029-44d7-ae33-7578253179c0
+
+```
+
+### File name {#iso19139-elem-gmd-fileName-22a500ee0f0599f36ee1e97aff0fe087}
+
+Name
+
+:
+
+> gmd:fileName
+
+Description
+
+:
+
+```{=html}
+Name of the file that contains a graphic that provides an illustration of the
+ dataset. It could be a public image document URL.
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+ http://sdi.eea.europa.eu/public/catalogue-graphic-overview/e8a366b7-0029-44d7-ae33-7578253179c0.png
+
+
+```
+
+### File type {#iso19139-elem-gmd-fileType-b4c84bb6fe0143438998bfddb778200c}
+
+Name
+
+:
+
+> gmd:fileType
+
+Description
+
+:
+
+```{=html}
+Format in which the illustration is encoded
+```
+```{=html}
+format in which the illustration is encoded Examples: CGM, EPS, GIF, JPEG, PBM, PS,
+ TIFF, XWD
+```
+### Film distortion information availability {#iso19139-elem-gmd-filmDistortionInformationAvailability-a778dce0bc8a88cdba2c1315d18d0e28}
+
+Name
+
+:
+
+> gmd:filmDistortionInformationAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not Calibration Reseau information is
+ available
+```
+### Format distributor {#iso19139-elem-gmd-formatDistributor-36ea0561d2f735b297700bf79e7dbe09}
+
+Name
+
+:
+
+> gmd:formatDistributor
+
+Description
+
+:
+
+```{=html}
+Provides information about the distributor’s format
+```
+### Function {#iso19139-elem-gmd-function-c66a8adca4499131f846c360fca82678}
+
+Name
+
+:
+
+> gmd:function
+
+Description
+
+:
+
+```{=html}
+Code for function performed by the online resource
+```
+### Geographic element {#iso19139-elem-gmd-geographicElement-4b7f68f3310760569dbdba10bad944c2}
+
+Name
+
+:
+
+> gmd:geographicElement
+
+Description
+
+:
+
+```{=html}
+Provides geographic component of the extent of the referring
+ object
+```
+``` xml
+
+
+
+ -33.90432
+
+
+ 38.1471
+
+
+ 26.988714
+
+
+ 60.57849
+
+
+
+```
+
+### Geographic identifier {#iso19139-elem-gmd-geographicIdentifier-6e21f053992dfa6b4eb02d6b91cbbe44}
+
+Name
+
+:
+
+> gmd:geographicIdentifier
+
+Description
+
+:
+
+```{=html}
+Identifier used to represent a geographic area
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Geometric object count {#iso19139-elem-gmd-geometricObjectCount-465f480e8e30a8c083af02492722eefc}
+
+Name
+
+:
+
+> gmd:geometricObjectCount
+
+Description
+
+:
+
+```{=html}
+Total number of the point or vector object type occurring in the
+ dataset
+```
+### Geometric objects {#iso19139-elem-gmd-geometricObjects-e10321f246589a7ed91638fa939b766b}
+
+Name
+
+:
+
+> gmd:geometricObjects
+
+Description
+
+:
+
+```{=html}
+Information about the geometric objects used in the dataset
+```
+### Geometric object type {#iso19139-elem-gmd-geometricObjectType-bf17aa906a7cd305707e10d6acd0e62d}
+
+Name
+
+:
+
+> gmd:geometricObjectType
+
+Description
+
+:
+
+```{=html}
+Name of point and vector spatial objects used to locate zero-, one-, and
+ two-dimensional spatial locations in the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### GeoreferencedParameters {#iso19139-elem-gmd-georeferencedParameters-252d097ee7c185a35fde200a066e1c51}
+
+Name
+
+:
+
+> gmd:georeferencedParameters
+
+Description
+
+:
+
+```{=html}
+GeoreferencedParameters
+```
+### Graphic overview {#iso19139-elem-gmd-graphicOverview-f08bb356ded2aa6be5b6e67f15770173}
+
+Name
+
+:
+
+> gmd:graphicOverview
+
+Description
+
+:
+
+```{=html}
+Provides a graphic that illustrates the resource(s) (should include a legend
+ for the graphic)
+```
+``` xml
+
+
+
+
+ http://sdi.eea.europa.eu/public/catalogue-graphic-overview/e8a366b7-0029-44d7-ae33-7578253179c0.png
+
+
+
+
+```
+
+### Graphics file {#iso19139-elem-gmd-graphicsFile-e812a025f08ccad44b6f3a37fcc7d6c5}
+
+Name
+
+:
+
+> gmd:graphicsFile
+
+Description
+
+:
+
+```{=html}
+Full application schema given as a graphics file
+```
+### Handling description {#iso19139-elem-gmd-handlingDescription-0c88196efd7b0ce89bc76138514281ff}
+
+Name
+
+:
+
+> gmd:handlingDescription
+
+Description
+
+:
+
+```{=html}
+Additional information about the restrictions on handling the
+ resource
+```
+### Has {#iso19139-elem-gmd-has-f3ff1915df87b300aba1f0a17c387f0f}
+
+Name
+
+:
+
+> gmd:has
+
+Description
+
+:
+
+```{=html}
+Has
+```
+### Hierarchy level {#iso19139-elem-gmd-hierarchyLevel-2b6d53b433d8f9c0cc58606d27eecc17}
+
+Name
+
+:
+
+> gmd:hierarchyLevel
+
+Description
+
+:
+
+```{=html}
+Scope to which the metadata applies (see annex H for more information about
+ metadata hierarchy levels)
+```
+``` xml
+
+
+
+```
+
+### Hierarchy level name {#iso19139-elem-gmd-hierarchyLevelName-1c79276b0501d07055d7480b292899f0}
+
+Name
+
+:
+
+> gmd:hierarchyLevelName
+
+Description
+
+:
+
+```{=html}
+Name of the hierarchy levels for which the metadata is provided
+```
+### Hours of service {#iso19139-elem-gmd-hoursOfService-52bbcc8182a0293962afd16ee768c579}
+
+Name
+
+:
+
+> gmd:hoursOfService
+
+Description
+
+:
+
+```{=html}
+Time period (including time zone) when individuals can contact the organization
+ or individual
+```
+### Identification info {#iso19139-elem-gmd-identificationInfo-4fe68a205ff13feeccf0b58e08f39472}
+
+Name
+
+:
+
+> gmd:identificationInfo
+
+Description
+
+:
+
+```{=html}
+Basic information about the resource(s) to which the metadata
+ applies
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+
+ The data set combines the Corine based MAES (Mapping and Assessment of
+ Ecosystems and their Services) ecosystem classes with the non-spatial EUNIS habitat
+ classification (LEVEL 1) for a better biological characterization of ecosystems across
+ Europe (EEA-39). As such it represents probabilities of EUNIS habitat presence for each
+ MAES ecosystem type.
+
+ The data set aims to combine spatially explicit land cover information with non-spatially
+ referenced habitat information to improve our knowledge about ecosystems and their
+ distribution across Europe. The work supports the MAES process, Target 2 Action 5 of the
+ implementation of the EU Biodiversity Strategy to 2020, established to achieve the Aichi
+ targets of the Convention of Biological Diversity (CBD).
+
+ The objective of the ecosystem data set produced by EEA and its Topic Centre ETC/SIA was
+ to improve the biological description of land cover based ecosystem types. It represents
+ probabilities of EUNIS habitat presence in ecosystem types at European level. Since it is
+ not based on spatial explicit mapping the spatial and thematic accuracy is not of same
+ quality as delineated maps.
+
+ The MAES ecosystem typology differentiates three levels: whereas the level 2 of the MAES
+ proposal follows closely the EUNIS level 1, the third level of the MAES typology
+ corresponds to the EUNIS level 2. This level will be the base for the mapping approach.
+
+
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+ http://www.eea.europa.eu
+
+
+ WWW:LINK-1.0-http--link
+
+
+ Europen Environment Agency public website
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ http://sdi.eea.europa.eu/public/catalogue-graphic-overview/e8a366b7-0029-44d7-ae33-7578253179c0.png
+
+
+
+
+
+
+
+ Land cover
+
+
+ Habitats and biotopes
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.httpinspireeceuropaeutheme-theme
+
+
+
+
+
+
+
+
+
+
+
+ ecosystem
+
+
+ ecosystem type
+
+
+ land cover
+
+
+ environmental assessment
+
+
+ habitat
+
+
+
+
+
+
+
+ GEMET - Concepts, version 2.4
+
+
+
+
+ 2010-01-13
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.gemet
+
+
+
+
+
+
+
+
+
+
+
+ Unless otherwise indicated, re-use of content on the EEA website
+ for commercial or non-commercial purposes is permitted free of charge, provided that
+ the source is acknowledged. The EEA re-use policy follows Directive 2003/98/EC of the
+ European Parliament and the Council on the re-use of public sector information
+ throughout the European Union and Commission Decision 2006/291/EC, Euratom on the
+ re-use of Commission information. The EEA accepts no responsibility or liability
+ whatsoever for the re-use of content accessible on its website. Any inquiries about
+ re-use of content on the EEA website should be addressed to Ove Caspersen, EEA,
+ Kongens Nytorv 6, DK-1050 Copenhagen K, Tel +45 33 36 71 00, Fax +45 33 36 71 99,
+ e-mail copyrights at eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+ no limitations
+
+
+
+
+
+
+
+
+
+ 100
+
+
+
+
+
+
+
+ biota
+
+
+ environment
+
+
+
+
+
+
+ -33.90432
+
+
+ 38.1471
+
+
+ 26.988714
+
+
+ 60.57849
+
+
+
+
+
+
+
+
+
+
+
+ 2006-01-01
+ 2006-12-31
+
+
+
+
+
+
+
+
+```
+
+### Identifier {#iso19139-elem-gmd-identifier-c4f31fd808ee0eaa1e5525c5ff0edd23}
+
+Name
+
+:
+
+> gmd:identifier
+
+Description
+
+:
+
+```{=html}
+Unique identifier for the resource. EXAMPLE: Universal Product Code (UPC),
+ National Stock Number (NSN)
+```
+### Citation identifier {#iso19139-elem-gmd-identifier-gmd-CI_Citation-20221b6aedbb9cb4a515e5d396ea859e}
+
+Name
+
+:
+
+> gmd:identifier
+
+Context
+
+:
+
+> gmd:CI_Citation
+
+Description
+
+:
+
+```{=html}
+Identifier of the citation
+```
+### Identifier {#iso19139-elem-gmd-identifier-gmd-MD_Authority-85169d0c6f948867bbf79c0907e0fdfe}
+
+Name
+
+:
+
+> gmd:identifier
+
+Context
+
+:
+
+> gmd:MD_Authority
+
+Description
+
+:
+
+```{=html}
+Identifier which belongs to the authority
+```
+### Illumination azimuth angle {#iso19139-elem-gmd-illuminationAzimuthAngle-9c67704111e2bddeebc608da99ff3d92}
+
+Name
+
+:
+
+> gmd:illuminationAzimuthAngle
+
+Description
+
+:
+
+```{=html}
+Illumination azimuth measured in degrees clockwise from true north at the time
+ the image is taken. For images from a scanning device, refer to the centre pixel of the
+ image
+```
+### Illumination elevation angle {#iso19139-elem-gmd-illuminationElevationAngle-fadd6e99799d86a8d2817d3154e4c615}
+
+Name
+
+:
+
+> gmd:illuminationElevationAngle
+
+Description
+
+:
+
+```{=html}
+Illumination elevation measured in degrees clockwise from the target plane at
+ intersection of the optical line of sight with the Earth_s surface. For images from a
+ scanning device, refer to the centre pixel of the image
+```
+### Image quality code {#iso19139-elem-gmd-imageQualityCode-fc1f077f8b9f3893a031f8b27beaac71}
+
+Name
+
+:
+
+> gmd:imageQualityCode
+
+Description
+
+:
+
+```{=html}
+Specifies the image quality
+```
+```{=html}
+specifies the image quality
+```
+### Imaging condition {#iso19139-elem-gmd-imagingCondition-e9c7d7a924d3b3e2c92c646337c793d1}
+
+Name
+
+:
+
+> gmd:imagingCondition
+
+Description
+
+:
+
+```{=html}
+Conditions affected the image
+```
+### Included with dataset {#iso19139-elem-gmd-includedWithDataset-0148507e25f25653e843ec66cf6cb878}
+
+Name
+
+:
+
+> gmd:includedWithDataset
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the feature catalogue is included with the
+ dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ false
+
+```
+
+### Individual name {#iso19139-elem-gmd-individualName-60930dbb71e453e392be49149226d811}
+
+Name
+
+:
+
+> gmd:individualName
+
+Description
+
+:
+
+```{=html}
+Name of the responsible person- surname, given name, title separated by a
+ delimiter
+```
+### Initiative Type {#iso19139-elem-gmd-initiativeType-94726ec412440a3e8b82802d3ebffa3e}
+
+Name
+
+:
+
+> gmd:initiativeType
+
+Description
+
+:
+
+```{=html}
+Type of initiative under which the aggregate dataset was produced
+```
+### ISBN {#iso19139-elem-gmd-ISBN-a7253d49f82ee6bb2b5a531fb70a3820}
+
+Name
+
+:
+
+> gmd:ISBN
+
+Description
+
+:
+
+```{=html}
+International Standard Book Number
+```
+### ISSN {#iso19139-elem-gmd-ISSN-9bed905bb20090904f7fc371e411169b}
+
+Name
+
+:
+
+> gmd:ISSN
+
+Description
+
+:
+
+```{=html}
+International Standard Serial Number
+```
+### Issue identification {#iso19139-elem-gmd-issueIdentification-4722b88dd305fc8ebd00fbf712853119}
+
+Name
+
+:
+
+> gmd:issueIdentification
+
+Description
+
+:
+
+```{=html}
+Information identifying the issue of the series
+```
+### Keyword {#iso19139-elem-gmd-keyword-9589bb538b9fd1c10931fcfb09274b90}
+
+Name
+
+:
+
+> gmd:keyword
+
+Description
+
+:
+
+```{=html}
+Commonly used word(s) or formalised word(s) or phrase(s) used to describe the
+ subject
+```
+### Metadata language {#iso19139-elem-gmd-language-98a1fec5ea30c100ef63f1ca4bd6dbdb}
+
+Name
+
+:
+
+> gmd:language
+
+Description
+
+:
+
+```{=html}
+Language used for documenting metadata
+```
+
+Condition
+
+:
+
+> conditional
+
+### Language {#iso19139-elem-gmd-language-gmd-MD_DataIdentification-beb634f41383e04b84205a263a51618b}
+
+Name
+
+:
+
+> gmd:language
+
+Context
+
+:
+
+> gmd:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Language(s) used within the dataset
+```
+```{=html}
+language(s) used within the dataset
+```
+### Language {#iso19139-elem-gmd-language-gmd-MD_FeatureCatalogueDescription-71920ebc293a169b2af5b096755545eb}
+
+Name
+
+:
+
+> gmd:language
+
+Context
+
+:
+
+> gmd:MD_FeatureCatalogueDescription
+
+Description
+
+:
+
+```{=html}
+Language(s) used within the catalogue
+```
+### Language {#iso19139-elem-gmd-languageCode-09e902b21da745d04364587ce8c4b5de}
+
+Name
+
+:
+
+> gmd:languageCode
+
+Description
+
+:
+
+```{=html}
+Language code
+```
+### ISO Language code {#iso19139-elem-gmd-LanguageCode-c2d8944958443fe48234c4019a990643}
+
+Name
+
+:
+
+> gmd:LanguageCode
+
+Description
+
+:
+
+```{=html}
+Language code
+```
+### Lens distortion information availability {#iso19139-elem-gmd-lensDistortionInformationAvailability-16305ddb1c7fe831e1d0bd2856b18441}
+
+Name
+
+:
+
+> gmd:lensDistortionInformationAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not lens aberration correction information is
+ available
+```
+### Hierarchy level {#iso19139-elem-gmd-level-cb01720c4e97d12d16a28aea6ce52f8a}
+
+Name
+
+:
+
+> gmd:level
+
+Description
+
+:
+
+```{=html}
+Hierarchical level of the data specified by the scope
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+```
+
+### Level description {#iso19139-elem-gmd-levelDescription-a2ac63be295342f5027433592380cbe8}
+
+Name
+
+:
+
+> gmd:levelDescription
+
+Description
+
+:
+
+```{=html}
+Detailed description about the level of the data specified by the
+ scope
+```
+### Lineage {#iso19139-elem-gmd-LI_Lineage-d8883febc8ab15d913eae9f7582b776d}
+
+Name
+
+:
+
+> gmd:LI_Lineage
+
+Description
+
+:
+
+```{=html}
+Information about the events or source data used in constructing the data
+ specified by the scope or lack of knowledge about lineage
+```
+``` xml
+
+
+ The data set production implied 2 steps. First re-classification of
+ CORINE Land Cover 2006 and bathymetry data using the 7 terrestrial (urban, cropland,
+ grassland, woodland and forest, heathland and shrub, sparsely vegetated land,
+ wetland), 1 freshwater (river and lakes), and 4 marine (marine inlets and transitional
+ waters, coastal, shelf, open ocean) classes of the MAES ecosystem typology (Maes et
+ al., 2013). The classes also provide links to major policy lines such as agriculture,
+ forestry, territorial cohesion, water and marine related policies. The second step
+ comprised refinement of the ecosystem types by attributing EUNIS habitat information
+ to each ecosystem type (see http://eunis.eea.europa.eu/habitats.jsp). The refinement
+ process used reference data such as potential natural vegetation, elevation, slope,
+ aspect, soil, geology, environmental regions and other spatial referenced information
+ which allowed attribution of the EUNIS habitat characteristics to the spatial mapping
+ units of the MAES ecosystem types. The geometric and thematic accuracy of EUNIS class
+ presence was also estimated and mapped. The method is described in the EEA Technical
+ Report 06/2015: European Ecosystem Assessment – Concept, Data, and Implementation.
+ The basis for the update was CORINE land cover 2006 (CLC 2006). It includes Albania,
+ Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic,
+ Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Kosovo
+ (under UNSCR 1244/99), Latvia, Liechtenstein, Lithuania, Luxembourg, the former
+ Yugoslavian Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland,
+ Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
+ the United Kingdom. For Greece that has not participated in the CLC 2006 activity the
+ CLC 2000 data was used instead.
+
+
+
+
+```
+
+### Process step {#iso19139-elem-gmd-LI_ProcessStep-df37dc21ccbd656f4dd53e1e6e4aa42e}
+
+Name
+
+:
+
+> gmd:LI_ProcessStep
+
+Description
+
+:
+
+```{=html}
+Information about an event in the creation process for the data specified by
+ the scope
+```
+```{=html}
+information about an event or transformation in the life of a dataset including the
+ process used to maintain the dataset
+```
+### Source {#iso19139-elem-gmd-LI_Source-29725376e7b2367004e7834b84786158}
+
+Name
+
+:
+
+> gmd:LI_Source
+
+Description
+
+:
+
+```{=html}
+Information about the source data used in creating the data specified by the
+ scope
+```
+### Lineage {#iso19139-elem-gmd-lineage-7ec1911d2050ab2ba82079b8fa118182}
+
+Name
+
+:
+
+> gmd:lineage
+
+Description
+
+:
+
+```{=html}
+Non-quantitative quality information about the lineage of the data specified by
+ the scope
+```
+``` xml
+
+
+
+ The data set production implied 2 steps. First re-classification of
+ CORINE Land Cover 2006 and bathymetry data using the 7 terrestrial (urban, cropland,
+ grassland, woodland and forest, heathland and shrub, sparsely vegetated land,
+ wetland), 1 freshwater (river and lakes), and 4 marine (marine inlets and transitional
+ waters, coastal, shelf, open ocean) classes of the MAES ecosystem typology (Maes et
+ al., 2013). The classes also provide links to major policy lines such as agriculture,
+ forestry, territorial cohesion, water and marine related policies. The second step
+ comprised refinement of the ecosystem types by attributing EUNIS habitat information
+ to each ecosystem type (see http://eunis.eea.europa.eu/habitats.jsp). The refinement
+ process used reference data such as potential natural vegetation, elevation, slope,
+ aspect, soil, geology, environmental regions and other spatial referenced information
+ which allowed attribution of the EUNIS habitat characteristics to the spatial mapping
+ units of the MAES ecosystem types. The geometric and thematic accuracy of EUNIS class
+ presence was also estimated and mapped. The method is described in the EEA Technical
+ Report 06/2015: European Ecosystem Assessment – Concept, Data, and Implementation.
+ The basis for the update was CORINE land cover 2006 (CLC 2006). It includes Albania,
+ Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic,
+ Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Kosovo
+ (under UNSCR 1244/99), Latvia, Liechtenstein, Lithuania, Luxembourg, the former
+ Yugoslavian Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland,
+ Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
+ the United Kingdom. For Greece that has not participated in the CLC 2006 activity the
+ CLC 2000 data was used instead.
+
+
+
+
+
+```
+
+### Linkage {#iso19139-elem-gmd-linkage-ddec55285da8318007d8ba8df6febcb5}
+
+Name
+
+:
+
+> gmd:linkage
+
+Description
+
+:
+
+```{=html}
+Location (address) for on-line access using a Uniform Resource Locator address
+ or similar addressing scheme such as http://www.statkart.no/isotc211
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Other language {#iso19139-elem-gmd-locale-826113f1d130f65f95c78f6b16227c4b}
+
+Name
+
+:
+
+> gmd:locale
+
+Description
+
+:
+
+```{=html}
+Use this section to define other metadata language (multilingual metadata).
+```
+### Localised string {#iso19139-elem-gmd-LocalisedCharacterString-9fd46342f3b1b7c5b63898df1b997f3a}
+
+Name
+
+:
+
+> gmd:LocalisedCharacterString
+
+Description
+
+:
+
+### Localised string {#iso19139-elem-gmd-localisedString-56cb8674dae4c0ea7855baaf3d864ff3}
+
+Name
+
+:
+
+> gmd:localisedString
+
+Description
+
+:
+
+### Maintenance and update frequency {#iso19139-elem-gmd-maintenanceAndUpdateFrequency-a1048fe8ad8a58b19b4a8d93d9276069}
+
+Name
+
+:
+
+> gmd:maintenanceAndUpdateFrequency
+
+Description
+
+:
+
+```{=html}
+Frequency with which changes and additions are made to the resource after the
+ initial resource is completed
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+```
+
+### Maintenance note {#iso19139-elem-gmd-maintenanceNote-9d819b6669d1940c147b60f1d769a43e}
+
+Name
+
+:
+
+> gmd:maintenanceNote
+
+Description
+
+:
+
+```{=html}
+Information regarding specific requirements for maintaining the
+ resource
+```
+### Maximum occurrence {#iso19139-elem-gmd-maximumOccurrence-586bc521966d29003dc6cea416d0cc02}
+
+Name
+
+:
+
+> gmd:maximumOccurrence
+
+Description
+
+:
+
+```{=html}
+Maximum occurrence of the extended element
+```
+### Maximum value {#iso19139-elem-gmd-maximumValue-46bb37dbbb47d975b9c88ee47687a50a}
+
+Name
+
+:
+
+> gmd:maximumValue
+
+Description
+
+:
+
+```{=html}
+Highest vertical extent contained in the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Maximum value {#iso19139-elem-gmd-maxValue-c5b953b90711bd9c01bc5efaeeeb51e1}
+
+Name
+
+:
+
+> gmd:maxValue
+
+Description
+
+:
+
+```{=html}
+Longest wavelength that the sensor is capable of collecting within a designated
+ band
+```
+### Aggregate Information {#iso19139-elem-gmd-MD_AggregateInformation-878370a145c71919312573e325a5657a}
+
+Name
+
+:
+
+> gmd:MD_AggregateInformation
+
+Description
+
+:
+
+```{=html}
+Aggregate dataset information
+```
+### Application Schema Information {#iso19139-elem-gmd-MD_ApplicationSchemaInformation-bdc5888debf009cc4d4e8527e7a46bc3}
+
+Name
+
+:
+
+> gmd:MD_ApplicationSchemaInformation
+
+Description
+
+:
+
+```{=html}
+Information about the application schema used to build the
+ dataset
+```
+### Band {#iso19139-elem-gmd-MD_Band-3997e9a8c1d5b8a25690a55dd55c107b}
+
+Name
+
+:
+
+> gmd:MD_Band
+
+Description
+
+:
+
+```{=html}
+Range of wavelengths in the electromagnetic spectrum
+```
+```{=html}
+range of wavelengths in the electromagnetic spectrum
+```
+### Browse Graphic {#iso19139-elem-gmd-MD_BrowseGraphic-bdf4d487d1e389d01ed977eb34d5fc1b}
+
+Name
+
+:
+
+> gmd:MD_BrowseGraphic
+
+Description
+
+:
+
+```{=html}
+Graphic that provides an illustration of the dataset (should include a legend
+ for the graphic)
+```
+``` xml
+
+
+
+ http://sdi.eea.europa.eu/public/catalogue-graphic-overview/e8a366b7-0029-44d7-ae33-7578253179c0.png
+
+
+
+```
+
+### Cell geometry code {#iso19139-elem-gmd-MD_CellGeometryCode-35ad1470fb7f4d2e62f3fe43080d5f6a}
+
+Name
+
+:
+
+> gmd:MD_CellGeometryCode
+
+Description
+
+:
+
+```{=html}
+code indicating whether grid data is point or area
+```
+### Standard codelists Cell geometry code (gmd:MD_CellGeometryCode)
+
+| code | label | description |
+|-------|-------|------------------------------|
+| point | Point | Each cell represents a point |
+| area | Area | Each cell represents an area |
+
+### Characterset code {#iso19139-elem-gmd-MD_CharacterSetCode-d8a4713835858ceca74003ca966d0a21}
+
+Name
+
+:
+
+> gmd:MD_CharacterSetCode
+
+Description
+
+:
+
+```{=html}
+name of the character coding standard used for the
+ resource
+```
+### Standard codelists Characterset code (gmd:MD_CharacterSetCode)
+
+| code | label | description |
+|------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| ucs2 | UCS2 | 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| ucs4 | UCS4 | 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| utf7 | UTF7 | 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf8 | UTF8 | 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf16 | UTF16 | 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| 8859part1 | 8859 Part 1 | ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 |
+| 8859part2 | 8859 Part 2 | ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 |
+| 8859part3 | 8859 Part 3 | ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 |
+| 8859part4 | 8859 Part 4 | ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 |
+| 8859part5 | 8859 Part 5 | ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet |
+| 8859part6 | 8859 Part 6 | ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet |
+| 8859part7 | 8859 Part 7 | ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet |
+| 8859part8 | 8859 Part 8 | ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet |
+| 8859part9 | 8859 Part 9 | ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 |
+| 8859part10 | 8859 Part 10 | ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 |
+| 8859part11 | 8859 Part 11 | ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet |
+| 8859part13 | 8859 Part 13 | ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 |
+| 8859part14 | 8859 Part 14 | ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) |
+| 8859part15 | 8859 Part 15 | ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 |
+| 8859part16 | 8859 Part 16 | ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 |
+| jis | JIS | Japanese code set used for electronic transmission |
+| shiftJIS | Shift JIS | Japanese code set used on MS-DOS machines |
+| eucJP | EUC JP | Japanese code set used on UNIX based machines |
+| usAscii | US ASCII | United States ASCII code set (ISO 646 US) |
+| ebcdic | EBCDIC | IBM mainframe code set |
+| eucKR | EUC KR | Korean code set |
+| big5 | Big 5 | Traditional Chinese code set used in Taiwan, Hong Kong of China and other areas |
+| GB2312 | GB2312 | Simplified Chinese code set |
+
+``` xml
+
+```
+
+### Classification code {#iso19139-elem-gmd-MD_ClassificationCode-f8c03303f33489e96e1e8063a4468c46}
+
+Name
+
+:
+
+> gmd:MD_ClassificationCode
+
+Description
+
+:
+
+```{=html}
+Name of the handling restrictions on the dataset
+```
+### Standard codelists Classification code (gmd:MD_ClassificationCode)
+
+| code | label | description |
+|--------------|--------------|--------------------------------------------------------------------------------------------|
+| unclassified | Unclassified | Available for general disclosure |
+| restricted | Restricted | Not for general disclosure |
+| confidential | Confidential | Available for someone who can be entrusted with information |
+| secret | Secret | Kept or meant to be kept private, unknown, or hidden from all but a select group of people |
+| topSecret | Top secret | Of the highest secrecy |
+
+### Constraints {#iso19139-elem-gmd-MD_Constraints-324782b12272766c3ea9027e10fb6b8a}
+
+Name
+
+:
+
+> gmd:MD_Constraints
+
+Description
+
+:
+
+``` xml
+
+
+ Unless otherwise indicated, re-use of content on the EEA website
+ for commercial or non-commercial purposes is permitted free of charge, provided that
+ the source is acknowledged. The EEA re-use policy follows Directive 2003/98/EC of the
+ European Parliament and the Council on the re-use of public sector information
+ throughout the European Union and Commission Decision 2006/291/EC, Euratom on the
+ re-use of Commission information. The EEA accepts no responsibility or liability
+ whatsoever for the re-use of content accessible on its website. Any inquiries about
+ re-use of content on the EEA website should be addressed to Ove Caspersen, EEA,
+ Kongens Nytorv 6, DK-1050 Copenhagen K, Tel +45 33 36 71 00, Fax +45 33 36 71 99,
+ e-mail copyrights at eea.europa.eu
+
+
+
+```
+
+### Content type code {#iso19139-elem-gmd-MD_CoverageContentTypeCode-3a8fb87615b97ed59c74b013dfebf5fe}
+
+Name
+
+:
+
+> gmd:MD_CoverageContentTypeCode
+
+Description
+
+:
+
+```{=html}
+specific type of information represented in the cell
+```
+### Standard codelists Content type code (gmd:MD_CoverageContentTypeCode)
+
+| code | label | description |
+|------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------|
+| image | Image | Meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter |
+| thematicClassification | Thematic classification | Code value with no quantitative meaning, used to represent a physical quantity |
+| physicalMeasurement | Physical measurement | Value in physical units of the quantity being measured |
+
+### Coverage Description {#iso19139-elem-gmd-MD_CoverageDescription-1f81296a593d08ad1a336c34877d7307}
+
+Name
+
+:
+
+> gmd:MD_CoverageDescription
+
+Description
+
+:
+
+```{=html}
+information about the content of a grid data cell
+```
+### Data identification {#iso19139-elem-gmd-MD_DataIdentification-f23816274b5af937b7fc035607866193}
+
+Name
+
+:
+
+> gmd:MD_DataIdentification
+
+Description
+
+:
+
+```{=html}
+Information required to identify a dataset
+```
+``` xml
+
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+
+ The data set combines the Corine based MAES (Mapping and Assessment of
+ Ecosystems and their Services) ecosystem classes with the non-spatial EUNIS habitat
+ classification (LEVEL 1) for a better biological characterization of ecosystems across
+ Europe (EEA-39). As such it represents probabilities of EUNIS habitat presence for each
+ MAES ecosystem type.
+
+ The data set aims to combine spatially explicit land cover information with non-spatially
+ referenced habitat information to improve our knowledge about ecosystems and their
+ distribution across Europe. The work supports the MAES process, Target 2 Action 5 of the
+ implementation of the EU Biodiversity Strategy to 2020, established to achieve the Aichi
+ targets of the Convention of Biological Diversity (CBD).
+
+ The objective of the ecosystem data set produced by EEA and its Topic Centre ETC/SIA was
+ to improve the biological description of land cover based ecosystem types. It represents
+ probabilities of EUNIS habitat presence in ecosystem types at European level. Since it is
+ not based on spatial explicit mapping the spatial and thematic accuracy is not of same
+ quality as delineated maps.
+
+ The MAES ecosystem typology differentiates three levels: whereas the level 2 of the MAES
+ proposal follows closely the EUNIS level 1, the third level of the MAES typology
+ corresponds to the EUNIS level 2. This level will be the base for the mapping approach.
+
+
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+ http://www.eea.europa.eu
+
+
+ WWW:LINK-1.0-http--link
+
+
+ Europen Environment Agency public website
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ http://sdi.eea.europa.eu/public/catalogue-graphic-overview/e8a366b7-0029-44d7-ae33-7578253179c0.png
+
+
+
+
+
+
+
+ Land cover
+
+
+ Habitats and biotopes
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.httpinspireeceuropaeutheme-theme
+
+
+
+
+
+
+
+
+
+
+
+ ecosystem
+
+
+ ecosystem type
+
+
+ land cover
+
+
+ environmental assessment
+
+
+ habitat
+
+
+
+
+
+
+
+ GEMET - Concepts, version 2.4
+
+
+
+
+ 2010-01-13
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.gemet
+
+
+
+
+
+
+
+
+
+
+
+ Unless otherwise indicated, re-use of content on the EEA website
+ for commercial or non-commercial purposes is permitted free of charge, provided that
+ the source is acknowledged. The EEA re-use policy follows Directive 2003/98/EC of the
+ European Parliament and the Council on the re-use of public sector information
+ throughout the European Union and Commission Decision 2006/291/EC, Euratom on the
+ re-use of Commission information. The EEA accepts no responsibility or liability
+ whatsoever for the re-use of content accessible on its website. Any inquiries about
+ re-use of content on the EEA website should be addressed to Ove Caspersen, EEA,
+ Kongens Nytorv 6, DK-1050 Copenhagen K, Tel +45 33 36 71 00, Fax +45 33 36 71 99,
+ e-mail copyrights at eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+ no limitations
+
+
+
+
+
+
+
+
+
+ 100
+
+
+
+
+
+
+
+ biota
+
+
+ environment
+
+
+
+
+
+
+ -33.90432
+
+
+ 38.1471
+
+
+ 26.988714
+
+
+ 60.57849
+
+
+
+
+
+
+
+
+
+
+
+ 2006-01-01
+ 2006-12-31
+
+
+
+
+
+
+
+```
+
+### Data type code {#iso19139-elem-gmd-MD_DatatypeCode-0bba106513fd53d5cba911355f212732}
+
+Name
+
+:
+
+> gmd:MD_DatatypeCode
+
+Description
+
+:
+
+```{=html}
+datatype of element or entity
+```
+### Standard codelists Data type code (gmd:MD_DatatypeCode)
+
+| code | label | description |
+|-----------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| class | Class | Descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior |
+| codelist | Codelist | Descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior |
+| enumeration | Enumeration | Data type whose instances form a list of named literal values, not extendable |
+| codelistElement | Codelist element | Permissible value for a codelist or enumeration |
+| abstractClass | Abstract class | Class that cannot be directly instantiated |
+| aggregateClass | Aggregate class | Class that is composed of classes it is connected to by an aggregate relationship |
+| specifiedClass | Specified class | Subclass that may be substituted for its superclass |
+| datatypeClass | Datatype class | Class with few or no operations whose primary purpose is to hold the abstract state of another class for transmittal, storage, encoding or persistent storage |
+| interfaceClass | Interface class | Named set of operations that characterize the behavior of an element |
+| unionClass | Union class | Class describing a selection of one of the specified types |
+| metaClass | Meta class | Class whose instances are classes |
+| typeClass | Type class | Class used for specification of a domain of instances (objects), together with the operations applicable to the objects. A type may have attributes and associations |
+| characterString | Character string | Free text field |
+| integer | Integer | Numerical field |
+| association | Association | Semantic relationship between two classes that involves connections among their instances |
+
+### Digital transfer options {#iso19139-elem-gmd-MD_DigitalTransferOptions-2c4f72aed0a9f9f5330a03d767a19e18}
+
+Name
+
+:
+
+> gmd:MD_DigitalTransferOptions
+
+Description
+
+:
+
+```{=html}
+Technical means and media by which a resource is obtained from the
+ distributor
+```
+``` xml
+
+
+
+
+
+ http://www.eea.europa.eu/data-and-maps/data/ds_resolveuid/d851e1b7f678468b8f0b1b98930ba3e1
+
+
+
+ WWW:LINK-1.0-http--link
+
+
+
+
+
+
+
+```
+
+### Dimension {#iso19139-elem-gmd-MD_Dimension-bc1cce714363bca430f062ece77911bb}
+
+Name
+
+:
+
+> gmd:MD_Dimension
+
+Description
+
+:
+
+```{=html}
+Axis properties
+```
+### Dimension type code {#iso19139-elem-gmd-MD_DimensionNameTypeCode-18f3e8f68c2b8cfbaed2e3f76dbfa8c7}
+
+Name
+
+:
+
+> gmd:MD_DimensionNameTypeCode
+
+Description
+
+:
+
+```{=html}
+name of the dimension
+```
+### Standard codelists Dimension type code (gmd:MD_DimensionNameTypeCode)
+
+| code | label | description |
+|------------|-------------|------------------------------------------------------------|
+| row | Row | Ordinate (y) axis |
+| column | Column | Abscissa (x) axis |
+| vertical | Vertical | Vertical (z) axis |
+| track | Track | Along the direction of motion of the scan point |
+| crossTrack | Cross track | Perpendicular to the direction of motion of the scan point |
+| line | Line | Scan line of a sensor |
+| sample | Sample | Element along a scan line |
+| time | Time | Duration |
+
+### Distribution {#iso19139-elem-gmd-MD_Distribution-54490632933db13de8c9b59dfa70abe1}
+
+Name
+
+:
+
+> gmd:MD_Distribution
+
+Description
+
+:
+
+```{=html}
+Information about the distributor of and options for obtaining the
+ resource
+```
+``` xml
+
+
+
+
+ GTiff
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.eea.europa.eu/data-and-maps/data/ds_resolveuid/d851e1b7f678468b8f0b1b98930ba3e1
+
+
+
+ WWW:LINK-1.0-http--link
+
+
+
+
+
+
+
+
+
+```
+
+### Distribution Units {#iso19139-elem-gmd-MD_DistributionUnits-ec18c729b051ecf4cbef23146d4c6b51}
+
+Name
+
+:
+
+> gmd:MD_DistributionUnits
+
+Description
+
+:
+
+### Distributor {#iso19139-elem-gmd-MD_Distributor-d6824c3ac5e1b658b17c1547ded49dba}
+
+Name
+
+:
+
+> gmd:MD_Distributor
+
+Description
+
+:
+
+```{=html}
+Information about the distributor
+```
+### Extended Element Information {#iso19139-elem-gmd-MD_ExtendedElementInformation-42b92809323020ccb9cb0def9d6ba040}
+
+Name
+
+:
+
+> gmd:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+New metadata element, not found in ISO 19115, which is required to describe
+ geographic data
+```
+### Feature catalogue description {#iso19139-elem-gmd-MD_FeatureCatalogueDescription-1b529353783b4f3bb4f593e052f37339}
+
+Name
+
+:
+
+> gmd:MD_FeatureCatalogueDescription
+
+Description
+
+:
+
+```{=html}
+Information identifying the feature catalogue or the conceptual
+ schema
+```
+``` xml
+
+
+ false
+
+
+
+```
+
+### Format {#iso19139-elem-gmd-MD_Format-de100d011b7723caf6cfed1dfd2d521e}
+
+Name
+
+:
+
+> gmd:MD_Format
+
+Description
+
+:
+
+```{=html}
+Description of the computer language construct that specifies the
+ representation of data objects in a record, file, message, storage device or
+ transmission channel
+```
+``` xml
+
+
+ GTiff
+
+
+
+
+
+```
+
+### Geometric objects {#iso19139-elem-gmd-MD_GeometricObjects-194ec1e062c0a1e8a95764b03ba61b2c}
+
+Name
+
+:
+
+> gmd:MD_GeometricObjects
+
+Description
+
+:
+
+```{=html}
+Number of objects, listed by geometric object type, used in the
+ dataset
+```
+### Geometric Object Type {#iso19139-elem-gmd-MD_GeometricObjectTypeCode-0343e1ce72823eeb2e13f5c1c7d8a362}
+
+Name
+
+:
+
+> gmd:MD_GeometricObjectTypeCode
+
+Description
+
+:
+
+### Standard codelists Geometric Object Type (gmd:MD_GeometricObjectTypeCode)
+
+| code | label | description |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------|
+| complex | Complex | Set of geometric primitives such that their boundaries can be represented as a union of other primitives |
+| composite | Composite | Connected set of curves, solids or surfaces |
+| curve | Curve | Bounded, 1-dimensional geometric primitive, representing the continuous image of a line |
+| point | Point | Zero-dimensional geometric primitive, representing a position but not having an extent |
+| solid | Solid | Bounded, connected 3-dimensional geometric primitive, representing the continuous image of a region of space |
+| surface | Surface | Bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane |
+
+### Georectified {#iso19139-elem-gmd-MD_Georectified-a0093e969409fbdfa09e2fbbd2d856c2}
+
+Name
+
+:
+
+> gmd:MD_Georectified
+
+Description
+
+:
+
+```{=html}
+Grid whose cells are regularly spaced in a geographic (i.e., lat / long) or map
+ coordinate system defined in the Spatial Referencing System (SRS) so that any cell in
+ the grid can be geolocated given its grid coordinate and the grid origin, cell spacing,
+ and orientation
+```
+### Georeferenceable {#iso19139-elem-gmd-MD_Georeferenceable-758d9a268ea6785de91ddd68102f643b}
+
+Name
+
+:
+
+> gmd:MD_Georeferenceable
+
+Description
+
+:
+
+```{=html}
+Grid with cells irregularly spaced in any given geographic/map projection
+ coordinate system, whose individual cells can be geolocated using geolocation
+ information supplied with the data but cannot be geolocated from the grid properties
+ alone
+```
+### Grid spatial representation {#iso19139-elem-gmd-MD_GridSpatialRepresentation-f6383abd79082f30ad3d9e0e6d582ae4}
+
+Name
+
+:
+
+> gmd:MD_GridSpatialRepresentation
+
+Description
+
+:
+
+```{=html}
+Information about grid spatial objects in the dataset
+```
+### Identifier {#iso19139-elem-gmd-MD_Identifier-a8075d9fcf78f296408f5a47a15f72e3}
+
+Name
+
+:
+
+> gmd:MD_Identifier
+
+Description
+
+:
+
+```{=html}
+Value uniquely identifying an object within a namespace
+```
+### Image description {#iso19139-elem-gmd-MD_ImageDescription-36a3b51ff28072d6b260523149eeb9bd}
+
+Name
+
+:
+
+> gmd:MD_ImageDescription
+
+Description
+
+:
+
+```{=html}
+Information about an image's suitability for use
+```
+### Imaging Condition Code {#iso19139-elem-gmd-MD_ImagingConditionCode-606883a4bccc60f4019ebc03e22ec7e9}
+
+Name
+
+:
+
+> gmd:MD_ImagingConditionCode
+
+Description
+
+:
+
+```{=html}
+code which indicates conditions which may affect the
+ image
+```
+### Standard codelists Imaging Condition Code (gmd:MD_ImagingConditionCode)
+
+| code | label | description |
+|--------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| blurredImage | Blurred image | Portion of the image is blurred |
+| cloud | Cloud | Portion of the image is partially obscured by cloud cover |
+| degradingObliquity | Degrading obliquity | Acute angle between the plane of the ecliptic (the plane of the Earth s orbit) and the plane of the celestial equator |
+| fog | Fog | Portion of the image is partially obscured by fog |
+| heavySmokeOrDust | Heavy smoke or dust | Portion of the image is partially obscured by heavy smoke or dust |
+| night | Night | Image was taken at night |
+| rain | Rain | Image was taken during rainfall |
+| semiDarkness | Semi darkness | Image was taken during semi-dark conditions -- twilight conditions |
+| shadow | Shadow | Portion of the image is obscured by shadow |
+| snow | Snow | Portion of the image is obscured by snow |
+| terrainMasking | Terrain masking | The absence of collection data of a given point or area caused by the relative location of topographic features which obstruct the collection path between the collector(s) and the subject(s) of interest |
+
+### Keywords {#iso19139-elem-gmd-MD_Keywords-aa987246245f8ec027b557d023a95fc4}
+
+Name
+
+:
+
+> gmd:MD_Keywords
+
+Description
+
+:
+
+```{=html}
+Keywords, their type and reference source
+```
+### Keyword Type Code {#iso19139-elem-gmd-MD_KeywordTypeCode-2f0c82ed31f17b806c452ec469485a6a}
+
+Name
+
+:
+
+> gmd:MD_KeywordTypeCode
+
+Description
+
+:
+
+```{=html}
+methods used to group similar keywords
+```
+### Standard codelists Keyword Type Code (gmd:MD_KeywordTypeCode)
+
+| code | label | description |
+|------------|------------|--------------------------------------------------------------------|
+| discipline | Discipline | Keyword identifies a branch of instruction or specialized learning |
+| place | Place | Keyword identifies a location |
+| stratum | Stratum | Keyword identifies the layer(s) of any deposited substance |
+| temporal | Temporal | Keyword identifies a time period related to the dataset |
+| theme | Theme | Keyword identifies a particular subject or topic |
+
+### Legal constraints {#iso19139-elem-gmd-MD_LegalConstraints-6ed172b96e894f417fd71106ceb3e0f7}
+
+Name
+
+:
+
+> gmd:MD_LegalConstraints
+
+Description
+
+:
+
+```{=html}
+Restrictions and legal prerequisites for accessing and using the resource or
+ metadata
+```
+``` xml
+
+
+
+
+
+ no limitations
+
+
+```
+
+### Maintenance Frequency {#iso19139-elem-gmd-MD_MaintenanceFrequencyCode-2338217a3e7f51c06e6f18cca73afb6c}
+
+Name
+
+:
+
+> gmd:MD_MaintenanceFrequencyCode
+
+Description
+
+:
+
+### Standard codelists Maintenance Frequency (gmd:MD_MaintenanceFrequencyCode)
+
+| code | label | description |
+|-------------|-------------|----------------------------------------------------------|
+| continual | Continual | Data is repeatedly and frequently updated |
+| daily | Daily | Data is updated each day |
+| weekly | Weekly | Data is updated on a weekly basis |
+| fortnightly | Fortnightly | Data is updated every two weeks |
+| monthly | Monthly | Data is updated each month |
+| quarterly | Quarterly | Data is updated every three months |
+| biannually | Biannually | Data is updated twice each year |
+| annually | Annually | Data is updated every year |
+| asNeeded | As needed | Data is updated as deemed necessary |
+| irregular | Irregular | Data is updated in intervals that are uneven in duration |
+| notPlanned | Not planned | There are no plans to update the data |
+| unknown | Unknown | Frequency of maintenance for the data is not known |
+
+``` xml
+
+```
+
+### Maintenance information {#iso19139-elem-gmd-MD_MaintenanceInformation-c8cc0a8f25b6943b1df7d5a1b46f915d}
+
+Name
+
+:
+
+> gmd:MD_MaintenanceInformation
+
+Description
+
+:
+
+```{=html}
+Information about the scope and frequency of updating
+```
+``` xml
+
+
+
+
+
+```
+
+### Medium {#iso19139-elem-gmd-MD_Medium-e532adb6d35b09f1dd8cc793984c3723}
+
+Name
+
+:
+
+> gmd:MD_Medium
+
+Description
+
+:
+
+```{=html}
+Information about the media on which the resource can be
+ distributed
+```
+### Medium format {#iso19139-elem-gmd-MD_MediumFormatCode-25bd3e7951957655817e6b930a2923fd}
+
+Name
+
+:
+
+> gmd:MD_MediumFormatCode
+
+Description
+
+:
+
+```{=html}
+method used to write to the medium
+```
+### Standard codelists Medium format (gmd:MD_MediumFormatCode)
+
+| code | label | description |
+|------------------|--------------------|------------------------------------------------------------|
+| cpio | CPIO | CoPy In / Out (UNIX file format and command) |
+| tar | TAR | Tape ARchive |
+| highSierra | High sierra | High sierra file system |
+| iso9660 | ISO9660 | Information processing volume and file structure of CD-ROM |
+| iso9660RockRidge | ISO9660 Rock Ridge | Rock ridge interchange protocol (UNIX) |
+| iso9660AppleHFS | ISO9660 Apple HFS | Hierarchical file system (Macintosh) |
+
+### Medium name code {#iso19139-elem-gmd-MD_MediumNameCode-a9abbe36f3dcf64d224bef1bfea190e7}
+
+Name
+
+:
+
+> gmd:MD_MediumNameCode
+
+Description
+
+:
+
+```{=html}
+name of the medium
+```
+### Standard codelists Medium name code (gmd:MD_MediumNameCode)
+
+| code | label | description |
+|---------------------------|-------------------------------|----------------------------------------------------|
+| cdRom | CDROM | Read-only optical disk |
+| dvd | DVD | Digital versatile disk |
+| dvdRom | DVDROM | Digital versatile disk, read only |
+| 3halfInchFloppy | 3 Half Inch Floppy | 3,5 inch magnetic disk |
+| 5quarterInchFloppy | 5 Quarter Inch Floppy | 5,25 inch magnetic disk |
+| 7trackTape | 7 Track tape | 7 track magnetic tape |
+| 9trackTape | 9 track tape | 9 track magnetic tape |
+| 3480Cartridge | 3480 Cartridge | 3480 cartridge tape drive |
+| 3490Cartridge | 3490 Cartridge | 3490 cartridge tape drive |
+| 3580Cartridge | 3580 Cartridge | 3580 cartridge tape drive |
+| 4mmCartridgeTape | 4 mm Cartridge tape | 4 millimetre magnetic tape |
+| 8mmCartridgeTape | 8 mm Cartridge tape | 8 millimetre magnetic tape |
+| 1quarterInchCartridgeTape | 1 Quarter inch cartridge tape | 0,25 inch magnetic tape |
+| digitalLinearTap | Digital linear tape | Half inch cartridge streaming tape drive |
+| onLine | Online | Direct computer linkage |
+| satellite | Satellite | Linkage through a satellite communication system |
+| telephoneLink | Telephone link | Communication through a telephone network |
+| hardcopy | Hardcopy | Pamphlet or leaflet giving descriptive information |
+
+### Metadata {#iso19139-elem-gmd-MD_Metadata-c2690d5de6984085623477c3bdc3275b}
+
+Name
+
+:
+
+> gmd:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Root entity which defines metadata about a resource or resources
+```
+``` xml
+
+
+ e8a366b7-0029-44d7-ae33-7578253179c0
+
+
+
+
+
+
+
+
+ df69de7e-3af1-4b4d-94d4-8bebe84c80b0
+
+
+
+
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+
+ 2016-01-15T16:57:35
+
+
+ ISO 19115:2003/19139
+
+
+
+ 1.0
+
+
+
+
+
+
+
+ urn:ogc:def:crs:EPSG:7.1:3035
+
+
+ OGP Surveying & Positioning Committee
+
+
+
+
+
+
+
+
+
+
+ Ecosystem types of Europe based on EUNIS level 1 (raster 100m) -
+ version 2.1, Dec. 2015
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+
+
+ 2015-12-08
+
+
+
+
+
+
+
+ 2.1
+
+
+
+
+ eea_r_3035_100_m_ecosystem-types-l1_2006_rev2-1
+
+
+
+
+
+
+
+ The data set combines the Corine based MAES (Mapping and Assessment of
+ Ecosystems and their Services) ecosystem classes with the non-spatial EUNIS habitat
+ classification (LEVEL 1) for a better biological characterization of ecosystems across
+ Europe (EEA-39). As such it represents probabilities of EUNIS habitat presence for each
+ MAES ecosystem type.
+
+ The data set aims to combine spatially explicit land cover information with non-spatially
+ referenced habitat information to improve our knowledge about ecosystems and their
+ distribution across Europe. The work supports the MAES process, Target 2 Action 5 of the
+ implementation of the EU Biodiversity Strategy to 2020, established to achieve the Aichi
+ targets of the Convention of Biological Diversity (CBD).
+
+ The objective of the ecosystem data set produced by EEA and its Topic Centre ETC/SIA was
+ to improve the biological description of land cover based ecosystem types. It represents
+ probabilities of EUNIS habitat presence in ecosystem types at European level. Since it is
+ not based on spatial explicit mapping the spatial and thematic accuracy is not of same
+ quality as delineated maps.
+
+ The MAES ecosystem typology differentiates three levels: whereas the level 2 of the MAES
+ proposal follows closely the EUNIS level 1, the third level of the MAES typology
+ corresponds to the EUNIS level 2. This level will be the base for the mapping approach.
+
+
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+ http://www.eea.europa.eu
+
+
+ WWW:LINK-1.0-http--link
+
+
+ Europen Environment Agency public website
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ http://sdi.eea.europa.eu/public/catalogue-graphic-overview/e8a366b7-0029-44d7-ae33-7578253179c0.png
+
+
+
+
+
+
+
+ Land cover
+
+
+ Habitats and biotopes
+
+
+
+
+
+
+
+ GEMET - INSPIRE themes, version 1.0
+
+
+
+
+ 2008-06-01
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.httpinspireeceuropaeutheme-theme
+
+
+
+
+
+
+
+
+
+
+
+ ecosystem
+
+
+ ecosystem type
+
+
+ land cover
+
+
+ environmental assessment
+
+
+ habitat
+
+
+
+
+
+
+
+ GEMET - Concepts, version 2.4
+
+
+
+
+ 2010-01-13
+
+
+
+
+
+
+
+
+
+
+ geonetwork.thesaurus.external.theme.gemet
+
+
+
+
+
+
+
+
+
+
+
+ Unless otherwise indicated, re-use of content on the EEA website
+ for commercial or non-commercial purposes is permitted free of charge, provided that
+ the source is acknowledged. The EEA re-use policy follows Directive 2003/98/EC of the
+ European Parliament and the Council on the re-use of public sector information
+ throughout the European Union and Commission Decision 2006/291/EC, Euratom on the
+ re-use of Commission information. The EEA accepts no responsibility or liability
+ whatsoever for the re-use of content accessible on its website. Any inquiries about
+ re-use of content on the EEA website should be addressed to Ove Caspersen, EEA,
+ Kongens Nytorv 6, DK-1050 Copenhagen K, Tel +45 33 36 71 00, Fax +45 33 36 71 99,
+ e-mail copyrights at eea.europa.eu
+
+
+
+
+
+
+
+
+
+
+ no limitations
+
+
+
+
+
+
+
+
+
+ 100
+
+
+
+
+
+
+
+ biota
+
+
+ environment
+
+
+
+
+
+
+ -33.90432
+
+
+ 38.1471
+
+
+ 26.988714
+
+
+ 60.57849
+
+
+
+
+
+
+
+
+
+
+
+ 2006-01-01
+ 2006-12-31
+
+
+
+
+
+
+
+
+
+
+
+ false
+
+
+
+
+
+
+
+
+
+ GTiff
+
+
+
+
+
+
+
+
+
+
+
+
+ http://www.eea.europa.eu/data-and-maps/data/ds_resolveuid/d851e1b7f678468b8f0b1b98930ba3e1
+
+
+
+ WWW:LINK-1.0-http--link
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The data set production implied 2 steps. First re-classification of
+ CORINE Land Cover 2006 and bathymetry data using the 7 terrestrial (urban, cropland,
+ grassland, woodland and forest, heathland and shrub, sparsely vegetated land,
+ wetland), 1 freshwater (river and lakes), and 4 marine (marine inlets and transitional
+ waters, coastal, shelf, open ocean) classes of the MAES ecosystem typology (Maes et
+ al., 2013). The classes also provide links to major policy lines such as agriculture,
+ forestry, territorial cohesion, water and marine related policies. The second step
+ comprised refinement of the ecosystem types by attributing EUNIS habitat information
+ to each ecosystem type (see http://eunis.eea.europa.eu/habitats.jsp). The refinement
+ process used reference data such as potential natural vegetation, elevation, slope,
+ aspect, soil, geology, environmental regions and other spatial referenced information
+ which allowed attribution of the EUNIS habitat characteristics to the spatial mapping
+ units of the MAES ecosystem types. The geometric and thematic accuracy of EUNIS class
+ presence was also estimated and mapped. The method is described in the EEA Technical
+ Report 06/2015: European Ecosystem Assessment – Concept, Data, and Implementation.
+ The basis for the update was CORINE land cover 2006 (CLC 2006). It includes Albania,
+ Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic,
+ Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Kosovo
+ (under UNSCR 1244/99), Latvia, Liechtenstein, Lithuania, Luxembourg, the former
+ Yugoslavian Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland,
+ Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
+ the United Kingdom. For Greece that has not participated in the CLC 2006 activity the
+ CLC 2000 data was used instead.
+
+
+
+
+
+
+
+
+```
+
+### Metadata Extension Information {#iso19139-elem-gmd-MD_MetadataExtensionInformation-646aa4503013cf2231a72dc4403c14e3}
+
+Name
+
+:
+
+> gmd:MD_MetadataExtensionInformation
+
+Description
+
+:
+
+```{=html}
+Information describing metadata extensions
+```
+### Obligation code {#iso19139-elem-gmd-MD_ObligationCode-50bf58bf346f8ea1982cbebde314ed79}
+
+Name
+
+:
+
+> gmd:MD_ObligationCode
+
+Description
+
+:
+
+```{=html}
+Obligation of the element or entity
+```
+### Standard codelists Obligation code (gmd:MD_ObligationCode)
+
+| code | label | description |
+|-------------|-------------|------------------------------------------------------|
+| mandatory | Mandatory | Element is always required |
+| optional | Optional | Element is not required |
+| conditional | Conditional | Element is required when a specific condition is met |
+
+### Pixel orientation code {#iso19139-elem-gmd-MD_PixelOrientationCode-7517f9a6da0ddf97e3a3edafceff4fc9}
+
+Name
+
+:
+
+> gmd:MD_PixelOrientationCode
+
+Description
+
+:
+
+```{=html}
+Point in a pixel corresponding to the Earth location of the pixel
+```
+### Standard codelists Pixel orientation code (gmd:MD_PixelOrientationCode)
+
+| code | label | description |
+|------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| center | Center | Point halfway between the lower left and the upper right of the pixel |
+| lowerLeft | Lower left | The corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value |
+| lowerRight | Lower right | Next corner counterclockwise from the lower left |
+| upperRight | Upper right | Next corner counterclockwise from the lower right |
+| upperLeft | Upper left | Next corner counterclockwise from the upper right |
+
+### Portrayal catalogue reference {#iso19139-elem-gmd-MD_PortrayalCatalogueReference-1de6d80081f48afcf87141f495b14382}
+
+Name
+
+:
+
+> gmd:MD_PortrayalCatalogueReference
+
+Description
+
+:
+
+```{=html}
+Information identifying the portrayal catalogue used
+```
+### Progress {#iso19139-elem-gmd-MD_ProgressCode-a705251bfb6aa840b2ddcdcb475e82ae}
+
+Name
+
+:
+
+> gmd:MD_ProgressCode
+
+Description
+
+:
+
+### Standard codelists Progress (gmd:MD_ProgressCode)
+
+| code | label | description |
+|-------------------|--------------------|--------------------------------------------------------------------------------------|
+| completed | Completed | Production of the data has been completed |
+| historicalArchive | Historical archive | Data has been stored in an offline storage facility |
+| obsolete | Obsolete | Data is no longer relevant |
+| onGoing | On going | Data is continually being updated |
+| planned | Planned | Fixed date has been established upon or by which the data will be created or updated |
+| required | Required | Data needs to be generated or updated |
+| underDevelopment | Under development | Data is currently in the process of being created |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|-------------|--------------|-------------|
+| notobsolete | Not obsolete | |
+
+### Range dimension {#iso19139-elem-gmd-MD_RangeDimension-6788b233d4b9866fff4fea73bb016784}
+
+Name
+
+:
+
+> gmd:MD_RangeDimension
+
+Description
+
+:
+
+```{=html}
+Information on the range of each dimension of a cell measurement
+ value
+```
+### Reference system {#iso19139-elem-gmd-MD_ReferenceSystem-2700a53ffd47f02aee2059e4520f399f}
+
+Name
+
+:
+
+> gmd:MD_ReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Information about the reference system.
+```
+```{=html}
+information about the reference system
+```
+``` xml
+
+
+
+
+ urn:ogc:def:crs:EPSG:7.1:3035
+
+
+ OGP Surveying & Positioning Committee
+
+
+
+
+```
+
+### Representative fraction {#iso19139-elem-gmd-MD_RepresentativeFraction-66b5d251e519833e03ebd5b5b0f2d075}
+
+Name
+
+:
+
+> gmd:MD_RepresentativeFraction
+
+Description
+
+:
+
+```{=html}
+Derived from Scale where MD_RepresentativeFraction.denominator = 1 /
+ Scale.measure And Scale.targetUnits = Scale.sourceUnits
+```
+### Resolution {#iso19139-elem-gmd-MD_Resolution-b305b6f73606a0b11af969489ef2b5ac}
+
+Name
+
+:
+
+> gmd:MD_Resolution
+
+Description
+
+:
+
+```{=html}
+Level of detail expressed as a scale factor or a ground distance
+```
+``` xml
+
+
+ 100
+
+
+```
+
+### Access Restriction {#iso19139-elem-gmd-MD_RestrictionCode-gmd-accessConstraints-12f24e671b178093fc3c8cf32539ce44}
+
+Name
+
+:
+
+> gmd:MD_RestrictionCode
+
+Context
+
+:
+
+> gmd:accessConstraints
+
+Description
+
+:
+
+### Standard codelists Access Restriction (gmd:MD_RestrictionCode)
+
+| code | label | description |
+|----------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| copyright | Copyright | Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor |
+| patent | Patent | Government has granted exclusive right to make, sell, use or license an invention or discovery |
+| patentPending | Pending patent | Produced or sold information awaiting a patent |
+| trademark | Trademark | A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer |
+| license | License | Formal permission to do something |
+| intellectualPropertyRights | Intellectual property rights | Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity |
+| restricted | Restricted | Withheld from general circulation or disclosure |
+| otherRestrictions | Other restrictions | Limitation not listed |
+
+``` xml
+
+```
+
+### Use Restriction {#iso19139-elem-gmd-MD_RestrictionCode-gmd-useConstraints-56f57edb2ffb57e63fc7166ee5ae8350}
+
+Name
+
+:
+
+> gmd:MD_RestrictionCode
+
+Context
+
+:
+
+> gmd:useConstraints
+
+Description
+
+:
+
+### Standard codelists Access Restriction (gmd:MD_RestrictionCode)
+
+| code | label | description |
+|----------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| copyright | Copyright | Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor |
+| patent | Patent | Government has granted exclusive right to make, sell, use or license an invention or discovery |
+| patentPending | Pending patent | Produced or sold information awaiting a patent |
+| trademark | Trademark | A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer |
+| license | License | Formal permission to do something |
+| intellectualPropertyRights | Intellectual property rights | Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity |
+| restricted | Restricted | Withheld from general circulation or disclosure |
+| otherRestrictions | Other restrictions | Limitation not listed |
+
+``` xml
+
+```
+
+### Scope code {#iso19139-elem-gmd-MD_ScopeCode-9ffd6fc05da3527f72a3dcae95dd221e}
+
+Name
+
+:
+
+> gmd:MD_ScopeCode
+
+Description
+
+:
+
+```{=html}
+Class of information to which the referencing entity applies
+```
+### Standard codelists Scope code (gmd:MD_ScopeCode)
+
+| code | label | description |
+|----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| attribute | Attribute | Information applies to the attribute class |
+| attributeType | Attribute type | Information applies to the characteristic of a feature |
+| collectionHardware | Collection hardware | Information applies to the collection hardware class |
+| collectionSession | Collection session | Information applies to the collection session |
+| dataset | Dataset | Information applies to the dataset |
+| series | Series | Information applies to the series |
+| nonGeographicDataset | Non geographic dataset | Information applies to non-geographic data |
+| dimensionGroup | Dimension group | Information applies to a dimension group |
+| feature | Feature | Information applies to a feature |
+| featureType | Feature type | Information applies to a feature type |
+| propertyType | Property type | Information applies to a property type |
+| fieldSession | Field session | Information applies to a field session |
+| software | Software | Information applies to a computer program or routine |
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+| model | Model | Information applies to a copy or imitation of an existing or hypothetical object |
+| tile | Tile | Information applies to a tile, a spatial subset of geographic data |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|---------------------------------------------|------------------------------------------------|-------------|
+| map staticMap interactiveMap featureCatalog | Map Static map Interactive map Feature catalog | |
+
+Displayed only if
+
+:
+
+> /ancestor::node()[name()='gmd:MD_Metadata']/gmd:identificationInfo/srv:SV_ServiceIdentification
+
+### Standard codelists Scope code (gmd:MD_ScopeCode)
+
+| code | label | description |
+|---------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+
+### Scope description {#iso19139-elem-gmd-MD_ScopeDescription-8c0d8bbef826207eed5daeb5852c1538}
+
+Name
+
+:
+
+> gmd:MD_ScopeDescription
+
+Description
+
+:
+
+```{=html}
+Description of the class of information covered by the
+ information
+```
+
+Condition
+
+:
+
+> Either attributes, features, featureInstances, attributeInstnaces, dataset or other must be provided
+
+### Security constraints {#iso19139-elem-gmd-MD_SecurityConstraints-50cffe217644bdac6008fbf9f8b569c5}
+
+Name
+
+:
+
+> gmd:MD_SecurityConstraints
+
+Description
+
+:
+
+```{=html}
+Handling restrictions imposed on the resource or metadata for national security
+ or similar security concerns
+```
+### Service Identification {#iso19139-elem-gmd-MD_ServiceIdentification-fa001e116566fc975db65c9f5847bf42}
+
+Name
+
+:
+
+> gmd:MD_ServiceIdentification
+
+Description
+
+:
+
+```{=html}
+Identification of capabilities which a service provider makes available to a
+ service user through a set of interfaces that define a behaviour - See ISO 19119 -
+ Services for further information
+```
+### Spatial Representation Type {#iso19139-elem-gmd-MD_SpatialRepresentationTypeCode-7f5f469869ef3a8a1951b287a3494e69}
+
+Name
+
+:
+
+> gmd:MD_SpatialRepresentationTypeCode
+
+Description
+
+:
+
+### Standard codelists Spatial Representation Type (gmd:MD_SpatialRepresentationTypeCode)
+
+| code | label | description |
+|-------------|--------------|----------------------------------------------------------------------------------------------------|
+| vector | Vector | Vector data is used to represent geographic data |
+| grid | Grid | Grid data is used to represent geographic data |
+| textTable | Text, table | Textual or tabular data is used to represent geographic data |
+| tin | TIN | Triangulated irregular network |
+| stereoModel | Stereo model | Three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images |
+| video | Video | Scene from a video recording |
+
+``` xml
+
+```
+
+### Standard order process {#iso19139-elem-gmd-MD_StandardOrderProcess-3d3f736b3cad83dea0c4232e97bb7af4}
+
+Name
+
+:
+
+> gmd:MD_StandardOrderProcess
+
+Description
+
+:
+
+```{=html}
+Common ways in which the resource may be obtained or received, and related
+ instructions and fee information
+```
+### Topic category code {#iso19139-elem-gmd-MD_TopicCategoryCode-cb06862958376a6cf77f91294821ba48}
+
+Name
+
+:
+
+> gmd:MD_TopicCategoryCode
+
+Description
+
+:
+
+```{=html}
+High-level geographic data thematic classification to assist in the grouping
+ and search of available geographic data sets. Can be used to group keywords as well.
+ Listed examples are not exhaustive. NOTE It is understood there are overlaps between
+ general categories and the user is encouraged to select the one most
+ appropriate.
+```
+### Standard codelists Topic category code (gmd:MD_TopicCategoryCode)
+
+| code | label | description |
+|----------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| farming | Farming | Rearing of animals and/or cultivation of plants. Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock |
+| biota | Biota | Flora and/or fauna in natural environment. Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat |
+| boundaries | Boundaries | Legal land descriptions. Examples: political and administrative boundaries |
+| climatologyMeteorologyAtmosphere | Climatology, meteorology, atmosphere | Processes and phenomena of the atmosphere. Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation |
+| economy | Economy | Economic activities, conditions and employment. Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas |
+| elevation | Elevation | Height above or below sea level. Examples: altitude, bathymetry, digital elevation models, slope, derived products |
+| environment | Environment | Environmental resources, protection and conservation. Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape |
+| geoscientificInformation | Geoscientific information | Information pertaining to earth sciences. Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion |
+| health | Health | Health, health services, human ecology, and safety. Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services |
+| imageryBaseMapsEarthCover | Imagery base maps earth cover | Base maps. Examples: land cover, topographic maps, imagery, unclassified images, annotations |
+| intelligenceMilitary | Intelligence military | Military bases, structures, activities. Examples: barracks, training grounds, military transportation, information collection |
+| inlandWaters | Inland waters | Inland water features, drainage systems and their characteristics. Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts |
+| location | Location | Positional information and services. Examples: addresses, geodetic networks, control points, postal zones and services, place names |
+| oceans | Oceans | Features and characteristics of salt water bodies (excluding inland waters). Examples: tides, tidal waves, coastal information, reefs |
+| planningCadastre | Planning cadastre | Information used for appropriate actions for future use of the land. Examples: land use maps, zoning maps, cadastral surveys, land ownership |
+| society | Society | Characteristics of society and cultures. Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information |
+| structure | Structure | Man-made construction. Examples: buildings, museums, churches, factories, housing, monuments, shops, towers |
+| transportation | Transportation | Means and aids for conveying persons and/or goods. Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways |
+| utilitiesCommunication | Utilities communication | Energy, water and waste systems and communications infrastructure and services. Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks |
+
+### Topology Level {#iso19139-elem-gmd-MD_TopologyLevelCode-3b51519b669d9d171a75a1fd49e8f9c0}
+
+Name
+
+:
+
+> gmd:MD_TopologyLevelCode
+
+Description
+
+:
+
+### Standard codelists Topology Level (gmd:MD_TopologyLevelCode)
+
+| code | label | description |
+|------------------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| geometryOnly | Geometry only | Geometry objects without any additional structure which describes topology |
+| topology1D | Topology 1D | 1-dimensional topological complex -- commonly called chain-node topology |
+| planarGraph | Planar graph | 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.) |
+| fullPlanarGraph | Full planar graph | 2-dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called full topology in a cartographic 2D environment.) |
+| surfaceGraph | Surface graph | 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.) |
+| fullSurfaceGraph | Full surface graph | 2-dimensional topological complex that is isomorphic to a subset of a surface |
+| topology3D | Topology 3D | 3-dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.) |
+| fullTopology3D | Full topology 3D | Complete coverage of a 3D Euclidean coordinate space |
+| abstract | Abstract | Topological complex without any specified geometric realisation |
+
+### Usage {#iso19139-elem-gmd-MD_Usage-44b9e97d1ee076443e0f48c0f7d40819}
+
+Name
+
+:
+
+> gmd:MD_Usage
+
+Description
+
+:
+
+```{=html}
+Brief description of ways in which the resource(s) is/are currently
+ used
+```
+### Vector spatial representation {#iso19139-elem-gmd-MD_VectorSpatialRepresentation-080252d44368083a0c7b0d9d9560f519}
+
+Name
+
+:
+
+> gmd:MD_VectorSpatialRepresentation
+
+Description
+
+:
+
+```{=html}
+Information about the vector spatial objects in the dataset
+```
+### Measure description {#iso19139-elem-gmd-measureDescription-15e866aef3e37fc22a1e5777bbf435b1}
+
+Name
+
+:
+
+> gmd:measureDescription
+
+Description
+
+:
+
+```{=html}
+Description of the measure being determined
+```
+### Measure identification {#iso19139-elem-gmd-measureIdentification-d039c0be36450237d6b0e484e65d9330}
+
+Name
+
+:
+
+> gmd:measureIdentification
+
+Description
+
+:
+
+```{=html}
+Code identifying a registered standard procedure
+```
+### Medium format {#iso19139-elem-gmd-mediumFormat-2b3a955cfb7c1a5ab43b7ce1341888be}
+
+Name
+
+:
+
+> gmd:mediumFormat
+
+Description
+
+:
+
+```{=html}
+Method used to write to the medium
+```
+### Medium note {#iso19139-elem-gmd-mediumNote-668533707740bae1759a882d1db591a5}
+
+Name
+
+:
+
+> gmd:mediumNote
+
+Description
+
+:
+
+```{=html}
+Description of other limitations or requirements for using the
+ medium
+```
+### Metadata constraints {#iso19139-elem-gmd-metadataConstraints-gmd-MD_Metadata-130ad5b9aa5c191c31ca2a97d2ad629b}
+
+Name
+
+:
+
+> gmd:metadataConstraints
+
+Context
+
+:
+
+> gmd:MD_Metadata
+
+Description
+
+:
+
+```{=html}
+Provides restrictions on the access and use of metadata
+```
+### Metadata constraints {#iso19139-elem-gmd-metadataConstraints-0547cb4265a8d2f9663d558a9ac72d43}
+
+Name
+
+:
+
+> gmd:metadataConstraints
+
+Description
+
+:
+
+```{=html}
+Provides restrictions on the access and use of data
+```
+### Metadata Extension Information {#iso19139-elem-gmd-metadataExtensionInfo-4819d91b9727143a6c12cdb9ffeef2da}
+
+Name
+
+:
+
+> gmd:metadataExtensionInfo
+
+Description
+
+:
+
+```{=html}
+Information describing metadata extensions
+```
+### Metadata maintenance {#iso19139-elem-gmd-metadataMaintenance-2af9bf1fc8f71819e7361e5d6987358c}
+
+Name
+
+:
+
+> gmd:metadataMaintenance
+
+Description
+
+:
+
+```{=html}
+Provides information about the frequency of metadata updates, and the scope of
+ those updates
+```
+### Metadata standard name {#iso19139-elem-gmd-metadataStandardName-1e8d324f913f2da08b656d26e73e994d}
+
+Name
+
+:
+
+> gmd:metadataStandardName
+
+Description
+
+:
+
+```{=html}
+Name of the metadata standard (including profile name) used
+```
+``` xml
+
+ ISO 19115:2003/19139
+
+
+```
+
+### Metadata standard version {#iso19139-elem-gmd-metadataStandardVersion-ab0dd515a6ca9c890bc32d3615cd427f}
+
+Name
+
+:
+
+> gmd:metadataStandardVersion
+
+Description
+
+:
+
+```{=html}
+Version (profile) of the metadata standard used
+```
+``` xml
+
+ 1.0
+
+
+```
+
+### Minimum value {#iso19139-elem-gmd-minimumValue-d7415ce6a0445916b518cbced9bf748d}
+
+Name
+
+:
+
+> gmd:minimumValue
+
+Description
+
+:
+
+```{=html}
+Lowest vertical extent contained in the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Minimum value {#iso19139-elem-gmd-minValue-ca30535d2283f60660d6cb8c3e06264a}
+
+Name
+
+:
+
+> gmd:minValue
+
+Description
+
+:
+
+```{=html}
+Shortest wavelength that the sensor is capable of collecting within a
+ designated band
+```
+### Name {#iso19139-elem-gmd-name-gmd-MD_AbstractClass-55c76e5e1d36308ca08192f0f34145ef}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_AbstractClass
+
+Description
+
+:
+
+```{=html}
+Name
+```
+### Name {#iso19139-elem-gmd-name-gmd-MD_Medium-5e756c272348337b91b38d9f904b491a}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_Medium
+
+Description
+
+:
+
+```{=html}
+Name of the medium on which the resource can be received
+```
+### Name {#iso19139-elem-gmd-name-gmd-RS_ReferenceSystem-02b2a8b0e707e9507d341c5d67eaaa0d}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:RS_ReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Name of reference system used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Name {#iso19139-elem-gmd-name-gmd-MD_Format-6a971c2939bcf530ff1ef0496661407f}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_Format
+
+Description
+
+:
+
+```{=html}
+Name of the data transfer format(s)
+```
+```{=html}
+name of the data transfer format(s)
+```
+
+Condition
+
+:
+
+> mandatory
+
+Recommended values
+
+| code | label |
+|-----------------|-----------------|
+| Text | Text |
+| ESRI Shapefile | ESRI Shapefile |
+| Mapinfo MIF/MID | Mapinfo MIF/MID |
+| Mapinfo TAB | Mapinfo TAB |
+| KML | KML |
+| GML | GML |
+| GeoTIFF | GeoTIFF |
+| TIFF | TIFF |
+| ECW | ECW |
+| JPEG2000 | JPEG2000 |
+| ZIP | ZIP |
+| PDF | PDF |
+| PNG | PNG |
+| JPEG | JPEG |
+| OGC:WMC | OGC:WMC |
+| OGC:OWS-C | OGC OWS Context |
+
+### Name {#iso19139-elem-gmd-name-gmd-MD_ExtendedElementInformation-6f3a3922c51040816e19474d667dfae0}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Name of the extended metadata element
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Name {#iso19139-elem-gmd-name-gmd-MD_ApplicationSchemaInformation-8d1b515ce0e50b245935cd51d2c69e76}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_ApplicationSchemaInformation
+
+Description
+
+:
+
+```{=html}
+Name of the application schema used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Name of the resource {#iso19139-elem-gmd-name-gmd-CI_OnlineResource-440837e17f2a3bf02e6188d6cf477809}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:CI_OnlineResource
+
+Description
+
+:
+
+```{=html}
+Name of the online resource
+```
+### Name {#iso19139-elem-gmd-name-gmd-CI_Series-d8b38970368c2e8adf6a26f354b4e4a9}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:CI_Series
+
+Description
+
+:
+
+```{=html}
+Name of the series, or aggregate dataset, of which the dataset is a
+ part
+```
+### Name {#iso19139-elem-gmd-name-gmd-MD_CodeDomain-8f86c5309156f1cc30b5d6f56f08e8ad}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_CodeDomain
+
+Description
+
+:
+
+```{=html}
+Name of the code domain
+```
+### Name {#iso19139-elem-gmd-name-gmd-MD_CodeValue-870d040c56a98b1502ead34afc6ff2c6}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_CodeValue
+
+Description
+
+:
+
+```{=html}
+Value name
+```
+### Name {#iso19139-elem-gmd-name-gmd-MD_Attribute-5c723d5a648b525de45efddc22615249}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_Attribute
+
+Description
+
+:
+
+```{=html}
+Attribute name
+```
+### Name {#iso19139-elem-gmd-name-gmd-MD_Role-5a5e776d6bb1ee8d8cb7a5d518314bef}
+
+Name
+
+:
+
+> gmd:name
+
+Context
+
+:
+
+> gmd:MD_Role
+
+Description
+
+:
+
+```{=html}
+Role name
+```
+### Name {#iso19139-elem-gmd-name-9796db4d1cab411f64fa97871fd1dd7e}
+
+Name
+
+:
+
+> gmd:name
+
+Description
+
+:
+
+### Name of measure {#iso19139-elem-gmd-nameOfMeasure-9f6986c5c2ab012a799560402287fc82}
+
+Name
+
+:
+
+> gmd:nameOfMeasure
+
+Description
+
+:
+
+```{=html}
+Name of the test applied to the data
+```
+Recommended values
+
+| code | label |
+|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| | -- Completeness -- |
+| Excess item | Excess item |
+| Number of excess items | Number of excess items |
+| Rate of excess items | Rate of excess items |
+| Number of duplicate feature instances | Number of duplicate feature instances |
+| Missing item | Missing item |
+| Number of missing items | Number of missing items |
+| Rate of missing items | Rate of missing items -- Logical consistency / Conceptual consistency -- |
+| Conceptual schema noncompliance | Conceptual schema noncompliance |
+| Conceptual schema compliance | Conceptual schema compliance |
+| Number of items noncompliant to the rules of the conceptual schema | Number of items noncompliant to the rules of the conceptual schema |
+| Number of invalid overlaps of surfaces | Number of invalid overlaps of surfaces |
+| Non-compliance rate with respect to the rules of the conceptual schema | Non-compliance rate with respect to the rules of the conceptual schema |
+| Compliance rate with the rules of the conceptual schema | Compliance rate with the rules of the conceptual schema -- Logical consistency / Domain consistency -- |
+| Value domain non-conformance | Value domain non-conformance |
+| Value domain conformance | Value domain conformance |
+| Number of items not in conformance with their value domain | Number of items not in conformance with their value domain |
+| Value domain conformance rate | Value domain conformance rate |
+| Value domain non-conformance rate | Value domain non-conformance rate |
+| Physical structure conflicts | Physical structure conflicts |
+| Physical structure conflict rate | Physical structure conflict rate -- Logical consistency / Topological consistency -- |
+| Number of faulty point-curve connections | Number of faulty point-curve connections |
+| Rate of faulty point-curve connections | Rate of faulty point-curve connections |
+| Number of missing connection due to undershoots | Number of missing connection due to undershoots |
+| Number of missing connections due to overshoots | Number of missing connections due to overshoots |
+| Number of invalid slivers | Number of invalid slivers |
+| Number of invalid self intersect errors | Number of invalid self intersect errors |
+| Number of invalid self overlap errors | Number of invalid self overlap errors -- Positional accuracy / Absolute or external accuracy / General measures -- |
+| Mean value of positional uncertainties | Mean value of positional uncertainties |
+| Mean value of positional uncertainties excluding outliers | Mean value of positional uncertainties excluding outliers |
+| Number of positional uncertainties above a given threshold | Number of positional uncertainties above a given threshold |
+| Rate of positional errors above a given threshold | Rate of positional errors above a given threshold |
+| Covariance matrix | Covariance matrix -- Positional accuracy / Absolute or external accuracy / Vertical -- |
+| Linear error probable | Linear error probable |
+| Standard linear error | Standard linear error |
+| Linear map accuracy at 90% significance level | Linear map accuracy at 90% significance level |
+| Linear map accuracy at 95% significance level | Linear map accuracy at 95% significance level |
+| Linear map accuracy at 99% significance level | Linear map accuracy at 99% significance level |
+| Near certainty linear error | Near certainty linear error |
+| Root mean square error | Root mean square error |
+| Absolute linear error at 90% significance level of biased vertical data (Alternative 1) | Absolute linear error at 90% significance level of biased vertical data (Alternative 1) |
+| Absolute linear error at 90% significance level of biased vertical data | Absolute linear error at 90% significance level of biased vertical data -- Positional accuracy / Absolute or external accuracy / Horizontal -- |
+| Circular standard deviation | Circular standard deviation |
+| Circular error probable | Circular error probable |
+| Circular map accuracy standard | Circular map accuracy standard |
+| Circular error at 95% significance level | Circular error at 95% significance level |
+| Circular near certainty error | Circular near certainty error |
+| Root mean square error of planimetry | Root mean square error of planimetry |
+| Absolute circular error at 90% significance level of biased data (Alternative 2) | Absolute circular error at 90% significance level of biased data (Alternative 2) |
+| Absolute circular error at 90% significance level of biased data | Absolute circular error at 90% significance level of biased data |
+| Uncertainty ellipse | Uncertainty ellipse |
+| Confidence ellipse | Confidence ellipse -- Positional accuracy / Relative or internal accuracy -- |
+| Relative vertical error | Relative vertical error |
+| Relative horizontal error | Relative horizontal error -- Temporal accuracy / Accuracy of a time measurement -- |
+| Time accuracy at 68.3% significance level | Time accuracy at 68.3% significance level |
+| Time accuracy at 50% significance level | Time accuracy at 50% significance level |
+| Time accuracy at 90% significance level | Time accuracy at 90% significance level |
+| Time accuracy at 95% significance level | Time accuracy at 95% significance level |
+| Time accuracy at 99% significance level | Time accuracy at 99% significance level |
+| Time accuracy at 99.8% significance level | Time accuracy at 99.8% significance level -- Thematic accuracy / Classification correctness -- |
+| Number of incorrectly classified features | Number of incorrectly classified features |
+| Misclassification rate | Misclassification rate |
+| Misclassification matrix | Misclassification matrix |
+| Relative misclassification matrix | Relative misclassification matrix |
+| Kappa coefficient | Kappa coefficient -- Thematic accuracy / Non-quantitative attribute correctness -- |
+| Number of incorrect attribute values | Number of incorrect attribute values |
+| Rate of correct attribute values | Rate of correct attribute values |
+| Rate of incorrect attribute values | Rate of incorrect attribute values -- Thematic accuracy / Quantitative attribute accuracy -- |
+| Attribute value uncertainty at 68.3% significance level | Attribute value uncertainty at 68.3% significance level |
+| Attribute value uncertainty at 50% significance level | Attribute value uncertainty at 50% significance level |
+| Attribute value uncertainty at 90% significance level | Attribute value uncertainty at 90% significance level |
+| Attribute value uncertainty at 95% significance level | Attribute value uncertainty at 95% significance level |
+| Attribute value uncertainty at 99% significance level | Attribute value uncertainty at 99% significance level |
+| Attribute value uncertainty at 99.8% significance level | Attribute value uncertainty at 99.8% significance level |
+
+### North bound {#iso19139-elem-gmd-northBoundLatitude-7f5fd77fbea072c35f6d4c938f74dee5}
+
+Name
+
+:
+
+> gmd:northBoundLatitude
+
+Description
+
+:
+
+```{=html}
+Northern-most, coordinate of the limit of the dataset extent expressed in
+ latitude in decimal degrees (positive north)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ 60.57849
+
+```
+
+### Number of dimensions {#iso19139-elem-gmd-numberOfDimensions-be36128610852a3a86fe52230c125ae8}
+
+Name
+
+:
+
+> gmd:numberOfDimensions
+
+Description
+
+:
+
+```{=html}
+Number of independent spatial-temporal axes
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Obligation {#iso19139-elem-gmd-obligation-bd4d5c2002cbae677396f4195cfad3a6}
+
+Name
+
+:
+
+> gmd:obligation
+
+Description
+
+:
+
+```{=html}
+Obligation of the extended element
+```
+### Offline {#iso19139-elem-gmd-offLine-74ad66cbe02f22813b168bb80273d2fe}
+
+Name
+
+:
+
+> gmd:offLine
+
+Description
+
+:
+
+```{=html}
+Information about offline media on which the resource can be
+ obtained
+```
+### Offset {#iso19139-elem-gmd-offset-4d077570ef50ba2b1ea4f00396f1bb0a}
+
+Name
+
+:
+
+> gmd:offset
+
+Description
+
+:
+
+```{=html}
+The physical value corresponding to a cell value of zero
+```
+### OnLine resource {#iso19139-elem-gmd-onLine-c0b191c96e7e4d7dfc2a4ba2fd8946f4}
+
+Name
+
+:
+
+> gmd:onLine
+
+Description
+
+:
+
+```{=html}
+Information about online sources from which the resource can be
+ obtained
+```
+``` xml
+
+
+
+
+ http://www.eea.europa.eu/data-and-maps/data/ds_resolveuid/d851e1b7f678468b8f0b1b98930ba3e1
+
+
+
+ WWW:LINK-1.0-http--link
+
+
+
+
+
+
+```
+
+### Website {#iso19139-elem-gmd-onlineResource-8df8ae9d58f947d5aac1e7f95e5b7d59}
+
+Name
+
+:
+
+> gmd:onlineResource
+
+Description
+
+:
+
+```{=html}
+Define URL to access the website
+```
+```{=html}
+On-line information that can be used to contact the individual or
+ organisation
+```
+``` xml
+
+
+
+ http://www.eea.europa.eu
+
+
+ WWW:LINK-1.0-http--link
+
+
+ Europen Environment Agency public website
+
+
+
+
+
+
+
+```
+
+### Ordering instructions {#iso19139-elem-gmd-orderingInstructions-c6c68523c931c7138263c7d7895d9a16}
+
+Name
+
+:
+
+> gmd:orderingInstructions
+
+Description
+
+:
+
+```{=html}
+General instructions, terms and services provided by the
+ distributor
+```
+### Organisation name {#iso19139-elem-gmd-organisationName-d57c55f60d4bce260583a0e176106a31}
+
+Name
+
+:
+
+> gmd:organisationName
+
+Description
+
+:
+
+```{=html}
+Name of the responsible organization
+```
+
+Condition
+
+:
+
+> conditional
+
+### Orientation parameter availability {#iso19139-elem-gmd-orientationParameterAvailability-f4f1451cd1e6fada4b70115d7a0db4de}
+
+Name
+
+:
+
+> gmd:orientationParameterAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not orientation parameters are available
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Orientation parameter description {#iso19139-elem-gmd-orientationParameterDescription-871dba0b5e91443d58af60139e3483f0}
+
+Name
+
+:
+
+> gmd:orientationParameterDescription
+
+Description
+
+:
+
+```{=html}
+Description of parameters used to describe sensor orientation
+```
+### Other {#iso19139-elem-gmd-other-351c20974743a02b7c727421fd10411e}
+
+Name
+
+:
+
+> gmd:other
+
+Description
+
+:
+
+```{=html}
+Class of information that does not fall into the other categories to which the
+ information applies
+```
+### Other citation details {#iso19139-elem-gmd-otherCitationDetails-6045d0424a57c57988ec6627e728189a}
+
+Name
+
+:
+
+> gmd:otherCitationDetails
+
+Description
+
+:
+
+```{=html}
+Other information required to complete the citation that is not recorded
+ elsewhere
+```
+### Other constraints {#iso19139-elem-gmd-otherConstraints-696de5ef421a230cf560f7566a3c5028}
+
+Name
+
+:
+
+> gmd:otherConstraints
+
+Description
+
+:
+
+```{=html}
+Other restrictions and legal prerequisites for accessing and using the
+ resource
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+ no limitations
+
+```
+
+### Page {#iso19139-elem-gmd-page-7e8d6e17c5fe0179acfb038d3475d5dd}
+
+Name
+
+:
+
+> gmd:page
+
+Description
+
+:
+
+```{=html}
+Details on which pages of the publication the article was
+ published
+```
+### Parameter citation {#iso19139-elem-gmd-parameterCitation-6b75cc829b57fd174fa3d5f26ff52591}
+
+Name
+
+:
+
+> gmd:parameterCitation
+
+Description
+
+:
+
+```{=html}
+Reference providing description of the parameters
+```
+### Parent entity {#iso19139-elem-gmd-parentEntity-b8e88cd3a75905b5911d9c84d25a79c6}
+
+Name
+
+:
+
+> gmd:parentEntity
+
+Description
+
+:
+
+```{=html}
+Name of the metadata entity(s) under which this extended metadata element may
+ appear. The name(s) may be standard metadata element(s) or other extended metadata
+ element(s).
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Parent identifier {#iso19139-elem-gmd-parentIdentifier-e660d48fcd79782e330d99a6eee272bc}
+
+Name
+
+:
+
+> gmd:parentIdentifier
+
+Description
+
+:
+
+```{=html}
+File identifier of the metadata to which this metadata is a subset
+ (child)
+```
+``` xml
+
+ df69de7e-3af1-4b4d-94d4-8bebe84c80b0
+
+```
+
+### PartOf {#iso19139-elem-gmd-partOf-9ede50dac93d135983484fd0d7e44495}
+
+Name
+
+:
+
+> gmd:partOf
+
+Description
+
+:
+
+```{=html}
+PartOf
+```
+### Pass {#iso19139-elem-gmd-pass-bcbea9f82051424feefdcaa4953655c4}
+
+Name
+
+:
+
+> gmd:pass
+
+Description
+
+:
+
+```{=html}
+Indication of the conformance result where 0 = fail and 1 = pass
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Peak response {#iso19139-elem-gmd-peakResponse-47e14bef5b9ed8cac08540f6b2ebb11a}
+
+Name
+
+:
+
+> gmd:peakResponse
+
+Description
+
+:
+
+```{=html}
+Wavelength at which the response is the highest
+```
+### Phone {#iso19139-elem-gmd-phone-7bed516b088bd0d9ab349b4eaf477328}
+
+Name
+
+:
+
+> gmd:phone
+
+Description
+
+:
+
+```{=html}
+Telephone numbers at which the organization or individual may be
+ contacted
+```
+### Planned available datetime {#iso19139-elem-gmd-plannedAvailableDateTime-79d43570482162c903674e901789147c}
+
+Name
+
+:
+
+> gmd:plannedAvailableDateTime
+
+Description
+
+:
+
+```{=html}
+Date and time when the dataset will be available
+ (CCYY-MM-DDThh:mm:ss)
+```
+### Point in Pixel {#iso19139-elem-gmd-pointInPixel-39b5630aab74d9327175514d0b64f427}
+
+Name
+
+:
+
+> gmd:pointInPixel
+
+Description
+
+:
+
+```{=html}
+Point in a pixel corresponding to the Earth location of the pixel
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Point of contact {#iso19139-elem-gmd-pointOfContact-2a38035f4c8b63a35a4e6c44e6f4b624}
+
+Name
+
+:
+
+> gmd:pointOfContact
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s) and
+ organizations(s) associated with the resource(s)
+```
+``` xml
+
+
+
+ European Environment Agency
+
+
+
+
+
+
+ Kongens Nytorv 6
+
+
+ Copenhagen
+
+
+ K
+
+
+ 1050
+
+
+ Denmark
+
+
+ eea.enquiries@eea.europa.eu
+
+
+
+
+
+
+ http://www.eea.europa.eu
+
+
+ WWW:LINK-1.0-http--link
+
+
+ Europen Environment Agency public website
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+### Polygon {#iso19139-elem-gmd-polygon-136906da71badd3d1d6c10c5e703e952}
+
+Name
+
+:
+
+> gmd:polygon
+
+Description
+
+:
+
+```{=html}
+Sets of points defining the bounding polygon
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Portrayal catalogue citation {#iso19139-elem-gmd-portrayalCatalogueCitation-7d46a0799fd5dc5455fa1122c5e45608}
+
+Name
+
+:
+
+> gmd:portrayalCatalogueCitation
+
+Description
+
+:
+
+```{=html}
+Bibliographic reference to the portrayal catalogue cited
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Portrayal catalogue info {#iso19139-elem-gmd-portrayalCatalogueInfo-0a09defe8c7ca8431460b5690da9a52d}
+
+Name
+
+:
+
+> gmd:portrayalCatalogueInfo
+
+Description
+
+:
+
+```{=html}
+Provides information about the catalogue of rules defined for the portrayal of
+ a resource(s)
+```
+### Position name {#iso19139-elem-gmd-positionName-9d7a0dfd5bc41e337c9deae85d95b272}
+
+Name
+
+:
+
+> gmd:positionName
+
+Description
+
+:
+
+```{=html}
+Role or position of the responsible person
+```
+
+Condition
+
+:
+
+> conditional
+
+### Postal code {#iso19139-elem-gmd-postalCode-c108b19cdeff41b0d6c4c3cc2dde38c9}
+
+Name
+
+:
+
+> gmd:postalCode
+
+Description
+
+:
+
+```{=html}
+ZIP or other postal code
+```
+### Presentation form {#iso19139-elem-gmd-presentationForm-98bab46932258a48a69ea02060e41909}
+
+Name
+
+:
+
+> gmd:presentationForm
+
+Description
+
+:
+
+```{=html}
+Mode in which the resource is represented
+```
+### Processing level code {#iso19139-elem-gmd-processingLevelCode-9e2c3bf1cbd69b356f1c4f854ece6474}
+
+Name
+
+:
+
+> gmd:processingLevelCode
+
+Description
+
+:
+
+```{=html}
+Image distributor_s code that identifies the level of radiometric and geometric
+ processing that has been applied
+```
+### Processor {#iso19139-elem-gmd-processor-9ef327f7c0d24ccd64eb52cbc0dc76fe}
+
+Name
+
+:
+
+> gmd:processor
+
+Description
+
+:
+
+```{=html}
+Identification of, and means of communication with, person(s) and
+ organization(s) associated with the process step
+```
+### Process step {#iso19139-elem-gmd-processStep-e129334e8e68357571622aba3880e659}
+
+Name
+
+:
+
+> gmd:processStep
+
+Description
+
+:
+
+```{=html}
+Information about an event in the creation process for the data specified by
+ the scope
+```
+
+Condition
+
+:
+
+> conditional
+
+### PropertyType {#iso19139-elem-gmd-propertyType-12fff0b8b43529f0300c32a5e13c9f89}
+
+Name
+
+:
+
+> gmd:propertyType
+
+Description
+
+:
+
+```{=html}
+PropertyType
+```
+### Protocol {#iso19139-elem-gmd-protocol-447dfb15f197f008cd2326a7dab836e8}
+
+Name
+
+:
+
+> gmd:protocol
+
+Description
+
+:
+
+```{=html}
+Connection protocol to be used
+```
+Recommended values
+
+| code | label |
+|--------------------------------------|------------------------------------------------|
+| ESRI:REST | ArcGIS REST Services |
+| GLG:KML-2.0-http-get-map | Google Earth KML service (ver 2.0) |
+| OGC API - Coverages | OGC API - Coverages |
+| OGC API - Features | OGC API - Features |
+| OGC API - Maps | OGC API - Maps |
+| OGC API - Records | OGC API - Records |
+| OGC:CSW | OGC-CSW Catalogue Service for the Web |
+| OGC:KML | OGC-KML Keyhole Markup Language |
+| OGC:GML | OGC-GML Geography Markup Language |
+| OGC:ODS | OGC-ODS OpenLS Directory Service |
+| OGC:OGS | OGC-ODS OpenLS Gateway Service |
+| OGC:OUS | OGC-ODS OpenLS Utility Service |
+| OGC:OPS | OGC-ODS OpenLS Presentation Service |
+| OGC:ORS | OGC-ODS OpenLS Route Service |
+| OGC:SOS | OGC-SOS Sensor Observation Service |
+| OGC:SPS | OGC-SPS Sensor Planning Service |
+| OGC:SAS | OGC-SAS Sensor Alert Service |
+| OGC:WCS | OGC-WCS Web Coverage Service |
+| OGC:WCS-1.1.0-http-get-capabilities | OGC-WCS Web Coverage Service (ver 1.1.0) |
+| OGC:WCTS | OGC-WCTS Web Coordinate Transformation Service |
+| OGC:WFS | OGC-WFS Web Feature Service |
+| INSPIRE Atom | INSPIRE Atom |
+| OGC:WFS-1.0.0-http-get-capabilities | OGC-WFS Web Feature Service (ver 1.0.0) |
+| OGC:WFS-G | OGC-WFS-G Gazzetteer Service |
+| OGC:WMC | OGC-WMC Web Map Context |
+| OGC:WMS | OGC-WMS Web Map Service |
+| OGC:WMS-1.1.1-http-get-capabilities | OGC-WMS Capabilities service (ver 1.1.1) |
+| OGC:WMS-1.3.0-http-get-capabilities | OGC-WMS Capabilities service (ver 1.3.0) |
+| OGC:WMS-1.1.1-http-get-map | OGC Web Map Service (ver 1.1.1) |
+| OGC:WMS-1.3.0-http-get-map | OGC Web Map Service (ver 1.3.0) |
+| OGC:WMTS | OGC-WMTS Web Map Tiled Service |
+| OGC:WMTS-1.0.0-http-get-capabilities | OGC-WMTS Capabilities service (ver 1.0.0) |
+| OGC:SOS-1.0.0-http-get-observation | OGC-SOS Get Observation (ver 1.0.0) |
+| OGC:SOS-1.0.0-http-post-observation | OGC-SOS Get Observation (POST) (ver 1.0.0) |
+| OGC:WNS | OGC-WNS Web Notification Service |
+| OGC:WPS | OGC-WPS Web Processing Service |
+| OGC:OWS-C | OGC OWS Context |
+| TMS | Tiled Map Service |
+| WWW:DOWNLOAD-1.0-ftp--download | File for download through FTP |
+| WWW:DOWNLOAD-1.0-http--download | File for download |
+| | GIS file |
+| | GIS RASTER file |
+| WWW:LINK-1.0-http--ical | iCalendar (URL) |
+| WWW:LINK-1.0-http--link | Web address (URL) |
+| DOI | Digital Object Identifier (DOI) |
+| WWW:LINK-1.0-http--partners | Partner web address (URL) |
+| WWW:LINK-1.0-http--related | Related link (URL) |
+| WWW:LINK-1.0-http--rss | RSS News feed (URL) |
+| WWW:LINK-1.0-http--samples | Showcase product (URL) |
+| DB:POSTGIS | PostGIS database table |
+| DB:ORACLE | ORACLE database table |
+| WWW:LINK-1.0-http--opendap | OPeNDAP URL |
+| RBNB:DATATURBINE | Data Turbine |
+| UKST | Unknown Service Type |
+
+### Free text {#iso19139-elem-gmd-PT_FreeText-00c48876cdf6707df460773d91476446}
+
+Name
+
+:
+
+> gmd:PT_FreeText
+
+Description
+
+:
+
+```{=html}
+Description of a multi-language free text metadata element
+```
+### Locale {#iso19139-elem-gmd-PT_Locale-8114a4813936b84f0e6b123bb5e3018b}
+
+Name
+
+:
+
+> gmd:PT_Locale
+
+Description
+
+:
+
+```{=html}
+Locale
+```
+### PT_LocaleContainer {#iso19139-elem-gmd-PT_LocaleContainer-ec355086fbe079f5ebbbc4857c6eb002}
+
+Name
+
+:
+
+> gmd:PT_LocaleContainer
+
+Description
+
+:
+
+```{=html}
+PT_LocaleContainer
+```
+### Purpose {#iso19139-elem-gmd-purpose-b905736188713702d2a05d889f970ffa}
+
+Name
+
+:
+
+> gmd:purpose
+
+Description
+
+:
+
+```{=html}
+Summary of the intentions with which the resource(s) was
+ developed
+```
+### Radiometric calibration data availability {#iso19139-elem-gmd-radiometricCalibrationDataAvailability-92db9f55cf1ae86606dbd3b7ed2d0b3e}
+
+Name
+
+:
+
+> gmd:radiometricCalibrationDataAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not the radiometric calibration information for
+ generating the radiometrically calibrated standard data product is
+ available
+```
+### Rationale {#iso19139-elem-gmd-rationale-a89f98c606cd39bd67cf29f996518913}
+
+Name
+
+:
+
+> gmd:rationale
+
+Description
+
+:
+
+```{=html}
+Requirement or purpose for the process step
+```
+### Rationale {#iso19139-elem-gmd-rationale-gmd-MD_ExtendedElementInformation-64a2e17ba633ec3f5d97e33b725e8f57}
+
+Name
+
+:
+
+> gmd:rationale
+
+Context
+
+:
+
+> gmd:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Reason for creating the extended element
+```
+### Reference system identifier {#iso19139-elem-gmd-referenceSystemIdentifier-5393a29789a4b6def1795d5a9e70f665}
+
+Name
+
+:
+
+> gmd:referenceSystemIdentifier
+
+Description
+
+:
+
+```{=html}
+Name of reference system
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+
+
+ urn:ogc:def:crs:EPSG:7.1:3035
+
+
+ OGP Surveying & Positioning Committee
+
+
+
+```
+
+### Reference System Information {#iso19139-elem-gmd-referenceSystemInfo-c7702a2e8ac03097e306ab3a02406765}
+
+Name
+
+:
+
+> gmd:referenceSystemInfo
+
+Description
+
+:
+
+```{=html}
+Description of the spatial and temporal reference systems used in the
+ dataset
+```
+``` xml
+
+
+
+
+
+ urn:ogc:def:crs:EPSG:7.1:3035
+
+
+ OGP Surveying & Positioning Committee
+
+
+
+
+
+```
+
+### Report {#iso19139-elem-gmd-report-b06b527383afbca245b4712f3bf3ae44}
+
+Name
+
+:
+
+> gmd:report
+
+Description
+
+:
+
+```{=html}
+Quantitative quality information for the data specified by the
+ scope
+```
+
+Condition
+
+:
+
+> conditional
+
+### Resolution {#iso19139-elem-gmd-resolution-0e9dc8264836da5a43380f555c0b608a}
+
+Name
+
+:
+
+> gmd:resolution
+
+Description
+
+:
+
+```{=html}
+Degree of detail in the grid dataset
+```
+### Resource constraints {#iso19139-elem-gmd-resourceConstraints-3ce815f506c31e6b5ef8e4e7022eefad}
+
+Name
+
+:
+
+> gmd:resourceConstraints
+
+Description
+
+:
+
+```{=html}
+Provides information about constraints which apply to the
+ resource(s)
+```
+### Resource format {#iso19139-elem-gmd-resourceFormat-0c19b5193142c6b6f0aac987fffe8f20}
+
+Name
+
+:
+
+> gmd:resourceFormat
+
+Description
+
+:
+
+```{=html}
+Provides a description of the format of the resource(s)
+```
+### Resource maintenance {#iso19139-elem-gmd-resourceMaintenance-a3c2f1eb185aa1d3e7d475c40a1ff637}
+
+Name
+
+:
+
+> gmd:resourceMaintenance
+
+Description
+
+:
+
+```{=html}
+Provides information about the frequency of resource updates, and the scope of
+ those updates
+```
+``` xml
+
+
+
+
+
+
+
+```
+
+### Resource specific usage {#iso19139-elem-gmd-resourceSpecificUsage-c0f6662f0924e6ebd022b685a53e20ea}
+
+Name
+
+:
+
+> gmd:resourceSpecificUsage
+
+Description
+
+:
+
+```{=html}
+Provides basic information about specific application(s) for which the
+ resource(s) has/have been or is being used by different users
+```
+### Responsible Party {#iso19139-elem-gmd-responsibleParty-b189af81ab93bbbf28bf2b083d6872fd}
+
+Name
+
+:
+
+> gmd:responsibleParty
+
+Description
+
+:
+
+### Result {#iso19139-elem-gmd-result-83539788e54d2fc7d166ac779dc43f0b}
+
+Name
+
+:
+
+> gmd:result
+
+Description
+
+:
+
+```{=html}
+Value (or set of values) obtained from applying a data quality measure or the
+ out come of evaluating the obtained value (or set of values) against a specified
+ acceptable conformance quality level
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Role {#iso19139-elem-gmd-role-gmd-MD_Association-55ee20aa2f0f637012d7953158864d2a}
+
+Name
+
+:
+
+> gmd:role
+
+Context
+
+:
+
+> gmd:MD_Association
+
+Description
+
+:
+
+```{=html}
+Reference to the ends (roles) of a concrete association
+```
+### Role {#iso19139-elem-gmd-role-9b10bc0f5a8317c592877c27ad3012a4}
+
+Name
+
+:
+
+> gmd:role
+
+Description
+
+:
+
+```{=html}
+Function performed by the responsible party
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Identifier {#iso19139-elem-gmd-RS_Identifier-025635f516171e942cfaac8bbf43e014}
+
+Name
+
+:
+
+> gmd:RS_Identifier
+
+Description
+
+:
+
+```{=html}
+Identifier used for reference systems
+```
+### Rule {#iso19139-elem-gmd-rule-887b5f15d45db38bcc0ee11f1a6ca843}
+
+Name
+
+:
+
+> gmd:rule
+
+Description
+
+:
+
+```{=html}
+Specifies how the extended element relates to other existing elements and
+ entities
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Scale Denominator {#iso19139-elem-gmd-scaleDenominator-973704798e0501bf6ac83bd85b435b61}
+
+Name
+
+:
+
+> gmd:scaleDenominator
+
+Description
+
+:
+
+```{=html}
+Denominator of the representative fraction on a source map
+```
+### Scale factor {#iso19139-elem-gmd-scaleFactor-398805b3fa36127ee65a6de3b4f55118}
+
+Name
+
+:
+
+> gmd:scaleFactor
+
+Description
+
+:
+
+```{=html}
+Scale factor which has been applied to the cell value
+```
+### Schema ASCII {#iso19139-elem-gmd-schemaAscii-385bafc95d8b97ba2389183fd84d899e}
+
+Name
+
+:
+
+> gmd:schemaAscii
+
+Description
+
+:
+
+```{=html}
+Full application schema given as an ASCII file
+```
+### Schema language {#iso19139-elem-gmd-schemaLanguage-f8c161d4db9348a3a2305531704febf0}
+
+Name
+
+:
+
+> gmd:schemaLanguage
+
+Description
+
+:
+
+```{=html}
+Identification of the schema language used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Scope {#iso19139-elem-gmd-scope-66b29437893946bbaf08cabb26cdabbd}
+
+Name
+
+:
+
+> gmd:scope
+
+Description
+
+:
+
+```{=html}
+The specific data to which the data quality information applies
+```
+``` xml
+
+
+
+
+
+
+
+```
+
+### Sequence identifier {#iso19139-elem-gmd-sequenceIdentifier-eba100dcb9223d7b7564306d0df388fb}
+
+Name
+
+:
+
+> gmd:sequenceIdentifier
+
+Description
+
+:
+
+```{=html}
+Number that uniquely identifies instances of bands of wavelengths on which a
+ sensor operates
+```
+### Series {#iso19139-elem-gmd-series-98524248b047e1a31966f4fc05c765fb}
+
+Name
+
+:
+
+> gmd:series
+
+Description
+
+:
+
+```{=html}
+Information about the series, or aggregate dataset, of which the dataset is a
+ part
+```
+### SeriesMetadata {#iso19139-elem-gmd-seriesMetadata-4c8e5c0d23156817b1195ca9ab10846d}
+
+Name
+
+:
+
+> gmd:seriesMetadata
+
+Description
+
+:
+
+```{=html}
+SeriesMetadata
+```
+### Short name {#iso19139-elem-gmd-shortName-917a52683f1b7433b4aed3ffc10fc6b3}
+
+Name
+
+:
+
+> gmd:shortName
+
+Description
+
+:
+
+```{=html}
+Short form suitable for use in an implementation method such as XML or SGML.
+ NOTE other methods may be used
+```
+### Software development file {#iso19139-elem-gmd-softwareDevelopmentFile-7a4e9679561964e460d50c3c6584e9e7}
+
+Name
+
+:
+
+> gmd:softwareDevelopmentFile
+
+Description
+
+:
+
+```{=html}
+Full application schema given as a software development file
+```
+### Software development file format {#iso19139-elem-gmd-softwareDevelopmentFileFormat-4dc69820e56575d743271b86b05dea17}
+
+Name
+
+:
+
+> gmd:softwareDevelopmentFileFormat
+
+Description
+
+:
+
+```{=html}
+Software dependent format used for the application schema software dependent
+ file
+```
+### Source {#iso19139-elem-gmd-source-056931601d7cb713381cbf1eea87f599}
+
+Name
+
+:
+
+> gmd:source
+
+Description
+
+:
+
+```{=html}
+Information about the source data used in creating the data specified by the
+ scope
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+```
+
+### Source {#iso19139-elem-gmd-source-gmd-MD_ExtendedElementInformation-459f928a9ea29688b69af501b0fc033e}
+
+Name
+
+:
+
+> gmd:source
+
+Context
+
+:
+
+> gmd:MD_ExtendedElementInformation
+
+Description
+
+:
+
+```{=html}
+Name of the person or organization creating the extended element
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+```
+
+### Source citation {#iso19139-elem-gmd-sourceCitation-4988d0a64d3bd85bdf52c9faa14103de}
+
+Name
+
+:
+
+> gmd:sourceCitation
+
+Description
+
+:
+
+```{=html}
+Recommended reference to be used for the source data
+```
+### Source extent {#iso19139-elem-gmd-sourceExtent-51d5c1b2516371920a3f12b76a38f48b}
+
+Name
+
+:
+
+> gmd:sourceExtent
+
+Description
+
+:
+
+```{=html}
+Information about the spatial, vertical and temporal extent of the source
+ data
+```
+
+Condition
+
+:
+
+> conditional
+
+### Source reference system {#iso19139-elem-gmd-sourceReferenceSystem-fb3e6e3ecd849e31bc89d8f8aeae43a6}
+
+Name
+
+:
+
+> gmd:sourceReferenceSystem
+
+Description
+
+:
+
+```{=html}
+Spatial reference system used by the source data
+```
+### Source step {#iso19139-elem-gmd-sourceStep-d6d84c09e8e8991a68956351c1398122}
+
+Name
+
+:
+
+> gmd:sourceStep
+
+Description
+
+:
+
+```{=html}
+Information about an event in the creation process for the source
+ data
+```
+### South bound {#iso19139-elem-gmd-southBoundLatitude-894a6499ac85eb19180f3fa2a4582263}
+
+Name
+
+:
+
+> gmd:southBoundLatitude
+
+Description
+
+:
+
+```{=html}
+Southern-most coordinate of the limit of the dataset extent, expressed in
+ latitude in decimal degrees (positive north)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ 26.988714
+
+```
+
+### Spatial extent {#iso19139-elem-gmd-spatialExtent-7e0ee4e6812d3469ab8b3853903d1b34}
+
+Name
+
+:
+
+> gmd:spatialExtent
+
+Description
+
+:
+
+```{=html}
+Spatial extent component of composite spatial and temporal extent
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Spatial representation info {#iso19139-elem-gmd-spatialRepresentationInfo-f93705d4877ccd4c41819cc79677d6f2}
+
+Name
+
+:
+
+> gmd:spatialRepresentationInfo
+
+Description
+
+:
+
+```{=html}
+Digital representation of spatial information in the dataset
+```
+### Spatial representation type {#iso19139-elem-gmd-spatialRepresentationType-1617a07231ac2246d0844778962d4ca0}
+
+Name
+
+:
+
+> gmd:spatialRepresentationType
+
+Description
+
+:
+
+```{=html}
+Method used to spatially represent geographic information
+```
+``` xml
+
+
+
+```
+
+### Spatial resolution {#iso19139-elem-gmd-spatialResolution-c248e07cdd5b0b6d769bd187d279535a}
+
+Name
+
+:
+
+> gmd:spatialResolution
+
+Description
+
+:
+
+```{=html}
+Factor which provides a general understanding of the density of spatial data in
+ the dataset
+```
+``` xml
+
+
+
+ 100
+
+
+
+```
+
+### Specification {#iso19139-elem-gmd-specification-gmd-DQ_ConformanceResult-a820ababbd31f20c7492dd90785ec10b}
+
+Name
+
+:
+
+> gmd:specification
+
+Context
+
+:
+
+> gmd:DQ_ConformanceResult
+
+Description
+
+:
+
+```{=html}
+Citation of product specification or user requirement against which data is
+ being evaluated
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Specification {#iso19139-elem-gmd-specification-gmd-MD_Format-1888e6a22d633ee827c05b7f0bcd948c}
+
+Name
+
+:
+
+> gmd:specification
+
+Context
+
+:
+
+> gmd:MD_Format
+
+Description
+
+:
+
+```{=html}
+Name of a subset, profile, or product specification of the format
+```
+### Specification {#iso19139-elem-gmd-specification-4e210a94d2d6b382f34228d46d514e0f}
+
+Name
+
+:
+
+> gmd:specification
+
+Description
+
+:
+
+### Specific usage {#iso19139-elem-gmd-specificUsage-4791e1ef0814b94a33276de9cc4e28d7}
+
+Name
+
+:
+
+> gmd:specificUsage
+
+Description
+
+:
+
+```{=html}
+Brief description of the resource and/or resource series usage
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Statement {#iso19139-elem-gmd-statement-593ac58687a7831e3112879ec00a306e}
+
+Name
+
+:
+
+> gmd:statement
+
+Description
+
+:
+
+```{=html}
+General explanation of the data producer_s knowledge about the lineage of a
+ dataset
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+ The data set production implied 2 steps. First re-classification of
+ CORINE Land Cover 2006 and bathymetry data using the 7 terrestrial (urban, cropland,
+ grassland, woodland and forest, heathland and shrub, sparsely vegetated land,
+ wetland), 1 freshwater (river and lakes), and 4 marine (marine inlets and transitional
+ waters, coastal, shelf, open ocean) classes of the MAES ecosystem typology (Maes et
+ al., 2013). The classes also provide links to major policy lines such as agriculture,
+ forestry, territorial cohesion, water and marine related policies. The second step
+ comprised refinement of the ecosystem types by attributing EUNIS habitat information
+ to each ecosystem type (see http://eunis.eea.europa.eu/habitats.jsp). The refinement
+ process used reference data such as potential natural vegetation, elevation, slope,
+ aspect, soil, geology, environmental regions and other spatial referenced information
+ which allowed attribution of the EUNIS habitat characteristics to the spatial mapping
+ units of the MAES ecosystem types. The geometric and thematic accuracy of EUNIS class
+ presence was also estimated and mapped. The method is described in the EEA Technical
+ Report 06/2015: European Ecosystem Assessment – Concept, Data, and Implementation.
+ The basis for the update was CORINE land cover 2006 (CLC 2006). It includes Albania,
+ Austria, Belgium, Bosnia and Herzegovina, Bulgaria, Croatia, Cyprus, Czech Republic,
+ Denmark, Estonia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Kosovo
+ (under UNSCR 1244/99), Latvia, Liechtenstein, Lithuania, Luxembourg, the former
+ Yugoslavian Republic of Macedonia, Malta, Montenegro, the Netherlands, Norway, Poland,
+ Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
+ the United Kingdom. For Greece that has not participated in the CLC 2006 activity the
+ CLC 2000 data was used instead.
+
+
+```
+
+### Status {#iso19139-elem-gmd-status-d9744a135669d7e6915b63168cf07b27}
+
+Name
+
+:
+
+> gmd:status
+
+Description
+
+:
+
+```{=html}
+Status of the resource(s)
+```
+### Subset {#iso19139-elem-gmd-subset-0bdb2733b084445c24aa766c936bbbf1}
+
+Name
+
+:
+
+> gmd:subset
+
+Description
+
+:
+
+```{=html}
+Subset
+```
+### Superset {#iso19139-elem-gmd-superset-5bde61a529de9ae44e7fdda16a962a52}
+
+Name
+
+:
+
+> gmd:superset
+
+Description
+
+:
+
+```{=html}
+Superset
+```
+### Supplemental Information {#iso19139-elem-gmd-supplementalInformation-70bc533abfda351b79e707eb88576e9a}
+
+Name
+
+:
+
+> gmd:supplementalInformation
+
+Description
+
+:
+
+```{=html}
+Any other descriptive information about the dataset
+```
+### Temporal element {#iso19139-elem-gmd-temporalElement-98c13f1732cd7f7c06320d907eec27ce}
+
+Name
+
+:
+
+> gmd:temporalElement
+
+Description
+
+:
+
+```{=html}
+Provides temporal component of the extent of the referring object
+```
+
+Condition
+
+:
+
+> conditional
+
+``` xml
+
+
+
+
+ 2006-01-01
+ 2006-12-31
+
+
+
+
+```
+
+### TextGroup {#iso19139-elem-gmd-textGroup-a4c4555fd1e21193bfead46ef919ddb2}
+
+Name
+
+:
+
+> gmd:textGroup
+
+Description
+
+:
+
+```{=html}
+TextGroup
+```
+### Thesaurus name {#iso19139-elem-gmd-thesaurusName-9b47e5bba6e4b04eb489a597f7052fa7}
+
+Name
+
+:
+
+> gmd:thesaurusName
+
+Description
+
+:
+
+```{=html}
+Name of the formally registered thesaurus or a similar authoritative source of
+ keywords
+```
+### Title {#iso19139-elem-gmd-title-cc3002a2d81bcdbc5bf4c8735faf6980}
+
+Name
+
+:
+
+> gmd:title
+
+Description
+
+:
+
+```{=html}
+Name by which the cited resource is known
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Title {#iso19139-elem-gmd-title-gmd-MD_Legislation-8081549b6348e976f57d3e1e1649febd}
+
+Name
+
+:
+
+> gmd:title
+
+Context
+
+:
+
+> gmd:MD_Legislation
+
+Description
+
+:
+
+```{=html}
+Reference to legal title
+```
+### Tone gradation {#iso19139-elem-gmd-toneGradation-428708b5612bd1414b331fed6f3006a3}
+
+Name
+
+:
+
+> gmd:toneGradation
+
+Description
+
+:
+
+```{=html}
+Number of discrete numerical values in the grid data
+```
+### Topic category {#iso19139-elem-gmd-topicCategory-beb19f9aa38425d24bc8c438657fff74}
+
+Name
+
+:
+
+> gmd:topicCategory
+
+Description
+
+:
+
+```{=html}
+Main theme(s) of the dataset
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Topology level {#iso19139-elem-gmd-topologyLevel-329db7737da48376e857292bb39d799a}
+
+Name
+
+:
+
+> gmd:topologyLevel
+
+Description
+
+:
+
+```{=html}
+Code which identifies the degree of complexity of the spatial
+ relationships
+```
+### Transfer options {#iso19139-elem-gmd-transferOptions-5d585a7834225f656f9b59b8a350324f}
+
+Name
+
+:
+
+> gmd:transferOptions
+
+Description
+
+:
+
+```{=html}
+Provides information about technical means and media by which a resource is
+ obtained from the distributor
+```
+``` xml
+
+
+
+
+
+
+ http://www.eea.europa.eu/data-and-maps/data/ds_resolveuid/d851e1b7f678468b8f0b1b98930ba3e1
+
+
+
+ WWW:LINK-1.0-http--link
+
+
+
+
+
+
+
+
+```
+
+### Transfer size {#iso19139-elem-gmd-transferSize-6fb8cca7a1c7bf60b84b95ffc22c87d1}
+
+Name
+
+:
+
+> gmd:transferSize
+
+Description
+
+:
+
+```{=html}
+Estimated size of a unit in the specified transfer format, expressed in
+ megabytes. The transfer size is > 0.0
+```
+### Transformation dimension description {#iso19139-elem-gmd-transformationDimensionDescription-fecd0ea824eac2e867a85d80ba80807f}
+
+Name
+
+:
+
+> gmd:transformationDimensionDescription
+
+Description
+
+:
+
+```{=html}
+Description of the information about which grid dimensions are the spatial
+ dimensions
+```
+### Transformation dimension mapping {#iso19139-elem-gmd-transformationDimensionMapping-38cf0a9e5888085e44c75c1dd91663d0}
+
+Name
+
+:
+
+> gmd:transformationDimensionMapping
+
+Description
+
+:
+
+```{=html}
+Information about which grid dimensions are the spatial
+ dimensions
+```
+### Transformation parameter availability {#iso19139-elem-gmd-transformationParameterAvailability-11c9a0d6d9a25e8cf235b1e22c31f83e}
+
+Name
+
+:
+
+> gmd:transformationParameterAvailability
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not parameters for transformation between image
+ coordinates and geographic or map coordinates exist (are available)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Triangulation indicator {#iso19139-elem-gmd-triangulationIndicator-823a9f2b26c8ebb297aad2682939cee2}
+
+Name
+
+:
+
+> gmd:triangulationIndicator
+
+Description
+
+:
+
+```{=html}
+Indication of whether or not triangulation has been performed upon the
+ image
+```
+### Turnaround {#iso19139-elem-gmd-turnaround-b28170fffa4b93f27be7f98c1f5277d9}
+
+Name
+
+:
+
+> gmd:turnaround
+
+Description
+
+:
+
+```{=html}
+Typical turnaround time for the filling of an order
+```
+### Type {#iso19139-elem-gmd-type-3fcd7fe79fb12bc2f3687ac760ab3896}
+
+Name
+
+:
+
+> gmd:type
+
+Description
+
+:
+
+```{=html}
+Subject matter used to group similar keywords
+```
+### Type {#iso19139-elem-gmd-type-gmd-MD_CodeDomain-136dd2846e6d50fe2afe1fbee0b111e1}
+
+Name
+
+:
+
+> gmd:type
+
+Context
+
+:
+
+> gmd:MD_CodeDomain
+
+Description
+
+:
+
+```{=html}
+Datatype of the code domain
+```
+### Type definition {#iso19139-elem-gmd-type-gmd-MD_Type-4a34cb5da02cab9e18a0ece8b743a12e}
+
+Name
+
+:
+
+> gmd:type
+
+Context
+
+:
+
+> gmd:MD_Type
+
+Description
+
+:
+
+```{=html}
+Data type definition
+```
+```{=html}
+Data type definition, formal of informal (i.e. Text12, Line)
+```
+### Value unit {#iso19139-elem-gmd-units-b4d317a2179c6ac4d27f23f2e44414c4}
+
+Name
+
+:
+
+> gmd:units
+
+Description
+
+:
+
+```{=html}
+Units in which sensor wavelengths are expressed
+```
+### Units of distribution {#iso19139-elem-gmd-unitsOfDistribution-fba1dcd6123d4448a543ca1b292783c8}
+
+Name
+
+:
+
+> gmd:unitsOfDistribution
+
+Description
+
+:
+
+```{=html}
+Tiles, layers, geographic areas, etc., in which data is available
+```
+### Update scope {#iso19139-elem-gmd-updateScope-789803d91659dcd11b3b3393c90922f2}
+
+Name
+
+:
+
+> gmd:updateScope
+
+Description
+
+:
+
+```{=html}
+Scope of data to which maintenance is applied
+```
+### Update scope description {#iso19139-elem-gmd-updateScopeDescription-998eb6c6cec2e3f5f61934d06123ad2c}
+
+Name
+
+:
+
+> gmd:updateScopeDescription
+
+Description
+
+:
+
+```{=html}
+Additional information about the range or extent of the resource
+```
+### URL {#iso19139-elem-gmd-URL-1926834a548a71264f070931031c7163}
+
+Name
+
+:
+
+> gmd:URL
+
+Description
+
+:
+
+```{=html}
+URL
+```
+### Usage datetime {#iso19139-elem-gmd-usageDateTime-eb4261bf01930ac70a65c335557a0ffa}
+
+Name
+
+:
+
+> gmd:usageDateTime
+
+Description
+
+:
+
+```{=html}
+Date and time of the first use or range of uses of the resource and/or resource
+ series (YYYY-MM-DDThh:mm:ss)
+```
+### Use constraints {#iso19139-elem-gmd-useConstraints-9f5825b49b04c7539ccf1b67d89cae3a}
+
+Name
+
+:
+
+> gmd:useConstraints
+
+Description
+
+:
+
+```{=html}
+Constraints applied to assure the protection of privacy or intellectual
+ property, and any special restrictions or limitations or warnings on using the
+ resource
+```
+### Use limitation {#iso19139-elem-gmd-useLimitation-07252e81be8d86aea4553aa3df807d8b}
+
+Name
+
+:
+
+> gmd:useLimitation
+
+Description
+
+:
+
+```{=html}
+Limitation affecting the fitness for use of the resource. Example, _not to be
+ used for navigation_
+```
+``` xml
+
+ Unless otherwise indicated, re-use of content on the EEA website
+ for commercial or non-commercial purposes is permitted free of charge, provided that
+ the source is acknowledged. The EEA re-use policy follows Directive 2003/98/EC of the
+ European Parliament and the Council on the re-use of public sector information
+ throughout the European Union and Commission Decision 2006/291/EC, Euratom on the
+ re-use of Commission information. The EEA accepts no responsibility or liability
+ whatsoever for the re-use of content accessible on its website. Any inquiries about
+ re-use of content on the EEA website should be addressed to Ove Caspersen, EEA,
+ Kongens Nytorv 6, DK-1050 Copenhagen K, Tel +45 33 36 71 00, Fax +45 33 36 71 99,
+ e-mail copyrights at eea.europa.eu
+
+
+```
+
+### User contact info {#iso19139-elem-gmd-userContactInfo-441ca49469790a846c9fd368696c77f8}
+
+Name
+
+:
+
+> gmd:userContactInfo
+
+Description
+
+:
+
+```{=html}
+Identification of and means of communicating with person(s) and organization(s)
+ using the resource(s)
+```
+
+Condition
+
+:
+
+> mandatory
+
+### User defined maintenance frequency {#iso19139-elem-gmd-userDefinedMaintenanceFrequency-ad78ef111593b28eb264caef44637052}
+
+Name
+
+:
+
+> gmd:userDefinedMaintenanceFrequency
+
+Description
+
+:
+
+```{=html}
+Maintenance period other than those defined
+```
+### User determined limitations {#iso19139-elem-gmd-userDeterminedLimitations-7298d0a46cbf569447e0db1962896136}
+
+Name
+
+:
+
+> gmd:userDeterminedLimitations
+
+Description
+
+:
+
+```{=html}
+Applications, determined by the user for which the resource and/or resource
+ series is not suitable
+```
+### User note {#iso19139-elem-gmd-userNote-c06ef82acaa22bad47a878213d4a8dea}
+
+Name
+
+:
+
+> gmd:userNote
+
+Description
+
+:
+
+```{=html}
+Explanation of the application of the legal constraints or other restrictions
+ and legal prerequisites for obtaining and using the resource or metadata
+```
+### Value {#iso19139-elem-gmd-value-gmd-DQ_QuantitativeResult-4da008be3457344e7b9b220bd613e546}
+
+Name
+
+:
+
+> gmd:value
+
+Context
+
+:
+
+> gmd:DQ_QuantitativeResult
+
+Description
+
+:
+
+```{=html}
+Quantitative value or values, content determined by the evaluation procedure
+ used
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Value {#iso19139-elem-gmd-value-00279de566515e1bf93ae185e5ffe42f}
+
+Name
+
+:
+
+> gmd:value
+
+Description
+
+:
+
+### Value {#iso19139-elem-gmd-value-gmd-MD_Type-41077608c8230790f00082e7545295d2}
+
+Name
+
+:
+
+> gmd:value
+
+Context
+
+:
+
+> gmd:MD_Type
+
+Description
+
+:
+
+```{=html}
+Data type value
+```
+### Value type {#iso19139-elem-gmd-valueType-3f097375c7a73b4f120433e3774ef780}
+
+Name
+
+:
+
+> gmd:valueType
+
+Description
+
+:
+
+```{=html}
+Quantitative conformance quality level value or range of values
+```
+Recommended values
+
+| code | label |
+|---------------------------------|---------------------------------|
+| Boolean | Boolean |
+| Real | Real |
+| Integer | Integer |
+| Ratio | Ratio |
+| Percentage | Percentage |
+| Measure(s) (value(s) + unit(s)) | Measure(s) (value(s) + unit(s)) |
+
+### Value unit {#iso19139-elem-gmd-valueUnit-65c0838f9052c0ff77f2372033ae87d2}
+
+Name
+
+:
+
+> gmd:valueUnit
+
+Description
+
+:
+
+```{=html}
+Value unit for reporting a data quality result
+```
+
+Condition
+
+:
+
+> mandatory
+
+### Version {#iso19139-elem-gmd-version-gmd-RS_Identifier-d861feedf8dd2aef87eb06aeb0e4a2eb}
+
+Name
+
+:
+
+> gmd:version
+
+Context
+
+:
+
+> gmd:RS_Identifier
+
+Description
+
+:
+
+```{=html}
+Version identifier for the namespace
+```
+``` xml
+
+
+
+```
+
+### Version {#iso19139-elem-gmd-version-30c3096d796063300c4dd7a64593e2aa}
+
+Name
+
+:
+
+> gmd:version
+
+Description
+
+:
+
+```{=html}
+Version of the format (date, number, etc.)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+
+
+```
+
+### Vertical CRS {#iso19139-elem-gmd-verticalCRS-34034733808b1ab00927f9445d415259}
+
+Name
+
+:
+
+> gmd:verticalCRS
+
+Description
+
+:
+
+```{=html}
+Provides information about the origin from which the maximum and minimum elevation
+ values are measured
+```
+### Vertical element {#iso19139-elem-gmd-verticalElement-28aa2675a263f8317e4046addeeae416}
+
+Name
+
+:
+
+> gmd:verticalElement
+
+Description
+
+:
+
+```{=html}
+Provides vertical component of the extent of the referring object
+```
+
+Condition
+
+:
+
+> conditional
+
+### Voice {#iso19139-elem-gmd-voice-4387e4ef043bc3002639aee8885c0a96}
+
+Name
+
+:
+
+> gmd:voice
+
+Description
+
+:
+
+```{=html}
+Telephone number by which individuals can speak to the responsible organization
+ or individual
+```
+### Volumes {#iso19139-elem-gmd-volumes-546112edbc2350b220b2ac0a3b22cf80}
+
+Name
+
+:
+
+> gmd:volumes
+
+Description
+
+:
+
+```{=html}
+Number of items in the media identified
+```
+### West bound {#iso19139-elem-gmd-westBoundLongitude-e24eb3c341fa09426f2c5f733a9151f0}
+
+Name
+
+:
+
+> gmd:westBoundLongitude
+
+Description
+
+:
+
+```{=html}
+Western-most coordinate of the limit of the dataset extent, expressed in
+ longitude in decimal degrees (positive east)
+```
+
+Condition
+
+:
+
+> mandatory
+
+``` xml
+
+ -33.90432
+
+```
+
+### Axis {#iso19139-elem-gml-axis-3fefc5dac3952c40be7017bc2a26f9b7}
+
+Name
+
+:
+
+> gml:axis
+
+Description
+
+:
+
+### Axis abbreviation {#iso19139-elem-gml-axisAbbrev-df25e0618e0c705cdc907bc2965b6239}
+
+Name
+
+:
+
+> gml:axisAbbrev
+
+Description
+
+:
+
+### Axis direction {#iso19139-elem-gml-axisDirection-7c5e69d4b1a66ecd9567ae9529e20da9}
+
+Name
+
+:
+
+> gml:axisDirection
+
+Description
+
+:
+
+### Begin {#iso19139-elem-gml-begin-fcd7703f3e5afd04b33646f5b0d6ea36}
+
+Name
+
+:
+
+> gml:begin
+
+Description
+
+:
+
+### Begin date {#iso19139-elem-gml-beginPosition-1d6323a4d959ef33b6f719047ae9a25d}
+
+Name
+
+:
+
+> gml:beginPosition
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+``` xml
+2006-01-01
+```
+
+### Catalogue symbol {#iso19139-elem-gml-catalogSymbol-8f175b4e3cadb1e37646c4c134f9bcc5}
+
+Name
+
+:
+
+> gml:catalogSymbol
+
+Description
+
+:
+
+### Coordinates {#iso19139-elem-gml-coordinates-d446715f3936aafc2075e980669135bd}
+
+Name
+
+:
+
+> gml:coordinates
+
+Description
+
+:
+
+```{=html}
+Used to record an array of tuples or coordinates.
+```
+### Coordinate system axis {#iso19139-elem-gml-CoordinateSystemAxis-50e3c608cbb8fb6d07159798b299a8b3}
+
+Name
+
+:
+
+> gml:CoordinateSystemAxis
+
+Description
+
+:
+
+### Description {#iso19139-elem-gml-description-473b14977bb5684339b11d3ad6ab4630}
+
+Name
+
+:
+
+> gml:description
+
+Description
+
+:
+
+```{=html}
+Text description of the element
+```
+### Description reference {#iso19139-elem-gml-descriptionReference-0e8fc63ab0aeb3d807a818fad310d15c}
+
+Name
+
+:
+
+> gml:descriptionReference
+
+Description
+
+:
+
+### Domain of validity {#iso19139-elem-gml-domainOfValidity-8c497852e8c983accd03d26668bf6fc4}
+
+Name
+
+:
+
+> gml:domainOfValidity
+
+Description
+
+:
+
+### Duration {#iso19139-elem-gml-duration-6f1b3e01444852276db9d1615edb9cd2}
+
+Name
+
+:
+
+> gml:duration
+
+Description
+
+:
+
+```{=html}
+Conforms to the ISO 8601 syntax for temporal length as implemented by the XML
+ Schema duration type.
+```
+### End {#iso19139-elem-gml-end-b99c9d3cc2fa4edcdc69ee20ca1b674e}
+
+Name
+
+:
+
+> gml:end
+
+Description
+
+:
+
+### End date {#iso19139-elem-gml-endPosition-466dd41e369b5b90bb57a53dcf488685}
+
+Name
+
+:
+
+> gml:endPosition
+
+Description
+
+:
+
+```{=html}
+Formatted as 2007-09-12T15:00:00 (YYYY-MM-DDTHH:mm:ss)
+```
+``` xml
+2006-12-31
+```
+
+### Outer boundary {#iso19139-elem-gml-exterior-49870353f6025fcb331e0d0e87168e54}
+
+Name
+
+:
+
+> gml:exterior
+
+Description
+
+:
+
+```{=html}
+The outer boundary of a solid.
+```
+### Identifier {#iso19139-elem-gml-id-e8faeae0ab7c5bebeb5cba50387cfd35}
+
+Name
+
+:
+
+> gml:id
+
+Description
+
+:
+
+```{=html}
+Unique identifier
+```
+### Ellipsoid {#iso19139-elem-gml-id-gmd-MD_CRS-e2a3e87e63c806772242ecb35ff81500}
+
+Name
+
+:
+
+> gml:id
+
+Context
+
+:
+
+> gmd:MD_CRS
+
+Description
+
+:
+
+```{=html}
+Identity of the ellipsoid used
+```
+```{=html}
+identity of the ellipsoid used
+```
+### Identifier {#iso19139-elem-gml-identifier-d7806b0981ddec95743cf0e85ac8d36f}
+
+Name
+
+:
+
+> gml:identifier
+
+Description
+
+:
+
+### Inner boundary {#iso19139-elem-gml-interior-6ddebd0b5c7dc0777295fc86afb4313c}
+
+Name
+
+:
+
+> gml:interior
+
+Description
+
+:
+
+```{=html}
+The inner boundary of a solid
+```
+### Linear ring {#iso19139-elem-gml-LinearRing-1bc0cfb7a90a767379f93b111300ac0e}
+
+Name
+
+:
+
+> gml:LinearRing
+
+Description
+
+:
+
+```{=html}
+A gml:LinearRing is defined by four or more coordinate tuples, with linear
+ interpolation between them; the first and last coordinates shall be
+ coincident.
+```
+### Line {#iso19139-elem-gml-LineString-b166d0e353c3e73518b724843023efa3}
+
+Name
+
+:
+
+> gml:LineString
+
+Description
+
+:
+
+```{=html}
+A gml:LineString is a special curve that consists of a single segment with
+ linear interpolation. It is defined by two or more coordinate tuples, with linear
+ interpolation between them.
+```
+### Maximum value {#iso19139-elem-gml-maximumValue-68f16f3f15cbadbf4b0c79c0de6f6d66}
+
+Name
+
+:
+
+> gml:maximumValue
+
+Description
+
+:
+
+### Metadata property {#iso19139-elem-gml-metaDataProperty-af33b267cd577920546a32c08acec8c5}
+
+Name
+
+:
+
+> gml:metaDataProperty
+
+Description
+
+:
+
+### Minimum value {#iso19139-elem-gml-minimumValue-6223553305a9824c34b3609d668a341e}
+
+Name
+
+:
+
+> gml:minimumValue
+
+Description
+
+:
+
+### Name {#iso19139-elem-gml-name-14e682acf85693b8dfb78d998145cf51}
+
+Name
+
+:
+
+> gml:name
+
+Description
+
+:
+
+### Point {#iso19139-elem-gml-Point-236f5581e92c5dfacd954d5bed8a1b5c}
+
+Name
+
+:
+
+> gml:Point
+
+Description
+
+:
+
+```{=html}
+A gml:Point is defined by a single coordinate tuple.
+```
+### Polygon {#iso19139-elem-gml-Polygon-b82b498d78a2b6eec8fe7f45ea7211f7}
+
+Name
+
+:
+
+> gml:Polygon
+
+Description
+
+:
+
+```{=html}
+A gml:Polygon is a special surface that is defined by a single surface patch.
+ The boundary of this patch is coplanar and the polygon uses planar interpolation in its
+ interior.
+```
+### Projected CRS {#iso19139-elem-gml-ProjectedCRS-f948bfb32d6ed749c86a752010533ba7}
+
+Name
+
+:
+
+> gml:ProjectedCRS
+
+Description
+
+:
+
+### Quantity Type {#iso19139-elem-gml-quantityType-d7b9caf379c87262ea3f4942b6ce87a0}
+
+Name
+
+:
+
+> gml:quantityType
+
+Description
+
+:
+
+### Quantity Type Reference {#iso19139-elem-gml-quantityTypeReference-2cfae888d8691872634683ab688ee495}
+
+Name
+
+:
+
+> gml:quantityTypeReference
+
+Description
+
+:
+
+### Range meaning {#iso19139-elem-gml-rangeMeaning-49f4157213948e7780595134a0b92110}
+
+Name
+
+:
+
+> gml:rangeMeaning
+
+Description
+
+:
+
+### Realization epoch {#iso19139-elem-gml-realizationEpoch-e4489082a0b01cdc199d2888a25a963f}
+
+Name
+
+:
+
+> gml:realizationEpoch
+
+Description
+
+:
+
+### Related time {#iso19139-elem-gml-relatedTime-505f65f26a66aa61f3d6646b84b1013b}
+
+Name
+
+:
+
+> gml:relatedTime
+
+Description
+
+:
+
+```{=html}
+Defines the relation of a given time to the object.
+```
+### Remarks {#iso19139-elem-gml-remarks-f62f842081ee60b9c42dd65a57b7f45d}
+
+Name
+
+:
+
+> gml:remarks
+
+Description
+
+:
+
+### Scope {#iso19139-elem-gml-scope-8a0aa936cc32e5ee6b5973381fe80db5}
+
+Name
+
+:
+
+> gml:scope
+
+Description
+
+:
+
+### Time edge {#iso19139-elem-gml-TimeEdge-2b29e2f8f85c4fc53a553674e4277644}
+
+Name
+
+:
+
+> gml:TimeEdge
+
+Description
+
+:
+
+### Time instant {#iso19139-elem-gml-TimeInstant-e042092aa87a5391fc360ec34e412e96}
+
+Name
+
+:
+
+> gml:TimeInstant
+
+Description
+
+:
+
+### Time interval {#iso19139-elem-gml-timeInterval-b6f129024d67efd7c0614e30e6564f32}
+
+Name
+
+:
+
+> gml:timeInterval
+
+Description
+
+:
+
+```{=html}
+conforms to ISO 11404 which is based on floating point values for temporal length.
+ ISO 11404 syntax specifies the use of a positiveInteger together with appropriate values for
+ radix and factor. The resolution of the time interval is to one radix ^(-factor) of the
+ specified time unit.
+ The value of the unit is either selected from the units for time intervals from ISO 31-1:1992,
+ or is another suitable unit. The encoding is defined for GML in gml:TimeUnitType. The second
+ component of this union type provides a method for indicating time units other than the six
+ standard units given in the enumeration.
+```
+### Time node {#iso19139-elem-gml-TimeNode-c03fe80fbd29824670ed95a8a519b5c6}
+
+Name
+
+:
+
+> gml:TimeNode
+
+Description
+
+:
+
+### Time period {#iso19139-elem-gml-TimePeriod-a5053bd95c76a6e191ffaa0b8e83f68c}
+
+Name
+
+:
+
+> gml:TimePeriod
+
+Description
+
+:
+
+``` xml
+
+ 2006-01-01
+ 2006-12-31
+
+```
+
+### Time position {#iso19139-elem-gml-timePosition-659967113b43569d7fc2280efe5729b3}
+
+Name
+
+:
+
+> gml:timePosition
+
+Description
+
+:
+
+### Time position {#iso19139-elem-gml-TimePosition-68b54fb54b86e8c5a00afe7d12b835c5}
+
+Name
+
+:
+
+> gml:TimePosition
+
+Description
+
+:
+
+### unitsSystem {#iso19139-elem-gml-unitsSystem-0206dd6fb8b96985f94443d14d675927}
+
+Name
+
+:
+
+> gml:unitsSystem
+
+Description
+
+:
+
+### Unit of measure {#iso19139-elem-gml-uom-d45a808198fd4d356dcf4684218aed03}
+
+Name
+
+:
+
+> gml:uom
+
+Description
+
+:
+
+### Vertical CRS {#iso19139-elem-gml-VerticalCRS-a414c00efb0426d91a8c140471c7a36d}
+
+Name
+
+:
+
+> gml:VerticalCRS
+
+Description
+
+:
+
+### Vertical CS {#iso19139-elem-gml-verticalCS-e44a286116a042cd66d8c9a185537785}
+
+Name
+
+:
+
+> gml:verticalCS
+
+Description
+
+:
+
+### Vertical CS {#iso19139-elem-gml-VerticalCS-e37f66628a9000cd0b4e612a1112becf}
+
+Name
+
+:
+
+> gml:VerticalCS
+
+Description
+
+:
+
+### Vertical datum {#iso19139-elem-gml-verticalDatum-8b0192217f46b813d6fbd5d5cbe6ff87}
+
+Name
+
+:
+
+> gml:verticalDatum
+
+Description
+
+:
+
+### Vertical datum {#iso19139-elem-gml-VerticalDatum-31b851524264ca4dd621e6d16600b4d4}
+
+Name
+
+:
+
+> gml:VerticalDatum
+
+Description
+
+:
+
+### Anchor {#iso19139-elem-gmx-Anchor-d0ccf7ef89bd129a31fe766fae38f1df}
+
+Name
+
+:
+
+> gmx:Anchor
+
+Description
+
+:
+
+```{=html}
+Supports hyper-linking capabilities and ensures a web-like implementation of
+ CharacterStrings
+```
+### Field of application {#iso19139-elem-gmx-fieldOfApplication-f2323295efe7d63cdd639724e044b20b}
+
+Name
+
+:
+
+> gmx:fieldOfApplication
+
+Description
+
+:
+
+```{=html}
+Field of application
+```
+### File name {#iso19139-elem-gmx-FileName-37df0ee2c2072b5a1f6088f3a8d1b023}
+
+Name
+
+:
+
+> gmx:FileName
+
+Description
+
+:
+
+```{=html}
+File name and source URL.
+```
+### Name {#iso19139-elem-gmx-name-c095560004def24f75abbb05e2d62079}
+
+Name
+
+:
+
+> gmx:name
+
+Description
+
+:
+
+```{=html}
+Feature catalogue name
+```
+### Scope {#iso19139-elem-gmx-scope-d18924953739105e2d01daf31cf284e0}
+
+Name
+
+:
+
+> gmx:scope
+
+Description
+
+:
+
+```{=html}
+Scope definition
+```
+### Date {#iso19139-elem-gmx-versionDate-3f4501418cb1164a3da629e121552ecd}
+
+Name
+
+:
+
+> gmx:versionDate
+
+Description
+
+:
+
+```{=html}
+Catalogue date
+```
+### Version {#iso19139-elem-gmx-versionNumber-45d0e848e304b12f16f75be3f780c97c}
+
+Name
+
+:
+
+> gmx:versionNumber
+
+Description
+
+:
+
+```{=html}
+Catalogue version
+```
+### Period duration {#iso19139-elem-gts-TM_PeriodDuration-e6be5bc9a1ef33b78246171f9d092eb5}
+
+Name
+
+:
+
+> gts:TM_PeriodDuration
+
+Description
+
+:
+
+```{=html}
+The duration data type is used to specify a time interval.
+
+The time interval is specified in the following form "PnYnMnDTnHnMnS" where:
+
+* P indicates the period (required)
+* nY indicates the number of years
+* nM indicates the number of months
+* nD indicates the number of days
+* T indicates the start of a time section (required if you are going to specify hours,
+minutes, or seconds)
+* nH indicates the number of hours
+* nM indicates the number of minutes
+* nS indicates the number of seconds
+```
+### Hidden Elements {#iso19139-elem-hidden-elements-3fcbdb1b81d4fa9c9694a3e7fa33ae88}
+
+Name
+
+:
+
+> hidden-elements
+
+Description
+
+:
+
+```{=html}
+Child elements and attributes have been hidden because you do no have access to
+ view those elements
+```
+### Identifier {#iso19139-elem-id-0dd23b8448c65513bc5df360f10d9f80}
+
+Name
+
+:
+
+> id
+
+Description
+
+:
+
+```{=html}
+Unique identifier
+```
+### Indeterminate position {#iso19139-elem-indeterminatePosition-260a886b2a2f47a9172910d795854c9c}
+
+Name
+
+:
+
+> indeterminatePosition
+
+Description
+
+:
+
+### Standard codelists Indeterminate position (indeterminatePosition)
+
+| code | label |
+|---------|---------|
+| after | After |
+| before | Before |
+| now | Now |
+| unknown | Unknown |
+
+### Indirect projection system (for non geographical resources) {#iso19139-elem-InDirectReferenceSystem-0267274a7311c04c19a066850b7c34da}
+
+Name
+
+:
+
+> InDirectReferenceSystem
+
+Description
+
+:
+
+```{=html}
+ReferenceSystem derived / specify that it is an indirect
+ reference
+```
+### Radix {#iso19139-elem-radix-f013f1c6757bf6c47831308d9161bdc0}
+
+Name
+
+:
+
+> radix
+
+Description
+
+:
+
+### Source URL {#iso19139-elem-src-45b17fa1ca5386cd5f963342f4af3e0d}
+
+Name
+
+:
+
+> src
+
+Description
+
+:
+
+```{=html}
+URL of the document.
+```
+### Spatial Reference System Name {#iso19139-elem-srsName-b8afc1ab5f5b09552205c4795ccadeaa}
+
+Name
+
+:
+
+> srsName
+
+Description
+
+:
+
+```{=html}
+Name of the Spatial Reference System. By default set to
+ geographic (epsg:4326)
+```
+### Access Properties {#iso19139-elem-srv-accessProperties-0b17bae21a9a08a66679b18470ccc23e}
+
+Name
+
+:
+
+> srv:accessProperties
+
+Description
+
+:
+
+```{=html}
+Information about the availability of the service eg. fees, availability,
+ oredering instructions
+```
+### Connect Point {#iso19139-elem-srv-connectPoint-7982557d282f2f8e26ce6349f893e18f}
+
+Name
+
+:
+
+> srv:connectPoint
+
+Description
+
+:
+
+```{=html}
+Handle for accessing the service interface
+```
+### Contains Operations {#iso19139-elem-srv-containsOperations-5765a967aadd33b5ba92cde03c9ce30e}
+
+Name
+
+:
+
+> srv:containsOperations
+
+Description
+
+:
+
+```{=html}
+Provides information about the operations that comprise the
+ service
+```
+### Coupled Resource {#iso19139-elem-srv-coupledResource-09de21d33ee8e6c814d675f23350d40e}
+
+Name
+
+:
+
+> srv:coupledResource
+
+Description
+
+:
+
+```{=html}
+Details of services coupled with this one
+```
+### Coupling Type {#iso19139-elem-srv-couplingType-bc1606dff717a83807e97a1a3789e30a}
+
+Name
+
+:
+
+> srv:couplingType
+
+Description
+
+:
+
+```{=html}
+Type of Coupling
+```
+### Distributed Computing Platforms {#iso19139-elem-srv-DCP-4da4ef80cec961d437cc5191b256fb0f}
+
+Name
+
+:
+
+> srv:DCP
+
+Description
+
+:
+
+```{=html}
+Distributed computing platforms on which the operation has been
+ implemented
+```
+### Distributed Computing Platforms list {#iso19139-elem-srv-DCPList-dbbe623a769e6242e8fc2c6cb1ab4a6e}
+
+Name
+
+:
+
+> srv:DCPList
+
+Description
+
+:
+
+### Standard codelists Distributed Computing Platforms list (srv:DCPList)
+
+| description | code | label |
+|--------------------|-------------|--------------|
+| DCP is XML | XML | XML |
+| DCP is CORBA | CORBA | CORBA |
+| DCP is JAVA | JAVA | JAVA |
+| DCP is COM | COM | COM |
+| DCP is SQL | SQL | SQL |
+| DCP is WebServices | WebServices | Web services |
+
+### Depends On {#iso19139-elem-srv-dependsOn-f4d4b9fc1640b60874e70642ab2280be}
+
+Name
+
+:
+
+> srv:dependsOn
+
+Description
+
+:
+
+```{=html}
+List of operations that must be completed immediately before current operation
+ is invoked, structured as a list for capturing alternate predecessor paths and sets for
+ capturing parallel predecessor paths
+```
+### Description {#iso19139-elem-srv-description-5b9e6dc049d103b7b405144a4b2ddc54}
+
+Name
+
+:
+
+> srv:description
+
+Description
+
+:
+
+```{=html}
+Narrative explanation of the services in the chain and resulting output or role
+ of the parameter
+```
+### Direction {#iso19139-elem-srv-direction-6554a8cbde610419936242537ba0f647}
+
+Name
+
+:
+
+> srv:direction
+
+Description
+
+:
+
+### Extent {#iso19139-elem-srv-extent-64a5e3a1fb91876497dd5bad40e89e49}
+
+Name
+
+:
+
+> srv:extent
+
+Description
+
+:
+
+```{=html}
+Geographic/Temporal Extent of Service
+```
+### Identifier {#iso19139-elem-srv-identifier-c2dabee10730bbcfc96d13572c1cec92}
+
+Name
+
+:
+
+> srv:identifier
+
+Description
+
+:
+
+```{=html}
+Identifier of resource to which the operation applies
+```
+### Invocation Name {#iso19139-elem-srv-invocationName-ff1507450b257e37f591b7f95addbdad}
+
+Name
+
+:
+
+> srv:invocationName
+
+Description
+
+:
+
+```{=html}
+The name used to invoke this interface within the context of the DCP. The name
+ is identical for all DCPs
+```
+### Keywords {#iso19139-elem-srv-keywords-f46cb2bd1f2e70ef2e62eb2edb510123}
+
+Name
+
+:
+
+> srv:keywords
+
+Description
+
+:
+
+```{=html}
+Keywords describing service
+```
+### Name {#iso19139-elem-srv-name-9889811abcd6d2d0bc76dc5467a06f7e}
+
+Name
+
+:
+
+> srv:name
+
+Description
+
+:
+
+```{=html}
+The name, as used by the service for this chain or parameter
+```
+### Operates On {#iso19139-elem-srv-operatesOn-fc0165e60dcb452c05c9f1d95416b89a}
+
+Name
+
+:
+
+> srv:operatesOn
+
+Description
+
+:
+
+```{=html}
+Provides information on the datasets that the service operates on
+```
+### Operation Description {#iso19139-elem-srv-operationDescription-61305b5372e54d3cdd60a8dc8b1587c7}
+
+Name
+
+:
+
+> srv:operationDescription
+
+Description
+
+:
+
+```{=html}
+Free text description of the intent of the operation and the results of the
+ operation
+```
+### Operation Name {#iso19139-elem-srv-operationName-33abdef7fb8954ae3842f74904326896}
+
+Name
+
+:
+
+> srv:operationName
+
+Description
+
+:
+
+```{=html}
+A unique identifier for this interface
+```
+### Optionality {#iso19139-elem-srv-optionality-32be37d11746cc993b5b447b15480f70}
+
+Name
+
+:
+
+> srv:optionality
+
+Description
+
+:
+
+```{=html}
+Indication if the parameter is required
+```
+### Parameters {#iso19139-elem-srv-parameters-c842f4d88772de0790d36a4789c54b0c}
+
+Name
+
+:
+
+> srv:parameters
+
+Description
+
+:
+
+```{=html}
+The parameters that are required for this interface
+```
+### Provider Name {#iso19139-elem-srv-providerName-67c5eeff01e2702cdca4d5543566b572}
+
+Name
+
+:
+
+> srv:providerName
+
+Description
+
+:
+
+```{=html}
+A unique identifier for this organization
+```
+### Repeatability {#iso19139-elem-srv-repeatability-20aecf37a789cf6d34f906ca151e6cfb}
+
+Name
+
+:
+
+> srv:repeatability
+
+Description
+
+:
+
+```{=html}
+Indication if more than one value of the parameter may be
+ provided
+```
+### Restrictions {#iso19139-elem-srv-restrictions-eddcbda30442882032776be29da19b00}
+
+Name
+
+:
+
+> srv:restrictions
+
+Description
+
+:
+
+```{=html}
+Legal and security constraints on accessing the service and distributing data
+ generated by the service
+```
+### Service Contact {#iso19139-elem-srv-serviceContact-ecd84df84bea000426f14d1faaf78266}
+
+Name
+
+:
+
+> srv:serviceContact
+
+Description
+
+:
+
+```{=html}
+Information for contacting the service provider
+```
+### Service Type {#iso19139-elem-srv-serviceType-31230933e2a7436c80955195b74bc0a0}
+
+Name
+
+:
+
+> srv:serviceType
+
+Description
+
+:
+
+```{=html}
+Service type name from a registry of services. For example, the values of the
+ nameSpace and name attributes of GeneralName may be 'OGC' and 'catalogue'
+```
+Recommended values
+
+| code | label |
+|-------------------|-------------------------------------------------|
+| OGC:WMS | OGC Web Map Service (OGC:WMS) |
+| OGC:WFS | OGC Web Feature Service (OGC:WFS) |
+| OGC:WCS | OGC Web Coverage Service (OGC:WCS) |
+| W3C:HTML:DOWNLOAD | Download (W3C:HTML:DOWNLOAD) |
+| W3C:HTML:LINK | Information (W3C:HTML:LINK) |
+| discovery | INSPIRE Discovery Service (discovery) |
+| view | INSPIRE View Service (view) |
+| download | INSPIRE Download Service (download) |
+| transformation | INSPIRE Transformation Service (transformation) |
+| other | INSPIRE Other Services (other) |
+
+### Service Version {#iso19139-elem-srv-serviceTypeVersion-4187a8061f591f97903093667295daa0}
+
+Name
+
+:
+
+> srv:serviceTypeVersion
+
+Description
+
+:
+
+```{=html}
+Provides for searching based on the version of serviceType. For example, we may
+ only be interested in OGC Catalogue V1.1 services. If version is maintained as a
+ separate attribute, users can easily search for all services of a type regardless of the
+ version
+```
+### Coupled Resource {#iso19139-elem-srv-SV_CoupledResource-2d85cb6b044791b72116ba2a107bf03e}
+
+Name
+
+:
+
+> srv:SV_CoupledResource
+
+Description
+
+:
+
+```{=html}
+Details of services coupled with this one
+```
+### Coupling Type {#iso19139-elem-srv-SV_CouplingType-0ccd187bb4e974353b2967aeda26bb4f}
+
+Name
+
+:
+
+> srv:SV_CouplingType
+
+Description
+
+:
+
+```{=html}
+Type of Coupling
+```
+### Standard codelists Coupling Type (srv:SV_CouplingType)
+
+| code | label | description |
+|-------|-------|-------------------------------------------------------------------------------|
+| tight | Tight | Tightly coupled: data associated |
+| mixed | Mixed | Mixed coupled: data associated; in addition, external data might be processed |
+| loose | Loose | Loosely coupled: no data associated |
+
+### Operation {#iso19139-elem-srv-SV_OperationMetadata-360f31d3dfaf07269e52a98bdfd0782a}
+
+Name
+
+:
+
+> srv:SV_OperationMetadata
+
+Description
+
+:
+
+```{=html}
+Operation Metadata
+```
+### Parameter {#iso19139-elem-srv-SV_Parameter-614c824c473c037ce821444bc369929f}
+
+Name
+
+:
+
+> srv:SV_Parameter
+
+Description
+
+:
+
+```{=html}
+The parameters that are required for this interface
+```
+### Parameter direction {#iso19139-elem-srv-SV_ParameterDirection-fb7b80e085fc9d52b922e6ff63de2c0a}
+
+Name
+
+:
+
+> srv:SV_ParameterDirection
+
+Description
+
+:
+
+### Standard codelists Parameter direction (srv:SV_ParameterDirection)
+
+| code | label |
+|--------|--------------|
+| in | Input |
+| out | Output |
+| in/out | Input/output |
+
+### Service Identification (19119) {#iso19139-elem-srv-SV_ServiceIdentification-a03600ef3a3f59be9f022c9137a72deb}
+
+Name
+
+:
+
+> srv:SV_ServiceIdentification
+
+Description
+
+:
+
+```{=html}
+ISO 19119-2005 Service Identification
+```
+### Value type {#iso19139-elem-srv-valueType-5760ec25a3f9d6ee283d5fb5c6248c7c}
+
+Name
+
+:
+
+> srv:valueType
+
+Description
+
+:
+
+### Unit {#iso19139-elem-unit-945d85b3b91c6edfaa79c28f5354e396}
+
+Name
+
+:
+
+> unit
+
+Description
+
+:
+
+### Units of measure {#iso19139-elem-uom-deee964fae8827c5a9435a07abe4ceea}
+
+Name
+
+:
+
+> uom
+
+Description
+
+:
+
+Recommended values
+
+| code | label |
+|------|--------|
+| m | meters |
+
+### Metadata uuid {#iso19139-elem-uuidref-6f0ce82fb9f437e7a80804c85857a44a}
+
+Name
+
+:
+
+> uuidref
+
+Description
+
+:
+
+```{=html}
+Unique identifier
+```
+### URL {#iso19139-elem-xlink-href-24b46a26bc2f93ddbf7ff3a48bed324f}
+
+Name
+
+:
+
+> xlink:href
+
+Description
+
+:
+
+```{=html}
+Supplies the data that allows an XLink application to find a remote resource (or
+ resource fragment) [W3C XLINK]
+```
+### URL title {#iso19139-elem-xlink-title-83b73e889fe529eac02adecd853aa587}
+
+Name
+
+:
+
+> xlink:title
+
+Description
+
+:
+
+### Link {#iso19139-elem-xlink-type-2f3d5b15ae49cb486c0f798f25eb6ca0}
+
+Name
+
+:
+
+> xlink:type
+
+Description
+
+:
+
+```{=html}
+Link type
+```
+### Years {#iso19139-elem-years-b93df09e5de0ac46f913523035856630}
+
+Name
+
+:
+
+> years
+
+Description
+
+:
+
+### Zone {#iso19139-elem-zone-30b632c8b09244100577dcf6c0ddf419}
+
+Name
+
+:
+
+> zone
+
+Description
+
+:
+
+```{=html}
+Unique identifier for 100,000 metre grid zone
+```
+## Standard codelists
+
+List of all codelists available in the standard.
+
+### Standard codelists Date type code (gmd:CI_DateTypeCode) {#iso19139-cl-gmd-CI_DateTypeCode}
+
+| code | label | description |
+|-------------|-------------|---------------------------------------------------------------------------------------|
+| creation | Creation | Date identifies when the resource was brought into existence |
+| publication | Publication | Date identifies when the resource was issued |
+| revision | Revision | Date identifies when the resource was examined or re-examined and improved or amended |
+
+### Standard codelists OnLine function code (gmd:CI_OnLineFunctionCode) {#iso19139-cl-gmd-CI_OnLineFunctionCode}
+
+| code | label | description |
+|---------------|----------------|----------------------------------------------------------------------------------------|
+| download | Download | Online instructions for transferring data from one storage device or system to another |
+| information | Information | Online information about the resource |
+| offlineAccess | Offline access | Online instructions for requesting the resource from the provider |
+| order | Order | Online order process for obtening the resource |
+| search | Search | Online search interface for seeking out information about the resource |
+
+### Standard codelists Presentatiewijze code (gmd:CI_PresentationFormCode) {#iso19139-cl-gmd-CI_PresentationFormCode}
+
+| code | label | description |
+|------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| documentDigital | Digital document | Digital representation of a primarily textual item (can contain illustrations also) |
+| imageDigital | Digital image | Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format |
+| documentHardcopy | Hardcopy document | Representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media |
+| imageHardcopy | Hardcopy image | Likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user |
+| mapDigital | Digital map | Map represented in raster or vector form |
+| mapHardcopy | Hardcopy map | Map printed on paper, photographic material, or other media for use directly by the human user |
+| modelDigital | Digital model | Multi-dimensional digital representation of a feature, process, etc. |
+| modelHardcopy | Hardcopy model | 3-dimensional, physical model |
+| profileDigital | Digital profile | Vertical cross-section in digital form |
+| profileHardcopy | Hardcopy profile | Vertical cross-section printed on paper, etc. |
+| tableDigital | Digital table | Digital representation of facts or figures systematically displayed, especially in columns |
+| tableHardcopy | Hardcopy table | Representation of facts or figures systematically displayed, especially in columns, printed onpapers, photographic material, or other media |
+| videoDigital | Digital video | Digital video recording |
+| videoHardcopy | Hardcopy video | Video recording on film |
+
+### Standard codelists Role code (gmd:CI_RoleCode) {#iso19139-cl-gmd-CI_RoleCode}
+
+| code | label | description |
+|-----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| resourceProvider | Resource provider | Party that supplies the resource |
+| custodian | Custodian | Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource |
+| owner | Owner | Party that owns the resource |
+| user | User | Party who uses the resource |
+| distributor | Distributor | Party who distributes the resource |
+| originator | Originator | Party who created the resource |
+| pointOfContact | Point of contact | Party who can be contacted for acquiring knowledge about or acquisition of the resource |
+| principalInvestigator | Principal investigator | Key party responsible for gathering information and conducting research |
+| processor | Processor | Party that has processed the data in a manner such that the resource has been modified |
+| publisher | Publisher | Party who published the resource |
+| author | Author | Party who authored the resource |
+
+### Standard codelists Evaluation method type code (gmd:DQ_EvaluationMethodTypeCode) {#iso19139-cl-gmd-DQ_EvaluationMethodTypeCode}
+
+| code | label | description |
+|----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| directInternal | Direct internal | Method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated |
+| directExternal | Direct external | Method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data external to the dataset being evaluated is required |
+| indirect | Indirect | Method of evaluating the quality of a dataset based on external knowledge |
+
+### Standard codelists Association Type (gmd:DS_AssociationTypeCode) {#iso19139-cl-gmd-DS_AssociationTypeCode}
+
+| code | label | description |
+|------------------------|---------------------------|-------------------------------------------------------------------------------------|
+| crossReference | Cross reference | Reference from one dataset to another |
+| largerWorkCitation | Larger work citation | Reference to a master dataset of which this one is a part |
+| partOfSeamlessDatabase | Part of seamless database | Part of the same structured set of data held in a computer |
+| source | Source | Mapping and charting information from which the dataset content originates |
+| stereoMate | Stereo mate | Part of a set of imagery that when used together, provides three-dimensional images |
+
+### Standard codelists Initiative Type (gmd:DS_InitiativeTypeCode) {#iso19139-cl-gmd-DS_InitiativeTypeCode}
+
+| code | label | description |
+|---------------|---------------|-------------------------------------------------------------|
+| campaign | Campaign | Series of organized planned actions |
+| collection | Collection | Accumulation of datasets assembled for a specific purpose |
+| exercise | Exercise | Specific performance of a function or group of functions |
+| experiment | Experiment | Process designed to find if something is effective or valid |
+| investigation | Investigation | Search or systematic inquiry |
+| mission | Mission | Specific operation of a data collection system |
+| sensor | Sensor | Device or piece of equipment which detects or records |
+| operation | Operation | Action that is part of a series of actions |
+| platform | Platform | Vehicle or other support base that holds a sensor |
+| process | Process | Method of doing something involving a number of steps |
+| program | Program | Specific planned activity |
+| project | Project | Organized undertaking, research, or development |
+| study | Study | Examination or investigation |
+| task | Task | Piece of work |
+| trial | Trial | Process of testing to discover or demonstrate something |
+
+### Standard codelists Cell geometry code (gmd:MD_CellGeometryCode) {#iso19139-cl-gmd-MD_CellGeometryCode}
+
+| code | label | description |
+|-------|-------|------------------------------|
+| point | Point | Each cell represents a point |
+| area | Area | Each cell represents an area |
+
+### Standard codelists Characterset code (gmd:MD_CharacterSetCode) {#iso19139-cl-gmd-MD_CharacterSetCode}
+
+| code | label | description |
+|------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------|
+| ucs2 | UCS2 | 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| ucs4 | UCS4 | 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 |
+| utf7 | UTF7 | 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf8 | UTF8 | 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| utf16 | UTF16 | 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 |
+| 8859part1 | 8859 Part 1 | ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 |
+| 8859part2 | 8859 Part 2 | ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 |
+| 8859part3 | 8859 Part 3 | ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 |
+| 8859part4 | 8859 Part 4 | ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 |
+| 8859part5 | 8859 Part 5 | ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet |
+| 8859part6 | 8859 Part 6 | ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet |
+| 8859part7 | 8859 Part 7 | ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet |
+| 8859part8 | 8859 Part 8 | ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet |
+| 8859part9 | 8859 Part 9 | ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 |
+| 8859part10 | 8859 Part 10 | ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 |
+| 8859part11 | 8859 Part 11 | ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet |
+| 8859part13 | 8859 Part 13 | ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 |
+| 8859part14 | 8859 Part 14 | ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) |
+| 8859part15 | 8859 Part 15 | ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 |
+| 8859part16 | 8859 Part 16 | ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 |
+| jis | JIS | Japanese code set used for electronic transmission |
+| shiftJIS | Shift JIS | Japanese code set used on MS-DOS machines |
+| eucJP | EUC JP | Japanese code set used on UNIX based machines |
+| usAscii | US ASCII | United States ASCII code set (ISO 646 US) |
+| ebcdic | EBCDIC | IBM mainframe code set |
+| eucKR | EUC KR | Korean code set |
+| big5 | Big 5 | Traditional Chinese code set used in Taiwan, Hong Kong of China and other areas |
+| GB2312 | GB2312 | Simplified Chinese code set |
+
+### Standard codelists Classification code (gmd:MD_ClassificationCode) {#iso19139-cl-gmd-MD_ClassificationCode}
+
+| code | label | description |
+|--------------|--------------|--------------------------------------------------------------------------------------------|
+| unclassified | Unclassified | Available for general disclosure |
+| restricted | Restricted | Not for general disclosure |
+| confidential | Confidential | Available for someone who can be entrusted with information |
+| secret | Secret | Kept or meant to be kept private, unknown, or hidden from all but a select group of people |
+| topSecret | Top secret | Of the highest secrecy |
+
+### Standard codelists Content type code (gmd:MD_CoverageContentTypeCode) {#iso19139-cl-gmd-MD_CoverageContentTypeCode}
+
+| code | label | description |
+|------------------------|-------------------------|--------------------------------------------------------------------------------------------------------------------|
+| image | Image | Meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter |
+| thematicClassification | Thematic classification | Code value with no quantitative meaning, used to represent a physical quantity |
+| physicalMeasurement | Physical measurement | Value in physical units of the quantity being measured |
+
+### Standard codelists Data type code (gmd:MD_DatatypeCode) {#iso19139-cl-gmd-MD_DatatypeCode}
+
+| code | label | description |
+|-----------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| class | Class | Descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior |
+| codelist | Codelist | Descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior |
+| enumeration | Enumeration | Data type whose instances form a list of named literal values, not extendable |
+| codelistElement | Codelist element | Permissible value for a codelist or enumeration |
+| abstractClass | Abstract class | Class that cannot be directly instantiated |
+| aggregateClass | Aggregate class | Class that is composed of classes it is connected to by an aggregate relationship |
+| specifiedClass | Specified class | Subclass that may be substituted for its superclass |
+| datatypeClass | Datatype class | Class with few or no operations whose primary purpose is to hold the abstract state of another class for transmittal, storage, encoding or persistent storage |
+| interfaceClass | Interface class | Named set of operations that characterize the behavior of an element |
+| unionClass | Union class | Class describing a selection of one of the specified types |
+| metaClass | Meta class | Class whose instances are classes |
+| typeClass | Type class | Class used for specification of a domain of instances (objects), together with the operations applicable to the objects. A type may have attributes and associations |
+| characterString | Character string | Free text field |
+| integer | Integer | Numerical field |
+| association | Association | Semantic relationship between two classes that involves connections among their instances |
+
+### Standard codelists Dimension type code (gmd:MD_DimensionNameTypeCode) {#iso19139-cl-gmd-MD_DimensionNameTypeCode}
+
+| code | label | description |
+|------------|-------------|------------------------------------------------------------|
+| row | Row | Ordinate (y) axis |
+| column | Column | Abscissa (x) axis |
+| vertical | Vertical | Vertical (z) axis |
+| track | Track | Along the direction of motion of the scan point |
+| crossTrack | Cross track | Perpendicular to the direction of motion of the scan point |
+| line | Line | Scan line of a sensor |
+| sample | Sample | Element along a scan line |
+| time | Time | Duration |
+
+### Standard codelists Geometric Object Type (gmd:MD_GeometricObjectTypeCode) {#iso19139-cl-gmd-MD_GeometricObjectTypeCode}
+
+| code | label | description |
+|-----------|-----------|----------------------------------------------------------------------------------------------------------------|
+| complex | Complex | Set of geometric primitives such that their boundaries can be represented as a union of other primitives |
+| composite | Composite | Connected set of curves, solids or surfaces |
+| curve | Curve | Bounded, 1-dimensional geometric primitive, representing the continuous image of a line |
+| point | Point | Zero-dimensional geometric primitive, representing a position but not having an extent |
+| solid | Solid | Bounded, connected 3-dimensional geometric primitive, representing the continuous image of a region of space |
+| surface | Surface | Bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane |
+
+### Standard codelists Imaging Condition Code (gmd:MD_ImagingConditionCode) {#iso19139-cl-gmd-MD_ImagingConditionCode}
+
+| code | label | description |
+|--------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| blurredImage | Blurred image | Portion of the image is blurred |
+| cloud | Cloud | Portion of the image is partially obscured by cloud cover |
+| degradingObliquity | Degrading obliquity | Acute angle between the plane of the ecliptic (the plane of the Earth s orbit) and the plane of the celestial equator |
+| fog | Fog | Portion of the image is partially obscured by fog |
+| heavySmokeOrDust | Heavy smoke or dust | Portion of the image is partially obscured by heavy smoke or dust |
+| night | Night | Image was taken at night |
+| rain | Rain | Image was taken during rainfall |
+| semiDarkness | Semi darkness | Image was taken during semi-dark conditions -- twilight conditions |
+| shadow | Shadow | Portion of the image is obscured by shadow |
+| snow | Snow | Portion of the image is obscured by snow |
+| terrainMasking | Terrain masking | The absence of collection data of a given point or area caused by the relative location of topographic features which obstruct the collection path between the collector(s) and the subject(s) of interest |
+
+### Standard codelists Keyword Type Code (gmd:MD_KeywordTypeCode) {#iso19139-cl-gmd-MD_KeywordTypeCode}
+
+| code | label | description |
+|------------|------------|--------------------------------------------------------------------|
+| discipline | Discipline | Keyword identifies a branch of instruction or specialized learning |
+| place | Place | Keyword identifies a location |
+| stratum | Stratum | Keyword identifies the layer(s) of any deposited substance |
+| temporal | Temporal | Keyword identifies a time period related to the dataset |
+| theme | Theme | Keyword identifies a particular subject or topic |
+
+### Standard codelists Maintenance Frequency (gmd:MD_MaintenanceFrequencyCode) {#iso19139-cl-gmd-MD_MaintenanceFrequencyCode}
+
+| code | label | description |
+|-------------|-------------|----------------------------------------------------------|
+| continual | Continual | Data is repeatedly and frequently updated |
+| daily | Daily | Data is updated each day |
+| weekly | Weekly | Data is updated on a weekly basis |
+| fortnightly | Fortnightly | Data is updated every two weeks |
+| monthly | Monthly | Data is updated each month |
+| quarterly | Quarterly | Data is updated every three months |
+| biannually | Biannually | Data is updated twice each year |
+| annually | Annually | Data is updated every year |
+| asNeeded | As needed | Data is updated as deemed necessary |
+| irregular | Irregular | Data is updated in intervals that are uneven in duration |
+| notPlanned | Not planned | There are no plans to update the data |
+| unknown | Unknown | Frequency of maintenance for the data is not known |
+
+### Standard codelists Medium format (gmd:MD_MediumFormatCode) {#iso19139-cl-gmd-MD_MediumFormatCode}
+
+| code | label | description |
+|------------------|--------------------|------------------------------------------------------------|
+| cpio | CPIO | CoPy In / Out (UNIX file format and command) |
+| tar | TAR | Tape ARchive |
+| highSierra | High sierra | High sierra file system |
+| iso9660 | ISO9660 | Information processing volume and file structure of CD-ROM |
+| iso9660RockRidge | ISO9660 Rock Ridge | Rock ridge interchange protocol (UNIX) |
+| iso9660AppleHFS | ISO9660 Apple HFS | Hierarchical file system (Macintosh) |
+
+### Standard codelists Medium name code (gmd:MD_MediumNameCode) {#iso19139-cl-gmd-MD_MediumNameCode}
+
+| code | label | description |
+|---------------------------|-------------------------------|----------------------------------------------------|
+| cdRom | CDROM | Read-only optical disk |
+| dvd | DVD | Digital versatile disk |
+| dvdRom | DVDROM | Digital versatile disk, read only |
+| 3halfInchFloppy | 3 Half Inch Floppy | 3,5 inch magnetic disk |
+| 5quarterInchFloppy | 5 Quarter Inch Floppy | 5,25 inch magnetic disk |
+| 7trackTape | 7 Track tape | 7 track magnetic tape |
+| 9trackTape | 9 track tape | 9 track magnetic tape |
+| 3480Cartridge | 3480 Cartridge | 3480 cartridge tape drive |
+| 3490Cartridge | 3490 Cartridge | 3490 cartridge tape drive |
+| 3580Cartridge | 3580 Cartridge | 3580 cartridge tape drive |
+| 4mmCartridgeTape | 4 mm Cartridge tape | 4 millimetre magnetic tape |
+| 8mmCartridgeTape | 8 mm Cartridge tape | 8 millimetre magnetic tape |
+| 1quarterInchCartridgeTape | 1 Quarter inch cartridge tape | 0,25 inch magnetic tape |
+| digitalLinearTap | Digital linear tape | Half inch cartridge streaming tape drive |
+| onLine | Online | Direct computer linkage |
+| satellite | Satellite | Linkage through a satellite communication system |
+| telephoneLink | Telephone link | Communication through a telephone network |
+| hardcopy | Hardcopy | Pamphlet or leaflet giving descriptive information |
+
+### Standard codelists Obligation code (gmd:MD_ObligationCode) {#iso19139-cl-gmd-MD_ObligationCode}
+
+| code | label | description |
+|-------------|-------------|------------------------------------------------------|
+| mandatory | Mandatory | Element is always required |
+| optional | Optional | Element is not required |
+| conditional | Conditional | Element is required when a specific condition is met |
+
+### Standard codelists Pixel orientation code (gmd:MD_PixelOrientationCode) {#iso19139-cl-gmd-MD_PixelOrientationCode}
+
+| code | label | description |
+|------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| center | Center | Point halfway between the lower left and the upper right of the pixel |
+| lowerLeft | Lower left | The corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value |
+| lowerRight | Lower right | Next corner counterclockwise from the lower left |
+| upperRight | Upper right | Next corner counterclockwise from the lower right |
+| upperLeft | Upper left | Next corner counterclockwise from the upper right |
+
+### Standard codelists Progress (gmd:MD_ProgressCode) {#iso19139-cl-gmd-MD_ProgressCode}
+
+| code | label | description |
+|-------------------|--------------------|--------------------------------------------------------------------------------------|
+| completed | Completed | Production of the data has been completed |
+| historicalArchive | Historical archive | Data has been stored in an offline storage facility |
+| obsolete | Obsolete | Data is no longer relevant |
+| onGoing | On going | Data is continually being updated |
+| planned | Planned | Fixed date has been established upon or by which the data will be created or updated |
+| required | Required | Data needs to be generated or updated |
+| underDevelopment | Under development | Data is currently in the process of being created |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|-------------|--------------|-------------|
+| notobsolete | Not obsolete | |
+
+### Standard codelists Access Restriction (gmd:MD_RestrictionCode) {#iso19139-cl-gmd-MD_RestrictionCode}
+
+| code | label | description |
+|----------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| copyright | Copyright | Exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor |
+| patent | Patent | Government has granted exclusive right to make, sell, use or license an invention or discovery |
+| patentPending | Pending patent | Produced or sold information awaiting a patent |
+| trademark | Trademark | A name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer |
+| license | License | Formal permission to do something |
+| intellectualPropertyRights | Intellectual property rights | Rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity |
+| restricted | Restricted | Withheld from general circulation or disclosure |
+| otherRestrictions | Other restrictions | Limitation not listed |
+
+### Standard codelists Scope code (gmd:MD_ScopeCode) {#iso19139-cl-gmd-MD_ScopeCode}
+
+| code | label | description |
+|----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| attribute | Attribute | Information applies to the attribute class |
+| attributeType | Attribute type | Information applies to the characteristic of a feature |
+| collectionHardware | Collection hardware | Information applies to the collection hardware class |
+| collectionSession | Collection session | Information applies to the collection session |
+| dataset | Dataset | Information applies to the dataset |
+| series | Series | Information applies to the series |
+| nonGeographicDataset | Non geographic dataset | Information applies to non-geographic data |
+| dimensionGroup | Dimension group | Information applies to a dimension group |
+| feature | Feature | Information applies to a feature |
+| featureType | Feature type | Information applies to a feature type |
+| propertyType | Property type | Information applies to a property type |
+| fieldSession | Field session | Information applies to a field session |
+| software | Software | Information applies to a computer program or routine |
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+| model | Model | Information applies to a copy or imitation of an existing or hypothetical object |
+| tile | Tile | Information applies to a tile, a spatial subset of geographic data |
+
+Those values are defined in the standard but hidden when editing.
+
+| code | label | description |
+|---------------------------------------------|------------------------------------------------|-------------|
+| map staticMap interactiveMap featureCatalog | Map Static map Interactive map Feature catalog | |
+
+Displayed only if
+
+:
+
+> /ancestor::node()[name()='gmd:MD_Metadata']/gmd:identificationInfo/srv:SV_ServiceIdentification
+
+### Standard codelists Scope code (gmd:MD_ScopeCode)
+
+| code | label | description |
+|---------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+
+### Standard codelists Spatial Representation Type (gmd:MD_SpatialRepresentationTypeCode) {#iso19139-cl-gmd-MD_SpatialRepresentationTypeCode}
+
+| code | label | description |
+|-------------|--------------|----------------------------------------------------------------------------------------------------|
+| vector | Vector | Vector data is used to represent geographic data |
+| grid | Grid | Grid data is used to represent geographic data |
+| textTable | Text, table | Textual or tabular data is used to represent geographic data |
+| tin | TIN | Triangulated irregular network |
+| stereoModel | Stereo model | Three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images |
+| video | Video | Scene from a video recording |
+
+### Standard codelists Topic category code (gmd:MD_TopicCategoryCode) {#iso19139-cl-gmd-MD_TopicCategoryCode}
+
+| code | label | description |
+|----------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| farming | Farming | Rearing of animals and/or cultivation of plants. Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock |
+| biota | Biota | Flora and/or fauna in natural environment. Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat |
+| boundaries | Boundaries | Legal land descriptions. Examples: political and administrative boundaries |
+| climatologyMeteorologyAtmosphere | Climatology, meteorology, atmosphere | Processes and phenomena of the atmosphere. Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation |
+| economy | Economy | Economic activities, conditions and employment. Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas |
+| elevation | Elevation | Height above or below sea level. Examples: altitude, bathymetry, digital elevation models, slope, derived products |
+| environment | Environment | Environmental resources, protection and conservation. Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape |
+| geoscientificInformation | Geoscientific information | Information pertaining to earth sciences. Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion |
+| health | Health | Health, health services, human ecology, and safety. Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services |
+| imageryBaseMapsEarthCover | Imagery base maps earth cover | Base maps. Examples: land cover, topographic maps, imagery, unclassified images, annotations |
+| intelligenceMilitary | Intelligence military | Military bases, structures, activities. Examples: barracks, training grounds, military transportation, information collection |
+| inlandWaters | Inland waters | Inland water features, drainage systems and their characteristics. Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts |
+| location | Location | Positional information and services. Examples: addresses, geodetic networks, control points, postal zones and services, place names |
+| oceans | Oceans | Features and characteristics of salt water bodies (excluding inland waters). Examples: tides, tidal waves, coastal information, reefs |
+| planningCadastre | Planning cadastre | Information used for appropriate actions for future use of the land. Examples: land use maps, zoning maps, cadastral surveys, land ownership |
+| society | Society | Characteristics of society and cultures. Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information |
+| structure | Structure | Man-made construction. Examples: buildings, museums, churches, factories, housing, monuments, shops, towers |
+| transportation | Transportation | Means and aids for conveying persons and/or goods. Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways |
+| utilitiesCommunication | Utilities communication | Energy, water and waste systems and communications infrastructure and services. Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks |
+
+### Standard codelists Topology Level (gmd:MD_TopologyLevelCode) {#iso19139-cl-gmd-MD_TopologyLevelCode}
+
+| code | label | description |
+|------------------|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| geometryOnly | Geometry only | Geometry objects without any additional structure which describes topology |
+| topology1D | Topology 1D | 1-dimensional topological complex -- commonly called chain-node topology |
+| planarGraph | Planar graph | 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.) |
+| fullPlanarGraph | Full planar graph | 2-dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called full topology in a cartographic 2D environment.) |
+| surfaceGraph | Surface graph | 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.) |
+| fullSurfaceGraph | Full surface graph | 2-dimensional topological complex that is isomorphic to a subset of a surface |
+| topology3D | Topology 3D | 3-dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.) |
+| fullTopology3D | Full topology 3D | Complete coverage of a 3D Euclidean coordinate space |
+| abstract | Abstract | Topological complex without any specified geometric realisation |
+
+### Standard codelists (gmd:MX_ScopeCode) {#iso19139-cl-gmd-MX_ScopeCode}
+
+| code | label | description |
+|----------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| attribute | Attribute | Information applies to the attribute class |
+| attributeType | Attribute type | Information applies to the characteristic of a feature |
+| collectionHardware | Collection hardware | Information applies to the collection hardware class |
+| collectionSession | Collection session | Information applies to the collection session |
+| dataset | Dataset | Information applies to the dataset |
+| series | Series | Information applies to the series |
+| nonGeographicDataset | Non geographic dataset | Information applies to non-geographic data |
+| dimensionGroup | Dimension group | Information applies to a dimension group |
+| feature | Feature | Information applies to a feature |
+| featureType | Feature type | Information applies to a feature type |
+| propertyType | Property type | Information applies to a property type |
+| fieldSession | Field session | Information applies to a field session |
+| software | Software | Information applies to a computer program or routine |
+| service | Service | Information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case |
+| model | Model | Information applies to a copy or imitation of an existing or hypothetical object |
+| tile | Tile | Information applies to a tile, a spatial subset of geographic data |
+| initiative | Initiative | The referencing entity applies to a transfer aggregate which was originally identified as an initiative (DS_Initiative) |
+| stereomate | Stereo mate | The referencing entity applies to a transfer aggregate which was originally identified as a stereo mate (DS_StereoMate) |
+| sensor | Sensor | The referencing entity applies to a transfer aggregate which was originally identified as a sensor (DS_Sensor) |
+| platformSeries | Platform series | The referencing entity applies to a transfer aggregate which was originally identified as a platform series (DS_PlatformSeries) |
+| sensorSeries | Sensor series | The referencing entity applies to a transfer aggregate which was originally identified as a sensor series (DS_SensorSeries) |
+| productionSeries | Production series | The referencing entity applies to a transfer aggregate which was originally identified as a production series (DS_ProductionSeries) |
+| transferAggregate | Transfer aggregate | The referencing entity applies to a transfer aggregate which has no existence outside of the transfer context |
+| otherAggregate | Other aggregate | The referencing entity applies to a transfer aggregate which has an existence outside of the transfer context, but which does not pertains to a specific aggregate type. |
+
+### Standard codelists Distributed Computing Platforms list (srv:DCPList) {#iso19139-cl-srv-DCPList}
+
+| description | code | label |
+|--------------------|-------------|--------------|
+| DCP is XML | XML | XML |
+| DCP is CORBA | CORBA | CORBA |
+| DCP is JAVA | JAVA | JAVA |
+| DCP is COM | COM | COM |
+| DCP is SQL | SQL | SQL |
+| DCP is WebServices | WebServices | Web services |
+
+### Standard codelists Coupling Type (srv:SV_CouplingType) {#iso19139-cl-srv-SV_CouplingType}
+
+| code | label | description |
+|-------|-------|-------------------------------------------------------------------------------|
+| tight | Tight | Tightly coupled: data associated |
+| mixed | Mixed | Mixed coupled: data associated; in addition, external data might be processed |
+| loose | Loose | Loosely coupled: no data associated |
+
+### Standard codelists Parameter direction (srv:SV_ParameterDirection) {#iso19139-cl-srv-SV_ParameterDirection}
+
+| code | label |
+|--------|--------------|
+| in | Input |
+| out | Output |
+| in/out | Input/output |
+
+### Standard codelists (SDS_category) {#iso19139-cl-SDS_category}
+
+| code | label | description |
+|------------------------------------------------------------------------|---------------|---------------|
+| | harmonised | Harmonised |
+| | interoperable | Interoperable |
+| | invocable | Invocable |
+
+### Standard codelists (SDS_DCP) {#iso19139-cl-SDS_DCP}
+
+| code | label | description |
+|-------------|--------------|--------------|
+| xml | XML | XML |
+| corba | CORBA | CORBA |
+| java | JAVA | JAVA |
+| com | COM | COM |
+| sql | SQL | SQL |
+| webServices | Web Services | Web Services |
+
+### Standard codelists Nil reason (gco:nilReason) {#iso19139-cl-gco-nilReason}
+
+| code | label |
+|--------------|--------------|
+| missing | Missing |
+| inapplicable | Inapplicable |
+| template | Template |
+| unknown | Unknown |
+| withheld | Withheld |
+
+### Standard codelists Indeterminate position (indeterminatePosition) {#iso19139-cl-indeterminatePosition}
+
+| code | label |
+|---------|---------|
+| after | After |
+| before | Before |
+| now | Now |
+| unknown | Unknown |
diff --git a/docs/manual/docs/api/csw.md b/docs/manual/docs/api/csw.md
new file mode 100644
index 00000000000..87c95198a2a
--- /dev/null
+++ b/docs/manual/docs/api/csw.md
@@ -0,0 +1,71 @@
+# Catalog Service for the Web (CSW) {#csw-api}
+
+The CSW end point exposes the metadata records in your catalog in XML format using the OGC CSW protocol (version 2.0.2).
+
+Two protocols are available:
+
+- CSW: Provides the ability to search and publish metadata for data, services and related information.
+- CSW-T: Provides an interface for creating, modifying and deleting catalog records via the CSW protocol.
+
+## Configuration
+
+See [Configuring CSW](../administrator-guide/configuring-the-catalog/csw-configuration.md) for details of how to configure the CSW end point.
+
+## URL
+
+The following URL is the standard end point for the catalog (substitute your GeoNetwork URL):
+
+- ?
+
+Generally, the `VERSION` and `SERVICE` parameter are also added, along with the `REQUEST` parameter as detailed below:
+
+-
+
+## Requests
+
+The full set of requests supported by GeoNetwork can be found in `CSW test`, in the `Settings` section of the Admin Dashboard.
+
+See [Configuring CSW](../administrator-guide/configuring-the-catalog/csw-configuration.md) for more details of this function.
+
+When using the GetRecords operation for searching, 2 types of parameter can be use for searching:
+
+- The list of queryable listed in the GetCapabilities document
+- The fields in the index
+
+Example of a request using a standard queryable:
+
+``` xml
+
+
+
+
+
+ OnlineResourceType
+ OGC:WFS-1.1.0-http-get-feature
+
+
+
+
+
+```
+
+Example of a request using an index field name:
+
+``` xml
+
+
+
+
+
+ linkProtocol
+ OGC:WMS
+
+
+
+
+
+```
+
+The mapping between CSW standard queryable and the index fields are defined in **`web/src/main/webapp/WEB-INF/config-csw.xml`**.
diff --git a/docs/manual/docs/api/img/googlesheets-fn.png b/docs/manual/docs/api/img/googlesheets-fn.png
new file mode 100644
index 00000000000..b73d2347c47
Binary files /dev/null and b/docs/manual/docs/api/img/googlesheets-fn.png differ
diff --git a/docs/manual/docs/api/img/googlesheets-script.png b/docs/manual/docs/api/img/googlesheets-script.png
new file mode 100644
index 00000000000..6d7fe0ea990
Binary files /dev/null and b/docs/manual/docs/api/img/googlesheets-script.png differ
diff --git a/docs/manual/docs/api/img/opensearch-in-browser.png b/docs/manual/docs/api/img/opensearch-in-browser.png
new file mode 100644
index 00000000000..e9669c94c83
Binary files /dev/null and b/docs/manual/docs/api/img/opensearch-in-browser.png differ
diff --git a/docs/manual/docs/api/img/opensearch.png b/docs/manual/docs/api/img/opensearch.png
new file mode 100644
index 00000000000..1a7811af272
Binary files /dev/null and b/docs/manual/docs/api/img/opensearch.png differ
diff --git a/docs/manual/docs/api/index.md b/docs/manual/docs/api/index.md
new file mode 100644
index 00000000000..3f1424bac15
--- /dev/null
+++ b/docs/manual/docs/api/index.md
@@ -0,0 +1,25 @@
+# API Guide
+
+The API guide describes entry points that can be used to interact with the catalog.
+
+- [GeoNetwork API](the-geonetwork-api.md)
+
+ The GeoNetwork API allows to manage all the catalog (eg. users, groups, editing, formatter, processing).
+
+- [Search Service](search.md)
+
+ The main GeoNetwork search service for fast and flexible record retrieval.
+
+- [Catalog Service for the Web](csw.md)
+
+ The OGC Industry standard to search, retrieve record in XML format. Can be used to manage records with transaction operation.
+
+GeoNetwork 3.12.x only:
+
+- [OpenSearch and INSPIRE ATOM](opensearch.md)
+- [RDF DCAT](rdf-dcat.md)
+- [Open Archive Initiative](oai-pmh.md)
+
+No longer supported:
+
+- [Z39-50](z39-50.md)
diff --git a/docs/manual/docs/api/oai-pmh.md b/docs/manual/docs/api/oai-pmh.md
new file mode 100644
index 00000000000..b18419bb7c0
--- /dev/null
+++ b/docs/manual/docs/api/oai-pmh.md
@@ -0,0 +1,25 @@
+# Open Archive Initiative (OAI) {#oai-pmh}
+
+!!! warning
+
+ Not yet available in version 4.
+
+
+The OAI-PMH end point exposes the metadata records in your catalog in XML format using the version 2.0 of the OAI-PMH protocol.
+
+## Configuration
+
+The following URL is the standard end point for the catalog (substitute your GeoNetwork URL): ?
+
+## Requests
+
+Standard OAI-PMH requests can be done using the url above and the 6 verbs provided by the standard:
+
+- GetRecord
+- Identify
+- ListIdentifiers
+- ListMetadataFormats
+- ListRecords
+- ListSets
+
+Please see for further details.
diff --git a/docs/manual/docs/api/opensearch.md b/docs/manual/docs/api/opensearch.md
new file mode 100644
index 00000000000..1f2ba6a599f
--- /dev/null
+++ b/docs/manual/docs/api/opensearch.md
@@ -0,0 +1,44 @@
+# OpenSearch and INSPIRE ATOM {#opensearch-and-atom}
+
+!!! warning
+
+ Not yet available in version 4.
+
+
+## OpenSearch
+
+The catalog provides an opensearch entry point at . This service is advertised in the HTML.
+
+
+
+Browsers detect the availability of opensearch by checking the index page at the root of the (sub)domain. If you install geonetwork in a subfolder, consider to set up a rewrite rule forwarding the index request to the subfolder.
+
+An example of such a rewrite rule in Apache:
+
+``` text
+RewriteEngine on
+RewriteRule "^/$" "/geonetwork/" [R]
+```
+
+Verify in a browser if opensearch is detected by typing the url and then a space. The url bar should then give an indication that you're searching within the site.
+
+{width="300px"}
+
+## INSPIRE ATOM
+
+The INSPIRE technical guideline for download services facilitates an option to set up a download service based on OpenSearch and Atom. A separate OpenSearch endpoint is created for every Atom-based download service.
+
+!!! note
+
+ Only records based on the ISO19139 standard can be used with Atom. ISO19115-3 records are not.
+
+
+A remote ATOM feed can be registered in a metadata record (see [Linking data using ATOM feeds](../user-guide/associating-resources/linking-online-resources.md#linking-data-using-atom-feed)), but the catalog can also create ATOM feeds from records describing datasets and services.
+
+For a service metadata record, the corresponding ATOM feed is accessed at: `http://localhost:8080/geonetwork/srv/atom/describe/service?uuid=8b719ebd-646e-4963-b9e0-16b3c2a6d94e`. If the service is attached to one or more datasets (see [Linking a dataset with a service](../user-guide/associating-resources/linking-dataset-or-service.md)), then the feed will also expose each dataset as an `entry` in the feed. Check that the service type is set to `download` (if not, the dataset feed will return an exception).
+
+The dataset feed is accessible at: `http://localhost:8080/geonetwork/srv/atom/describe/dataset?spatial_dataset_identifier_code=b795de68-726c-4bdf-a62a-a42686aa5b6f`. Links will be created for each online resource flagged with a `function` set to `download`.
+
+Examples:
+
+-
diff --git a/docs/manual/docs/api/rdf-dcat.md b/docs/manual/docs/api/rdf-dcat.md
new file mode 100644
index 00000000000..eb5e8ded40e
--- /dev/null
+++ b/docs/manual/docs/api/rdf-dcat.md
@@ -0,0 +1,19 @@
+# RDF DCAT end point {#rdf-dcat}
+
+!!! warning
+
+ Not yet available in version 4.
+
+
+The RDF DCAT end point provides a way of getting information about the catalog, the datasets and services, and links to distributed resources in a machine-readable format. The formats of the output are based on DCAT, an RDF vocabulary that is designed to facilitate interoperability between web-based data catalogs.
+
+## URLS
+
+The following URLs are available (substitute your GeoNetwork URL):
+
+- : returns an RDF record for the given UUID
+- ?: returns a dcat:Catalog record. By default this will describe all the records in the catalog, but query filters are available (see below)
+
+## Query parameters
+
+- `_cat`: Metadata Category
diff --git a/docs/manual/docs/api/search.md b/docs/manual/docs/api/search.md
new file mode 100644
index 00000000000..705cd2bf112
--- /dev/null
+++ b/docs/manual/docs/api/search.md
@@ -0,0 +1,109 @@
+# Search Service {#q-search}
+
+## OpenAPI Search
+
+!!! note
+
+ GeoNetwork 4
+
+
+The Q Search endpoint is replaced by the ``/srv/api/search/records/_search`` endpoint.
+
+Parameter Reference:
+
+- [Search API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-search.html) (Elasticsearch)
+
+## Q Search
+
+!!! note
+
+ GeoNetwork 3
+
+
+The Q Search endpoint allows you to query the catalog programmatically. It is available in the local catalog at `http://localhost:8080/geonetwork/srv/eng/q` (otherwise substitute your catalog URL).
+
+### Query results parameters
+
+The following parameters can be appended to your request to format the results:
+
+- `_content_type=json`: returns results in json format. If this parameter is not provided, then the results are returned in xml format.
+- `sortBy`: sorts the results by different criteria (example: `sortBy=relevance`):
+ - `relevance` (default sorting method if not provided)
+ - `title` (metadata title)
+ - `changeDate` (metadata datestamp)
+ - `rating`
+ - `popularity`
+ - `denominatorDesc`
+ - `denominatorAsc`
+- `sortOrder=reverse`: Used to sort alphabetically. Note this will sort in **ASCENDING** order (eg A - Z)
+- `from`, `to`: Used to return a subset of the results, usually for pagination (example: `from=1&to=20`)
+- `fast`: Used to indicate the information to return. Possible values:
+ - `index`: returns the metadata information from the Lucene index (a subset of the information). In most cases this is the best option as the retrieval of information from the Lucene index is very fast.
+
+ The fields returned are configured in the `dumpFields` section in
+
+ - `false`: returns the raw (full) metadata. This is slower as it will retrieve every metadata attribute from the database. If this parameter is not provided, it returns a minimal set of information for each record: uuid, internal id, metadata schema, create/change dates
+- `buildSummary`: Returns a summary element with search facets that can be used to filter the metadata, typically used to provide quick filters (facets) on the search results page. Values:
+ - `true` (default, if the parameter is not provided).
+ - `false`: does not return the summary.
+- `summaryOnly`: Returns the summary (depending on the value of the parameter `buildSummary`) and results. Values:
+ - `0` (default, if the parameter is not provided).
+ - Any other value returns the summary only.
+- `resultType`: type of summary to return. Summaries are configured in the `summaryTypes` section in
+ - `hits` (default value if not provided), returns the fields configured in the `hits` section in
+ - `details` (recommended value to send), returns the fields configured in the `details` section in
+- `extraDumpFields`: a comma-separated list of additional fields that you wish to return alongside the fields returned according to the resultType you have chosen. The wildcard character `*` can be used to match multiple fields. For example `extraDumpFields=mycustomfield*` would match mycustomfield1 and mycustomfield2.
+- Other values in the summaries section are allowed
+
+### Query filter parameters
+
+You can search on any field(s) indexed in Lucene. For a complete reference see
+
+Note you can query the Lucene index graphically,using a Java-based graphical tool such as [Luke](https://github.com/DmitryKey/luke). Version [4.10.4](https://github.com/DmitryKey/luke/releases/tag/luke-4.10.4.1/) is required to work with the version of Lucene bundled with GeoNetwork. Download the jar file where you can access the GeoNetwork index files, then execute with:
+
+`java -jar luke-with-deps.jar`
+
+Then follow the instructions in the tool.
+
+Most relevant fields:
+
+- `any`: A special Lucene field that indexes all the text content in the metadata. Example:
+
+There are some additional query fields, that use the content from the Lucene field `any`.
+
+- `or`: extract the tokens of the query parameter to return the results that contain at least 1 of the tokens
+- `without`: extract the tokens of the query parameter to return the results that don't contain any of the tokens.
+- `phrase`: return the results that contain the exact text as provided in the search query parameter.
+- `title`: metadata title.
+- `abstract`: metadata abstract.
+- `topicCat`: metadata topic categories.
+- `keyword`: metadata keywords.
+- `type`: hierarchyLevel (dataset, service, etc.)
+
+If several tokens are included in the query, an AND query with all the tokens is executed. For example, `title=roads&topicCat=biota`. This query will return the results that contain roads in the title AND have the topic category biota.
+
+An OR query of several fields can be executed using the format: `field1_OR_field2_OR_... =value`. For example, `title_OR_abstract=roads` returns the metadata that contain roads in the title OR the abstract.
+
+Additionally an OR query of several values for a single field can be executed, if the Lucene configuration for that field allows it, with the following format: `field=value1 or value2 or ...` For example `topicCat=biota or farming`, returns the metadata where the topic category is either biota OR farming. If the query was executed as `topicCat=biota&topicCat=farming` then only the metadata with BOTH topic categories would be returned.
+
+### Date Searches
+
+There are a number of ways that you can search by date. Date searches should be of the form YYYY-MM-DD
+
+- dateFrom/dateTo: uses the changeDate parameter in the index.
+- creationDateFrom/To: uses the creation date.
+- revisionDateFrom/To: uses the revision date.
+
+### Query examples
+
+Query with any field for metadata containing the string 'infrastructure', returning json, using the fast index to return results, and returning the fields configured in `config-summary.xml`:
+
+
+
+Query datasets with title containing the string 'infrastructure', returning json, using the fast index to return results, returning the fields configured in `config-summary.xml` and returning only the first 20 results (ordered by relevance):
+
+
+
+Query datasets with a revision date in June 2019 using the fast index to return results, returning the fields configured in `config-summary.xml` and returning only the first 20 results (ordered by relevance):
+
+
diff --git a/docs/manual/docs/api/the-geonetwork-api.md b/docs/manual/docs/api/the-geonetwork-api.md
new file mode 100644
index 00000000000..1c0540fac79
--- /dev/null
+++ b/docs/manual/docs/api/the-geonetwork-api.md
@@ -0,0 +1,397 @@
+# GeoNetwork API
+
+The REST API and documentation are available in your catalog at page and linked from the footer on the home page.
+
+In version 4, the API description is using OpenAPI specification. Old path to the API including the version ``/srv/api/0.1/\...`` is replaced by ``/srv/api/\...``. The version of the API correspond to the version of the GeoNetwork instance.
+
+## Using the API to apply an XSL process
+
+This is an example to trigger an XSL process on a set of records. It illustrates how to make a set of actions using the API:
+
+``` shell
+CATALOG=http://localhost:8080/geonetwork
+CATALOGUSER=admin
+CATALOGPASS=admin
+PROCESS=migrate-201904
+
+rm -f /tmp/cookie;
+curl -s -c /tmp/cookie -o /dev/null \
+ -X GET \
+ -H "Accept: application/json" \
+ "$CATALOG/srv/api/me";
+TOKEN=`grep XSRF-TOKEN /tmp/cookie | cut -f 7`;
+curl \
+ -X GET \
+ -H "Accept: application/json" \
+ -H "X-XSRF-TOKEN: $TOKEN" --user $CATALOGUSER:$CATALOGPASS -b /tmp/cookie \
+ "$CATALOG/srv/api/me"
+
+# MUST return user details
+
+curl -X POST "$CATALOG/srv/api/search/records/_search?bucket=111" \
+ -H 'Accept: application/json' \
+ -H 'Content-Type: application/json;charset=utf-8' \
+ -H "X-XSRF-TOKEN: $TOKEN" -c /tmp/cookie -b /tmp/cookie --user $CATALOGUSER:$CATALOGPASS \
+ -d '{"from":0,"size":0,"query":{"query_string":{"query":"+linkUrl:*data-and-maps*"}}}'
+
+
+curl -X PUT "$CATALOG/srv/api/selections/111" -H "accept: application/json" \
+ -H "X-XSRF-TOKEN: $TOKEN" -c /tmp/cookie -b /tmp/cookie --user $CATALOGUSER:$CATALOGPASS
+#Body response = number of selected records
+
+curl -X GET "$CATALOG/srv/api/selections/111" -H "accept: application/json" \
+ -H "X-XSRF-TOKEN: $TOKEN" -c /tmp/cookie -b /tmp/cookie --user $CATALOGUSER:$CATALOGPASS
+#Body returns an array of selected records
+
+curl -X POST "$CATALOG/srv/api/processes/$PROCESS?bucket=111&index=false" \
+ -H "accept: application/json" -H "X-XSRF-TOKEN: $TOKEN" -c /tmp/cookie -b /tmp/cookie --user $CATALOGUSER:$CATALOGPASS
+```
+
+## Loop on search results and apply changes (processing and batch editing)
+
+This is an example to highlight how to loop over specific search results (here only series) and apply various changes:
+
+``` shell
+SERVER=http://localhost:8080/geonetwork
+CATALOGUSER=admin
+CATALOGPASS=admin
+
+type=series
+from=0
+size=1000
+
+rm results.json
+rm -f /tmp/cookie;
+
+curl -s -c /tmp/cookie -o /dev/null \
+ -X GET \
+ --user $CATALOGUSER:$CATALOGPASS \
+ -H "Accept: application/json" \
+ "$SERVER/srv/api/me";
+
+TOKEN=`grep XSRF-TOKEN /tmp/cookie | cut -f 7`;
+JSESSIONID=`grep JSESSIONID /tmp/cookie | cut -f 7`;
+
+curl "$SERVER/srv/api/search/records/_search" \
+ -X 'POST' \
+ -H 'Accept: application/json, text/plain, */*' \
+ -H 'Content-Type: application/json;charset=UTF-8' \
+ --data-raw "{\"query\":{\"query_string\":{\"query\": \"+isHarvested:false +resourceType: $type\"}},\"from\":$from, \"size\":$size, \"_source\": {\"include\": [\"resourceTitleObject.default\"]}, \"sort\": [{\"resourceTitleObject.default.keyword\": \"asc\"}]}" \
+ -H "X-XSRF-TOKEN: $TOKEN" -H "Cookie: XSRF-TOKEN=$TOKEN; JSESSIONID=$JSESSIONID" \
+ --compressed \
+ -o results.json
+
+for hit in $(jq -r '.hits.hits[] | @base64' results.json); do
+ _jq() {
+ echo "${hit}" | base64 --decode | jq -r "${1}"
+ }
+
+ title=$(_jq '._source.resourceTitleObject.default')
+ uuid=$(_jq '._id')
+ echo "__________"
+ echo "### $uuid"
+
+ # Update series from its members using XSL process
+ curl $AUTH "$SERVER/srv/api/records/$uuid/processes/collection-updater" \
+ -X 'POST' \
+ -H 'Accept: application/json, text/plain, */*' \
+ -H "X-XSRF-TOKEN: $TOKEN" \
+ -H "Cookie: XSRF-TOKEN=$TOKEN; JSESSIONID=$JSESSIONID" \
+ --compressed
+
+ curl $AUTH "$SERVER/srv/api/selections/s101" \
+ -X 'DELETE' \
+ -H 'Accept: application/json, text/javascript, */*; q=0.01' \
+ -H "X-XSRF-TOKEN: $TOKEN" \
+ -H "Cookie: XSRF-TOKEN=$TOKEN; JSESSIONID=$JSESSIONID" \
+ --compressed
+
+ curl $AUTH "$SERVER/srv/api/selections/s101?uuid=$uuid" \
+ -X 'PUT' \
+ -H 'Accept: application/json, text/javascript, */*; q=0.01' \
+ -H "X-XSRF-TOKEN: $TOKEN" \
+ -H "Cookie: XSRF-TOKEN=$TOKEN; JSESSIONID=$JSESSIONID" \
+ --compressed
+
+ # Keep only the first 2 resource identifiers using batch editing
+ curl $AUTH "$SERVER/srv/api/records/batchediting?bucket=s101" \
+ -X 'PUT' \
+ -H 'Accept: application/json, text/plain, */*' \
+ -H 'Content-Type: application/json;charset=UTF-8' \
+ -H "X-XSRF-TOKEN: $TOKEN" \
+ -H "Cookie: XSRF-TOKEN=$TOKEN; JSESSIONID=$JSESSIONID" \
+ --data-raw "[{\"xpath\":\"/gmd:identificationInfo/*/gmd:citation/*/gmd:identifier[position() > 2]\",\"value\":\"\"}]" \
+ --compressed
+done;
+```
+
+## Using the search API in Google sheet
+
+In Extensions --> App script create a new function. Here we create a function which run a search and return a list of matching UUIDs:
+
+
+
+``` js
+function getUuidForSearch(query) {
+ var options = {
+ 'method' : 'post',
+ 'contentType': 'application/json',
+ 'payload' : "{\"query\":{\"query_string\":{\"query\":\"" + query + "\"}}}"
+ };
+ var response = UrlFetchApp.fetch('http://localhost:8080/catalogue/srv/api/search/records/_search', options);
+ var hits = JSON.parse(response).hits;
+ Logger.log(hits.hits);
+ return hits.hits.length > 0 ? hits.hits.map(function(v) {return v._id}).join('###') : null;
+}
+```
+
+Then use the function in formula. Here we search for records matching particular keywords:
+
+
+
+## Building client for the API using codegen
+
+The API is described using the open API specification. [Codegen](https://swagger.io/swagger-codegen/) is a tool to build an API client based on the specification. To build a Java client use the following procedure.
+
+First, create a configuration file apiconfig.json for the API:
+
+``` json
+{
+ "groupId":"org.geonetwork-opensource",
+ "artifactId":"OpenApiClient",
+ "artifactVersion":"0.0.1",
+ "library":"okhttp-gson",
+ "apiPackage":"org.fao.geonet.openapi",
+ "modelPackage":"org.fao.geonet.openapi.model"
+}
+```
+
+``` shell
+java -jar swagger-codegen-cli.jar generate \
+ -i http://localhost:8080/geonetwork/srv/v2/api-docs \
+ -l java \
+ -c apiconfig.json \
+ -o /tmp/gn-openapi-java-client
+
+cd /tmp/gn-openapi-java-client
+
+mvn clean install
+```
+
+Once compiled, the Java client can be used as a dependency; eg. for Maven:
+
+``` xml
+
+ org.geonetwork-opensource
+ OpenApiClient
+ 0.0.1
+
+```
+
+Then the client API can be used in your Java application:
+
+``` java
+import com.squareup.okhttp.Interceptor;
+import com.squareup.okhttp.Request;
+import com.squareup.okhttp.Response;
+import org.fao.geonet.ApiClient;
+import org.fao.geonet.ApiException;
+import org.fao.geonet.Configuration;
+import org.fao.geonet.openapi.MeApi;
+import org.fao.geonet.openapi.RecordsApi;
+import org.fao.geonet.openapi.model.MeResponse;
+import org.fao.geonet.openapi.model.SimpleMetadataProcessingReport;
+import org.junit.jupiter.api.BeforeAll;
+import org.junit.jupiter.api.Test;
+import org.junit.jupiter.api.TestInstance;
+
+import java.io.IOException;
+import java.util.Arrays;
+import java.util.Base64;
+
+import static org.junit.jupiter.api.Assertions.assertEquals;
+import static org.junit.jupiter.api.Assertions.assertNotNull;
+
+@TestInstance(TestInstance.Lifecycle.PER_CLASS)
+public class GnJavaApiClientTest {
+
+ private static final String CATALOGUE_URL = "http://localhost:8080/geonetwork";
+
+ ApiClient client;
+
+ private static final String USERNAME = "admin";
+ private static final String PASSWORD = "admin";
+
+
+ @BeforeAll
+ private void initConfiguration() {
+ client
+ = Configuration.getDefaultApiClient();
+ client.setBasePath(CATALOGUE_URL);
+ }
+
+ /**
+ * Get user information when anonymous or connected.
+ */
+ @Test
+ public void getMeInfoTest() {
+ try {
+ client.getHttpClient().networkInterceptors().clear();
+
+ MeApi meApi = new MeApi();
+ MeResponse meResponse = meApi.getMe();
+ // User is not authenticated
+ assertEquals(null, meResponse);
+
+ // Configure HTTP basic authorization: basicAuth
+ client.getHttpClient().networkInterceptors().add(new BasicAuthInterceptor(USERNAME, PASSWORD));
+
+ meResponse = meApi.getMe();
+ // User is authenticated
+ assertEquals(USERNAME, meResponse.getName());
+
+ } catch (ApiException e) {
+ e.printStackTrace();
+ }
+ }
+
+
+ /**
+ * Insert and delete a record.
+ */
+ @Test
+ public void insertAndDeleteRecord() {
+
+ // Configure HTTP basic authorization: basicAuth
+ client.getHttpClient().networkInterceptors().add(new BasicAuthInterceptor(USERNAME, PASSWORD));
+
+
+ try {
+ final RecordsApi api = new RecordsApi();
+
+ SimpleMetadataProcessingReport report = api.insert("METADATA",
+ null,
+ Arrays.asList(new String[]{"http://sextant.ifremer.fr/geonetwork/srv/fre/xml.metadata.get?uuid=ec41b8b2-c184-46e7-86c6-a24f0ac295ad"}),
+ null, null,
+ true, "NOTHING",
+ null,
+ null,
+ false,
+ null,
+ null,
+ null);
+
+ int nbOfRecordInserted = report.getMetadataInfos().size();
+
+
+ // One record MUST be inserted
+ assertEquals(1, nbOfRecordInserted);
+
+ if (nbOfRecordInserted == 1) {
+ Object[] list = report.getMetadataInfos().keySet().toArray();
+ String metadataId = (String) list[0];
+ String record = api.getRecord(metadataId, "application/xml");
+ assertNotNull(record);
+
+ api.deleteRecord(metadataId, false);
+
+ try {
+ api.getRecord(metadataId, "application/xml");
+ } catch (ApiException e) {
+ assertEquals(404, e.getCode());
+ }
+ }
+ } catch (ApiException e) {
+ e.printStackTrace();
+ }
+ }
+
+
+ /**
+ * Interceptor to add basic authentication header on each request.
+ *
+
+```
+
+
+
+The text needs to be contained in one root HTML element. It can also contains more complex layout and be displayed on condition (eg. only display it if the is a resource identifier):
+
+``` xml
+
+
+
+
+
+ The dataset identifier shall be unique and ideally meaningful, following
+ this convention.
+
+
+
+
+
+```
+
+
+
+## Step 6: Translation
+
+If working with a multilingual interface, configure the form using references to translation file content.
+
+``` xml
+
+```
+
+Translation are stored in the `loc/language_code/strings.xml` file (see `schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/loc/eng/strings.xml`).
+
+``` xml
+
+
+
+
+
+
+ The dataset identifier shall be unique and ideally meaningful, following
+ this convention.
+
+
+
+
+
+```
+
+Same kind of references can be used for field, section and action labels:
+
+``` xml
+
+```
+
+``` xml
+
+
+ Identifiant de la ressource
+
+```
+
+## Step 7: File upload
+
+To upload data, additional documents to the record, a component (also named `directive` from an AngularJS perspective) can be used:
+
+``` xml
+
+
+
+
+
+
+
+```
+
+It allows to easily add files which will be referenced in the distribution section of the record:
+
+
+
+Instead of keeping the upload form in the main part of the editor, the section can be moved to a side panel (ie. outside the `tab`):
+
+``` xml
+
+
+
+
+
+```
+
+
+
+## Step 8: Set overview
+
+``` xml
+
+
+
+
+
+
+```
+
+
+
+## Step 9: Classification
+
+To add keywords, add a field first but also explain how to encode keywords using a thesaurus configuration:
+
+``` xml
+
+
+
+
+
+
+
+
+
+```
+
+If the thesaurus is loaded in the admin console, the keyword picker looks like:
+
+
+
+## Step 10: Understanding the "flat" mode
+
+ISO Standards are known to be able to describe the details and provides many elements and descriptors but as we've seen before for the resource identifier, we sometimes want to focus on a specific descriptor.
+
+For example, adding a new section with the spatial resolution:
+
+``` xml
+
+
+
+```
+
+The spatial resolution as defined in ISO can be various things: a scale, a resolution, a LOD, an angular or vertical sampling measure. Each types have specific encoding and the default form mechanism is using the standard definition (ie. the XML schema or XSD) and as such can create complex form:
+
+
+
+To improve that situation, a `flat` mode can be used at the tab level:
+
+``` xml
+
+
+```
+
+When using the `flat`, the same field is displayed as:
+
+
+
+In this mode, the form is not created using the XSD, but using the XML document only. Note the changes:
+
+- less nested levels
+- no `+` action
+- no menu to choose the type of resolution
+
+To overcome this:
+
+- Adjust the XPath to point to the final element to edit (to avoid all nested levels). Use the `del` attribute to properly remove the parent element.
+- Use `flatModeExceptions` to allow adding optional element in a `flat` tab
+- Use `action` in order to add the various type of elements.
+
+Also note here the double `/` which is a particularity for elements having substitute like the spatial resolution. The metadocument (containing the XSD + the XML of the metadata) contains extra element `geonet:choose` when an element has subsitutions.
+
+``` xml
+
+
+
+
+
+
+
+```
+
+
diff --git a/docs/manual/docs/customizing-application/img/Editor-Constraints-Choices-Modified.png b/docs/manual/docs/customizing-application/img/Editor-Constraints-Choices-Modified.png
new file mode 100644
index 00000000000..d89db54cb48
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/Editor-Constraints-Choices-Modified.png differ
diff --git a/docs/manual/docs/customizing-application/img/Editor-Constraints-Choices.png b/docs/manual/docs/customizing-application/img/Editor-Constraints-Choices.png
new file mode 100644
index 00000000000..2ddc81e71dc
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/Editor-Constraints-Choices.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-home.png b/docs/manual/docs/customizing-application/img/agg-decorator-home.png
new file mode 100644
index 00000000000..b3012ba6d9a
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-home.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-icon-fixed.png b/docs/manual/docs/customizing-application/img/agg-decorator-icon-fixed.png
new file mode 100644
index 00000000000..8962e2579d7
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-icon-fixed.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-icon-inspire.png b/docs/manual/docs/customizing-application/img/agg-decorator-icon-inspire.png
new file mode 100644
index 00000000000..cc32e91c634
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-icon-inspire.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-icon-map.png b/docs/manual/docs/customizing-application/img/agg-decorator-icon-map.png
new file mode 100644
index 00000000000..b20f25d9d55
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-icon-map.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-icon.png b/docs/manual/docs/customizing-application/img/agg-decorator-icon.png
new file mode 100644
index 00000000000..0041895f560
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-icon.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-img-logo.png b/docs/manual/docs/customizing-application/img/agg-decorator-img-logo.png
new file mode 100644
index 00000000000..b0035b09687
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-img-logo.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-decorator-img.png b/docs/manual/docs/customizing-application/img/agg-decorator-img.png
new file mode 100644
index 00000000000..21d48dbc94c
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-decorator-img.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-home.png b/docs/manual/docs/customizing-application/img/agg-home.png
new file mode 100644
index 00000000000..f141e9ba343
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-home.png differ
diff --git a/docs/manual/docs/customizing-application/img/agg-search.png b/docs/manual/docs/customizing-application/img/agg-search.png
new file mode 100644
index 00000000000..d532d3e1d17
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/agg-search.png differ
diff --git a/docs/manual/docs/customizing-application/img/csrf1.png b/docs/manual/docs/customizing-application/img/csrf1.png
new file mode 100644
index 00000000000..658112abf82
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/csrf1.png differ
diff --git a/docs/manual/docs/customizing-application/img/csrf2.png b/docs/manual/docs/customizing-application/img/csrf2.png
new file mode 100644
index 00000000000..c543651be42
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/csrf2.png differ
diff --git a/docs/manual/docs/customizing-application/img/editor-helper.png b/docs/manual/docs/customizing-application/img/editor-helper.png
new file mode 100644
index 00000000000..a85fd16830f
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/editor-helper.png differ
diff --git a/docs/manual/docs/customizing-application/img/es-get-doc.png b/docs/manual/docs/customizing-application/img/es-get-doc.png
new file mode 100644
index 00000000000..3b4a83c4ccc
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/es-get-doc.png differ
diff --git a/docs/manual/docs/customizing-application/img/facet.png b/docs/manual/docs/customizing-application/img/facet.png
new file mode 100644
index 00000000000..013c6f6b3bc
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/facet.png differ
diff --git a/docs/manual/docs/customizing-application/img/formatter.png b/docs/manual/docs/customizing-application/img/formatter.png
new file mode 100644
index 00000000000..c64d5a43a30
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/formatter.png differ
diff --git a/docs/manual/docs/customizing-application/img/kb-index-fields.png b/docs/manual/docs/customizing-application/img/kb-index-fields.png
new file mode 100644
index 00000000000..171214ff4c8
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/kb-index-fields.png differ
diff --git a/docs/manual/docs/customizing-application/img/kb-index-pattern.png b/docs/manual/docs/customizing-application/img/kb-index-pattern.png
new file mode 100644
index 00000000000..1c0f3c4496c
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/kb-index-pattern.png differ
diff --git a/docs/manual/docs/customizing-application/img/pages-api.png b/docs/manual/docs/customizing-application/img/pages-api.png
new file mode 100644
index 00000000000..8fa3ce99707
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/pages-api.png differ
diff --git a/docs/manual/docs/customizing-application/img/vega.png b/docs/manual/docs/customizing-application/img/vega.png
new file mode 100644
index 00000000000..54ceeda71eb
Binary files /dev/null and b/docs/manual/docs/customizing-application/img/vega.png differ
diff --git a/docs/manual/docs/customizing-application/implementing-a-schema-plugin.md b/docs/manual/docs/customizing-application/implementing-a-schema-plugin.md
new file mode 100644
index 00000000000..985c742e0b5
--- /dev/null
+++ b/docs/manual/docs/customizing-application/implementing-a-schema-plugin.md
@@ -0,0 +1,1380 @@
+# Implementing schema plugins {#implementing-a-schema-plugin}
+
+## Metadata schemas and profiles
+
+A metadata schema describes:
+
+1. the names, descriptions and any value codelists of the elements in the metadata schema
+2. how the elements of the metadata schema are laid out in a metadata document (structure)
+3. constraints on elements and content in a metadata document
+4. documentation on how the elements of the metadata schema should be used
+5. sample metadata documents and metadata templates
+6. scripts to convert metadata documents to and from other metadata schemas
+
+A metadata schema is usually an implementation of a metadata standard.
+
+A metadata profile is an adaptation of a metadata schema to suit the needs of a particular community. A metadata profile contains all the components of a metadata schema but may extend, restrict or redefine these components.
+
+## Implementing a metadata schema or profile
+
+There are many ways in which a metadata schema or profile can be implemented. This section will describe the way in which metadata schemas are implemented on or .
+
+Each metadata schema is a Maven module implemented as a filesystem tree. The root of the tree is the name of the metadata schema in abbreviated form. The essential components of a metadata schema in the `src/main/plugin/` folder and are laid out as follows:
+
+1. **loc** directory with subdirectories for each three letter language code that this information is localized into, with the content in XML files (labels.xml, codelists.xml). For example: `loc/eng/codelists.xml` describes the english codelists for metadata elements
+2. **schema** directory and file named **schema.xsd** providing a single entry point to the XSD hierarchy. For example: `schema/gmd/gmd.xsd`
+3. **schematron** directory has constraints on elements and content in a metadata document implemented using the ISO schematron language
+4. **docs** directory has documentation on how the elements of the metadata schema should be used.
+5. **sample-data** directory has sample metadata documents
+6. **convert** directory has XSLTs that convert metadata documents to and from other schemas
+
+More information on the content of these directories and files will be given in the next section.
+
+!!! info "See Also"
+
+ Some schemas on or have more information than described above because they have been implemented as GeoNetwork schema plugins.
+
+
+## Schema Plugins
+
+A schema plugin that can be used in GeoNetwork is a directory of stylesheets, XML schema descriptions (XSDs) and other information necessary for GeoNetwork to index, view and possibly edit content from XML metadata records.
+
+To be used in GeoNetwork, a schema directory can be manually placed in the `schema_plugins` sub directory of the GeoNetwork data directory. For some schema an additional JAR file should be added to the WEB-INF/lib folder. The default GeoNetwork data directory location is `INSTALL_DIR/web/geonetwork/WEB-INF/data`.
+
+The contents of these schemas are parsed during GeoNetwork initialization. If valid, they will be available for use when GeoNetwork starts up.
+
+Schemas can also added to GeoNetwork dynamically if a zip archive of the schema directory is created and then uploaded to GeoNetwork in one of following ways using functions in the Administration menu:
+
+1. Server file path (specified using file chooser)
+2. HTTP URL (eg. )
+3. As an online resource attached to an ISO19115/19139 metadata record
+
+Uploaded schemas are also stored in the `schema_plugins` sub directory of the GeoNetwork data directory.
+
+!!! info "See Also"
+
+ A template module is available here and is a good example to start with.
+
+
+### Contents of a GeoNetwork schema
+
+When installed, a GeoNetwork schema is a directory.
+
+The following subdirectories can be present in `src/main/plugin/`:
+
+- **schema**: (*Optional*) Directory containing the official XSDs of the metadata schema. If the schema is described by a DTD then this directory is optional. Note that schemas described by a DTD cannot be edited by GeoNetwork.
+- **schematron**: (*Optional*) Directory containing the schematrons used to check conditions on content.
+- **docs**: (*Optional*) Documentation about the schema
+- **index-fields**: (*Mandatory*) Directory of XSLT required to index metadata record.
+- **loc**: (*Mandatory*) Directory of localized information: labels, codelists or schema specific strings. Eg. `loc/eng/codelists.xml`
+- **convert**: (*Mandatory*) Directory of XSLTs to convert metadata from or to this schema. This could be to convert metadata to other schemas or to convert metadata from other schemas and formats to this schema. Eg. `convert/oai_dc.xsl`
+- **layout**: (*Mandatory for version 3.x*) contains configuration for presenting metadata in the editor.
+- **formatter**: (*Optional for version 3.x*) contains configuration for presenting metadata using Groovy or XSLT formatter.
+- **present**: (*Mandatory for version 2.x*) contains XSLTs for presenting metadata in the viewer/editor.
+- **present/csw**: (*Mandatory*) contains XSLTs for response to CSW requests for brief, summary and full records.
+- **process**: (*Optional*) contains XSLTs for processing metadata elements by metadata suggestions mechanism (see **suggest.xsl** below).
+- **sample-data**: (*Optional*) Sample metadata for this schema. The metadata samples are in MEF format so that samples can have thumbnails or browse graphics as well as online resources.
+- **templates**: (*Optional*) Directory containing template and subtemplate metadata records for this schema. Template metadata records are usually metadata records with the set of elements (and content) that will be used for a specific purpose. Eg. iso19139.mcp schema has a 'Minimum Element' template that has the mandatory elements for the schema and a example of the content that is expected.
+
+The following stylesheets can be present:
+
+- **extract-date-modified.xsl**: (*Mandatory*) Extract the date of modification from the metadata record.
+- **extract-gml.xsl**: (*Mandatory*) Extract the spatial extent from the metadata record as a GML GeometryCollection element.
+- **extract-thumbnails.xsl**: (*Optional*) Extract the browse graphic/thumbnail from the metadata record.
+- **extract-uuid.xsl**: (*Mandatory*) Extract the UUID of the metadata record.
+- **extract-relations.xsl**: (*Optional*) Extract the associated resources of the metadata record (eg. online source, thumbnails).
+- **set-thumbnail.xsl**: (*Optional*) Set the browse graphic/thumbnail in the metadata record.
+- **set-uuid.xsl**: (*Optional*) Set the UUID of the metadata record.
+- **suggest.xsl**: (*Optional*) XSLT run by metadata suggestions service. The XSLT contains processes that can be registered and run on different elements of a metadata record. eg. expand keyword field with comma separated content into multiple keyword fields. See [Suggestion for improving metadata content](../user-guide/workflow/suggestion.md) for more info.
+- **unset-thumbnail.xsl**: (*Optional*) Remove the browse graphic/thumbnail from the metadata record.
+- **update-child-from-parent-info.xsl**: (*Optional*) XSLT to specify which elements in a child record are updated from a parent record. Used to manage hierarchical relationships between metadata records.
+- **update-fixed-info.xsl**: (*Optional*) XSLT to update 'fixed' content in metadata records.
+
+The following configuration files can be present:
+
+- **oasis-catalog.xml**: (*Optional*) An oasis catalog describing any mappings that should be used for this schema eg. mapping URLs to local copies such as schemaLocations eg. is mapped to `schema/gmd/gmd.xsd`. Path names used in the oasis catalog are relative to the location of this file which is the schema directory.
+- **schema.xsd**: (*Optional*) XML schema directory file that includes the XSDs used by this metadata schema. If the schema uses a DTD then this file should not be present. Metadata records from schemas that use DTDs cannot be edited in GeoNetwork.
+- **schema-conversions.xml**: (*Optional*) XML file that describes the converters that can be applied to records belonging to this schema. This information is used to show these conversions as options for the user to choose when a metadata record belonging to this schema is shown in the search results.
+- **schema-ident.xml**: (*Mandatory*) XML file that contains the schema name, identifier, version number and details on how to recognise metadata records that belong to this schema. This file has an XML schema definition in `INSTALL_DIR/web/geonetwork/xml/validation/schemaPlugins/schema-ident.xsd` which is used to validate it when the schema is loaded.
+- **schema-substitutes.xml**: (*Optional*) XML file that redefines the set of elements that can be used as substitutes for a specific element.
+- **schema-suggestions.xml**: (*Optional*) XML file that tells the editor which child elements of a complex element to automatically expand in the editor.
+
+In the `index-fields` folder, the following files are required:
+
+- **index.xsl**: (*Mandatory*) Index the metadata record content. The output produce a list of field and values to index.
+
+To help in understanding what each of these components is and what is required, we will now give a step-by-step example of how to build a schemaPlugin for GeoNetwork.
+
+### Preparation
+
+In order to create a schema plugin for GeoNetwork, you should check out the source code:
+
+``` shell
+git clone --recursive https://github.com/geonetwork/core-geonetwork
+```
+
+Then you could check out the schema plugin repository containing examples:
+
+``` shell
+git clone --recursive https://github.com/geonetwork/schema-plugins
+```
+
+To work with the example shown here, you should create your new schema plugin in a subdirectory of the schemas Maven module (see `schemas`). The `iso19139.xyz` plugin from the schema plugin repository could be a good start.
+
+Once created, you need to register your new plugin in the build of the application. To do this:
+
+- Add the plugin as a module of the schemas module (see `schemas/pom.xml`):
+
+ ``` xml
+ iso19139.xyz
+ ```
+
+- Register the plugin in the webapp in the `copy-schemas` execution (see `web/pom.xml`):
+
+ ``` xml
+
+ ${project.basedir}/../schemas/iso19139.xyz/src/main/plugin
+ ${basedir}/src/main/webapp/WEB-INF/data/config/schema_plugins
+
+ ```
+
+- Optionally register the dependency if you plugin implement custom Java (see `web/pom.xml`):
+
+ ``` xml
+
+ ${project.groupId}
+ schema-iso19139.xyz
+ ${project.version}
+
+ ```
+
+### Example - ISO19115/19139 Marine Community Profile (MCP)
+
+The Marine Community Profile (MCP) is a profile of ISO19115/19139 developed for and with the Marine Community. The profile extends the ISO19115 metadata standard and is implemented using an extension of the XML implementation of ISO19115 described in ISO19139. Both the ISO19115 metadata standard and its XML implementation, ISO19139, are available through ISO distribution channels.
+
+The documentation for the Marine Community Profile can be found at . The implementation of the Marine Community Profile as XML schema definitions is based on the approach described at . The XML schema definitions (XSDs) are available at the URL .
+
+Looking at the XML schema definitions, the profile adds a few new elements to the base ISO19139 standard. So the basic idea in defining a plugin Marine Community Profile schema for GeoNetwork is to use as much of the basic ISO19139 schema definition supplied with GeoNetwork as possible.
+
+We'll now describe in basic steps how to create each of the components of a plugin schema for GeoNetwork that implements the MCP.
+
+#### Creating the schema-ident.xml file
+
+Now we need to provide the information necessary to identify the schema and metadata records that belong to the schema. The schema-ident.xml file for the MCP is as follows:
+
+``` xml
+
+
+ iso19139.mcp
+ 19c9a2b2-dddb-11df-9df4-001c2346de4c
+ 1.5
+
+ http://bluenet3.antcrc.utas.edu.au/mcp
+ http://bluenet3.antcrc.utas.edu.au/mcp-1.5-experimental/schema.xsd
+ http://www.isotc211.org/2005/gmd
+ http://www.isotc211.org/2005/gmd/gmd.xsd
+ http://www.isotc211.org/2005/srv
+ http://schemas.opengis.net/iso/19139/20060504/srv/srv.xsd
+
+
+
+
+
+ Australian Marine Community Profile of ISO 19115:2005/19139|
+ Marine Community Profile of ISO 19115:2005/19139
+
+
+
+
+ 1.5-experimental|
+ MCP:BlueNet V1.5-experimental|
+ MCP:BlueNet V1.5
+
+
+
+
+
+```
+
+Each of the elements is as follows:
+
+- **name** - the name by which the schema will be known in GeoNetwork. If the schema is a profile of a base schema already added to GeoNetwork then the convention is to call the schema ..
+- **id** - a unique identifier for the schema.
+- **version** - the version number of the schema. Multiple versions of the schema can be present in GeoNetwork.
+- **schemaLocation** - a set of pairs, where the first member of the pair is a namespace URI and the second member is the official URL of the XSD. The contents of this element will be added to the root element of any metadata record displayed by GeoNetwork as a schemaLocation/noNamespaceSchemaLocation attribute, if such as attribute does not already exist. It will also be used whenever an official schemaLocation/noNamespaceSchemaLocation is required (eg. in response to a ListMetadataFormats OAI request).
+- **autodetect** - contains elements or attributes (with content) that must be present in any metadata record that belongs to this schema. This is used during schema detection whenever GeoNetwork receives a metadata record of unknown schema.
+- **filters** - (Optional) contains custom filter to be applied based on user privileges
+
+After creating this file you can validate it manually using the XML schema definition (XSD) in `INSTALL_DIR/web/geonetwork/xml/validation/schemaPlugins/schema-ident.xsd`. This XSD is also used to validate this file when the schema is loaded. If schema-ident.xml fails validation, the schema will not be loaded.
+
+#### More on autodetect
+
+The autodetect section of schema-ident.xml is used when GeoNetwork needs to identify which metadata schema a record belongs to.
+
+The five rules that can be used in this section in order of evaluation are:
+
+1. **Attributes** - Find one or more attributes and/or namespaces in the document. An example use case is a profile of ISO19115/19139 that adds optional elements under a new namespace to gmd:identificationInfo/gmd:MD_DataIdentification. To detect records that belong to this profile the autodetect section in the schema-ident.xml file could look something like the following:
+
+ ``` xml
+
+
+
+
+ ```
+
+ Some other points about attributes autodetect:
+
+ - multiple attributes can be specified - all must be match for the record to be recognized as belonging to this schema.
+ - if the attributes have a namespace then the namespace should be specified on the autodetect element or somewhere in the schema-ident.xml document.
+
+2. **Elements** - Find one or more elements in the document. An example use case is the one shown in the example schema-ident.xml file earlier:
+
+ ``` xml
+
+
+
+
+ Australian Marine Community Profile of ISO 19115:2005/19139|
+ Marine Community Profile of ISO 19115:2005/19139
+
+
+
+
+ 1.5-experimental|
+ MCP:BlueNet V1.5-experimental|
+ MCP:BlueNet V1.5
+
+
+
+
+ ```
+
+ Some other points about elements autodetect:
+
+ - multiple elements can be specified - eg. as in the above, both metadataStandardName and metadataStandardVersion have been specified - all must be match for the record to be recognized as belonging to this schema.
+ - multiple values for the elements can be specified. eg. as in the above, a match for gmd:metadataStandardVersion will be found for `1.5-experimental` OR `MCP:BlueNet V1.5-experimental` OR `MCP:BlueNet V1.5` - the vertical line or pipe character '|' is used to separate the options here. Regular expression can be used also.
+ - if the elements have a namespace then the namespace(s) should be specified on the autodetect element or somewhere in the schema-ident.xml document before the element in which they are used - eg. in the above there are there namespace declarations on the autodetect element so as not to clutter the content.
+
+3. **Root element** - root element of the document must match. An example use case is the one used for the eml-gbif schema. Documents belonging to this schema always have root element of eml:eml so the autodetect section for this schema is:
+
+ ``` xml
+
+
+
+
+
+ ```
+
+ Some other points about root element autodetect:
+
+ - multiple elements can be specified - any element in the set that matches the root element of the record will trigger a match.
+ - if the elements have a namespace then the namespace(s) should be specified on the autodetect element or somewhere in the schema-ident.xml document before the element that uses them - eg. as in the above there is a namespace declaration on the autodetect element for clarity.
+
+4. **Namespaces** - Find one or more namespaces in the document. An example use case is the one used for the csw:Record schema. Records belonging to the csw:Record schema can have three possible root elements: csw:Record, csw:SummaryRecord and csw:BriefRecord, but instead of using a multiple element root autodetect, we could use the common csw namespace for autodetect as follows:
+
+ ``` xml
+
+
+
+ ```
+
+ Some other points about namespaces autodetect:
+
+ - multiple namespaces can be specified - all must be present for the record to be recognized as belonging to this schema.
+ - the prefix is ignored. A namespace match occurs if the namespace URI found in the record matches the namespace URI specified in the namespaces autodetect element.
+
+5. **Default schema** - This is the fail-safe provision for records that don't match any of the installed schemas. The value for the default schema is specified in the appHandler configuration of the `INSTALL_DIR/web/geonetwork/WEB-INF/config.xml` config file or it could be a default specified by the operation calling autodetect (eg. a value parsed from a user bulk loading some metadata records). For flexibility and accuracy reasons it is preferable that records be detected using the autodetect information of an installed schema. The default schema is just a 'catch all' method of assigning records to a specific schema. The config element in `INSTALL_DIR/web/geonetwork/WEB-INF/config.xml` looks like the following:
+
+ ``` xml
+
+ .....
+
+ .....
+
+ ```
+
+#### More on autodetect evaluation
+
+The rules for autodetect are evaluated as follows:
+
+``` shell
+for-each autodetect rule type in ( 'attributes/namespaces', 'elements',
+ 'namespaces', 'root element' )
+ for-each schema
+ if schema has autodetect rule type then
+ check rule for a match
+ if match add to list of previous matches
+ end if
+ end for-each
+
+ if more than one match throw 'SCHEMA RULE CONFLICT EXCEPTION'
+ if one match then set matched = first match and break loop
+end for-each
+
+if no match then
+ if namespaces of record and default schema overlap then
+ set match = default schema
+ else throw 'NO SCHEMA MATCHES EXCEPTION'
+end if
+
+return matched schema
+```
+
+As an example, suppose we have three schemas iso19139.mcp, iso19139.mcp-1.4 and iso19139.mcp-cmar with the following autodetect elements:
+
+##### iso19139.mcp-1.4
+
+``` xml
+
+
+
+
+ Australian Marine Community Profile of ISO 19115:2005/19139
+
+
+
+ MCP:BlueNet V1.4
+
+
+
+```
+
+##### iso19139.mcp-cmar
+
+``` xml
+
+
+
+```
+
+##### iso19139.mcp
+
+``` xml
+
+
+
+
+
+```
+
+A record going through autodetect processing (eg. on import) would be checked against:
+
+- iso19139.mcp-cmar first as it has an 'attributes' rule
+- then iso19139.mcp-1.4 as it has an 'elements' rules
+- then finally against iso19139.mcp, as it has a 'root element' rule.
+
+The idea behind this processing algorithm is that base schemas will use a 'root element' rule (or the more difficult to control 'namespaces' rule) and profiles will use a finer or more specific rule such as 'attributes' or 'elements'.
+
+#### More on filters
+
+The goal is to add the capability to configure the download and dynamic operation based on the catalog content where they could have different meanings depending :
+
+- on the schema (eg. URL to a file for download is not located at the same place for dublin core and ISO19139)
+- on the record encoding rules (eg. download could be WFS links and not only uploaded file).
+
+Filter configuration for each type of operation is defined in schema-ident.xml in the filters section.
+
+A filter define:
+
+- an operation (which match canEdit, canDownload, canDynamic method in AccessManager)
+- an XPath to select elements to filter
+- an optional element definition to substitute the replaced element by (if a match is found this element attributes or children are inserted). This is used to highlight removed element.
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+The filters are applied in XMLSerializer according to user privileges.
+
+After setting up schema-ident.xml, our new GeoNetwork plugin schema for MCP contains:
+
+ schema-ident.xml
+
+#### Creating the schema-conversions.xml file {#schema_conversions}
+
+This file describes the converters that can be applied to metadata records that belong to the schema. Each converter must be manually defined as a GeoNetwork (Jeeves) service that can be called to transform a particular metadata record to a different schema. The schema-conversions.xml file for the MCP is as follows:
+
+``` xml
+
+
+
+
+
+
+```
+
+Each converter has the following attributes:
+
+- **name** - the name of the converter. This is the service name of the GeoNetwork (Jeeves) service and should be unique (prefixing the service name with ``xml_`` is a good way to make this name unique).
+- **nsUri** - the primary namespace of the schema produced by the converter. eg. xml_iso19139.mcpTorifcs transforms metadata records from iso19139.mcp to the RIFCS schema. Metadata records in the RIFCS metadata schema have primary namespace URI of .
+- **schemaLocation** - the location (URL) of the XML schema definition (XSD) corresponding to the nsURI.
+- **xslt** - the name of the XSLT that actually carries out the transformation. This XSLT should be located in the convert subdirectory of the schema plugin.
+
+After setting up schema-conversions.xml, our new GeoNetwork plugin schema for MCP contains:
+
+ schema-conversions.xml schema-ident.xml
+
+#### Creating the schema directory and schema.xsd file {#schema_and_schema_xsd}
+
+The schema and schema.xsd components are used by the GeoNetwork editor and validation functions.
+
+GeoNetwork's editor uses the XSDs to build a form that will not only order the elements in a metadata document correctly but also offer options to create any elements that are not in the metadata document. The idea behind this approach is twofold. Firstly, the editor can use the XML schema definition rules to help the user avoid creating a document that is structurally incorrect eg. missing mandatory elements or elements not ordered correctly. Secondly, the same editor code can be used on any XML metadata document with a defined XSD.
+
+If you are defining your own metadata schema then you can create an XML schema document using the XSD language. The elements of the language can be found online at or you can refer to a textbook such as Priscilla Walmsley's Definitive XML Schema (Prentice Hall, 2002). GeoNetwork's XML schema parsing code understands almost all of the XSD language with the exception of redefine, any and anyAttribute (although the last two can be handled under special circumstances).
+
+In the case of the Marine Commuity Profile, we are basically defining a number of extensions to the base standard ISO19115/19139. These extensions are defined using the XSD extension mechanism on the types defined in ISO19139. The following snippet shows how the Marine Community Profile extends the gmd:MD_Metadata element to add a new element called revisionDate:
+
+``` xml
+
+
+
+
+
+
+
+ Extends the metadata element to include revisionDate
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+In short, we have defined a new element mcp:MD_Metadata with type mcp:MD_Metadata_Type, which is an extension of gmd:MD_Metadata_Type. By extension, we mean that the new type includes all of the elements of the old type plus one new element, mcp:revisionDate. A mandatory attribute (gco:isoType) is also attached to mcp:MD_Metadata with a fixed value set to the name of the element that we extended (gmd:MD_Metadata).
+
+By defining the profile in this way, it is not necessary to modify the underlying ISO19139 schemas. So the schema directory for the MCP essentially consists of the extensions plus the base ISO19139 schemas. One possible directory structure is as follows:
+
+ extensions gco gmd gml gmx gsr gss gts resources srv xlink
+
+The extensions directory contains a single file mcpExtensions.xsd, which imports the gmd namespace. The remaining directories are the ISO19139 base schemas.
+
+The schema.xsd file, which is the file GeoNetwork looks for, will import the mcpExtensions.xsd file and any other namespaces not imported as part of the base ISO19139 schema. It is shown as follows:
+
+``` xml
+
+
+
+
+
+
+```
+
+At this stage, our new GeoNetwork plugin schema for MCP contains:
+
+``` shell
+schema-conversions.xml schema-ident.xml schema.xsd schema
+```
+
+#### Creating the extract-\... XSLTs
+
+GeoNetwork needs to extract certain information from a metadata record and translate it into a common, simplified XML structure that is independent of the metadata schema. Rather than do this with Java coded XPaths, XSLTs are used to process the XML and return the common, simplified XML structure.
+
+The three xslts we'll create are:
+
+- **extract-date-modified.xsl** - this XSLT processes the metadata record and extracts the date the metadata record was last modified. For the MCP, this information is held in the mcp:revisionDate element which is a child of mcp:MD_Metadata. The easiest way to create this for MCP is to copy extract-date-modified.xsl from the iso19139 schema and modify it to suit the MCP namespace and to use mcp:revisionDate in place of gmd:dateStamp.
+- **extract-gml.xsl** - this XSLT processes the metadata record and extracts the spatial extent as a gml GeometryCollection element. The gml is passed to geotools for insertion into the spatial index (either a shapefile or a spatial database). For ISO19115/19139 and profiles, this task is quite easy because spatial extents (apart from the bounding box) are encoded as gml in the metadata record. Again, the easiest way to create this for the MCP is to copy extract-gml.xsd from the iso19139 schema ad modify it to suit the MCP namespace.
+
+An example bounding box fragment from an MCP metadata record is:
+
+``` xml
+
+
+
+
+
+ 112.9
+
+
+ 153.64
+
+
+ -43.8
+
+
+ -9.0
+
+
+
+
+
+```
+
+Running extract-gml.xsl on the metadata record that contains this XML will produce:
+
+``` xml
+
+
+
+
+
+ 112.9,-9.0, 153.64,-9.0, 153.64,-43.8, 112.9,-43.8, 112.9,-9.0
+
+
+
+
+
+```
+
+If there is more than one extent in the metadata record, then they should also appear in this gml:GeometryCollection element.
+
+To find out more about gml, see Lake, Burggraf, Trninic and Rae, "GML Geography Mark-Up Language, Foundation for the Geo-Web", Wiley, 2004.
+
+Finally, a note on projections. It is possible to have bounding polygons in an MCP record in a projection other than EPSG:4326. GeoNetwork transforms all projections known to GeoTools (and encoded in a form that GeoTools understands) to EPSG:4326 when writing the spatial extents to the shapefile or spatial database.
+
+- **extract-uuid.xsl** - this XSLT processes the metadata record and extracts the identifier for the record. For the MCP and base ISO standard, this information is held in the gmd:fileIdentifier element which is a child of mcp:MD_Metadata.
+
+These xslts can be tested by running them on a metadata record from the schema. You should use the saxon xslt processor. For example:
+
+``` shell
+java -jar INSTALL_DIR/web/geonetwork/WEB-INF/lib/saxon-9.1.0.8b-patch.jar
+ -s testmcp.xml -o output.xml extract-gml.xsl
+```
+
+At this stage, our new GeoNetwork plugin schema for MCP contains:
+
+ extract-date-modified.xsl extract-gml.xsd extract-uuid.xsl
+ schema-conversions.xml schema-ident.xml schema.xsd schema
+
+#### Creating the localized strings in the loc directory
+
+The loc directory contains localized strings specific to this schema, arranged by language abbreviation in sub-directories.
+
+You should provide localized strings in whatever languages you expect your schema to be used in.
+
+Localized strings for this schema can be used in the presentation xslts and schematron error messages. For the presentation xslts:
+
+- codelists for controlled vocabulary fields should be in loc//codelists.xml eg. `loc/eng/codelists.xml`
+- label strings that replace XML element names with more intelligible/alternative phrases and rollover help strings should be in loc//labels.xml eg. `loc/eng/labels.xml`.
+- all other localized strings should be in loc//strings.xml eg. `loc/eng/strings.xml`
+
+Note that because the MCP is a profile of ISO19115/19139 and we have followed the GeoNetwork naming convention for profiles, we need only include the labels and codelists that are specific to the MCP or that we want to override. Other labels and codelists will be retrieved from the base schema iso19139.
+
+#### More on codelists.xml
+
+Typically codelists are generated from enumerated lists in the metadata schema XSDs such as the following from for gmd:MD_TopicCategoryCode in the iso19139 schema:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+The following is part of the codelists.xml entry manually created for this element:
+
+``` xml
+
+
+ farming
+
+ Rearing of animals and/or cultivation of plants. Examples: agriculture,
+ irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and
+ livestock
+
+
+
+ biota
+
+ Flora and/or fauna in natural environment. Examples: wildlife, vegetation,
+ biological sciences, ecology, wilderness, sealife, wetlands, habitat
+
+
+
+ boundaries
+
+ Legal land descriptions. Examples: political and administrative
+ boundaries
+
+
+ .....
+
+
+```
+
+The codelists.xml file maps the enumerated values from the XSD to a localized label and a description via the code element.
+
+A localized copy of codelists.xml is made available on an XPath to the presentation XSLTs eg. /root/gui/schemas/iso19139/codelist for the iso19139 schema.
+
+The XSLT metadata.xsl which contains templates used by all metadata schema presentation XSLTs, handles the creation of a select list/drop down menu in the editor and display of the code and description in the metadata viewer.
+
+The iso19139 schema has additional codelists that are managed external to the XSDs in catalog/vocabulary files such as These have also been added to the codelists.xml file so that they can be localized, overridden in profiles and include an extended description to provide more useful information when viewing the metadata record.
+
+To use the ISO19139 codelist in a profile you can add a template to point to the codelist to use:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+To override some of the ISO19139 codelist, you can check if the codelist is defined in xyz profile and if not use the ISO19139 one:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+The iso19139 schema has additional templates in its presentation xslts to handlese codelists because they are specific to that schema. These are discussed in the section on presentation XSLTs later in this manual.
+
+#### More on labels.xml
+
+A localized copy of labels.xml is made available on an XPath to the presentation XSLTs eg. /root/gui/schemas/iso19139/labels for the iso19139 schema.
+
+The `labels.xml` file can also be used to provide helper values in the form of a drop down/select list for free text fields. As an example:
+
+``` xml
+
+
+ Recognition of those who contributed to the resource(s)
+
+
+
+
+
+```
+
+This would result in the Editor (through the XSLT metadata.xsl) displaying the credit field with these helper options listed beside it in a drop down/select menu something like the following:
+
+
+
+#### More on strings.xml
+
+A localized copy of `strings.xml` is made available on an XPath to the presentation XSLTs eg. /root/gui/schemas/iso19139/strings for the iso19139 schema.
+
+After adding the localized strings, our new GeoNetwork plugin schema for MCP contains:
+
+ extract-date-modified.xsl extract-gml.xsd extract-uuid.xsl
+ loc present schema-conversions.xml schema-ident.xml schema.xsd
+ schema
+
+#### Creating the presentations using formatter
+
+!!! info "Version Added"
+
+ 3.0
+
+
+!!! info "See Also"
+
+ See formatter section TODO for version 3.x
+
+
+#### Customizing the editor
+
+!!! info "Version Added"
+
+ 3.0
+
+
+!!! info "See Also"
+
+ See editor configuration section TODO for version 3.x
+
+
+#### Creating the presentations XSLTs in the present directory
+
+!!! warning "Deprecated"
+
+ 3.0.0
+
+
+Each metadata schema should contain XSLTs that display and possibly edit metadata records that belong to the schema. These XSLTs are held in the `present` directory.
+
+To be used in the XSLT include/import hierarchy these XSLTs must follow a naming convention: metadata-.xsl. So for example, the presentation xslt for the iso19139 schema is `metadata-iso19139.xsl`. For the MCP, since our schema name is iso19139.mcp, the presentation XSLT would be called `metadata-iso19193.mcp.xsl`.
+
+Any XSLTs included by the presentation XSLT should also be in the present directory (this is a convention for clarity - it is not mandatory as include/import URLs can be mapped in the oasis-catalog.xml for the schema to other locations).
+
+There are certain XSLT templates that the presentation XSLT must have:
+
+- the **main** template, which must be called: metadata-. For the MCP profile of iso19139 the main template would look like the following (taken from metadata-iso19139.mcp.xsl):
+
+```{=html}
+
+```
+
+
+
+
+
+
+
+
+
+
+
+
+Analyzing this template:
+
+1. The name="metadata-iso19139.mcp" is used by the main element processing template in metadata.xsl: elementEP. The main metadata services, show and edit, end up calling metadata-show.xsl and metadata-edit.xsl respectively with the metadata record passed from the Java service. Both these XSLTs, process the metadata record by applying the elementEP template from metadata.xsl to the root element. The elementEP template calls this main schema template using the schema name iso19139.mcp.
+2. The job of this main template is set to process all the elements of the metadata record using templates declared with a mode name that matches the schema name or the name of the base schema (in this case iso19139). This modal processing is to ensure that only templates intended to process metadata elements from this schema or the base schema are applied. The reason for this is that almost all profiles change or add a small number of elements to those in the base schema. So most of the metadata elements in a profile can be processed in the mode of the base schema. We'll see later in this section how to override processing of an element in the base schema.
+
+- a **completeTab** template, which must be called: CompleteTab. This template will display all tabs, apart from the 'default' (or simple mode) and the 'XML View' tabs, in the left hand frame of the editor/viewer screen. Here is an example for the MCP:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ...... (same as for iso19139CompleteTab in
+ GEONETWORK_DATA_DIR/schema_plugins/iso19139/present/
+ metadata-iso19139.xsl) ......
+
+
+```
+
+This template is called by the template named "tab" (which also adds the "default" and "XML View" tabs) in `INSTALL_DIR/web/geonetwork/xsl/metadata-tab-utils.xsl` using the schema name. That XSLT also has the code for the "displayTab" template.
+
+'mcpMinimum', 'mcpCore', 'complete' etc are the names of the tabs. The name of the current or active tab is stored in the global variable "currTab" available to all presentation XSLTs. Logic to decide what to display when a particular tab is active should be contained in the root element processing tab.
+
+- a **root element** processing tab. This tab should match on the root element of the metadata record. For example, for the iso19139 schema:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ .........
+
+
+```
+
+This template is basically a very long "choose" statement with "when" clauses that test the value of the currently defined tab (in global variable currTab). Each "when" clause will display the set of metadata elements that correspond to the tab definition using "elementEP" directly (as in the "when" clause for the 'identification' tab above) or via a named template (as in the 'metadata' tab above). For the MCP our template is similar to the one above for iso19139, except that the match would be on "mcp:MD_Metadata" (and the processing mode may differ - see the section 'An alternative XSLT design for profiles' below for more details).
+
+- a **brief** template, which must be called: Brief. This template processes the metadata record and extracts from it a format neutral summary of the metadata for purposes such as displaying the search results. Here is an example for the eml-gbif schema (because it is fairly short!):
+
+``` xml
+
+
+
+ <xsl:value-of select="normalize-space(dataset/title[1])"/>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+Analyzing this template:
+
+1. The template matches on an element eml-gbifBrief, created by the mode="brief" template in metadata-utils.xsl. The metadata record will be the first child in the /metadata XPath.
+2. Then process metadata elements to produce a flat XML structure that is used by search-results-xhtml.xsl to display a summary of the metadata record found by a search.
+
+Once again, for profiles of an existing schema, it makes sense to use a slightly different approach so that the profile need not duplicate templates. Here is an example from metadata-iso19139.mcp.xsl:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+This template splits the processing between the base iso19139 schema and a brief template that handles elements specific to the profile. This assumes that:
+
+1. The base schema has separated the element from the remainder of its brief processing so that it can be called by profiles
+2. The profile includes links to equivalent elements that can be used by the base schema to process common elements eg. for ISO19139, elements in the profile have gco:isoType attributes that give the name of the base element and can be used in XPath matches such as "gmd:MD_DataIdentification|*[@gco:isoType='gmd:MD_DataIdentification']".
+
+- templates that match on elements specific to the schema. Here is an example from the eml-gbif schema:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+ ,
+
+
+
+ (
+
+ )
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+Analyzing this template:
+
+1. In view mode the individual keywords from the set are concatenated into a comma separated string with the name of the thesaurus in brackets at the end.
+2. In edit mode, the keywordSet is handled as a complex element ie. the user can add individual keyword elements with content and a single thesaurus name.
+3. This is an example of the type of processing that can be done on an element in a metadata record.
+
+For profiles, templates for elements can be defined in the same way except that the template will process in the mode of the base schema. Here is an example showing the first few lines of a template for processing the mcp:revisionDate element:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+ ......
+```
+
+If a template for a profile is intended to override a template in the base schema, then the template can be defined in the presentation XSLT for the profile with a priority attribute set to a high number and an XPath condition that ensures the template is processed for the profile only. For example in the MCP, we can override the handling of gmd:EX_GeographicBoundingBox in metadata-iso19139.xsl by defining a template in metadata-iso19139.mcp.xsl as follows:
+
+``` xml
+
+
+......
+```
+
+Finally, a profile may also extend some of the existing codelists in the base schema. These extended codelists should be held in a localized codelists.xml. As an example, in iso19139 these codelists are often attached to elements like the following:
+
+``` xml
+
+ custodian
+
+```
+
+Templates for handling these elements are in the iso19139 presentation XSLT `GEONETWORK_DATA_DIR/schema_plugins/iso19139/present/metadata-iso19139.xsl`. These templates use the name of the element (eg. gmd:CI_RoleCode) and the codelist XPath (eg. /root/gui/schemas/iso19139/codelists) to build select list/drop down menus when editing and to display a full description when viewing. See templates near the template named 'iso19139Codelist'. These templates can handle the extended codelists for any profile because they:
+
+- match on any element that has a child element with attribute codeList
+- use the schema name in the codelists XPath
+- fall back to the base iso19139 schema if the profile codelist doesn't have the required codelist
+
+However, if you don't need localized codelists, it is often easier and more direct to extract codelists directly from the `gmxCodelists.xml` file. This is in fact the solution that has been adopted for the MCP. The `gmxCodelists.xml` file is included in the presentation xslt for the MCP using a statement like:
+
+``` xml
+
+```
+
+Check the codelist handling templates in `metadata-iso19139.mcp.xsl` to see how this works.
+
+#### An alternative XSLT design for profiles
+
+In all powerful languages there will be more than one way to achieve a particular goal. This alternative XSLT design is for processing profiles. The idea behind the alternative is based on the following observations about the GeoNetwork XSLTs:
+
+1. All elements are initially processed by apply-templates in mode "elementEP".
+2. The template "elementEP" (see `INSTALL_DIR/web/geonetwork/xsl/metadata.xsl`) eventually calls the **main** template of the schema/profile.
+3. The main template can initially process the element in a mode particular to the profile and if this is not successful (ie. no template matches and thus no HTML elements are returned), process the element in the mode of the base schema.
+
+The advantage of this design is that overriding a template for an element in the base schema does not need the priority attribute or an XPath condition check on the schema name.
+
+Here is an example for the MCP (iso19139.mcp) with base schema iso19139:
+
+- the **main** template, which must be called: metadata-iso19139.mcp.xsl:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+Analyzing this template:
+
+1. The name="metadata-iso19139.mcp" is used by the main element processing template in metadata.xsl: elementEP. The main metadata services, show and edit, end up calling metadata-show.xsl and metadata-edit.xsl respectively with the metadata record passed from the Java service. Both these XSLTs, process the metadata record by applying the elementEP template from metadata.xsl to the root element. elementEP calls the appropriate main schema template using the schema name.
+2. The job of this main template is set to process all the elements of the metadata profile. The processing takes place in one of two modes. Firstly, the element is processed in the profile mode (iso19139.mcp). If a match is found then HTML elements will be returned and copied to the output document. If no HTML elements are returned then the element is processed in the base schema mode, iso19139.
+
+- templates that match on elements specific to the profile have mode iso19139.mcp:
+
+``` xml
+
+
+
+
+ .....
+
+```
+
+- templates that override elements in the base schema are processed in the profile mode iso19139.mcp
+
+``` xml
+
+
+
+
+ .....
+
+```
+
+Notice that the template header of the profile has a simpler design than that used for the original design? Neither the priority attribute or the schema XPath condition is required because we are using a different mode to the base schema.
+
+- To support processing in two modes we need to add a null template to the profile mode iso19139.mcp as follows:
+
+``` xml
+
+```
+
+This template will match all elements that we don't have a specific template for in the profile mode iso19139.mcp. These elements will be processed in the base schema mode iso19139 instead because the null template returns nothing (see the main template discussion above).
+
+The remainder of the discussion in the original design relating to tabs etc applies to the alternative design and is not repeated here.
+
+#### CSW Presentation XSLTs
+
+The CSW server can be asked to provide records in a number of output schemas. The two supported by GeoNetwork are:
+
+- **ogc** - - a dublin core derivative
+- **iso** - - ISO19115/19139
+
+From each of these output schemas, a **brief**, **summary** or **full** element set can be requested.
+
+These output schemas and element sets are implemented in GeoNetwork as XSLTs and they are stored in the 'csw' subdirectory of the 'present' directory. The ogc output schema XSLTs are implemented as ogc-brief.xsl, ogc-summary and ogc-full.xsl. The iso output schema XSLTs are implemented as iso-brief.xsl, iso-summary.xsl and iso-full.xsl.
+
+To create these XSLTs for the MCP, the best option is to copy and modify the csw presentation XSLTs from the base schema iso19139.
+
+After creating the presentation XSLTs, our new GeoNetwork plugin schema for MCP contains:
+
+ extract-date-modified.xsl extract-gml.xsd extract-uuid.xsl
+ loc present schema-conversions.xml schema-ident.xml schema.xsd
+ schema
+
+#### Creating the index.xsl to index content from the metadata record
+
+This XSLT indexes the content of elements in the metadata record. The essence of this XSLT is to select elements from the metadata record and map them to index field names. Using Kibana user can browse the index and check all fields available. The number of fields depends on the catalog as some fields are dynamic eg. codelist, thesaurus.
+
+In Kibana, navigate to ``Stack Management --> Index pattern``
+
+
+
+Select ``gn-records`` to retrieve the list of fields:
+
+
+
+If Elasticsearch instance is accessible, user can get the details about a record using (``Kibana --> dev tools`` can also be used to get the document details):
+
+
+
+For example, here is the mapping created between the metadata element mcp:revisionDate and the index field changeDate:
+
+``` xml
+
+
+
+```
+
+Notice that we are creating a new XML document. The Field elements in this document are read by GeoNetwork to create a document object for indexing (see the SearchManager class in the GeoNetwork source).
+
+Once again, because the MCP is a profile of ISO19115/19139, it is probably best to modify `index.xsl` from the schema iso19139 to handle the namespaces and additional elements of the MCP.
+
+At this stage, our new GeoNetwork plugin schema for MCP contains:
+
+ extract-date-modified.xsl extract-gml.xsd extract-uuid.xsl
+ index.xsl loc present schema-conversions.xml schema-ident.xml
+ schema.xsd schema
+
+#### Creating the sample-data directory
+
+This is a simple directory. Put MEF files with sample metadata in this directory. Make sure they have a `.mef` suffix.
+
+A MEF file is a zip archive with the metadata, thumbnails, file based online resources and an info file describing the contents. The contents of a MEF file are discussed in more detail in the next section of this manual.
+
+Sample data in this directory can be added to the catalog using the Administration menu.
+
+At this stage, our new GeoNetwork plugin schema for MCP contains:
+
+ extract-date-modified.xsl extract-gml.xsd extract-uuid.xsl
+ index-fields.xsl loc present sample-data schema-ident.xml schema.xsd
+ schema
+
+#### Creating schematrons to describe MCP conditions
+
+Schematrons are rules that are used to check conditions and content in the metadata record as part of the two stage validation process used by GeoNetwork.
+
+Schematron rules are created in the schematrons directory that you checked out earlier - see [Preparation](implementing-a-schema-plugin.md#preparation) above.
+
+An example rule is:
+
+``` xml
+
+
+
+ $loc/strings/M30
+
+
+ $loc/strings/alert.M30
+ $loc/strings/report.M30
+
+
+```
+
+As for most of GeoNetwork, the output of this rule can be localized to different languages. The corresponding localized strings are:
+
+``` xml
+
+
+ .....
+
+ [ISOFTDS19139:2005-TableA1-Row15] - Check point description required if available
+
+ .....
+
+
'checkPointDescription' is mandatory if 'checkPointAvailability' = 1 or true.
+
+ .....
+
+ Check point description documented.
+
+ .....
+
+
+```
+
+Procedure for adding schematron rules, working within the schematrons directory:
+
+1. Place your schematron rules in 'rules'. Naming convention is 'schematron-rules-.sch' eg. `schematron-rules-iso-mcp.sch`. Place localized strings for the rule assertions into 'rules/loc/'.
+
+Schematron rules are compiled when the schema is loaded.
+
+At this stage, our new GeoNetwork plugin schema for MCP contains:
+
+ extract-date-modified.xsl extract-gml.xsd extract-uuid.xsl
+ index-fields.xsl loc present sample-data schema-conversions.xml
+ schema-ident.xml schema.xsd schema schematron/schematron-rules-iso-mcp.sch
+
+#### Adding the components necessary to create and edit MCP metadata
+
+So far we have added all the components necessary for GeoNetwork to identify, view and validate MCP metadata records. Now we will add the remaining components necessary to create and edit MCP metadata records.
+
+We'll start with the XSLTs that set the content of various elements in the MCP metadata records.
+
+#### Creating set-uuid.xsl
+
+- **set-uuid.xsl** - this XSLT takes as a parameter the UUID of the metadata record and writes it into the appropriate element of the metadata record. For the MCP this element is the same as the base ISO schema (called iso19139 in GeoNetwork), namely gmd:fileIdentifier. However, because the MCP uses a different namespace on the root element, this XSLT needs to be modified.
+
+#### Creating the update-\... XSLTs
+
+- **update-fixed-info.xsl** - this XSLT is run after editing to fix certain elements and content in the metadata record. For the MCP there are a number of actions we would like to take to 'hard-wire' certain elements and content. To do this the XSLT the following processing logic:
+
+```{=html}
+
+```
+ if the element is one that we want to process then
+ add a template with a match condition for that element and process it
+ else copy the element to output
+
+Because the MCP is a profile of ISO19115/19139, the easiest path to creating this XSLT is to copy update-fixed-info.xsl from the iso19139 schema and modify it for the changes in namespace required by the MCP and then to include the processing we want.
+
+A simple example of MCP processing is to make sure that the gmd:metadataStandardName and gmd:metadataStandardVersion elements have the content needed to ensure that the record is recognized as MCP. To do this we can add two templates as follows:
+
+``` xml
+
+
+ Australian Marine Community Profile of ISO 19115:2005/19139
+
+
+
+
+
+ MCP:BlueNet V1.5
+
+
+```
+
+Processing by `update-fixed-info.xsl` can be enabled/disabled using the *Automatic Fixes* check box in the System Configuration menu. By default, it is enabled.
+
+Some important tasks handled in `upgrade-fixed-info.xsl`:
+
+- creating URLs for metadata with attached files (eg. onlineResources with 'File for download' in iso19139)
+- setting date stamp/revision date
+- setting codelist URLs to point to online ISO codelist catalogs
+- adding default spatial reference system attributes to spatial extents
+
+A specific task required for the MCP `update-fixed-info.xsl` was to automatically create an online resource with a URL pointing to the metadata.show service with parameter set to the metadata uuid. This required some changes to the update-fixed-info.xsl supplied with iso19139. In particular:
+
+- the parent elements may not be present in the metadata record
+- processing of the online resource elements for the metadata point of truth URL should not interfere with other processing of online resource elements
+
+Rather than describe the individual steps required to implement this and the decisions required in the XSLT language, take a look at the `update-fixed-info.xsl` already present for the MCP schema in the iso19139.mcp directory and refer to the dot points above.
+
+#### Creating the templates directory
+
+This is a simple directory. Put XML metadata files to be used as templates in this directory. Make sure they have a `.xml` suffix. Templates in this directory can be added to the catalog using the Administration menu.
+
+#### Editor behaviour: Adding schema-suggestions.xml and schema-substitutes.xml
+
+- **schema-suggestions.xml** - The default behaviour of the GeoNetwork advanced editor when building the editor forms is to show elements that are not in the metadata record as unexpanded elements. To add these elements to the record, the user will have to click on the '+' icon next to the element name. This can be tedious especially as some metadata standards have elements nested in others (ie. complex elements). The schema-suggestions.xml file allows you to specify elements that should be automatically expanded by the editor. An example of this is the online resource information in the ISO19115/19139 standard. If the following XML was added to the `schema-suggestions.xml` file:
+
+``` xml
+
+
+
+
+
+```
+
+The effect of this would be that when an online resource element was expanded, then input fields for the protocol (a drop down/select list), name and description would automatically appear in the editor.
+
+Once again, a good place to start when building a `schema-suggestions.xml` file for the MCP is the `schema-suggestions.xml` file for the iso19139 schema.
+
+- **schema-substitutes.xml** - Recall from the earlier [Creating the schema directory and schema.xsd file](implementing-a-schema-plugin.md#schema_and_schema_xsd) section, that the method we used to extend the base ISO19115/19139 schemas is to extend the base type, define a new element with the extended base type and allow the new element to substitute for the base element. So for example, in the MCP, we want to add a new resource constraint element that holds Creative Commons and other commons type licensing information. This requires that the MD_Constraints type be extended and a new mcp:MD_Commons element be defined which can substitute for gmd:MD_Constraints. This is shown in the following snippet of XSD:
+
+``` xml
+
+
+
+ Add MD_Commons as an extension of gmd:MD_Constraints_Type
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+For MCP records, the GeoNetwork editor will show a choice of elements from the substitution group for gmd:MD_Constraints when adding 'Resource Constraints' to the metadata document. This will now include mcp:MD_Commons.
+
+
+
+Note that by similar process, two other elements, now deprecated in favour of MD_Commons, were also added as substitutes for MD_Constraints. If it was necessary to constrain the choices shown in this menu, say to remove the deprecated elements and limit the choices to just legal, security and commons, then this can be done by the following piece of XML in the schema-substitutes.xml file:
+
+``` xml
+
+
+
+
+
+```
+
+The result of this change is shown below.
+
+
+
+Once again, a good place to start when building a schema-substitutes.xml file for the MCP is the schema-substitutes.xml file for the iso19139 schema.
+
+#### Adding components to support conversion of metadata records to other schemas
+
+#### Creating the convert directory
+
+If the new GeoNetwork plugin schema is to support on the fly translation of metadata records to other schemas, then the convert directory should be created and populated with appropriate XSLTs.
+
+#### Supporting OAIPMH conversions
+
+The OAIPMH server in GeoNetwork can deliver metadata records from any of the schemas known to GeoNetwork. It can also be configured to deliver schemas not known to GeoNetwork if an XSLT exists to convert a metadata record to that schema. The file `INSTALL_DIR/web/geonetwork/WEB-INF/config-oai-prefixes.xml` describes the schemas (known as prefixes in OAI speak) that can be produced by an XSLT. A simple example of the content of this file is shown below:
+
+``` xml
+
+
+
+```
+
+In the case of the prefix oai_dc shown above, if a schema converter with prefix *oai_dc* exists in the `schema-conversions.xml` file of a GeoNetwork schema, then records that belong to this schema will be transformed and included in OAIPMH requests for the *oai_dc* prefix. See [Creating the schema-conversions.xml file](implementing-a-schema-plugin.md#schema_conversions) for more info.
+
+To add oai_dc support for the MCP, the easiest method is to copy oai_dc.xsl from the convert directory of the iso19139 schema, modify it to cope with the different namespaces and additional elements of the MCP and add it to the `schema-conversions.xml` file for the MCP.
diff --git a/docs/manual/docs/customizing-application/index.md b/docs/manual/docs/customizing-application/index.md
new file mode 100644
index 00000000000..97a5f4d9b26
--- /dev/null
+++ b/docs/manual/docs/customizing-application/index.md
@@ -0,0 +1,15 @@
+# Customizing guide
+
+- [Search application](search-ui/index.md)
+- [Customizing metadata views](creating-custom-view.md)
+- [Customizing editor](editor-ui/creating-custom-editor.md)
+- [Custom editor examples](editor-ui/custom-editor-examples.md)
+- [Building a custom form step by step](editor-ui/tutorial.md)
+- [Theming](changing-layout.md)
+- [Configuring search fields](configuring-search-fields.md)
+- [Configuring faceted search](configuring-faceted-search.md)
+- [Advanced configuration](advanced-configuration.md)
+- [Adding static pages](adding-static-pages.md)
+- [Implementing schema plugins](implementing-a-schema-plugin.md)
+- [Characterset](characterset.md)
+- [Miscellaneous](misc.md)
diff --git a/docs/manual/docs/customizing-application/misc.md b/docs/manual/docs/customizing-application/misc.md
new file mode 100644
index 00000000000..b2e93584cfd
--- /dev/null
+++ b/docs/manual/docs/customizing-application/misc.md
@@ -0,0 +1,146 @@
+# Miscellaneous {#customizing-misc}
+
+## Invalid CSRF Token
+
+GeoNetwork has a security filter that prevents CSRF attacks. See more info about this type of attack on . All calls to POST, DELETE and PUT endpoints without the proper token will return an error.
+
+
+
+By default, all AngularJS requests will take care of this token, but all third party APIs and custom user interface calls will have to manually add this token to the request. The token is stored on a cookie called XSRF-TOKEN. This cookie contains a string that has to be added to all requests either by a parameter called "_csrf" or by a header called X-XSRF-TOKEN.
+
+
+
+### Example of CSRF call using curl {#example-csrf-curl}
+
+First, do a call to a POST endpoint to get the session and the csrf
+
+``` bash
+$rm -f /tmp/cookie; curl -c /tmp/cookie http://localhost:8080/geonetwork/srv/eng/info?type=me -X POST ; cat /tmp/cookie
+
+
+
+
+ Error 403 Expected CSRF token not found. Has your session expired?
+
+
HTTP ERROR 403
+
Problem accessing /geonetwork/srv/eng/info. Reason:
+
Expected CSRF token not found. Has your session expired?
Powered by Jetty:// 9.3.9.v20160517
+
+
+
+# Netscape HTTP Cookie File
+# https://curl.haxx.se/docs/http-cookies.html
+# This file was generated by libcurl! Edit at your own risk.
+
+localhost FALSE /geonetwork FALSE 0 XSRF-TOKEN 3825c5f1-49b3-4c62-bc3a-1916d5872d02
+```
+
+Then, using the cookie and the token, you can do whatever you want:
+
+``` bash
+$curl -v -X POST "http://localhost:8080/geonetwork/srv/eng/info?type=me" -H "X-XSRF-TOKEN: 3825c5f1-49b3-4c62-bc3a-1916d5872d02" --user admin:admin -b /tmp/cookie
+* Trying ::1...
+ * TCP_NODELAY set
+ * Connected to localhost (::1) port 8080 (#0)
+ * Server auth using Basic with user 'admin'
+ > POST /geonetwork/srv/eng/info?type=me HTTP/1.1
+ > Host: localhost:8080
+ > Authorization: Basic YWRtaW46YWRtaW4=
+ > User-Agent: curl/7.52.1
+ > Accept: */*
+ > Cookie: XSRF-TOKEN=3825c5f1-49b3-4c62-bc3a-1916d5872d02
+ > X-XSRF-TOKEN: 3825c5f1-49b3-4c62-bc3a-1916d5872d02
+ >
+ < HTTP/1.1 200 OK
+ < Date: Wed, 17 May 2017 08:52:05 GMT
+ * Added cookie JSESSIONID="1na1v7dpu7d7bcsnelvh0vnvn" for domain localhost, path /geonetwork, expire 0
+ < Set-Cookie: JSESSIONID=1na1v7dpu7d7bcsnelvh0vnvn;Path=/geonetwork
+ < Expires: Thu, 01 Jan 1970 00:00:00 GMT
+ * Added cookie serverTime="1495011125647" for domain localhost, path /, expire 0
+ < Set-Cookie: serverTime=1495011125647;Path=/
+ * Added cookie sessionExpiry="1495011125647" for domain localhost, path /, expire 0
+ < Set-Cookie: sessionExpiry=1495011125647;Path=/
+ < Content-Type: application/xml; charset=UTF-8
+ < Pragma: no-cache
+ < Cache-Control: no-cache
+ < Expires: -1
+ < Transfer-Encoding: chunked
+ < Server: Jetty(9.3.9.v20160517)
+ <
+
+
+
+ Administrator
+ admin
+ 1
+ admin
+ admin
+
+
+
+
+
+ /geonetwork
+ srv
+
+
+
+* Curl_http_done: called premature == 0
+
+* Connection #0 to host localhost left intact
+```
+
+## Using the H2 database {#using-h2-database}
+
+!!! info "Important"
+
+ The instructions below should only be used to examine the database for trouble-shooting purposes as it is possible to corrupt it using this method. Always take a backup first before making any changes!
+
+
+If you are using the default embedded H2 database and you need to examine the tables, you can do so using a Graphical UI. Two that have been tested are:
+
+- dbeaver ()
+- h2's own tool ()
+
+The following approach uses the h2 tool.
+
+### Find the Geonetwork database
+
+This is called `gn.h2.db`. The location is dependent on which web server you are using, and where your data directory is. See [Configuring the database](../install-guide/configuring-database.md) for more information. Note that on windows you will need to use a path of the form `driveletter/path/to/gn.h2.db`.
+
+### Using the H2 tool
+
+Download the platform independent zip file from and unblock/extract it. At a command prompt change to the following directory:
+
+`h2/bin`
+
+Note that using the included bat or shell scripts to access the database seem to show errors, so the command prompt approach is recommended.
+
+Make a note of the URL to your database. This will be of the form:
+
+`jdbc:h2:path/to/gn`
+
+Note do not include `.h2.db` at the end of the path.
+
+Type the following command to access the tool:
+
+`java -cp h2*.jar org.h2.tools.shell`
+
+You will be asked for the URL, which you made a note of above. The default credentials are:
+
+- username: www-data
+- password: www-data
+
+You may need to do one or other of the following:
+
+- Shut down GeoNetwork
+- Remove the lock file `gn.lock.db`
+- Give write permissions on `gn.h2.db`
+
+When you have successfully connected you will see a prompt as below, where you can enter SQL commands. These should end with a semicolon.
+
+`sql>`
+
+A useful command reference can be found at
+
+To leave the tool, type `quit` and press enter.
diff --git a/docs/manual/docs/customizing-application/search-ui/configdefault.md b/docs/manual/docs/customizing-application/search-ui/configdefault.md
new file mode 100644
index 00000000000..b7894c7abca
--- /dev/null
+++ b/docs/manual/docs/customizing-application/search-ui/configdefault.md
@@ -0,0 +1,44 @@
+# Change default view configuration {#configdefaultview}
+
+## The Settings
+
+In order to enable developers to specify some configuration settings, we tried as much as possible to use settings instead of hardcoded value in core code.
+
+Those settings are mainly stored in 2 AngularJS `value` objects:
+
+- `gnViewerSettings`
+- `gnSearchSettings`
+
+Those objects are injected via AngularJs `$inject` concept into all core services and directives.
+
+## Viewer settings
+
+The `gnViewSettings` object contains all settings regarding to the map viewer page.
+
+- `defaultContext` : path to the default OWS Context. If not set, the `ol.View` object needs to be defined for your map.
+- `bgLayers` : Array of layers that will be managed by the background layer selector. This value is used only if `defaultContext` is not defined.
+- `servicesUrl` : Config object for predefined WMS and WMTS servers entries.
+
+## Search settings
+
+The `gnSearchSettings` object contains all settings regarding to the main search page.
+
+- `olStyles` : `ol.style.Style` definition for some features in the map (drawn object, measure, metadata extent bounding box etc\...).
+- `viewerMap` : The `ol.Map` object used for the viewer. This map object may be extended if you have set the `defaultContext` setting.
+- `searchMap` : The `ol.Map` object used for the search page.
+- `hitsperpageValues` : An array to specify the possible values for the number of metadata by result page.
+- `sortbyValues` : An array to specify the possible values for the sort by option in the result list page.
+- `resultViewTpls` : The template used to render search result. By default it is a grid.
+- `formatter` : Set options to the metadata view.
+- `linkTypes` : Binding between resources protocol and action in metadata result list (for example open WMS in mapviewer).
+
+## Update this settings
+
+Note that some settings are set in the database (for example the `viewerSettings.mapConfig` object comes from database settings) so you can edit them in [settings admin page](../../administrator-guide/configuring-the-catalog/system-configuration.md).
+
+For others, you can just edit the config file (See `web-ui/src/main/resources/catalog/views/default/config.js`) and change some setting values.
+
+!!! info "Important"
+
+ If you change existing files, you expose yourself to having merge issues on new version upgrades. The best way keeps to create your own view.
+
diff --git a/docs/manual/docs/customizing-application/search-ui/customview.md b/docs/manual/docs/customizing-application/search-ui/customview.md
new file mode 100644
index 00000000000..eae5c2bc7b7
--- /dev/null
+++ b/docs/manual/docs/customizing-application/search-ui/customview.md
@@ -0,0 +1,57 @@
+# Create your own view {#customview}
+
+If you prefer not to edit shared default files, or if you want a really different UI, the best way is to create your own custom view.
+
+## Add a new view
+
+As presented in previous section, you will need to set up several files to load a new UI view.
+
+- create a new folder in `web-ui/src/main/resources/catalog/views/`.
+- add a `templates/index.html` in this folder.
+- add a javascript file loading your main AngularJS module
+- add less files
+
+## Customize your view
+
+Let's say we want to create a custom view name `al`.
+
+- You will need to create a new folder `web-ui/src/main/resources/catalog/views/geoportal`.
+
+- Add a new file `web-ui/src/main/resources/catalog/views/geoportal/templates/index.html` containing
+
+ ``` html
+
Welcome to geoportal
+ ```
+
+- Add a new file `web-ui/src/main/resources/catalog/views/geoportal/search.js` containing
+
+ ``` js
+ (function() {
+
+ goog.provide('gn_search_geoportal');
+ goog.require('gn_search');
+
+ var module = angular.module('gn_search_geoportal', ['gn_search']);
+
+ })();
+ ```
+
+ !!! note
+
+ You must include `gn_search` module.
+
+
+- Add a new file `web-ui/src/main/resources/catalog/geoportal/views/geoportal/less/gn_search_geoportal.less` containing
+
+ ``` css
+ .geoportal {
+ font-size: 36px;
+ font-weight: bold;
+ }
+ ```
+
+## Launch your view
+
+To see your new view, you can launch the ``catalog.search`` service with a new parameter view:
+
+Or, go into admin settings page and set the `system/ui/defaultView` (*User interface configuration -> Choose the user interface to use*) to `geoportal`.
diff --git a/docs/manual/docs/customizing-application/search-ui/enrichview.md b/docs/manual/docs/customizing-application/search-ui/enrichview.md
new file mode 100644
index 00000000000..ecc966e0f76
--- /dev/null
+++ b/docs/manual/docs/customizing-application/search-ui/enrichview.md
@@ -0,0 +1,110 @@
+# Enrich your custom view {#enrichsearchview}
+
+Now we created our structure with basic content, we want to create a real catalog page.
+
+For that, you can include default view content, or build your own application on top of core GeoNetwork components.
+
+## GeoNetwork components
+
+UI design is based on shared widgets, logic and components. In AngularJS terms, we talk about `es` and `es`.
+
+All components are stored in the folder [components](https://github.com/geonetwork/core-geonetwork/tree/develop/web-ui/src/main/resources/catalog/components)
+
+### Main page components
+
+Main search input
+
+``` html
+
+```
+
+Facets panel
+
+``` html
+
+
+```
+
+Alert info manager
+
+``` html
+
+```
+
+Result list
+
+``` html
+
+```
+
+Geographic search
+
+``` html
+
+```
+
+### Main map components
+
+- wmsimport
+- map search input
+- draw panel
+- measure panel
+- print panel
+- layer manager
+- background layer selector
+- etc\...
+
+So you can reuse all these components in your templates to build the view you want.
+
+## Styles
+
+!!! info "Important"
+
+ You should import default style and add custom CSS rules instead of creating your own from scratch.
+
+
+In `gn_search_geoportal.less`, import default less files.
+
+1. Import common search styles (if you start a new view from scratch)
+
+ ``` css
+ @import "../../../style/gn_search.less";
+ ```
+
+2. Import default view search styles (if you base your view on top of default one)
+
+ ``` css
+ @import "../../default/less/gn_search_default.less";
+ ```
+
+3. Then, in your less file, you can start adding new rules
+
+ ``` none
+ .gn-resultview .list-group-item {
+ background-color: red;
+ &:hover {
+ background-color: orange;
+ }
+ }
+ ```
diff --git a/docs/manual/docs/customizing-application/search-ui/index.md b/docs/manual/docs/customizing-application/search-ui/index.md
new file mode 100644
index 00000000000..4f33b9697aa
--- /dev/null
+++ b/docs/manual/docs/customizing-application/search-ui/index.md
@@ -0,0 +1,7 @@
+# Search application {#customizing-searchui}
+
+- [Create your own view](loadview.md)
+- [Change default view configuration](configdefault.md)
+- [Create your own view](customview.md)
+- [Enrich your custom view](enrichview.md)
+- [Wro4j resource management](wro4jdependencies.md)
diff --git a/docs/manual/docs/customizing-application/search-ui/loadview.md b/docs/manual/docs/customizing-application/search-ui/loadview.md
new file mode 100644
index 00000000000..eb1400920a9
--- /dev/null
+++ b/docs/manual/docs/customizing-application/search-ui/loadview.md
@@ -0,0 +1,44 @@
+# Create your own view {#loadsearchpage}
+
+The search page is served by the ``catalog.search`` service.
+
+This service ends up into `base-layout-cssjs-loader.xsl` (See `web/src/main/webapp/xslt/base-layout-cssjs-loader.xsl`) which contains the logic to load the right html page.
+
+## The view parameter
+
+You can pass a parameter `view` to the ``catalog.search`` url to point on a custom view.
+
+If no parameter is specified, the view value will be taken from the `system/ui/defaultView` settings, and if no setting is set, is value will be `default`.
+
+It will be stored in `$searchView` XSLT variable.
+
+## Loading the view
+
+The view is loaded from (See `web/src/main/webapp/xslt/ui-search/search.xsl`):
+
+``` xml
+
+```
+
+The view main template is loaded through the AngularJS directive `ng-include` and will point on the path `/web-ui/src/main/resources/catalog/views/${view}/templates/index.html`.
+
+For the default view, you can find this template in `web-ui/src/main/resources/catalog/views/default/templates/index.html`.
+
+## Loading the javascript
+
+To init AngularJS main module you have to use the directive ``ng-app`` and point on your main AngularJS module.
+
+``` xml
+
+```
+
+In the case of the search page (``catalog.search``), the `$angularApp` variable equals `gn_search`. And for the `lt` view the `$angularModule` equals `gn_search_default`.
+
+So, by default, the main AngularJS module is loaded here from `gn_search_default` module declared here (See `web-ui/src/main/resources/catalog/views/default/module.js`.
+
+From here, you can build your AngularJS module dependency tree and load your application.
+
+## CSS files
+
+In the same logic, the CSS that is loaded into the page is `gn_search_default.less`.
diff --git a/docs/manual/docs/customizing-application/search-ui/wro4jdependencies.md b/docs/manual/docs/customizing-application/search-ui/wro4jdependencies.md
new file mode 100644
index 00000000000..6b33e3b817e
--- /dev/null
+++ b/docs/manual/docs/customizing-application/search-ui/wro4jdependencies.md
@@ -0,0 +1,43 @@
+# Wro4j resource management {#wro4jdependencies}
+
+Wro4j lib is used to manage resources of the web applications. Mostly, it
+
+- builds dependency tree between js source files
+- minifies javascript
+- compiles less files
+- manages live update in development mode
+- manages caching in production mode
+
+## Dependency Tree
+
+When the AngularJs entry module is `gn_search_geoportal`, the wro4j entry point is the key `gn_search_geoportal` as well, that means that it is the file that declares `goog.provide('gn_search_geoportal')`.
+
+That is why you need to be sure there is a good mapping between AngularJs module dependencies and wro4j dependency tree.
+
+For example, when you have this for wro4j:
+
+``` js
+goog.provide('gn_search_default');
+
+goog.require('gn_search');
+goog.require('gn_search_default_config');
+goog.require('gn_related_directive');
+```
+
+You need to be sure you create your AngularJs module with same dependency injection:
+
+``` js
+var module = angular.module('gn_search_default',
+ [
+ 'gn_search',
+ 'gn_search_default_config',
+ 'gn_related_directive'
+ ]);
+```
+
+!!! info "Important"
+
+ Whenever you change a `goog.require` or `goog.provide` statements, you need to relaunch wro4j dependency tree creation. This can be done with Jetty or Tomcat restart.
+
+
+Following this principles, you are now free to add new modules, components, directives or services to your application.
diff --git a/docs/manual/docs/devel/docs/index.md b/docs/manual/docs/devel/docs/index.md
new file mode 100644
index 00000000000..aefbe8c54b4
--- /dev/null
+++ b/docs/manual/docs/devel/docs/index.md
@@ -0,0 +1,3 @@
+# Documentation Guide
+
+Working with GeoNetwork documentation, markdown formatting, and writing style guide.
diff --git a/docs/manual/docs/devel/docs/markdown/files/example.xsd b/docs/manual/docs/devel/docs/markdown/files/example.xsd
new file mode 100644
index 00000000000..e69de29bb2d
diff --git a/docs/manual/docs/devel/docs/markdown/index.fr.md b/docs/manual/docs/devel/docs/markdown/index.fr.md
new file mode 100644
index 00000000000..4d9e535b9f2
--- /dev/null
+++ b/docs/manual/docs/devel/docs/markdown/index.fr.md
@@ -0,0 +1,304 @@
+# Documentation
+
+## Guide de rédaction {#writing-guide}
+
+GeoCat a fourni un [guide d\'écriture](https://geocat.github.io/geocat-themes/) pour la documentation sphinx. Bien que les conventions d\'écriture doivent être respectées, l\'adaptation des directives sphinx au formatage markdown nécessite un certain travail.
+
+Lors de la conversion en markdown, nous pouvons nous concentrer uniquement sur l\'aspect visuel, en convertissant de nombreuses directives sphinx en leur équivalent visuel le plus proche :
+
+| Markdown | Directive Sphinx |
+|--------------------------|----------------------------------------|
+| `**strong**` | gui-label, menuselection |
+| `` `monospace` `` | saisie de texte, sélection d\'éléments |
+| `*emphasis*` | chiffre (légende) |
+| `***strong-emphasis***` | commande |
+| `` `monospace-strong` `` | fichier |
+
+Veuillez noter que les conventions ci-dessus sont importantes pour la cohérence et sont requises par le processus de traduction.
+
+### Composants de l\'interface utilisateur {#user-interface-components}
+
+Utilisez `**strong**` pour nommer les composants de l\'interface utilisateur à des fins d\'interaction (appuyer pour les boutons, cliquer pour les liens).
+
+Avant-première :
+
+> Accédez à la page **Couches de données** et cliquez sur **Ajouter** pour créer une nouvelle couche.
+
+Markdown :
+
+```markdown
+Navigate to **Data Layers** page,
+and press **Add** to create a new layer.
+```
+
+Texte riche et structuré :
+
+```rst
+Navigate to :menuselection:`Data Layers` page,
+and press :guilabel:`Add`` to create a new layer.
+```
+
+### Données de l\'utilisateur {#user-input}
+
+Utiliser `` `item` `` pour les données fournies par l\'utilisateur, ou les éléments d\'une liste ou d\'un arbre: :
+
+Avant-première :
+
+> Sélectionnez `Basemap` couche.
+
+Markdown :
+
+```markdown
+Select `Basemap` layer.
+```
+
+Texte riche et structuré :
+
+```
+Select ``Basemap`` layer.
+```
+
+Utiliser `` `text` `` pour la saisie du texte fourni par l\'utilisateur :
+
+Avant-première :
+
+> Utilisez le champ de *recherche pour* saisir `Ocean*`.
+
+Markdown :
+
+```markdown
+Use the *Search* field enter `Ocean*`.
+```
+
+Texte riche et structuré :
+
+```
+Use the :guilabel:`Serach` field to enter :kbd:`Ocean*`.
+```
+
+Utilisez `++key++` pour les touches du clavier.
+
+Avant-première :
+
+> Appuyez sur ++Control-s++ pour effectuer une recherche.
+
+Markdown :
+
+```markdown
+Press ++control+s++ to search.
+```
+
+Texte riche et structuré :
+
+```
+Press :key:``Control-s`` to search.
+```
+
+Utilisez une liste de définitions pour documenter la saisie des données. Les noms des champs utilisent strong car ils nomment un élément de l\'interface utilisateur. Les valeurs des champs à saisir utilisent monspace car il s\'agit d\'une entrée utilisateur à saisir.
+
+Avant-première :
+
+1. Pour vous connecter en tant qu\'administrateur du GeoServer en utilisant le mot de passe par défaut :
+
+ **Utilisateur**
+
+ : `admin`
+
+ **Mot de passe**
+
+ : `geoserver`
+
+ **Souvenez-vous de moi**
+
+ : Non vérifié
+
+ **Connexion** presse.
+
+Markdown : listes de définitions
+
+```markdown
+1. To login as the GeoServer administrator using the default password:
+
+ **User**
+
+ : `admin`
+
+ **Password**
+
+ : `geoserver`
+
+ **Remeber me**
+
+ : Unchecked
+
+ Press **Login**.
+```
+
+Texte structuré riche : liste-tableau
+
+```
+#. To login as the GeoServer administrator using the default password:
+
+ .. list-table::
+ :widths: 30 70
+ :width: 100%
+ :stub-columns: 1
+
+ * - User:
+ - :kbd:`admin`
+ * - Password:
+ - :kbd:`geoserver`
+ * - Remember me
+ - Unchecked
+
+ Press :guilabel:`Login`.
+```
+
+### Applications, commandes et outils {#applications-commands-and-tools}
+
+Utilisez les **caractères gras** et *italiques* pour les noms propres d\'applications, de commandes, d\'outils et de produits.
+
+Avant-première :
+
+Lancez ***pgAdmin*** et connectez-vous à la base de données `tutorial`.
+
+Markdown :
+
+```markdown
+Launch ***pgAdmin*** and connect to the databsae `tutorial`.
+```
+
+Texte riche et structuré :
+
+```
+Launch :command:`pgAdmin` and connect to the ``tutorial`` database.
+```
+
+### Fichiers {#files}
+
+Utilisez le **gras** **monospace** pour les fichiers et les dossiers :
+
+Aperçu Voir le fichier de configuration **`WEB-INF/config-security/config-security-ldap.xml`** pour plus de détails
+
+Markdown :
+
+```markdown
+See configuration file
+**`WEB-INF/config-security/config-security-ldap.xml`**
+for details
+```
+
+Texte riche et structuré :
+
+```
+See configuration
+file :file:`WEB-INF/config-security/config-security-ldap.xml`
+for details
+```
+
+### Liens et références {#links-and-references}
+
+Types de liens spécifiques :
+
+Référence à une autre section du document (une certaine attention est requise pour faire référence à un titre spécifique) :
+
+Les éditeurs ont la possibilité de [gérer les](index.md) enregistrements.
+
+```
+Editors have option to :ref:`manage ` records.
+Editors have option to [manage](../editor/publish/index.md#publish-records) records.
+```
+
+Téléchargement de fichiers d\'échantillons :
+
+Exemple :
+
+Télécharger le schéma [**`example.xsd`**](files/example.xsd).
+
+```
+Download schema :download:`example.xsd `.
+Download schema [**`example.xsd`**](files/example.xsd).
+```
+
+### Icônes, images et figures {#icons-images-and-figures}
+
+Material for markdown dispose d\'une prise en charge étendue des icônes. Pour la plupart des éléments de l\'interface utilisateur, il est possible d\'utiliser directement l\'icône appropriée dans Markdown :
+
+```markdown
+1. Press the *Validate :fontawesome-solid-check:* button at the top of the page.
+```
+
+Ajoutez les icônes du cusotm à **`overrides/.icons/geocat`**:
+
+```markdown
+Thank you from the GeoCat team!
+:geocat-logo:
+```
+
+Les figures sont traitées par convention, en ajoutant un texte en relief après chaque image et en faisant confiance aux règles CSS pour assurer une présentation cohérente :
+
+```markdown
+
+*Value is required for Begin Date*
+```
+
+Les images brutes ne sont pas utilisées très souvent :
+
+```markdown
+
+```
+
+### Tableaux {#tables}
+
+La documentation n\'utilise que des tables de pipes (supportées par ***mkdocs*** et ***pandoc***) :
+
+En tête / en queue `|`:
+
+| Première tête | Deuxième en-tête | Troisième en-tête |
+|--------------------|--------------------|--------------------|
+| Cellule de contenu | Cellule de contenu | Cellule de contenu |
+| Cellule de contenu | Cellule de contenu | Cellule de contenu |
+
+Alignement des colonnes à l\'aide de `:`
+
+| Première tête | Deuxième en-tête | Troisième en-tête |
+|:--------------|:----------------:|------------------:|
+| Gauche | Centre | Droit |
+| Gauche | Centre | Droit |
+
+## Traduction {#translation}
+
+La traduction utilise ***pandoc*** pour convertir en `html` pour la conversion par ***Deepl***.
+
+Des extensions spécifiques de ***pandoc*** sont utilisées pour s\'adapter aux capacités de ***mkdocs***.
+
+| extension mkdocs | extension pandoc |
+|------------------|------------------|
+| tables | tables_pipe |
+
+D\'autres différences dans le markdown nécessitent un traitement avant/après des fichiers markdown et html. Ces étapes sont automatisées dans le script python ***translate*** (consultez les commentaires pour plus de détails).
+
+Pour traduire une variable environnementale en clé d\'authentification Deepl :
+
+```
+export DEEPL_AUTH="xxxxxxxx-xxx-...-xxxxx:fx"
+```
+
+Pour tester chaque étape individuellement :
+
+```
+python3 -m translate html docs/devel/docs/docs.md
+python3 -m translate document target/translate/devel/docs/docs.html target/translate/devel/docs/docs.fr.html
+python3 -m translate markdown target/translate/devel/docs/docs.fr.html
+
+cp target/translate/devel/docs/docs.fr.md docs/devel/docs/docs.fr.md
+```
+
+Pour tester les formats markdown / html uniquement :
+
+```
+python3 -m translate convert docs/devel/docs/docs.md
+python3 -m translate markdown target/translate/devel/docs/docs.html
+
+diff docs/devel/docs/docs.md target/translate/devel/docs/docs.md
+```
diff --git a/docs/manual/docs/devel/docs/markdown/index.md b/docs/manual/docs/devel/docs/markdown/index.md
new file mode 100644
index 00000000000..f5f815bc228
--- /dev/null
+++ b/docs/manual/docs/devel/docs/markdown/index.md
@@ -0,0 +1,314 @@
+# Markdown
+
+These markdown conventions are carefully constructed for consistent representation of user interface elements, files, data and field input.
+
+
+| Markdown | Directive |
+|--------------------------|-----------------------------|
+| `**strong**` | gui label, menu selection |
+| `` `monospace` `` | text input, item selection |
+| `*emphasis*` | figure (caption) |
+| `***strong-emphasis***` | application, command |
+| **`monospace-strong`** | file |
+
+!!! note
+
+ The above conventions are important for consistency and are required by the translation process.
+
+ As an example we do not wish to translate a search terms, so these are represented as monospace text input.
+
+## User interface components
+
+Use `**strong**` to name user interface components for interaction (press for buttons, click for link).
+
+Preview:
+
+> Navigate to **Data --> Layers** page, and press **Add** to create a new layer.
+
+Markdown:
+
+```markdown
+Navigate to **Data --> Layers** page,
+and press **Add** to create a new layer.
+```
+
+Rich structured text:
+
+```rst
+Navigate to :menuselection:`Data Layers` page,
+and press :guilabel:`Add`` to create a new layer.
+```
+
+## User input
+
+Use `` `item` `` for user supplied input, or item in a list or tree::
+
+Preview:
+
+> Select `Basemap` layer.
+
+Markdown:
+
+```markdown
+Select `Basemap` layer.
+```
+
+Rich structured text:
+
+```
+Select ``Basemap`` layer.
+```
+
+Use `` `text` `` for user supplied text input:
+
+Preview:
+
+> Use the *Search* field enter `Ocean*`.
+
+Markdown:
+
+```markdown
+Use the *Search* field enter `Ocean*`.
+```
+
+Rich structured text:
+
+```
+Use the :guilabel:`Serach` field to enter :kbd:`Ocean*`.
+```
+
+Use `++key++` for keyboard keys.
+
+Preview:
+
+> Press ++control+s++ to search.
+
+Markdown:
+
+```markdown
+Press ++control+s++ to search.
+```
+
+Rich structured text:
+
+```
+Press :key:``Control-s`` to search.
+```
+
+Use definition list to document data entry. The field names use strong as they name a user interface element. Field values to input uses monspace as user input to type in.
+
+Preview:
+
+1. To login as the GeoServer administrator using the default password:
+
+ **User**
+
+ : `admin`
+
+ **Password**
+
+ : `geoserver`
+
+ **Remeber me**
+
+ : Unchecked
+
+ Press **Login**.
+
+Markdown: definition lists
+
+```markdown
+1. To login as the GeoServer administrator using the default password:
+
+ **User**
+
+ : `admin`
+
+ **Password**
+
+ : `geoserver`
+
+ **Remeber me**
+
+ : Unchecked
+
+ Press **Login**.
+```
+
+Rich structured text: list-table
+
+```
+#. To login as the GeoServer administrator using the default password:
+
+ .. list-table::
+ :widths: 30 70
+ :width: 100%
+ :stub-columns: 1
+
+ * - User:
+ - :kbd:`admin`
+ * - Password:
+ - :kbd:`geoserver`
+ * - Remember me
+ - Unchecked
+
+ Press :guilabel:`Login`.
+```
+
+## Applications, commands and tools
+
+Use **bold** and *italics* for proper names of applications, commands, tools, and products.
+
+Preview:
+
+Launch ***pgAdmin*** and connect to the databsae `tutorial`.
+
+Markdown:
+
+```markdown
+Launch ***pgAdmin*** and connect to the databsae `tutorial`.
+```
+
+Rich structured text:
+
+```
+Launch :command:`pgAdmin` and connect to the ``tutorial`` database.
+```
+
+## Files
+
+Use **bold** **monospace** for files and folders:
+
+Preview See configuration file **`WEB-INF/config-security/config-security-ldap.xml`** for details
+
+Markdown:
+
+```markdown
+See configuration file
+**`WEB-INF/config-security/config-security-ldap.xml`**
+for details
+```
+
+Rich structured text:
+
+```
+See configuration
+file :file:`WEB-INF/config-security/config-security-ldap.xml`
+for details
+```
+
+## Links and references
+
+Specific kinds of links:
+
+Reference to other section of the document (some care is required to reference a specific heading):
+
+Editors have option to [manage](index.md) records.
+
+```
+Editors have option to :ref:`manage ` records.
+Editors have option to [manage](../editor/publish/index.md#publish-records) records.
+```
+
+Download of sample files:
+
+Example:
+
+> Download schema [**`example.xsd`**](files/example.xsd).
+
+```
+Download schema :download:`example.xsd `.
+Download schema [**`example.xsd`**](files/example.xsd).
+```
+
+## Icons, Images and Figures
+
+Material for markdown has extensive icon support, for most user interface elements we can directly make use of the appropriate icon in Markdown:
+
+```markdown
+1. Press the *Validate :fontawesome-solid-check:* button at the top of the page.
+```
+
+Add cusotm icons to **`overrides/.icons/geocat`**:
+
+```markdown
+Thank you from the GeoCat team!
+:geocat-logo:
+```
+
+Figures are handled by convention, adding emphasized text after each image, and trust CSS rules to provide a consistent presentation:
+
+```markdown
+
+*Value is required for Begin Date*
+```
+
+Raw images are not used very often:
+
+```markdown
+
+```
+
+## Tables
+
+Documentation uses pipe-tables only (supported by both ***mkdocs*** and ***pandoc***):
+
+Leading / tailing `|`:
+
+| First Header | Second Header | Third Header |
+|--------------|---------------|--------------|
+| Content Cell | Content Cell | Content Cell |
+| Content Cell | Content Cell | Content Cell |
+
+Column alignment using `:`
+
+| First Header | Second Header | Third Header |
+|:-------------|:-------------:|-------------:|
+| Left | Center | Right |
+| Left | Center | Right |
+
+## Inline
+
+Here is a snippet to include markdown files inline, requires opening tag ``{%`` and closing tag ``%}``:
+
+``` markdown
+{ %
+ include-markdown './version-4.2.4.md'
+ heading-offset=3
+% }
+```
+
+Use a glob pattern to inline many files, shown with option to adjusting header level:
+
+``` markdown
+{ %
+ include-markdown './version-4.0.*.md'
+ exclude = './version-4.2.4.md'
+ heading-offset = 3
+% }
+```
+
+For including markdown files inline, we have to exclude them from ``mkdocs.yml`` warnings:
+
+``` yaml
+plugins:
+ - exclude:
+ glob:
+ - 'overview/change-log/version*'
+```
+
+Use ``include`` to include normal files, shown with start and end to capture a snippet, and dedent for appearance:
+
+``` markdown
+{ %
+ include 'record.xml'
+ dedent="true"
+ start=""
+ end=""
+% }
+```
+
+Reference:
+
+* [mkdocs-include-markdown-plugin](https://pypi.org/project/mkdocs-include-markdown-plugin/)
+* [mkdocs-exclude](https://pypi.org/project/mkdocs-exclude/)
diff --git a/docs/manual/docs/devel/docs/style/index.md b/docs/manual/docs/devel/docs/style/index.md
new file mode 100644
index 00000000000..53f9b5ee273
--- /dev/null
+++ b/docs/manual/docs/devel/docs/style/index.md
@@ -0,0 +1,195 @@
+# Style Guide
+
+Writing style guide to help creating consistent documentation for GeoNetwork.
+
+This style guide is useful as a reference when reviewing pull-requests for documentation.
+
+## Content conventions
+
+### Be concise
+
+Documentation should be concise and not just a brain dump. Reference material should contain short pages and be easy to refer to without having to scroll through a large volume of text. Tutorials can be longer, depending on scope. If the point of the document is to share your thoughts and insights, it belongs in a blog post. This documentation is a manual, not a wiki.
+
+### Avoid marketing
+
+If the point of the document is to showcase a new feature it does not belong in the documentation. Write an article or a blog post about it. If it is necessary to point out a technical benefit of a feature then do so from a technical standpoint.
+
+Bad
+
+> Sub-Portals are a great way to provide a team with their own catalogue!
+
+Good
+
+> Sub-Portals define a distinct catalogue for use.
+
+### Be professional
+
+Avoid the use of slang or other "colorful" language. The point of a technical document is to be informative, not to keep the reader amused. Avoiding slang helps keep the document accessible to as large an audience as possible.
+
+
+Bad
+
+> 2. Next, fire up whatever tool you use to browse the web and point it in the direction of ...
+
+Good
+
+> 2. Next, start your web browser and navigate to ...
+
+### Use direct commands
+
+When providing step-by-step instructions, number steps and use direct commands or requests. Avoid the use of "we" and "let's".
+
+Bad
+
+> Now let's select a record by ...
+
+Good
+
+> 1. Select a record by ...
+
+
+## Naming conventions
+
+Reference:
+
+* [Wikipedia naming conventions](https://en.wikipedia.org/wiki/Wikipedia:Naming_conventions)
+
+### Capitalization of page names
+
+Each word in the page name should be capitalized except for articles (such as "the", "a", "an") and conjunctions (such as "and", "but", "or"). A page name should never start with an article.
+
+Bad
+
+> Adding a wms or wfs service
+
+Good
+
+> Adding a WMS or WFS service
+
+Bad
+
+> The Harvester Tutorial
+
+Good
+
+> Harvester Tutorial
+
+### Capitalization of section names
+
+Do not capitalize second and subsequent words unless the title is almost always capitalized in English (like proper names). Thus, capitalize John Wayne and Art Nouveau, but not Video Games.
+
+Bad
+
+> Creating a New Record
+
+Good
+
+> Creating a new record
+
+### Verb usage
+
+It is recommended that the gerund (the -ing form in English) be used unless there is a more common noun form. For example, an article on swimming is better than one on swim.
+
+Bad
+
+> Create a new datastore
+
+Good
+
+> Creating a new datastore
+
+### Avoid plurals
+
+Create page titles that are in the singular. Exceptions to this are nouns that are always plural (scissors, trousers), a small class that requires a plural (polar coordinates, Bantu languages, The Beatles).
+
+Bad
+
+> templates tutorial
+
+Good
+
+> Template tutorial
+
+Formatting
+----------
+
+### Code and command line
+
+Any code or command line snippets should be formatted as code:
+
+``` json
+{
+ code: 'This is a code block.'
+}
+```
+
+When lines are longer than 80 characters, extend multiple lines in a format appropriate for the language in use.
+If possible, snippets should be functional when pasted directly into the appropriate target.
+
+For example, XML make no distinction between a single space and multiple spaces, so the following snippets are fine:
+
+
+``` xml
+
+```
+
+For shell scripts, new lines can be escaped with a backslash character (`\`).
+
+```bash
+mvn clean install \
+ -DskipTests
+```
+```
+BUIILD SUCCESS
+```
+
+It is helpful to seperate out input from output, so that the command can be easily copied as shown above.
+
+## Terminology conventions
+
+This section concerns the language or terminology used for each section of our documentation.
+
+### Online Help
+
+The readers for online-help are visitors to a website, focused on finding information.
+
+The online help is used by a wide range of organisations and is intended to be read by members of the public.
+
+With this in mind please avoid using "metadata expert" language when writing online help. Indeed many visitors may not have a geospatial background and will be pleased to find a map.
+
+* Try and avoid using the word `catalogue`, as this is really just a `web site` or `site` for visitors
+* Try and avoid using the word `metadata`, as really this is a site providing a `list` of `information`
+* Try and avoid using the word `metadata`, if you really need to use `record` (as is done in our advanced search screen)
+* Avoid mentioning `schema` or `iso19139` as this is expert knowledge, at best `standard` or `national standard` may be appropriate.
+* Avoid mentioning `GeoNetwork`
+
+Examples:
+
+* Visitors seek `information`, and are shown `records` about that information
+* Visitors may `search` for `information`
+* Visitors may `browse` or `explore` the `list` of `records`
+
+### User-Guide
+
+The readers of the user-gude are operators responsible for the editing, review and publication of metadata records.
+
+In addition administrators are responsible for the publication and security (including user management). This also incudes defining sub-portals to make it easier for teams to manage and publish distinct content.
+
+Preferred terminology:
+
+- `Catalog Home Page`
+- `GeoNetwork` (check capitalisation please)
+- `Metadata Catalog`
+- `Sub-Portal`
+- `Record` (or `Metadata Record` please)
+
+ The word `Metadata` can both be singular (referencing a `metadata record` and plural (referencing the topic of metadata). In the same fashion `data` is plural while `datum` is singular -- but we do not have `metadatum`!
+
+### Maintainer-Guide
+
+The readers of the maintainer-guide are system administrators responsible for the installation, integration and update of the GeoNetwork application as a whole.
+
+Example:
+
+* Rather than re-explain topics like Elasticsearch optimization, provide GeoNetwork guidance with the expectation it will be used as provided. Link to references for those wishing to know more.
diff --git a/docs/manual/docs/devel/docs/translation/index.md b/docs/manual/docs/devel/docs/translation/index.md
new file mode 100644
index 00000000000..30b9c673dde
--- /dev/null
+++ b/docs/manual/docs/devel/docs/translation/index.md
@@ -0,0 +1,71 @@
+# Translation
+
+The ``mkdocs-static-i18n`` plugin is setup based on suffix, with **`index.md`** is the default English, and **``index.fr.md``** used for French:
+
+``` text
+| index.md
+| index.fr.md
++ img/
+ | figure.png
+ + figure.fr.png
+```
+
+The mkdocs-material-theme language chooser is configured by this plugin allowing the selection of language at runtime.
+
+Reference:
+
+* [mkdocs-static-i18n](https://ultrabug.github.io/mkdocs-static-i18n/)
+
+## Deepl Translation
+
+Translation uses ***pandoc*** to convert to `html` for conversion by ***Deepl***.
+
+Specific ***pandoc*** extensions are used to match the capabilities of ***mkdocs***:
+
+| markdown extension | pandoc extension |
+|----------------------|------------------------|
+| tables | pipe_tables |
+| pymdownx.keys | |
+| pymdownx.superfences | backtick_code_blocks |
+| admonition | fenced_divs |
+
+The differences differences in markdown requires pre/post processing of markdown and html files. These steps are automated in the ***translate*** python script (check comments for details). Supporting additional ***mkdocs*** features requires updating this script.
+
+1. Install [mkdocs_translate](https://github.com/jodygarnett/translate) python script:
+
+ ```
+ pip3 install git+https://github.com/jodygarnett/translate.git
+ ```
+
+2. To translate provide environmental variable with Deepl authentication key:
+
+ ```
+ cd core-geonetwork/docs
+ mkdir target
+ export DEEPL_AUTH="xxxxxxxx-xxx-...-xxxxx:fx"
+ ```
+
+3. And translate a file:
+
+ ``` bash
+ mkdocs_translate french manual/docs/contributing/style-guide.md
+ ```
+
+4. To test each stage individually:
+
+ ```
+ mkdocs_translate internal-html manual/docs/contributing/style-guide.md
+ mkdocs_translate internal-document target/contributing/style-guide.html target/contributing/style-guide.fr.html
+ mkdocs_translate internal-markdown target/contributing/style-guide.fr.html
+
+ cp target/contributing/style-guide.fr.md manual/docs/contributing/style-guide.fr.md
+ ```
+
+5. To test markdown / html round trip:
+
+ ```
+ mkdocs_translate convert manual/docs/contributing/style-guide.md
+ mkdocs_translate markdown target/contributing/style-guide.html
+
+ diff manual/docs/contributing/style-guide.md target/contributing/style-guide.md
+ ```
diff --git a/docs/manual/docs/devel/index.md b/docs/manual/docs/devel/index.md
new file mode 100644
index 00000000000..a02bf97c081
--- /dev/null
+++ b/docs/manual/docs/devel/index.md
@@ -0,0 +1,3 @@
+# Development Guide
+
+Working with GeoNetwork documentation, customization, and development.
diff --git a/docs/manual/docs/help/home/img/browse.png b/docs/manual/docs/help/home/img/browse.png
new file mode 100644
index 00000000000..5721db7ddb7
Binary files /dev/null and b/docs/manual/docs/help/home/img/browse.png differ
diff --git a/docs/manual/docs/help/home/img/browse_large_list.png b/docs/manual/docs/help/home/img/browse_large_list.png
new file mode 100644
index 00000000000..0e80321da75
Binary files /dev/null and b/docs/manual/docs/help/home/img/browse_large_list.png differ
diff --git a/docs/manual/docs/help/home/img/browse_latest.png b/docs/manual/docs/help/home/img/browse_latest.png
new file mode 100644
index 00000000000..597d44d467b
Binary files /dev/null and b/docs/manual/docs/help/home/img/browse_latest.png differ
diff --git a/docs/manual/docs/help/home/img/search.png b/docs/manual/docs/help/home/img/search.png
new file mode 100644
index 00000000000..d1e3d4ccf92
Binary files /dev/null and b/docs/manual/docs/help/home/img/search.png differ
diff --git a/docs/manual/docs/help/home/img/search_partial.png b/docs/manual/docs/help/home/img/search_partial.png
new file mode 100644
index 00000000000..912675174e0
Binary files /dev/null and b/docs/manual/docs/help/home/img/search_partial.png differ
diff --git a/docs/manual/docs/help/home/img/search_results.png b/docs/manual/docs/help/home/img/search_results.png
new file mode 100644
index 00000000000..a4a109bc5dc
Binary files /dev/null and b/docs/manual/docs/help/home/img/search_results.png differ
diff --git a/docs/manual/docs/help/home/img/search_wildcard.png b/docs/manual/docs/help/home/img/search_wildcard.png
new file mode 100644
index 00000000000..24c540389a2
Binary files /dev/null and b/docs/manual/docs/help/home/img/search_wildcard.png differ
diff --git a/docs/manual/docs/help/home/index.md b/docs/manual/docs/help/home/index.md
new file mode 100644
index 00000000000..865c6000722
--- /dev/null
+++ b/docs/manual/docs/help/home/index.md
@@ -0,0 +1,105 @@
+---
+tags:
+- Search
+- Catalog
+- Topics
+- Grid
+- List
+- Home
+hide:
+ - tags
+---
+
+# Home
+
+The Catalogue page is used to browse records, and has provides a quick search field.
+
+## Search Catalogue
+
+1. Enter the desired keywords and search terms into the **Search** field
+ at the top of the page and press the **:fontawesome-solid-magnifying-glass: Search** button
+ (or use the ++enter++ key), to list search results.
+
+
+ 
+
+ *Search field*
+
+2. Search for complete words.
+
+ Use **Search** field to enter: `Ocean`
+
+ Results are shown on the **Search** tab.
+
+
+ 
+
+ *Search results for Ocean*
+
+3. Search using the wildcard `*` to match the start or end of word.
+ Keep in mind the entire record contents is searched, not only the
+ titles and description.
+
+ Use **Search** field to enter: `Area*`
+
+
+ 
+
+ *Search for start of a word*
+
+4. The wildcard `*` can also be used multiple times to match part of a word.
+
+ Use **Search** field to enter: `*brass*`
+
+
+ 
+
+ *Search for part of a word*
+
+5. Search results are shown on the **Seach** tab, which allows filtering and exploring of records.
+
+## Browse Catalogue
+
+1. Navigate to **My GeoNetwork catalogue** to browse records.
+ In a production system the catalogue name and logo will
+ match your organisation or project team.
+
+2. The catalog page can be explored using the quick lists of:
+
+ - **Latest news**: recently updated records
+ - **Most popular**: frequently used records
+ - **Comments**: records with new comments and discussion
+
+
+ 
+
+ *Latest news*
+
+3. Records are displayed as
+ - :fontawesome-solid-table-cells-large: block list
+ - :fontawesome-solid-bars: large list
+ - :fontawesome-solid-align-justify: small list
+
+ using the toggle on the right.
+
+ Click on any of the listed records to view.
+
+
+ 
+
+ *Large list display of records*
+
+4. The catalog page provides a number of quick searches to browse
+ catalog contents:
+
+ - Use **Browse by Topics** to
+ explore records based on subject matter.
+ - Use **Browse by Resources** to
+ explore different kinds of content.
+
+ Each option lists "search facets" (shown as small bubbles), click
+ on a "search facet" such as `Dataset` to explore.
+
+ 
+ *Browse metadata catalogue*
+
diff --git a/docs/manual/docs/help/index.md b/docs/manual/docs/help/index.md
new file mode 100644
index 00000000000..8193a33d53e
--- /dev/null
+++ b/docs/manual/docs/help/index.md
@@ -0,0 +1,15 @@
+# Help
+
+This catalogue lists records of available datasets.
+
+## GeoNetwork opensource
+
+The catalogue uses ***GeoNetwork*** technology for listing, searching and reviewing records.
+
+GeoNetwork is a catalog application to manage spatially referenced resources. It provides powerful metadata editing and search functions as well as an interactive web map viewer. GeoNetwork is widely used as the foundation of Spatial Data Infrastructures worldwide.
+
+!!! info "Reference"
+
+ [GeoNetwork Manual](https://docs.geonetwork-opensource.org/4.4)
+
+ [GeoNetwork opensource](https://geonetwork-opensource.org)
diff --git a/docs/manual/docs/help/map/img/add_search.png b/docs/manual/docs/help/map/img/add_search.png
new file mode 100644
index 00000000000..f1b1e4976ac
Binary files /dev/null and b/docs/manual/docs/help/map/img/add_search.png differ
diff --git a/docs/manual/docs/help/map/img/add_search_field.png b/docs/manual/docs/help/map/img/add_search_field.png
new file mode 100644
index 00000000000..ea3c98ca8a6
Binary files /dev/null and b/docs/manual/docs/help/map/img/add_search_field.png differ
diff --git a/docs/manual/docs/help/map/img/add_services.png b/docs/manual/docs/help/map/img/add_services.png
new file mode 100644
index 00000000000..098c231f912
Binary files /dev/null and b/docs/manual/docs/help/map/img/add_services.png differ
diff --git a/docs/manual/docs/help/map/img/add_wms.png b/docs/manual/docs/help/map/img/add_wms.png
new file mode 100644
index 00000000000..d1c614baebc
Binary files /dev/null and b/docs/manual/docs/help/map/img/add_wms.png differ
diff --git a/docs/manual/docs/help/map/img/add_wms_style.png b/docs/manual/docs/help/map/img/add_wms_style.png
new file mode 100644
index 00000000000..d65e78a4681
Binary files /dev/null and b/docs/manual/docs/help/map/img/add_wms_style.png differ
diff --git a/docs/manual/docs/help/map/img/legend.png b/docs/manual/docs/help/map/img/legend.png
new file mode 100644
index 00000000000..6b1165e4207
Binary files /dev/null and b/docs/manual/docs/help/map/img/legend.png differ
diff --git a/docs/manual/docs/help/map/img/manage.png b/docs/manual/docs/help/map/img/manage.png
new file mode 100644
index 00000000000..74ec2c4691b
Binary files /dev/null and b/docs/manual/docs/help/map/img/manage.png differ
diff --git a/docs/manual/docs/help/map/img/manage_basemap.png b/docs/manual/docs/help/map/img/manage_basemap.png
new file mode 100644
index 00000000000..1a053462f4b
Binary files /dev/null and b/docs/manual/docs/help/map/img/manage_basemap.png differ
diff --git a/docs/manual/docs/help/map/img/manage_layers.png b/docs/manual/docs/help/map/img/manage_layers.png
new file mode 100644
index 00000000000..b7e7521e6d8
Binary files /dev/null and b/docs/manual/docs/help/map/img/manage_layers.png differ
diff --git a/docs/manual/docs/help/map/img/manage_order.png b/docs/manual/docs/help/map/img/manage_order.png
new file mode 100644
index 00000000000..5c486c57b26
Binary files /dev/null and b/docs/manual/docs/help/map/img/manage_order.png differ
diff --git a/docs/manual/docs/help/map/img/map.png b/docs/manual/docs/help/map/img/map.png
new file mode 100644
index 00000000000..7e2418c4085
Binary files /dev/null and b/docs/manual/docs/help/map/img/map.png differ
diff --git a/docs/manual/docs/help/map/img/map_download.png b/docs/manual/docs/help/map/img/map_download.png
new file mode 100644
index 00000000000..62d465ab58f
Binary files /dev/null and b/docs/manual/docs/help/map/img/map_download.png differ
diff --git a/docs/manual/docs/help/map/index.md b/docs/manual/docs/help/map/index.md
new file mode 100644
index 00000000000..474b3fc0a37
--- /dev/null
+++ b/docs/manual/docs/help/map/index.md
@@ -0,0 +1,189 @@
+---
+tags:
+- Map
+- Layers
+- Background Layers
+- Measure
+hide:
+ - tags
+---
+
+# Map
+
+The Catalogue includes an interactive map that is used to preview datasets.
+
+!!! info "How do I?"
+
+ [Visualizing Data](visualize/index.md)
+
+## Map area
+
+The map viewer has a number of features to explore the data:
+
+* Interactive map used to preview content.
+
+ Use the mouse to pan and zoom the map.
+
+* Controls used to add and manage map contents.
+
+* Navigation including **Zoom in**, **Zoom out**, **Zoom to extent**.
+
+* Location search including searching for your current position.
+
+ 
+ *Map viewer*
+
+## Add layers
+
+The interactive map views datasets as distinct layers. Layers can be drawn from a wide range of data sources.
+
+### Map
+
+Use records in the catalogue that include a saved map:
+
+1. From the **Map** viewer, press **Add layer** control, and change to **Map** tab.
+
+ This tab lists records that include saved Map.
+
+2. Use the **Search** field to locate the record to display.
+
+3. Use **Add to map** to include map contents.
+
+### Search
+
+Make use of records in the catalogue with web mapping services:
+
+1. From the **Map** viewer, press **Add layer** control, and change to **Search** tab.
+
+ 
+ *Add layer from search*
+
+2. Use the **Search** field to locate the record to display.
+
+ Only records with **Add to map** are listed.
+
+ 
+ *Search*
+
+3. Press **Add to map** to visualize the dataset.
+
+### Add layers services
+
+Use web mapping service:
+
+1. From the **Map** viewer, press **Add layer** control, and change to **Search** tab.
+
+ 
+
+2. To browse contents of a Web Map Service, supply a the service description URL
+ (known as ``GetCapabilities`` document).
+
+ **type a WMS service URL:**
+ : ``https://maps.geocat.net/geoserver/geocat/ows?service=wms&version=1.3.0&request=GetCapabilities``
+
+ The Web Map Service contents are immediately listed.
+
+3. Use WMS layers **Search** field to locate ``Coastline`` layer.
+
+ **Search**
+ : ``Coastline``
+
+ 
+ *Add WMS Layer*
+
+4. Press **:fontawesome-solid-plus: Add to map**.
+
+5. Use the WMS layers **Search** field to locate the ``Countries`` layer.
+
+ **Search**
+ : ``Countries``
+
+ Press the **:fontawesome-solid-paintbrush: Layer styles** to list styles available
+ for the ``Countries`` layer.
+
+ 
+ *Add WMS Layer style*
+
+6. Locate the ``mapcolor9` layer style, and press **Add to map**.
+
+### Add files
+
+Use **`KML`** files on the map.
+
+## Manage layers
+
+### Layer order
+
+1. From the **Map** viewer, press **Manage layers** control
+
+ 
+ *Manager layers*
+
+2. Placing the cursor over a layer shows **Move layer up**, **Move layer down**, and **Remove layer** button.
+
+ 
+ *Move layer up*
+
+3. Use these buttons to mange the layer order, and remove layers.
+
+### Background map
+
+1. From the **Map** viewer, press **Manage layers** control
+
+2. Change the **Background map** from `OpenStreetMap` to `Stamen Watercolor`.
+
+ 
+ *Manage basemap*
+
+## Legend
+
+1. From the **Map** viewer, press **Legend** control
+
+ 
+ *Legend*
+
+## Filter data
+
+Select a `WFS` layer to filter content, using a CQL query.
+
+## Use a WPS process
+
+Use a Web Processing Service to perform analysis and display the result.
+
+## Maps
+
+### Download map
+
+1. From the **Map** viewer, press **Maps** control
+
+2. Press ***Download --> OGC context (XML)** button
+
+### Load map
+
+1. From the **Map** viewer, press **Maps** control
+
+2. Press ***Load --> From file** button.
+
+ Select a previously downloaded OGC context file.
+
+### Load map reset to default
+
+1. From the **Map** viewer, press **Maps** control
+
+2. Press ***Load --> Default map** button.
+
+
+## Print
+
+## Measure
+
+## Annotation
+
+## Synchronize all layers
+
+## Zoom in/out, zoom to extent
+
+## Switch 2D to 3D
+
+## Graticule
+
diff --git a/docs/manual/docs/help/map/visualize/img/addtomap.png b/docs/manual/docs/help/map/visualize/img/addtomap.png
new file mode 100644
index 00000000000..36ac02e9df2
Binary files /dev/null and b/docs/manual/docs/help/map/visualize/img/addtomap.png differ
diff --git a/docs/manual/docs/help/map/visualize/img/addtomap_fr.png b/docs/manual/docs/help/map/visualize/img/addtomap_fr.png
new file mode 100644
index 00000000000..3985fe3a189
Binary files /dev/null and b/docs/manual/docs/help/map/visualize/img/addtomap_fr.png differ
diff --git a/docs/manual/docs/help/map/visualize/index.md b/docs/manual/docs/help/map/visualize/index.md
new file mode 100644
index 00000000000..4b28c8f3945
--- /dev/null
+++ b/docs/manual/docs/help/map/visualize/index.md
@@ -0,0 +1,86 @@
+# Visualizing Data
+
+All employees can use the data catalogue to search and discover
+environmental and scientific data. To begin, simply navigate to the Data
+Catalogue homepage and select a search type.
+
+!!! Overview
+
+ Geospatially enabled data in the data catalogue can be visualized using the interactive web map viewer feature.
+
+!!! Process
+
+ Discover > Combine Data/Select Data --> Visualize
+
+!!! Related training
+
+ Discovering Data, Accessing Data
+
+!!! Before You Start
+
+ There are no conditions to using this feature. Anyone accessing the Data
+ Catalogue can visualize geospatial data with the map viewer.
+
+## Discover
+
+1. To begin visualizing geospatial data, simply locate the data using
+ the data catalogue's search functionality (for more information,
+ see Discovering Data).
+
+2. If a dataset can be visualized using the map viewer you will see two
+ additional buttons: a globe or globe with drop down menu, and the
+ pushpin with drop down menu.
+
+ 
+ *Add to map and view on map buttons*
+
+ These allow you to:
+
+ - view on map, which will open the selected dataset in the map
+ viewer, or
+ - choose layers to view on map, which will open the selected
+ layers in map viewer, or
+ - add the dataset to the Map, where you can combine multiple
+ datasets to view in a single map.
+
+## View Data
+
+3. To view a single dataset on the map viewer, press the
+ **View on map*** button for that dataset. The map viewer will open
+ and display the data.
+
+ \[screenshot of search result, arrow points to view on map button\]
+
+## Combine Data
+
+4. By adding datasets to the Map Preview you are able to overlay
+ multiple datasets into a single viewer. This can be used to generate
+ new insights and support decision making.
+
+ \[screenshot of example displayed in map viewer\]
+
+ Add datasets to the preview list by pressing **Add to map list**
+ button (see pushpin icon) on each dataset from the search results
+ page or metadata details.
+
+ \[screenshot of search result and arrow to add to map preview
+ button\]
+
+5. The **Add to map list** with your selected datasets will display on
+ the left-hand side of the search results page. At any time you can:
+
+ \[screenshot of map preview list\]
+
+ - remove data you have added to the preview by clicking the **X**
+ beside the title
+ - combine and visualize the datasets by clicking **Add to map**.
+ Select the **Map** tab in the administration menu to view the
+ results.
+
+## Visualize
+
+6. Whether you have selected one or multiple datasets to visualize, the
+ map viewer has a number of features to explore the data.
+
+ \[screenshots of map viewer with expanded panel -- ie) add layers,
+ manage layers, etc\]
diff --git a/docs/manual/docs/help/record/img/about.png b/docs/manual/docs/help/record/img/about.png
new file mode 100644
index 00000000000..56d46834268
Binary files /dev/null and b/docs/manual/docs/help/record/img/about.png differ
diff --git a/docs/manual/docs/help/record/img/abstract.png b/docs/manual/docs/help/record/img/abstract.png
new file mode 100644
index 00000000000..0e4bc3ce5f4
Binary files /dev/null and b/docs/manual/docs/help/record/img/abstract.png differ
diff --git a/docs/manual/docs/help/record/img/additional.png b/docs/manual/docs/help/record/img/additional.png
new file mode 100644
index 00000000000..aef41b499b4
Binary files /dev/null and b/docs/manual/docs/help/record/img/additional.png differ
diff --git a/docs/manual/docs/help/record/img/citation.png b/docs/manual/docs/help/record/img/citation.png
new file mode 100644
index 00000000000..88b8dff1829
Binary files /dev/null and b/docs/manual/docs/help/record/img/citation.png differ
diff --git a/docs/manual/docs/help/record/img/data_distribution.png b/docs/manual/docs/help/record/img/data_distribution.png
new file mode 100644
index 00000000000..6ba98de6b8f
Binary files /dev/null and b/docs/manual/docs/help/record/img/data_distribution.png differ
diff --git a/docs/manual/docs/help/record/img/default_download_metadata.png b/docs/manual/docs/help/record/img/default_download_metadata.png
new file mode 100644
index 00000000000..555636b7053
Binary files /dev/null and b/docs/manual/docs/help/record/img/default_download_metadata.png differ
diff --git a/docs/manual/docs/help/record/img/default_metadata.png b/docs/manual/docs/help/record/img/default_metadata.png
new file mode 100644
index 00000000000..19e85a497ec
Binary files /dev/null and b/docs/manual/docs/help/record/img/default_metadata.png differ
diff --git a/docs/manual/docs/help/record/img/default_view.png b/docs/manual/docs/help/record/img/default_view.png
new file mode 100644
index 00000000000..6d4dc96345f
Binary files /dev/null and b/docs/manual/docs/help/record/img/default_view.png differ
diff --git a/docs/manual/docs/help/record/img/description.png b/docs/manual/docs/help/record/img/description.png
new file mode 100644
index 00000000000..0e73e3f2ff3
Binary files /dev/null and b/docs/manual/docs/help/record/img/description.png differ
diff --git a/docs/manual/docs/help/record/img/export_record_pdf.png b/docs/manual/docs/help/record/img/export_record_pdf.png
new file mode 100644
index 00000000000..f2b608d93f6
Binary files /dev/null and b/docs/manual/docs/help/record/img/export_record_pdf.png differ
diff --git a/docs/manual/docs/help/record/img/export_record_zip.png b/docs/manual/docs/help/record/img/export_record_zip.png
new file mode 100644
index 00000000000..9cf6f11f028
Binary files /dev/null and b/docs/manual/docs/help/record/img/export_record_zip.png differ
diff --git a/docs/manual/docs/help/record/img/full_download_metadata.png b/docs/manual/docs/help/record/img/full_download_metadata.png
new file mode 100644
index 00000000000..9d8dc0c3693
Binary files /dev/null and b/docs/manual/docs/help/record/img/full_download_metadata.png differ
diff --git a/docs/manual/docs/help/record/img/metadata.png b/docs/manual/docs/help/record/img/metadata.png
new file mode 100644
index 00000000000..9482c4fa9b3
Binary files /dev/null and b/docs/manual/docs/help/record/img/metadata.png differ
diff --git a/docs/manual/docs/help/record/img/permalink.png b/docs/manual/docs/help/record/img/permalink.png
new file mode 100644
index 00000000000..00cbf8b7bcc
Binary files /dev/null and b/docs/manual/docs/help/record/img/permalink.png differ
diff --git a/docs/manual/docs/help/record/img/permalink_copied.png b/docs/manual/docs/help/record/img/permalink_copied.png
new file mode 100644
index 00000000000..88d31ac5fff
Binary files /dev/null and b/docs/manual/docs/help/record/img/permalink_copied.png differ
diff --git a/docs/manual/docs/help/record/img/quality.png b/docs/manual/docs/help/record/img/quality.png
new file mode 100644
index 00000000000..ecffadb85f6
Binary files /dev/null and b/docs/manual/docs/help/record/img/quality.png differ
diff --git a/docs/manual/docs/help/record/img/record-xml.png b/docs/manual/docs/help/record/img/record-xml.png
new file mode 100644
index 00000000000..89db874b2e7
Binary files /dev/null and b/docs/manual/docs/help/record/img/record-xml.png differ
diff --git a/docs/manual/docs/help/record/img/record_default_view.png b/docs/manual/docs/help/record/img/record_default_view.png
new file mode 100644
index 00000000000..586ba7b37db
Binary files /dev/null and b/docs/manual/docs/help/record/img/record_default_view.png differ
diff --git a/docs/manual/docs/help/record/img/record_download.png b/docs/manual/docs/help/record/img/record_download.png
new file mode 100644
index 00000000000..54a29154cc8
Binary files /dev/null and b/docs/manual/docs/help/record/img/record_download.png differ
diff --git a/docs/manual/docs/help/record/img/record_navigation.png b/docs/manual/docs/help/record/img/record_navigation.png
new file mode 100644
index 00000000000..e50d0a6ad66
Binary files /dev/null and b/docs/manual/docs/help/record/img/record_navigation.png differ
diff --git a/docs/manual/docs/help/record/img/spatial_representation.png b/docs/manual/docs/help/record/img/spatial_representation.png
new file mode 100644
index 00000000000..0a93b3a795b
Binary files /dev/null and b/docs/manual/docs/help/record/img/spatial_representation.png differ
diff --git a/docs/manual/docs/help/record/img/technical.png b/docs/manual/docs/help/record/img/technical.png
new file mode 100644
index 00000000000..373ef0ba1c0
Binary files /dev/null and b/docs/manual/docs/help/record/img/technical.png differ
diff --git a/docs/manual/docs/help/record/index.md b/docs/manual/docs/help/record/index.md
new file mode 100644
index 00000000000..7b7b9c58a7a
--- /dev/null
+++ b/docs/manual/docs/help/record/index.md
@@ -0,0 +1,225 @@
+# View Record
+
+View record contents to discovering more in depth details about record and the dataset described.
+
+Locate record to view:
+
+1. Use **Search** field: `Ocean`
+
+2. Locate the record with title `Ocean`.
+
+ The background of the record will change to gray when your mouse is
+ over the `Harbour Porpoise Presence, Maritimes Region` record.
+
+ Click on the record to view.
+
+
+ 
+
+ *Search Ocean*
+
+3. The record contents are displayed, using the initial
+ **Default View** display mode.
+
+
+ 
+
+ *Default view*
+
+4. Record actions for viewing and download:
+
+ - **Next** and **Previous** buttons used to review search results.
+ - **Download** used to [export record](#download-from-record-view)
+ as `ZIP`, `XML` or `PDF`.
+ - The **Display mode** drop-down to change between **Default View**
+ and **Full View** covered in the next section.
+
+
+ 
+
+ *Record actions*
+
+## Default View
+
+The **Default view**, provides a quick summary of record contents:
+
+1. Use **Display mode** drop-down menu to select **Default view**.
+
+
+ 
+
+ *Change display mode to default view*
+
+2. Record title and description are shown at the top of the page.
+
+ 
+ *Record description*
+
+3. **About this resource** provides information on the contents, such as topic category.
+
+ 
+ *About this resource*
+
+4. **Technical information** provides details such data format.
+
+ 
+ *Technical information*
+
+5. **Metadata information** provides a button to download the XML record, contact information, and the
+ unique identifier.
+
+ 
+ *Metadata information*
+
+6. On the right hand side:
+
+ - **Spatial extent** is shown visually on a map
+ - Information on updates and feedback.
+
+
+ 
+
+ *Default view*
+
+## Full View
+
+The **Full view** is used to show complete record contents.
+
+1. Use **Display mode** drop-down menu to select **Full view**.
+
+2. The advanced view divides the record up into a number of tabs:
+
+ - Identification
+ - Distribution
+ - Quality
+ - Spatial Representation
+ - Reference Systems
+ - Metadata
+
+3. The **Identification** tab provides:
+
+ - Citation information:
+
+ 
+ *Citation details*
+
+ - Status and legal constraints (such as the Data Dissemination
+ Policy).
+
+ 
+ *Abstract and keywords*
+
+ - Additional information including temporal and spatial extent
+
+ 
+ *Additional identification information*
+
+4. The **Distribution** tab has details on how the content can be accessed.
+
+ 
+ *Data distribution details*
+
+5. The **Quality** tab lists data quality information.
+
+ 
+ *Data quality details*
+
+6. The **Spatial rep.** tab provides a summary of the spatial representation.
+
+ 
+ *Spatial representation details*
+
+7. The **Reference System** tab covers information on the spatial reference system used.
+
+ This is provided as a machine readable code to the reference system.
+
+ The example uses the code `http://www.opengis.net/def/crs/EPSG/0/26917` for the
+ `NAD83 / UTM zone 17N]` reference system.
+
+8. The **Metadata** tab covers the unique File Identifier, providing a link to view the XML document,
+ along with point of contact information for the record.
+
+ 
+ *Record metadata details*
+
+## XML Record
+
+1. The XML record can be shown from either:
+
+ - **Default View** metadata heading provides a **Download metadata** button.
+
+ 
+ *Default view download metadata*
+
+ - **Full View** metadata tab provides a link to **XML**.
+
+ 
+ *Full view download metadata*
+
+2. The XML file is downloaded, or shown directly in your browser.
+
+
+ 
+
+ *XML download shown in FireFox*
+
+3. Keep in mind XML record does not include any attached documents or thumbnails.
+
+ To download complete record information see the download section.
+
+## Download from record view
+
+Download the contents of a single record.
+
+1. View the `Harbour Porpoise Presence, Maritimes Region` record, showing a number of **:fontawesome-solid-download: Download** options:
+
+
+ 
+
+ *Record download options*
+
+2. **Permalink** provides a URL that
+ can be shared via email or message.
+
+ 
+ *Permalink to GEODBA.ACCOMMODATIONS record*
+
+ Use ++control+c++ (or ++command+c++ on macOS) to copy text to clipboard:
+
+ 
+ *Permalink copied*
+
+3. **Export (ZIP)** archive including:
+
+ - A folder containing complete **`metadata.xml`** record, and simplified
+ ***`metadata-iso19139.xml`*** record.
+ - ***`index.html`** and **`index.csv`** summary described in
+ the [previous section](#download-from-search-results).
+
+ 
+ *Export (ZIP) index.html summary*
+
+ This file is useful for exchanging information between systems. The
+ archive contents follows the "Metadata Exchange Format" convention
+ used to share records between catalogs.
+
+4. **Export (PDF)** document.
+
+
+ *XML download shown in FireFox*
+
+6. **Export (RDF)** machine readable
+ definition of vocabulary used.
+
+ This file is useful for exchanging information between systems.
+
diff --git a/docs/manual/docs/help/search/img/browse_results.png b/docs/manual/docs/help/search/img/browse_results.png
new file mode 100644
index 00000000000..c441f952caa
Binary files /dev/null and b/docs/manual/docs/help/search/img/browse_results.png differ
diff --git a/docs/manual/docs/help/search/img/browse_selection.png b/docs/manual/docs/help/search/img/browse_selection.png
new file mode 100644
index 00000000000..1512bda827a
Binary files /dev/null and b/docs/manual/docs/help/search/img/browse_selection.png differ
diff --git a/docs/manual/docs/help/search/img/distribution.png b/docs/manual/docs/help/search/img/distribution.png
new file mode 100644
index 00000000000..b1bef301033
Binary files /dev/null and b/docs/manual/docs/help/search/img/distribution.png differ
diff --git a/docs/manual/docs/help/search/img/download_records.png b/docs/manual/docs/help/search/img/download_records.png
new file mode 100644
index 00000000000..851bb0ec094
Binary files /dev/null and b/docs/manual/docs/help/search/img/download_records.png differ
diff --git a/docs/manual/docs/help/search/img/download_select_records.png b/docs/manual/docs/help/search/img/download_select_records.png
new file mode 100644
index 00000000000..4ef96bc5628
Binary files /dev/null and b/docs/manual/docs/help/search/img/download_select_records.png differ
diff --git a/docs/manual/docs/help/search/img/export_index_csv.png b/docs/manual/docs/help/search/img/export_index_csv.png
new file mode 100644
index 00000000000..2b7d742da86
Binary files /dev/null and b/docs/manual/docs/help/search/img/export_index_csv.png differ
diff --git a/docs/manual/docs/help/search/img/export_index_summary.png b/docs/manual/docs/help/search/img/export_index_summary.png
new file mode 100644
index 00000000000..9b0f02b63f2
Binary files /dev/null and b/docs/manual/docs/help/search/img/export_index_summary.png differ
diff --git a/docs/manual/docs/help/search/img/export_pdf.png b/docs/manual/docs/help/search/img/export_pdf.png
new file mode 100644
index 00000000000..022f3e82555
Binary files /dev/null and b/docs/manual/docs/help/search/img/export_pdf.png differ
diff --git a/docs/manual/docs/help/search/img/full_view.png b/docs/manual/docs/help/search/img/full_view.png
new file mode 100644
index 00000000000..fefd6a7e2ee
Binary files /dev/null and b/docs/manual/docs/help/search/img/full_view.png differ
diff --git a/docs/manual/docs/help/search/img/results_filter.png b/docs/manual/docs/help/search/img/results_filter.png
new file mode 100644
index 00000000000..8617e48f0ef
Binary files /dev/null and b/docs/manual/docs/help/search/img/results_filter.png differ
diff --git a/docs/manual/docs/help/search/img/search_acco.png b/docs/manual/docs/help/search/img/search_acco.png
new file mode 100644
index 00000000000..0f885715706
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_acco.png differ
diff --git a/docs/manual/docs/help/search/img/search_address.png b/docs/manual/docs/help/search/img/search_address.png
new file mode 100644
index 00000000000..b0992a28a3f
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_address.png differ
diff --git a/docs/manual/docs/help/search/img/search_advanced.png b/docs/manual/docs/help/search/img/search_advanced.png
new file mode 100644
index 00000000000..48b41aa2972
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_advanced.png differ
diff --git a/docs/manual/docs/help/search/img/search_map.png b/docs/manual/docs/help/search/img/search_map.png
new file mode 100644
index 00000000000..5e06a4822cf
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_map.png differ
diff --git a/docs/manual/docs/help/search/img/search_map_bbox.png b/docs/manual/docs/help/search/img/search_map_bbox.png
new file mode 100644
index 00000000000..83c4ea2ce35
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_map_bbox.png differ
diff --git a/docs/manual/docs/help/search/img/search_ocean.png b/docs/manual/docs/help/search/img/search_ocean.png
new file mode 100644
index 00000000000..60736e04642
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_ocean.png differ
diff --git a/docs/manual/docs/help/search/img/search_page.png b/docs/manual/docs/help/search/img/search_page.png
new file mode 100644
index 00000000000..e4304b2e339
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_page.png differ
diff --git a/docs/manual/docs/help/search/img/search_record_creation.png b/docs/manual/docs/help/search/img/search_record_creation.png
new file mode 100644
index 00000000000..ac74cebd039
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_record_creation.png differ
diff --git a/docs/manual/docs/help/search/img/search_resource_2016.png b/docs/manual/docs/help/search/img/search_resource_2016.png
new file mode 100644
index 00000000000..85af302100a
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_resource_2016.png differ
diff --git a/docs/manual/docs/help/search/img/search_result.png b/docs/manual/docs/help/search/img/search_result.png
new file mode 100644
index 00000000000..33c71bffd9d
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_result.png differ
diff --git a/docs/manual/docs/help/search/img/search_street.png b/docs/manual/docs/help/search/img/search_street.png
new file mode 100644
index 00000000000..daded696b40
Binary files /dev/null and b/docs/manual/docs/help/search/img/search_street.png differ
diff --git a/docs/manual/docs/help/search/img/selected-actions.png b/docs/manual/docs/help/search/img/selected-actions.png
new file mode 100644
index 00000000000..72a6487d46f
Binary files /dev/null and b/docs/manual/docs/help/search/img/selected-actions.png differ
diff --git a/docs/manual/docs/help/search/img/serach_accomidations.png b/docs/manual/docs/help/search/img/serach_accomidations.png
new file mode 100644
index 00000000000..d7a515ba677
Binary files /dev/null and b/docs/manual/docs/help/search/img/serach_accomidations.png differ
diff --git a/docs/manual/docs/help/search/index.md b/docs/manual/docs/help/search/index.md
new file mode 100644
index 00000000000..e5f6e10c9d5
--- /dev/null
+++ b/docs/manual/docs/help/search/index.md
@@ -0,0 +1,233 @@
+---
+tags:
+- Search
+- Catalog
+- Filter
+- Grid
+- List
+hide:
+ - tags
+---
+
+# Search
+
+The **Search** tab lists search results for filtering and sorting.
+
+## Search Catalogue
+
+1. Enter the desired keywords and search terms into the **Search** field
+ at the top of the page and press the **:fontawesome-solid-magnifying-glass: Search** button
+ (or use the ++enter++ key), to list search results.
+
+
+ 
+
+ *Search field*
+
+
+2. Search for complete words.
+
+ Use **Search** field to enter: `Ocean`
+
+
+ 
+
+ *Search results for Ocean*
+
+3. Search using the wildcard `*` to match the start or end of word.
+ Keep in mind the entire record contents is searched, not only the
+ titles and description.
+
+ Use **Search** field to enter: `Area*`
+
+
+ 
+
+ *Search for start of a word*
+
+4. The wildcard `*` can also be used multiple times to match part of a word.
+
+ Use **Search** field to enter: `*brass*`
+
+
+ 
+
+ *Search for part of a word*
+
+5. Filtering and exploring [search results](#search-results) is described below.
+
+
+## Search Results
+
+To further explore listed records:
+
+1. Navigate to the **:fontawesome-solid-magnifying-glass: Search** page (or browse or search the catalogue to
+ list search results).
+
+
+ 
+
+ *Search page*
+
+2. Use the **:fontawesome-solid-magnifying-glass: Filter** section on the right hand side to refine search results
+ using additional search facets, keywords, and details such as download format.
+
+ Click on the "search facet" `Oceans` to filter the search results to
+ matching records.
+
+
+ 
+
+ *Filter results*
+
+3. Options are provided at the top of the search results to:
+
+ * Presentation of matching records (as a **:fontawesome-solid-table-cells-large: Grid**
+ or **:fontawesome-solid-bars: List**)
+ * Sort the results
+ * Manage how many results are shown per page
+ * Advance to additional pages of results
+ * Quickly select records
+
+
+ 
+
+ *Browse results*
+
+4. To clear the search results use **:fontawesome-solid-xmark: Clear current search query, filters, and sorts**
+ at any time. This button is located in the **Search** field at the top of the page.
+
+5. The **:fontawesome-solid-ellipsis-vertical: Advanced** search options are located in the
+ **Search** field at the top of the page.
+
+ These options can be used to further refine search results by category, keywords, contact
+ or date range.
+
+
+ 
+
+ *Advanced search options*
+
+6. Open the **:fontawesome-solid-ellipsis-vertical: Advanced** search options panel.
+
+ Use the drop down menu for **Records created in the last** to select `this week`.
+ This acts as a short cut to fill in the **From** and **To** calendar fields.
+
+ Press the **:fontawesome-solid-magnifying-glass: Search** button to filter using this date range.
+
+
+ 
+
+ *Record updated in the last week*
+
+7. To search for data in the year `2016` use the advanced search
+ options to fill **Resources created in the last** in:
+
+ **From**
+ : `2016-01-01`
+
+ **To**
+ : `2016-12-31`
+
+ Press **Search** button to show data from `2016`.
+
+ 
+ *Resource updated in 2016*
+
+ !!! note
+
+ The **Resource** date filter shows records with data identification
+ (creation, publication, revision) dates included within the
+ calendar date range.
+
+8. A slide out map is provided at the bottom of the page, providing
+ visual feedback on the extent of each record.
+
+
+ 
+
+ *Search map*
+
+ The map can be controlled by by toggling beween two modes:
+
+ - Pan: Click and drag the map location, using the mouse wheel to
+ adjust zoom level.
+
+ - Bounding Box: Hold ++shift++ and click and drag to define an extent used to filter
+ records.
+
+ The drop down controls if the extent is used to list
+ only records that are withing, or all records that intersect.
+
+ 
+ *Search bounding box intersects*
+
+9. Records are selected (using the checkbox located next to each one)
+ to quickly download or generate a PDF of one or more records.
+
+
+ 
+
+ *Selected Records*
+
+10. Additional tips and tricks with search results:
+
+ - Details on
+ [selecting multiple records and exporting](#download-from-search-results)
+ as a `ZIP` or `PDF`.
+
+## Download from search results
+
+Multiple metadata records can be exported for download.
+
+
+To select records from multiple search results:
+
+1. Use the **Search** field to enter: `Ocean`
+
+ 
+ *Search results for Ocean*
+
+2. Use the checkboxes next to each record to select the contents for
+ download.
+
+ 
+ **Select records for download**
+
+3. At the top of the page the number of selected records is shown.
+
+ Next to the number of selected records is a **selected** drop-down,
+ offering a number of export options for download.
+
+ 
+ *Export options for download*
+
+4. **Export (ZIP)** archive including `xml` records along with any
+ attachments and thumbnails.
+
+ The resulting file includes:
+
+ - A folder for each metadata record exported
+
+ - ***`index.html`*** summary of contents
+
+ 
+ *Export ZIP index summary*
+
+ - ***`index.csv`*** summary of contents
+
+ 
+ *Export ZIP csv summary*
+
+5. **Export (PDF)** document of
+ exported records.
+
+ 
+ *Export PDF in Firefox*
+
+6. **Export (CSV)** download providing
+ a tabular summary of exported records.
+
+
+ 
+ *Export CSV*
diff --git a/docs/manual/docs/index.fr.md b/docs/manual/docs/index.fr.md
new file mode 100644
index 00000000000..a491841fe52
--- /dev/null
+++ b/docs/manual/docs/index.fr.md
@@ -0,0 +1,44 @@
+---
+hide:
+ - navigation
+---
+
+# GeoNetwork 4.4 {#toc}
+
+Bienvenue à GeoNetwork. Cette documentation est organisée en guides spécifiques destinés à différents publics.
+
+
+
+:fontawesome-solid-signs-post: [Vue d'ensemble](overview/index.md)
+
+: Historique de GeoNetwork, communauté, détails de la licence et derniers changements.
+
+:fontawesome-solid-circle-info: [Aide en ligne](help/index.md)
+
+: Aide en ligne pour les visiteurs du catalogue (aucune connexion n'est requise).
+
+:fontawesome-solid-person-circle-question: [Guide de l'utilisateur](user-guide/index.md)
+
+: Guide de l'utilisateur opérationnel décrivant l'édition, la révision et la gestion des enregistrements (nécessite une connexion).
+
+:fontawesome-solid-screwdriver-wrench: [Guide du mainteneur](maintainer-guide/index.md)
+
+: Instructions d'installation, de configuration et de mise à jour
+
+:fontawesome-solid-user-graduate: [Tutoriels](tutorials/index.md)
+
+: Explorer des sujets à l'aide de tutoriels étape par étape
+
+:fontawesome-solid-plug: [Référence API](api/index.md)
+
+: Référence API pour les développeurs accédant aux services du catalogue.
+
+:fontawesome-regular-file-code: [Développement](devel/index.md)
+
+: Informations sur le développement, la personnalisation de GeoNetwork et la participation au projet GeoNetwork.
+
+:fontawesome-regular-bookmark: [Annexes](annexes/index.md)
+
+: Informations de référence
+
+
diff --git a/docs/manual/docs/index.md b/docs/manual/docs/index.md
new file mode 100644
index 00000000000..5780bdfdb5e
--- /dev/null
+++ b/docs/manual/docs/index.md
@@ -0,0 +1,44 @@
+---
+hide:
+ - navigation
+---
+
+# GeoNetwork 4.4 {#toc}
+
+Welcome to GeoNetwork. This documentation is organized into specific guides targeting different audience.
+
+
+
+:fontawesome-solid-signs-post: [Overview](overview/index.md)
+
+: GeoNetwork background, community, license details, and the latest changes.
+
+:fontawesome-solid-circle-info: [Online Help](help/index.md)
+
+: Online help for visitors to the catalogue (no login required).
+
+:fontawesome-solid-person-circle-question: [User Guide](user-guide/index.md)
+
+: Operational user-guide describing the editing, review and management of records (requires-login).
+
+:fontawesome-solid-screwdriver-wrench: [Maintainer Guide](maintainer-guide/index.md)
+
+: Installation, setup and update instructions
+
+:fontawesome-solid-user-graduate: [Tutorials](tutorials/index.md)
+
+: Explore topics using step-by-step tutorials
+
+:fontawesome-solid-plug: [API Reference](api/index.md)
+
+: API Reference for developers accecssing catalogue services.
+
+:fontawesome-regular-file-code: [Development](devel/index.md)
+
+: Development information on customizing GeoNetwork and taking part in the GeoNetwork project.
+
+:fontawesome-regular-bookmark: [Annexes](annexes/index.md)
+
+: Reference information
+
+
diff --git a/docs/manual/docs/install-guide/configuring-database.md b/docs/manual/docs/install-guide/configuring-database.md
new file mode 100644
index 00000000000..213aedc9372
--- /dev/null
+++ b/docs/manual/docs/install-guide/configuring-database.md
@@ -0,0 +1,101 @@
+# Configuring the database {#configuring-database}
+
+## Introduction
+
+GeoNetwork uses a database to persist aspects such as metadata records, privileges and configurations. The database default structure is created by the application on initial startup. Subsequent releases of GeoNetwork will update the database structure automatically. For this reason the database user initially needs create privileges on the database. A number of database dialects are supported; ***H2***,***PostgreSQL***,***PostGIS***,***Oracle***,***SQL Server***. This section describes various options to configure the database connection.
+
+## H2 database
+
+By default, a [H2](https://www.h2database.com/html/main.html) database is configured and created when the application first starts. The H2 database named `gn.h2.db` is created:
+
+- In the **`jetty`** folder of the GeoNetwork application folder when using the [ZIP distribution](installing-from-zip.md).
+- In the **`bin`** folder of Tomcat when deploying the [WAR](installing-from-war-file.md) on Tomcat (started using `startup.sh`).
+
+!!! note
+
+ You don't **need** to configure the database if you are happy with the local H2 database. Only change the configuration if you wish to store the data on a remote database.
+
+
+## Configuring a database via config files
+
+The database dialect is configured in **`/WEB-INF/config-node/srv.xml`**. Uncomment the dialect to use.
+
+A jdbc driver is included for PostgreSQL, Oracle and H2. Other dialects require a jdbc driver to be installed. Download the jdbc library for the dialect and place it in `/WEB-INF/lib` or in the tomcat or GeoNetwork lib folder.
+
+To update the connection details, update the **`WEB-INF/config-db/jdbc.properties`** file with relevant connection information.
+
+GeoNetwork assumes data is stored in the default schema for a user. If this is not the case, you need to activate a setting `hibernate.default_schema` in **`/WEB-INF/config-spring-geonetwork.xml`**. There are some scripts that run directly on the database at initialisation and can't use the `hibernate.default-schema` parameter. For these scripts you need to set the default-schema manually. In PostgreSQL this is possible by appending `?currentSchema=example` to the database connection.
+
+## Configuring a database via JNDI
+
+The Java Naming and Directory Interface (JNDI) is a technology which allows to configure the database in tomcat and reference the JNDI connection by name.
+
+1. To activate JNDI, you need to activate the JNDI database type in **`/WEB-INF/config-node/srv.xml`**.
+
+2. Configure the JNDI connection in Tomcat by adding a new resource to **`TOMCAT/conf/context.xml`**. For jetty in **`WEB-INF/jetty-env.xml`**.
+
+ ``` xml
+
+ ```
+
+## Configuring a database via environment
+
+Setting configuration properties via environment variables is common in container environments such as Docker. 2 options exist:
+
+1. Add the parameters directly to the Java environment by substituting JAVA_OPTS.
+
+ ``` text
+ docker run --rm --name gn -p 8080:8080 -e JAVA_OPTS="
+ -Dgeonetwork.db.type=postgres
+ -Djdbc.database=example
+ -Djdbc.username=example
+ -Djdbc.password=xxx
+ -Djdbc.host=localhost
+ -Djdbc.port=5432" geonetwork:latest
+ ```
+
+2. Set an exact environment variable including '.'. Many of the GeoNetwork configuration parameters contain a dot, which is a challenge for substitution via environment variables. Docker is an exception here, it provides a mechanism to allow dots in environment variables.
+
+ ``` text
+ docker run --rm --name gn -p 8080:8080
+ -e geonetwork.db.type=postgres
+ -e jdbc.database=example
+ -e jdbc.username=example
+ -e jdbc.password=xxx
+ -e jdbc.host=localhost
+ -e jdbc.port=5432 geonetwork:latest
+ ```
+
+Within PostgreSQL it is possible to configure `es` or `is`. In the latter case GeoNetwork will use spatial capabilities of PostGIS to filter metadata. In the first case (and for other database dialects) a Shapefile is created for storage of metadata coverage.
+
+## Logging
+
+To see more details about the database connection and queries, the log can be switched to DEBUG level in `web/src/main/webapp/WEB-INF/classes/log4j.xml` (or see [Catalog Server](../administrator-guide/configuring-the-catalog/system-configuration.md#system-config-server) --> Log level).
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+## Summary
+
+There are various ways to configure a database in GeoNetwork. JNDI and environment are favourable, because when updating to a new version, or changing a database, you don't need to touch any application files.
diff --git a/docs/manual/docs/install-guide/customizing-data-directory.md b/docs/manual/docs/install-guide/customizing-data-directory.md
new file mode 100644
index 00000000000..07c02dc5ccc
--- /dev/null
+++ b/docs/manual/docs/install-guide/customizing-data-directory.md
@@ -0,0 +1,209 @@
+# Customizing the data directory {#customizing-data-directory}
+
+The data directory is the location on the file system where the catalog stores much of its custom configuration and uploaded files. This configuration defines such things as:
+
+- What thesaurus is used by GeoNetwork?
+- What schema is plugged in GeoNetwork?
+
+The data directory also contains a number of support files used by the catalog for various purposes:
+
+- index configuration
+- logos
+- uploaded document attached to metadata records
+- thumbnails
+
+It is a good idea to define an external data directory when going to production in order to make future updates easier. The data directory allows to run the WAR in readonly mode if needed.
+
+## Creating a new data directory
+
+The data directory needs to be created before starting the catalogue. It must be readable and writable by the user starting the catalogue.
+
+If the data directory is an empty folder, the catalogue will initialize the directory default structure using `INSTALL_DIR/web/geonetwork/WEB-INF/data`.
+
+If the data directory is not set, the following message is displayed in the log when the application starts:
+
+``` shell
+2015-12-16 07:59:17,108 WARN [geonetwork.data.directory] - - Data directory properties is not set. Use geonetwork.dir or geonetwork.dir properties.
+2015-12-16 07:59:17,108 WARN [geonetwork.data.directory] - - Data directory provided could not be used. Using default location: /data/dev/gn/3.0.x/web/src/main/webapp/WEB-INF/data
+```
+
+If the data directory is not accessible for the user, the log displays:
+
+``` shell
+2015-12-16 08:09:17,723 WARN [geonetwork.data.directory] - - Data directory '/tmp/gndatadir' is not writable. Set read/write privileges to user starting the catalogue (ie. francois).
+2015-12-16 08:09:17,723 WARN [geonetwork.data.directory] - - Data directory provided could not be used. Using default location: /data/dev/gn/3.0.x/web/src/main/webapp/WEB-INF/data
+```
+
+## Setting the data directory
+
+The data directory variable can be set using:
+
+- Java environment variable
+- Servlet context parameter
+- System environment variable
+- Bean configuration (added in version 3.0.4)
+
+For Java environment variable and servlet context parameter use:
+
+- .dir and if not set using geonetwork.dir
+
+For system environment variable use:
+
+- _dir and if not set using geonetwork_dir
+
+Resolution order is:
+
+1. .dir
+ 1. Java environment variable (ie. -D.dir=/a/data/dir)
+ 2. Servlet context parameter (ie. web.xml)
+ 3. Config.xml appHandler parameter (ie. config.xml)
+ 4. System environment variable (ie. _dir=/a/data/dir). "." is not supported in env variables
+2. geonetwork.dir
+ 1. Java environment variable (ie. -Dgeonetwork.dir=/a/data/dir)
+ 2. Servlet context parameter (ie. web.xml)
+ 3. Config.xml appHandler parameter (ie. config.xml)
+ 4. System environment variable (ie. geonetwork_dir=/a/data/dir). "." is not supported in env variables
+
+## Java System Property
+
+Depending on the servlet container used it is also possible to specify the data directory location with a Java System Property.
+
+For Tomcat, configuration is:
+
+``` shell
+CATALINA_OPTS="-Dgeonetwork.dir=/var/lib/geonetwork_data"
+```
+
+## Bean configuration
+
+!!! info "Version Added"
+
+ 3.0.4
+
+
+To configure the data directory using a custom bean configuration, update the GeonetworkDataDirectory bean in `core/src/main/resources/config-spring-geonetwork.xml`:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+## Using a S3 object storage
+
+If your infrastructure doesn't have a persistent storage available, you can configure GeoNetwork to use an Amazon S3 (or compatible) object storage to store the images and data.
+
+In order to do that, you must use a custom bean configuration. Replace the `filesystemStore`, `resourceStore` and `resources` beans in `core/src/main/resources/config-spring-geonetwork.xml` with something like that:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+The `s3credentials` bean can be left empty and the following system environment variables can be used to configure it (convenient in a container environment):
+
+- AWS_S3_PREFIX
+- AWS_S3_BUCKET
+- AWS_DEFAULT_REGION
+- AWS_S3_ENDPOINT
+- AWS_ACCESS_KEY_ID
+- AWS_SECRET_ACCESS_KEY
+
+## Structure of the data directory
+
+The data directory contains:
+
+``` text
+data_directory/
+ |--config: Extra configuration (eg. could contain overrides)
+ | |--schemaplugin-uri-catalog.xml
+ | |--codelist: The thesauri in SKOS format
+ | |--index: Index configuration
+ | |--schemaPlugins: The directory used to store new metadata standards
+ |
+ |--data
+ | |--metadata_data: The data related to metadata records
+ | |--resources:
+ | | |--htmlcache
+ | | |--images
+ | | | |--harvesting
+ | | | |--logos
+ | | | |--statTmp
+ | |
+ | |--metadata_subversion: The subversion repository
+ | |--backup: Folder containing removed metadata
+```
+
+## Advanced data directory configuration
+
+All sub-directories could be configured separately using Java system property. For example, to put the index config directory in a custom location use:
+
+- .indexConfig.dir and if not set using:
+- geonetwork.indexConfig.dir
+
+Examples:
+
+- Add the following Java properties to start-geonetwork.sh script:
+
+``` shell
+java -Xms1g -Xmx1g -Xss2M -XX:MaxPermSize=128m -Dgeonetwork.dir=/app/geonetwork_data_dir
+```
+
+- Add the following system properties to start-geonetwork.sh script:
+
+``` shell
+export geonetwork_dir=/app/geonetwork_data_dir
+```
+
+- If no changes are made to thesaurus or schema, it could be relevant to use the version from the webapp. In such case, set:
+
+``` shell
+-Dgeonetwork.dir=/data/catalogue
+-Dgeonetwork.schema.dir=/app/tomcat/webapps/geonetwork/WEB-INF/data/config/schema_plugins
+-Dgeonetwork.indexConfig.dir=/app/tomcat/webapps/geonetwork/WEB-INF/data/config/index
+-Dgeonetwork.codeList.dir=/app/tomcat/webapps/geonetwork/WEB-INF/data/config/codelist
+```
+
+The list of properties that can be set are:
+
+- geonetwork.dir
+- geonetwork.indexConfig.dir
+- geonetwork.config.dir
+- geonetwork.codeList.dir
+- geonetwork.schema.dir
+- geonetwork.data.dir
+- geonetwork.resources.dir
+- geonetwork.svn.dir
+- geonetwork.upload.dir
+- geonetwork.backup.dir
+- geonetwork.formatter.dir
+- geonetwork.htmlcache.dir
+
+## Check the configuration
+
+After startup, check the configuration in `Admin console` --> `Statistics and status` --> `Information` page.
+
+
diff --git a/docs/manual/docs/install-guide/img/datadirectory.png b/docs/manual/docs/install-guide/img/datadirectory.png
new file mode 100644
index 00000000000..2d4482fd701
Binary files /dev/null and b/docs/manual/docs/install-guide/img/datadirectory.png differ
diff --git a/docs/manual/docs/install-guide/img/docker.png b/docs/manual/docs/install-guide/img/docker.png
new file mode 100644
index 00000000000..f694e63bc24
Binary files /dev/null and b/docs/manual/docs/install-guide/img/docker.png differ
diff --git a/docs/manual/docs/install-guide/img/es-down.png b/docs/manual/docs/install-guide/img/es-down.png
new file mode 100644
index 00000000000..3ad3e5bf851
Binary files /dev/null and b/docs/manual/docs/install-guide/img/es-down.png differ
diff --git a/docs/manual/docs/install-guide/img/es-empty.png b/docs/manual/docs/install-guide/img/es-empty.png
new file mode 100644
index 00000000000..0d50d85a0b8
Binary files /dev/null and b/docs/manual/docs/install-guide/img/es-empty.png differ
diff --git a/docs/manual/docs/install-guide/img/home-page.png b/docs/manual/docs/install-guide/img/home-page.png
new file mode 100644
index 00000000000..42de71ab0f9
Binary files /dev/null and b/docs/manual/docs/install-guide/img/home-page.png differ
diff --git a/docs/manual/docs/install-guide/img/identified-user.png b/docs/manual/docs/install-guide/img/identified-user.png
new file mode 100644
index 00000000000..c59f0e8069f
Binary files /dev/null and b/docs/manual/docs/install-guide/img/identified-user.png differ
diff --git a/docs/manual/docs/install-guide/img/log-setting.png b/docs/manual/docs/install-guide/img/log-setting.png
new file mode 100644
index 00000000000..e7f775bab4e
Binary files /dev/null and b/docs/manual/docs/install-guide/img/log-setting.png differ
diff --git a/docs/manual/docs/install-guide/img/metadata-and-templates.png b/docs/manual/docs/install-guide/img/metadata-and-templates.png
new file mode 100644
index 00000000000..9d8cdf4a7a3
Binary files /dev/null and b/docs/manual/docs/install-guide/img/metadata-and-templates.png differ
diff --git a/docs/manual/docs/install-guide/img/once-samples-are-loaded.png b/docs/manual/docs/install-guide/img/once-samples-are-loaded.png
new file mode 100644
index 00000000000..aec27cdd380
Binary files /dev/null and b/docs/manual/docs/install-guide/img/once-samples-are-loaded.png differ
diff --git a/docs/manual/docs/install-guide/img/signin.png b/docs/manual/docs/install-guide/img/signin.png
new file mode 100644
index 00000000000..7a52e3b40f4
Binary files /dev/null and b/docs/manual/docs/install-guide/img/signin.png differ
diff --git a/docs/manual/docs/install-guide/img/templates.png b/docs/manual/docs/install-guide/img/templates.png
new file mode 100644
index 00000000000..c379f1e49f3
Binary files /dev/null and b/docs/manual/docs/install-guide/img/templates.png differ
diff --git a/docs/manual/docs/install-guide/index.md b/docs/manual/docs/install-guide/index.md
new file mode 100644
index 00000000000..fbe408ff852
--- /dev/null
+++ b/docs/manual/docs/install-guide/index.md
@@ -0,0 +1,28 @@
+# Installation guide {#installation}
+
+!!! info
+
+ GeoNetwork 4.4 requires a Java 11 environment (JRE) to be installed on your system. Later versions of Java will not work at present. This must be done prior to installation.
+
+ Prior versions of GeoNetwork require a Java 8 environment (JRE) to be installed on your system.
+
+Before you can use GeoNetwork on your own computer, you need to install it. There are several different ways to install GeoNetwork:
+
+- [Installing using a ZIP file](installing-from-zip.md)
+- [Installing from WAR file](installing-from-war-file.md)
+- [Installing with docker](installing-with-docker.md)
+- [Building from Source Code](installing-from-source-code.md)
+- [Installing search platform](installing-index.md)
+
+!!! note
+
+ A windows installer is also available from the GeoNetwork download page, [Installing a third-party distribution](https://geonetwork-opensource.org/downloads.html#third-party-distributions) .
+
+
+After installing the application, you can configure the following:
+
+- [Configuring the database](configuring-database.md)
+- [Customizing the data directory](customizing-data-directory.md)
+- [Logging](logging.md)
+- [Configuring printing of the map](map-print-setup.md)
+- [Loading templates and sample data](loading-samples.md)
diff --git a/docs/manual/docs/install-guide/installing-from-source-code.md b/docs/manual/docs/install-guide/installing-from-source-code.md
new file mode 100644
index 00000000000..8541a05ad9d
--- /dev/null
+++ b/docs/manual/docs/install-guide/installing-from-source-code.md
@@ -0,0 +1,180 @@
+# Building from Source Code {#installing-from-source-code}
+
+## System Requirements
+
+### Java 11
+
+GeoNetwork 4.4 is a Java 11 application that runs as a servlet, which means that a Java Development Kit (JDK) must be installed in order to build and run it. You can get a Java 11 JDK from your Linux distribution, [OpenJDK](https://openjdk.java.net/) or [Adoptium Temurin JDK](https://adoptopenjdk.net).
+
+Please note that the commercial distribution of [Oracle JDK](https://www.oracle.com/technetwork/java/javase/downloads) no longer provides Java 11 for testing purposes.
+
+Because GeoNetwork is developed with Java 11 (LTS), it won't run at all with earlier releases.
+
+- GeoNetwork should not be developed with newer versions of Java.
+- It won't run at all with earlier releases.
+- Java 17 (LTS) is **not supported** at this time.
+
+### Application Server
+
+Next, you need a servlet container. GeoNetwork ships with an embedded container, [Eclipse Jetty](https://www.eclipse.org/jetty/), which is fast and well-suited for most applications.
+
+We highly recommend [Apache Tomcat](https://tomcat.apache.org). Apache Tomcat provides load balancing, fault tolerance and other production features. Apache Tomcat is widely used with many organizations as a standardized environment for all their Java Web Applications.
+
+We recommend the following stable releases of Tomcat:
+
+- Apache Tomcat 9.0
+- Apache Tomcat 8.5
+
+GeoNetwork cannot use the newer versions of Apache Tomcat 10 which are based on the Jakarata Enterprise Edition web application standard.
+
+### Database
+
+Regarding storage, you need a Database Management System (DBMS) like Oracle, MySQL, Postgresql etc. GeoNetwork comes with an embedded DBMS (H2) which is used by default during installation. This DBMS can be used for small or desktop installations of no more than a few thousand metadata records with one or two users. If you have heavier demands then you should use a professional, stand alone DBMS.
+
+### Environment
+
+Being written in Java, GeoNetwork can run on any platform that supports Java: primarily Linux, Windows and macOS.
+
+GeoNetwork is not resource intensive and will not require a powerful machine. Good performance can be obtained with 1GB of RAM. However, the suggested amount is 2GB of RAM.
+
+For hard disk space, you have to consider the space required for the application itself (about 350 MB) and the space required for data, which could grow up to 50 GB or more. A simple (SSD) disk of 250 GB should be sufficient in most cases. You also need some disk space for the search index which is located in `GEONETWORK_DATA_DIR/index` (by default GEONETWORK_DATA_DIR is `INSTALL_DIR/web/geonetwork/WEB_INF/data`). However, even with a few thousand metadata records, the index is small so usually 500 MB of space is more than enough.
+
+The software runs in different ways depending on the servlet container you are using:
+
+- *Tomcat* - GeoNetwork is available as a WAR file which you can put into the Tomcat webapps directory. Tomcat will deploy the WAR file when it is started. You can then use the Tomcat manager web application to stop/start GeoNetwork. You can also use the startup.* and shutdown.* scripts located in the Tomcat bin directory (.* means .sh or .bat depending on your OS) but if you have other web applications in the Tomcat container, then they will also be affected.
+- *Jetty* - If you use the provided container you can use the scripts in GeoNetwork's bin directory. The scripts are startup.* and shutdown.* and you must be inside the bin directory to run them. You can use these scripts just after installation.
+
+## Tools
+
+The following tools are required to be installed to setup a development environment for GeoNetwork:
+
+- **Java 11** - Developing with GeoNetwork requires Java Development Kit (JDK) 11.
+- **Maven** 3.1.0+ - GeoNetwork uses [Maven](https://maven.apache.org/) to manage the build process and the dependencies. Once is installed, you should have the mvn command in your path (on Windows systems, you have to open a shell to check).
+- **Git** - GeoNetwork source code is stored and versioned in [a Git repository on Github](https://github.com/geonetwork/core-geonetwork). Depending on your operating system a variety of Git clients are available. Please check the Git website for some [alternatives](https://git-scm.com/downloads/guis) and good [documentation](https://git-scm.com/documentation). More documentation can be found on the [Github website](https://help.github.com/).
+- **Ant** - GeoNetwork uses [Ant](https://ant.apache.org/) to build the installer. Version 1.6.5 works but any other recent version should be OK. Once installed, you should have the Ant command in your path (on Windows systems, you have to open a shell to check).
+- **mkdocs** - To build the GeoNetwork documentation in a nice format, [mkdocs](https://www.mkdocs.org) is used. Please note that if you don't have a Python interpreter on your system, Sphinx will not work, so you need to install [Python](https://www.python.org/downloads/).
+
+## Building & Running
+
+If you only wish to quickly build and run GeoNetwork, execute the following:
+
+``` shell
+git clone --depth 3 --recursive https://github.com/geonetwork/core-geonetwork.git
+cd core-geonetwork
+mvn clean install -DskipTests
+
+cd es
+mvn install -Pes-download
+mvn exec:exec -Des-start
+
+cd web
+mvn jetty:run
+```
+
+Now open your browser and navigate to .
+
+For a more detailed explanation, please read on.
+
+### Check out the source code
+
+Clone the repository and build:
+
+``` shell
+git clone --recursive https://github.com/geonetwork/core-geonetwork.git
+cd core-geonetwork
+mvn clean install -DskipTests
+```
+
+### Submodules
+
+GeoNetwork use submodules, these were initialized by the `--recursive` option when cloning the repository.
+
+If you missed using `--recursive` run the following:
+
+``` shell
+cd core-geonetwork
+git submodule init
+git submodule update
+```
+
+Submodules are used to keep track of externals dependencies. It is necessary to init and update them after a branch change:
+
+``` shell
+git submodule update --init
+```
+
+Remember to rebuild the application after updating external dependencies.
+
+### Build GeoNetwork
+
+Once you checked out the code from Github repository, go inside the GeoNetwork's root folder and execute the Maven build command:
+
+``` shell
+mvn clean install
+```
+
+If the build is successful you'll get an output like:
+
+``` shell
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Reactor Summary:
+[INFO] ------------------------------------------------------------------------
+[INFO] GeoNetwork opensource ................................. SUCCESS [1.345s]
+[INFO] Caching xslt module ................................... SUCCESS [1.126s]
+[INFO] Jeeves modules ........................................ SUCCESS [3.970s]
+[INFO] ArcSDE module (dummy-api) ............................. SUCCESS [0.566s]
+[INFO] GeoNetwork web client module .......................... SUCCESS [23.084s]
+[INFO] GeoNetwork user interface module ...................... SUCCESS [15.940s]
+[INFO] Oaipmh modules ........................................ SUCCESS [1.029s]
+[INFO] GeoNetwork domain ..................................... SUCCESS [0.808s]
+[INFO] GeoNetwork core ....................................... SUCCESS [6.426s]
+[INFO] GeoNetwork CSW server ................................. SUCCESS [2.050s]
+[INFO] GeoNetwork health monitor ............................. SUCCESS [1.014s]
+[INFO] GeoNetwork harvesters ................................. SUCCESS [2.583s]
+[INFO] GeoNetwork services ................................... SUCCESS [3.178s]
+[INFO] GeoNetwork Web module ................................. SUCCESS [2:31.387s]
+[INFO] ------------------------------------------------------------------------
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESSFUL
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 3 minutes 35 seconds
+[INFO] Finished at: Sun Oct 27 16:21:46 CET 2013
+```
+
+Your local Maven repository now contain the GeoNetwork artifacts created (`$HOME/.m2/repository/org/geonetwork-opensource`).
+
+### Compilation options
+
+Many Maven build options are available, for instance, you might like to use following options :
+
+``` shell
+-- Skip test
+$ mvn install -DskipTests
+
+-- Offline use
+$ mvn install -o
+
+-- Build really fast with 2 threads per cpu core
+$ mvn install -o -DskipTests -T 2C
+```
+
+Please refer to the [Maven documentation](https://www.sonatype.com/books/mvnref-book/reference/public-book.html) for any other options.
+
+### Run embedded Jetty server
+
+Maven comes with built-in support for Jetty via a [plug-in](https://eclipse.dev/jetty/documentation/jetty-9/index.html#maven-and-jetty).
+
+To run GeoNetwork with the embedded Jetty server you have to change directory to the root of the **web** module, and then execute the following Maven command:
+
+``` shell
+mvn jetty:run -Penv-dev
+```
+
+After some moments of startup and initialization, GeoNetwork is available at:
+
+For changes related to the user interface in the ``web-ui`` module or the metadata schemas in the `schemas` module, these can be deployed in Jetty executing the following Maven command in the **web** module:
+
+``` shell
+mvn process-resources -DschemasCopy=true
+```
diff --git a/docs/manual/docs/install-guide/installing-from-war-file.md b/docs/manual/docs/install-guide/installing-from-war-file.md
new file mode 100644
index 00000000000..391d343dda3
--- /dev/null
+++ b/docs/manual/docs/install-guide/installing-from-war-file.md
@@ -0,0 +1,80 @@
+# Installing from WAR file
+
+This section describes how to install GeoNetwork with the WAR.
+
+At the end of the installation process you will end up with the web applications running.
+
+Host ports requirements:
+
+- Java web server [Apache Tomcat](https://tomcat.apache.org/) or [Jetty](https://www.eclipse.org/jetty/): 8080
+- [Elasticsearch](https://www.elastic.co/elasticsearch/): 9200
+- [Kibana](https://www.elastic.co/kibana/): 5601
+- Database eg. 5432 for a default [PostgreSQL](https://www.postgresql.org/) installation
+
+
+For [Apache Tomcat](https://tomcat.apache.org/) we recommend the following versions: 8.5.x and 9.0.x. The latest Apache Tomcat 10.x cannot be used at this time.
+
+For [Jetty](https://www.eclipse.org/jetty/) we the following versions: 9.4.x. Newer versions to Jetty cannot be used at this time.
+
+1. Download the WAR file
+
+ GeoNetwork releases are available in
+
+ You can download the WAR file `geonetwork.war` from your browser or use command line like
+
+ ``` shell
+ wget https://downloads.sourceforge.net/project/geonetwork/GeoNetwork_opensource/v3.10.2/geonetwork.war
+ ```
+
+2. Copy the WAR to the Java web server
+
+ After download, copy the WAR file in the webapp folder of Tomcat or Jetty.
+
+ ``` shell
+ cp geonetwork.war /usr/share/apache-tomcat{X}/webapps/.
+ ```
+
+3. Start the Java web server
+
+ If started, Tomcat will automatically deploy the application. If not, start the Java web server to deploy.
+
+ !!! note
+
+ You need to ensure Tomcat is configured with enough memory for GeoNetwork to launch. This can be be configured via the `setenv` script in tomcat with the appropriate memory for the JAVA_OPTS property). `-Xms2g -Xmx2g` is usually fine.
+
+ !!! note
+
+ For the `/monitor/metrics` endpoint to work correctly, you must add to `JAVA_OPTS` the following option: `--add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED`
+
+4. Configure the search platform
+
+ Open in your web browser. You should see the GeoNetwork home page indicating that the search is not yet available.
+
+ 
+
+ You need to install Elasticsearch or to configure GeoNetwork to use an existing instance.
+
+ Download Elasticsearch for your platform
+
+ ``` shell
+ wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.6.2-linux-x86_64.tar.gz
+ tar xvfz elasticsearch-7.6.2-linux-x86_64.tar.gz
+ cd elasticsearch-7.6.2-linux-x86_64/bin
+ ./elasticsearch
+ ```
+
+ Open in your web browser to check that Elasticsearch is running.
+
+ To use an existing instance check `on` in [Installing search platform](installing-index.md).
+
+5. Up and running?
+
+ Open or refresh in your web browser. You should see the GeoNetwork home page:
+
+ 
+
+ You have now a default GeoNetwork up and running.
+
+ To customize your catalog, you may follow the next steps to configure the database (See [Configuring the database](configuring-database.md)) instead of using the default H2 database and the data directory (See [Customizing the data directory](customizing-data-directory.md)) .
+
+ See [Loading templates and sample data](loading-samples.md) to start loading metadata records.
diff --git a/docs/manual/docs/install-guide/installing-from-zip.md b/docs/manual/docs/install-guide/installing-from-zip.md
new file mode 100644
index 00000000000..5202f10a1cc
--- /dev/null
+++ b/docs/manual/docs/install-guide/installing-from-zip.md
@@ -0,0 +1,13 @@
+# Installing using a ZIP file {#installing-from-zip}
+
+For Linux, macOS and Windows users, a zipped GeoNetwork distribution is available that includes the following:
+
+- GeoNetwork application
+- Jetty servlet container
+- Shell scripts (`.sh`, `.bat`) to start and stop GeoNetwork
+
+Please download the desired ZIP file and extract it to a preferred location on your machine. When done, open the containing folder and navigate to the `bin` folder. This should include 2 `.sh` files that can be used to start and stop GeoNetwork (use the `.bat` files on Windows). Please double-click on the `startup.sh` file to start the server.
+
+In the application root folder, you will find a `readme.html` file that includes some details on how to get started with GeoNetwork. Double-click it to view it in your browser.
+
+Then install the Elasticsearch instance (see [Installing search platform](installing-index.md)).
diff --git a/docs/manual/docs/install-guide/installing-index.md b/docs/manual/docs/install-guide/installing-index.md
new file mode 100644
index 00000000000..7369f99540f
--- /dev/null
+++ b/docs/manual/docs/install-guide/installing-index.md
@@ -0,0 +1,74 @@
+# Installing search platform {#installing-index}
+
+The GeoNetwork search engine is built on top of Elasticsearch. The platform is used to index records and also to analyze WFS data (See [Analyze and visualize data](../user-guide/analyzing/data.md) ), an [Elasticsearch](https://www.elastic.co/products/elasticsearch) instance must be installed next to the catalog.
+
+## Manual installation
+
+Download Elasticsearch 7.x (at least `7.9.2`) from and unzip the file.
+
+``` shell
+wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.9.2.tar.gz
+tar xvfz elasticsearch-7.9.2.tar.gz
+```
+
+Manually start and stop Elasticsearch using:
+
+``` shell
+elasticsearch-7.9.2/bin/elasticsearch
+```
+
+Stop Elasticsearch using
+
+``` shell
+elasticsearch-7.9.2/bin/elasticsearch stop
+```
+
+GeoNetwork will start even if Elasticsearch index is down. A warning will be displayed. Once the Elasticsearch index is up, indices are created if they do not exist.
+
+(Optional) Then create the default index (the application will create them automatically once the index is up and running and if no indices are found):
+
+## Customizing index
+
+User may want to customize the index settings for example to change language configuration (see `es/README.md`). Check the configuration file in `` `$GN_DATA_DIRECTORY/config/index ```. To manually remove and recreate the index, use the following:
+
+``` shell
+cd $GN_DATA_DIRECTORY/config/index
+curl -X DELETE http://localhost:9200/features
+curl -X DELETE http://localhost:9200/records
+curl -X DELETE http://localhost:9200/searchlogs
+
+curl -X PUT http://localhost:9200/features -H 'Content-Type: application/json' -d @features.json
+curl -X PUT http://localhost:9200/records -H 'Content-Type: application/json' -d @records.json
+curl -X PUT http://localhost:9200/searchlogs -H 'Content-Type: application/json' -d @searchlogs.json
+```
+
+## Install using Maven
+
+Running from the source code, use Maven to download.
+
+``` shell
+cd es
+mvn install -Pes-download
+mvn exec:exec -Des-start
+```
+
+To stop Elasticsearch when using Maven, simply stop the process as Elasticsearch is started in foreground mode.
+
+## Check installation
+
+Access Elasticsearch admin page from .
+
+## Configure connection
+
+Update Elasticsearch connection details in ```WEB-INF/config.properties``` and restart the application:
+
+``` shell
+es.protocol=http
+es.port=9200
+es.host=localhost
+es.url=${es.protocol}://${es.host}:${es.port}
+es.username=
+es.password=
+```
+
+It is not needed nor recommended to open port 9200 to the outside. GeoNetwork is protecting the Elasticsearch instance exposing only the search API and taking care of user privileges.
diff --git a/docs/manual/docs/install-guide/installing-with-docker.md b/docs/manual/docs/install-guide/installing-with-docker.md
new file mode 100644
index 00000000000..7ffbc71c461
--- /dev/null
+++ b/docs/manual/docs/install-guide/installing-with-docker.md
@@ -0,0 +1,13 @@
+# Installing with docker
+
+This section describes how to install GeoNetwork with docker.
+
+At the end of the installation process you will end up with the web applications running.
+
+Run with docker
+
+``` shell
+docker run --name some-geonetwork -d geonetwork
+```
+
+See for more details.
diff --git a/docs/manual/docs/install-guide/loading-samples.md b/docs/manual/docs/install-guide/loading-samples.md
new file mode 100644
index 00000000000..917833ee439
--- /dev/null
+++ b/docs/manual/docs/install-guide/loading-samples.md
@@ -0,0 +1,35 @@
+# Loading templates and sample data {#loading-samples}
+
+Open a web browser and go to the GeoNetwork homepage. If you installed it on your computer, this is probably at `http://localhost:8080/geonetwork`.
+
+When you use Docker, you can find our what IP and Port to connect to from the Kitematic application. Or run `docker ps` in a terminal (on Linux or OSX). This should give you the port the Docker is running on.
+
+
+
+Your opening screen should look like this:
+
+
+
+## Signing in and loading templates
+
+Click the `sign in` to connect as administrator. The default account is username `admin` with password `admin`.
+
+
+
+Once connected, the top toolbar should provide a link to the `Admin console` and your login details.
+
+
+
+Go to the `Admin console` and click on `Metadata and templates`:
+
+
+
+Choose the metadata standards you wish to use and click `Load templates for selected standards` and then `Load samples for selected standards` in order to load the example data:
+
+
+
+Once loaded, you will see an Import report on the right side of your screen.
+
+You can now go back to the Search page to see the loaded examples:
+
+
diff --git a/docs/manual/docs/install-guide/logging.md b/docs/manual/docs/install-guide/logging.md
new file mode 100644
index 00000000000..37b640f7734
--- /dev/null
+++ b/docs/manual/docs/install-guide/logging.md
@@ -0,0 +1,26 @@
+# Logging
+
+This section describes how to use the geonetwork log files to find more details on incidents.
+
+## Customising the log file location
+
+Log files are written to the generic log location of the container. It is possible to change the location of the logfiles with an environment parameter ``-Dlog_dir=/var/tomcat/``. The path should end with **`/`** and the log files will be created in **`/var/tomcat/logs/geonetwork.log`**.
+
+Details of some errors, such as xsl transformation errors, are not written to geonetwork.log. They are written to a file called **`catalina.out`**.
+
+## Setting the Loglevel
+
+GeoNetwork by default has 4 log levels: PROD, INDEX, SEARCH, DEV.
+
+- PROD is the default option, it will only log critical errors.
+- INDEX is similar to PROD, but with extended logging around the indexation process.
+- Search is similar to PROD, but with extended logging around the search process.
+- DEV is the most extended level, all debug messages will be logged.
+
+You can set the log level from the Admin --> Settings page.
+
+
+
+## Log4j
+
+GeoNetwork uses [log4j](https://logging.apache.org/log4j) for logging. The log4j configuration file is located at **`/WEB-INF/classes/log4j.xml`**. The configuration file configures for each debug level at what severity messages will be logged.
diff --git a/docs/manual/docs/install-guide/map-print-setup.md b/docs/manual/docs/install-guide/map-print-setup.md
new file mode 100644
index 00000000000..f8f07db07b3
--- /dev/null
+++ b/docs/manual/docs/install-guide/map-print-setup.md
@@ -0,0 +1,14 @@
+# Configuring printing of the map {# map-print-setup}
+
+This section describes how to configure the options to print maps. Printing a map generates a pdf file on the server which is downloaded by the client to be send to a printer. During pdf creation map data is downloaded from various sources to be included in the pdf.
+
+GeoNetwork needs to be able to access the external resource. Set up a webproxy in `gs` if your network requires a webproxy to be set up to access the internet.
+
+Locate the file ``WEB-INF/config-print/print-config.yaml``, this configuration file has a lot of options to customise the print options. Read more about the various parameters at
+
+The folder contains 3 template files:
+
+- ``template.pdf`` and ``template-landscape.pdf`` which are used to generate the map viewer pdf
+- ``template-thumbnail.pdf`` which is used to build a thumbnail in the metadata editor (see [Generating a thumbnail using WMS layers](../user-guide/associating-resources/linking-thumbnail.md#linking-thumbnail-from-wms)).
+
+These templates are created by exporting pdf from the included ``template.odf`` file in the folder.
diff --git a/docs/manual/docs/maintainer-guide/index.md b/docs/manual/docs/maintainer-guide/index.md
new file mode 100644
index 00000000000..3b829b3d8a2
--- /dev/null
+++ b/docs/manual/docs/maintainer-guide/index.md
@@ -0,0 +1,8 @@
+# Maintainer guide
+
+For installation instructions, please refer to the [Installation guide](../install-guide/index.md).
+
+- [Installation](../install-guide/index.md)
+- [Setup](../administrator-guide/index.md)
+- [Production Use](production-use/index.md)
+- [Updating the application](updating/index.md)
diff --git a/docs/manual/docs/maintainer-guide/production-use/index.md b/docs/manual/docs/maintainer-guide/production-use/index.md
new file mode 100644
index 00000000000..f0248070faf
--- /dev/null
+++ b/docs/manual/docs/maintainer-guide/production-use/index.md
@@ -0,0 +1,91 @@
+# Production use
+
+This paragraph shares some guidance around setting up GeoNetwork for production use.
+
+## Database
+
+GeoNetwork arrives with a file based H2 database. In production make sure to switch to an external database system, such as PostGres, Oracle or SQL server. Read more about setting up a database at [Configuring the database](../../install-guide/configuring-database.md)
+
+JNDI is a technology that allows GeoNetwork to delegate the configuration of the database to Tomcat. By using JNDI the database can be easily configured without the need to change config files inside the application folder.
+
+GeoNetwork may run out of database connections, especially if a catalogue is set up with many harvesters. You can increase the number of allowed connections (if the database allows it). But also consider to set up some periodical monitoring to evaluate if GeoNetwork is running out of connections. The catalogue will throw random errors if running low on connections.
+
+## Java container
+
+GeoNetwork 4.4 requires Java 11. The Oracle JRE version 8 is reaching end-of-live, we suggest to use the [openJDK](https://adoptopenjdk.net).
+
+GeoNetwork arrives with a default container called Jetty. Jetty is a powerful minimal container implementation. If you need more configuration options consider to use Tomcat. Other containers can be used, but there are not many user experiences. Read more at [Installing from WAR file](../../install-guide/installing-from-war-file.md)
+
+If you run Apache in front of Tomcat, make sure to enable [AJP](https://tomcat.apache.org/tomcat-4.0-doc/config/ajp.html), else you may run into page not found errors around login. On Apache 2, enable `mod_proxy_ajp` and set the `ProxyPass` and `ProxyPassReverse` on apache2.conf to use the AJP protocol on Tomcat URL and port 8009:
+
+``` shell
+ProxyPass /geonetwork ajp://gn_tomcat_host:8009/geonetwork
+ProxyPassReverse /geonetwork ajp://gn_tomcat_host:8009/geonetwork
+```
+
+On Tomcat 9, define an AJP Connector on port 8009 in server.xml.
+
+A common challenge in production use is the fact that Java only has a limited set of root certificates that it trusts natively. This causes problems if GeoNetwork tries to access a secure server which has a certificate not trusted by Java. An administrator has to explicitly [load the certificate in to the Java keystore](https://stackoverflow.com/questions/4325263/how-to-import-a-cer-certificate-into-a-java-keystore).
+
+## Data folder
+
+GeoNetwork requires a data folder to store objects uploaded by administrators and managers and some configuration options. By default this folder is located in **`/geonetwork/WEB-INF/data`**. In production situation configure the location of this folder outside the application and make sure the folder is backed up. You can use an environment variable to configure the location of the data folder. Read more at [Customizing the data directory](../../install-guide/customizing-data-directory.md)
+
+## Memory
+
+GeoNetwork is a memory intensive application. Consider to provide at least 2GB, but 4GB is probably better. But don't go higher than 6GB. Read more about memory in Java applications at the [geoserver documentation](https://docs.geoserver.org/stable/en/user/production/container.html). If you're setting up an instance of Elastic Search, consider to provide at least 8GB to Elastic.
+
+## Scaling
+
+GeoNetwork currently has challenges to be set up in a load balanced/fail over configuration. The search index is stored in memory and will not be aware of changes on records done in other nodes. An option to optimise this is introducing a master-minion model; modifications are done in master, minion harvest master at intervals. Each minion will have a local database. Typical aspects stored in the database, like groups, settings, user feedback and search statistics will not be synchronised between nodes. The data folder can be shared between nodes by using a network share.
+
+## GeoNetwork and Docker
+
+Docker is a popular virtualisation technology for hosting services. Conventions from Docker can also be used in other cloud environments. As GeoNetwork community we maintain a [docker image on docker hub](https://hub.docker.com/_/geonetwork). Note that for each version there is also a postgres tag which uses a remote postgres database. A best practices for Docker is to parameterise GeoNetwork using environment variables which are injected from docker machine or an orchestration.
+
+## Web Proxy
+
+GeoNetwork contains a web proxy to bypass cross browser communication limitations of browsers. This proxy is used for example:
+
+- Map viewer / GetCapabilities document retrieval
+- Map viewer / Load a WFS layer
+- Map viewer / WMS GetFeatureInfo
+- Record view / List atom feed resources
+- Editor / Warning if a link return http errors
+- Admin / Harvesting / GetCapabilities for CSW to retrieve queryable fields
+- Admin / Thesaurus / Add from INSPIRE registry
+
+A best practice is to whitelist a series of servers which are known to contain data services. However the best guidance here is to recommend to any data provider to enable [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) on their services, and then disable the web proxy. CORS fixes the cross browser communication limitation in the proper way.
+
+If set up in an incorrect way, remote users may get access to resources that should not be accessible to them, or impersonate themselves as the geonetwork server while browsing the web.
+
+GeoNetwork has 2 modes to limit the access via the proxy. The configuration of this mode is defined in ``WEB-INF/web.xml``.
+
+``` xml
+
+ securityMode
+ NONE
+
+```
+
+- NONE: (dis)allow certain domains via security configuration (default before 3.10.3)
+- DB_LINK_CHECK (default since 3.10.3)
+
+It is recommended to use the DB_LINK_CHECK mode. The following rules apply:
+
+- Authenticated users can use the proxy to all domains.
+- For anonymous users, if the host of the URL requested is not used in any metadata record links, then a NotAllowedException is returned. If a WMS URL is registered, all GetCapabilities, GetFeatureInfo will be accepted. That's why only a host check is done.
+- Also if a request is made directly to the proxy, a SecurityException is returned because no session exist. This limit its usage to user with a catalog session.
+- Catalog reviewers have to use the metadata link analysis tool to register links allowed for the proxy. The tool is available at 'Record and link analysis' in the ``Admin --> Statistics & status`` menu. In the future we may trigger link analysis as a background task to have an up to date list of links. For now, if the table is empty, the exception highlights the fact that the link analysis tool should be used to populate the list.
+
+One issue that anonymous users can encounter is if using the map viewer and the user adds a WMS/WFS service URL which is not registered in any metadata records and which has no CORS enabled. The user will not be able to add any layers from those services.
+
+## WEB
+
+Since an important part of the catalogue behaves like a normal website. Adopting website best practices is recommended:
+
+- GeoNetwork has a capability to login, for that reason browsers expect the site to run secure over https. However you have to consider that browsers on https sites will block any content included as http (mixed content). Many links (thumbnails, wms services, \...) in (archived) metadata may still be based on http. A consideration could be to run the website on both http and https and switch to https in case users login.
+- Engage with the popular search engines to either or not have your GeoNetwork listed in search results. Register the GeoNetwork Sitemap in the various search engine administration pages, and monitor the crawling and search behaviour. It will lead to interesting insights, such as search behaviour and dead links in metadata. In order to identify yourself to search engines, you need to place an identification file in the root of your website. At the same site also place the robots.txt file, which links to the sitemap. Robots.txt can also be used to guide the search engine to not crawl certain parts of the catalogue. If GeoNetwork is installed in the root folder, robots.txt is already in the correct location.
+- Verify that the catalogue uri's of records and api's are persistent over time. Other sites may deep link into the catalogue, those links should not be broken after a migration. Fix broken links by setting up forward rules that forward traffic to new url's. Prevent broken links in future by using [cool uri's](https://www.w3.org/TR/cooluris/). For example do not use a product name (eg GeoNetwork) in a url.
+- Provide a link to the authority managing the catalogue, a disclaimer, cookie warning and/or privacy policy on the header/footer of the site.
+- Monitor the availability of the application using a tool like zabbix, nagios or [geohealthcheck](https://geohealthcheck.org/).
diff --git a/docs/manual/docs/maintainer-guide/updating/index.md b/docs/manual/docs/maintainer-guide/updating/index.md
new file mode 100644
index 00000000000..a036fe0d636
--- /dev/null
+++ b/docs/manual/docs/maintainer-guide/updating/index.md
@@ -0,0 +1,7 @@
+# Updating the application {#updating}
+
+Since GeoNetwork 4.0.4, passwords stored in the database for the mail server, harvesters, etc. are encrypted with [Jasypt](http://www.jasypt.org/).
+
+By default, a random encryption password is generated when GeoNetwork is started, if it is not already defined, and it is stored in the file **`/geonetwork/WEB-INF/data/config/encryptor/encryptor.properties`**. If you have set the location of the data directory outside of the application, the file will be stored in this external location. Read more at [Customizing the data directory](../../install-guide/customizing-data-directory.md).
+
+The file with the encryption settings **must be copied** to the new installation when upgrading the application; otherwise, it will not be possible to decrypt the existing passwords stored in the database.
diff --git a/docs/manual/docs/overview/about.md b/docs/manual/docs/overview/about.md
new file mode 100644
index 00000000000..967fa95ba83
--- /dev/null
+++ b/docs/manual/docs/overview/about.md
@@ -0,0 +1,20 @@
+# About
+
+GeoNetwork opensource is a catalog allowing visitors to search and discover spatial information. Visitors are can the included map viewer to preview datasets interactively.
+
+GeoNetwork provides the tools to managing spatially referenced resources including record editing.
+
+The project is based on Open Standards both for data management, and interoperability between systems.
+
+## Core Features
+
+- Immediate search access to local and distributed geospatial catalogues
+- Up and downloading of data, graphics, documents, pdf files and any other content type
+- An interactive Web Map Viewer to combine Web Map Services from distributed servers around the world
+- Recently updated entries are accessible as RSS news feeds and as GeoRSS.
+- Online editing of metadata with a powerful template system
+- Native support for ISO19115/ISO19119/ISO19139/ISO19110 and Dublin Core formatted metadata
+- Scheduled harvesting and synchronization of metadata between distributed catalogues (GeoNetwork, CSW, OGC WxS GetCapabilities, WebDav, ArcSDE, Thredds, OGC WFS Features, OAI-PMH)
+- Fine-grained access control
+- Group and user management
+- Multi-lingual user interface
diff --git a/docs/manual/docs/overview/authors.md b/docs/manual/docs/overview/authors.md
new file mode 100644
index 00000000000..60099cdf93a
--- /dev/null
+++ b/docs/manual/docs/overview/authors.md
@@ -0,0 +1,54 @@
+# Author {#authors}
+
+## Project Steering Committee (PSC)
+
+The GeoNetwork Project Steering Committee (PSC) makes decisions on GeoNetwork opensource project issues.
+
+In brief the committee votes on proposals on the geonetwork-dev mailinglist. Proposals are available for review for at least two days, and a single veto is sufficient to delay progress though ultimately a majority of members can pass a proposal.
+
+### Members of the Project Steering Committee
+
+- Jeroen Ticheler (jeroen ticheler * geocat net) [GeoCat](https://www.geocat.net) - Chair
+- Francois Prunayre [Titellus](https://titellus.net)
+- Simon Pigot [CSIRO](https://www.csiro.au)
+- Florent Gravin [CamptoCamp](https://camptocamp.com)
+- Jose Garcia [GeoCat](https://www.geocat.net)
+- Jo Cook [Astun Technology](https://www.astuntechnology.com)
+- Paul van Genuchten [ISRIC](https://www.isric.org)
+
+### Former members of the PSC
+
+- Patrizia Monteduro (Patrizia Monteduro * fao org) [FAO-UN](https://www.fao.org)
+- Emanuele Tajariol (e tajariol * mclink it - GeoSolutions)
+- Jesse Eichar
+- Andrea Carboni (acarboni * crisalis-tech com - Independent consultant)
+- Archie Warnock (warnock * awcubed com) [A/WWW Enterprises](https://www.awcubed.com)
+
+## Committers
+
+Committers list is available [here for the core team](https://github.com/orgs/geonetwork/teams/committers) and [here for the documenter team](https://github.com/orgs/geonetwork/teams/documenters).
+
+- Emanuele Tajariol
+- Craig Jones
+- Florent Gravin
+- Francois Prunayre
+- Jeroen Ticheler
+- Jose Garcia
+- Maria Arias de Reyna
+- Juan Luis Rodriguez Ponce
+- Olivier Guyot
+- Pierre Mauduit
+- Simon Pigot
+- Paul van Genuchten
+- Antonio Cerciello
+- Michel Gabriel
+- Jody Garnett
+- David Blasby
+
+## Contributors
+
+Contributors list is available [here](https://github.com/geonetwork/core-geonetwork/graphs/contributors).
+
+## The documentation
+
+The documentation was written by the GeoNetwork opensource developers and other community members.
diff --git a/docs/manual/docs/overview/change-log/archive/index.md b/docs/manual/docs/overview/change-log/archive/index.md
new file mode 100644
index 00000000000..3c9dd91e5f5
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/archive/index.md
@@ -0,0 +1,90 @@
+# Archived
+
+The following series of GeoNetwork are no longer in active use and you are encouraged to migrate to a newer version.
+
+The GeoNetwork community is not large enough to maintain many active branches of GeoNetwork at one time. Older installations of GeoNetwork may be subject to disclosed security vulnerabilities resulting in our recommendation to update to the supported [stable](../stable/index.md) or [maintenance](../maintenance/index.md) series.
+
+Volunteers wishing to backport security fixes to older versions of GeoNetwork are welcome to do so. Commercial support providers are welcome to do so on behalf of their customers.
+
+## 4.0.x
+
+- [Version 4.0.6](../version-4.0.6.md)
+- [Version 4.0.5](../version-4.0.5.md)
+- [Version 4.0.4](../version-4.0.4.md)
+- [Version 4.0.3](../version-4.0.3.md)
+- [Version 4.0.2](../version-4.0.2.md)
+- [Version 4.0.1](../version-4.0.1.md)
+- [Version 4.0.0](../version-4.0.0.md)
+- [Version 4.0.0 Alpha.2](../version-4.0.0-alpha.2.md)
+- [Version 4.0.0 Alpha.1](../version-4.0.0-alpha.1.md)
+
+## 3.10.x
+
+- [Version 3.10.10](../version-3.10.10.md)
+- [Version 3.10.9](../version-3.10.9.md)
+- [Version 3.10.8](../version-3.10.8.md)
+- [Version 3.10.7](../version-3.10.7.md)
+- [Version 3.10.6](../version-3.10.6.md)
+- [Version 3.10.5](../version-3.10.5.md)
+- [Version 3.10.4](../version-3.10.4.md)
+- [Version 3.10.3](../version-3.10.3.md)
+- [Version 3.10.2](../version-3.10.2.md)
+- [Version 3.10.1](../version-3.10.1.md)
+- [Version 3.10.0](../version-3.10.0.md)
+- [Version 3.8.3](../version-3.8.3.md)
+- [Version 3.8.2](../version-3.8.2.md)
+- [Version 3.8.1](../version-3.8.1.md)
+- [Version 3.8.0](../version-3.8.0.md)
+- [Version 3.6.0](../version-3.6.0.md)
+- [Version 3.4.4](../version-3.4.4.md)
+- [Version 3.4.3](../version-3.4.3.md)
+- [Version 3.4.2](../version-3.4.2.md)
+- [Version 3.4.1](../version-3.4.1.md)
+- [Version 3.4.0](../version-3.4.0.md)
+- [Version 3.2.2](../version-3.2.2.md)
+- [Version 3.2.1](../version-3.2.1.md)
+- [Version 3.2.0](../version-3.2.0.md)
+- [Version 3.0.4](../version-3.0.4.md)
+- [Version 3.0.3](../version-3.0.3.md)
+- [Version 3.0.2](../version-3.0.2.md)
+- [Version 3.0.1](../version-3.0.1.md)
+- [Version 3.0.0](../version-3.0.0.md)
+
+## 3.8.x
+
+- [Version 3.8.3](../version-3.8.3.md)
+- [Version 3.8.2](../version-3.8.2.md)
+- [Version 3.8.1](../version-3.8.1.md)
+- [Version 3.8.0](../version-3.8.0.md)
+
+## 3.6.x
+
+- [Version 3.6.0](../version-3.6.0.md)
+
+## 3.4.x
+
+- [Version 3.4.4](../version-3.4.4.md)
+- [Version 3.4.3](../version-3.4.3.md)
+- [Version 3.4.2](../version-3.4.2.md)
+- [Version 3.4.1](../version-3.4.1.md)
+- [Version 3.4.0](../version-3.4.0.md)
+
+## 3.2.x
+
+- [Version 3.2.2](../version-3.2.2.md)
+- [Version 3.2.1](../version-3.2.1.md)
+- [Version 3.2.0](../version-3.2.0.md)
+
+## 3.0.x
+
+- [Version 3.0.4](../version-3.0.4.md)
+- [Version 3.0.3](../version-3.0.3.md)
+- [Version 3.0.2](../version-3.0.2.md)
+- [Version 3.0.1](../version-3.0.1.md)
+- [Version 3.0.0](../version-3.0.0.md)
+
+## 2.10.x
+
+All development has ceased:
+
+* [User Manual v2.10.4-0](https://geonetwork-opensource.org/manuals/2.10.4/eng/users/index.html)
diff --git a/docs/manual/docs/overview/change-log/img/360-admin-console.png b/docs/manual/docs/overview/change-log/img/360-admin-console.png
new file mode 100644
index 00000000000..7b3b3d6f81c
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/360-admin-console.png differ
diff --git a/docs/manual/docs/overview/change-log/img/360-record-history.png b/docs/manual/docs/overview/change-log/img/360-record-history.png
new file mode 100644
index 00000000000..c293d16986e
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/360-record-history.png differ
diff --git a/docs/manual/docs/overview/change-log/img/380-associated.png b/docs/manual/docs/overview/change-log/img/380-associated.png
new file mode 100644
index 00000000000..1f205d79b51
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/380-associated.png differ
diff --git a/docs/manual/docs/overview/change-log/img/380-related.png b/docs/manual/docs/overview/change-log/img/380-related.png
new file mode 100644
index 00000000000..8ce8fa81866
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/380-related.png differ
diff --git a/docs/manual/docs/overview/change-log/img/380-usersearches.png b/docs/manual/docs/overview/change-log/img/380-usersearches.png
new file mode 100644
index 00000000000..d2e19df7408
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/380-usersearches.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-facet-histogram.png b/docs/manual/docs/overview/change-log/img/3990-es-facet-histogram.png
new file mode 100644
index 00000000000..0d7b666e00f
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-facet-histogram.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-facet-more.png b/docs/manual/docs/overview/change-log/img/3990-es-facet-more.png
new file mode 100644
index 00000000000..d4f61b458a8
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-facet-more.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-facet-negative.png b/docs/manual/docs/overview/change-log/img/3990-es-facet-negative.png
new file mode 100644
index 00000000000..944f59b488e
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-facet-negative.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-facet-nested.png b/docs/manual/docs/overview/change-log/img/3990-es-facet-nested.png
new file mode 100644
index 00000000000..f0522180f50
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-facet-nested.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-facet-or.png b/docs/manual/docs/overview/change-log/img/3990-es-facet-or.png
new file mode 100644
index 00000000000..762c6cf795d
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-facet-or.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-index-multilingual.png b/docs/manual/docs/overview/change-log/img/3990-es-index-multilingual.png
new file mode 100644
index 00000000000..5a37b681289
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-index-multilingual.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-indexing-errors.png b/docs/manual/docs/overview/change-log/img/3990-es-indexing-errors.png
new file mode 100644
index 00000000000..b3d96c61f29
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-indexing-errors.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-morelikethis.png b/docs/manual/docs/overview/change-log/img/3990-es-morelikethis.png
new file mode 100644
index 00000000000..77fcb3b5e92
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-morelikethis.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-search-range.png b/docs/manual/docs/overview/change-log/img/3990-es-search-range.png
new file mode 100644
index 00000000000..5b033407911
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-search-range.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-es-suggest-phrase.png b/docs/manual/docs/overview/change-log/img/3990-es-suggest-phrase.png
new file mode 100644
index 00000000000..2a513777c3b
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-es-suggest-phrase.png differ
diff --git a/docs/manual/docs/overview/change-log/img/3990-kb-dq.png b/docs/manual/docs/overview/change-log/img/3990-kb-dq.png
new file mode 100644
index 00000000000..e9f40beb024
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/3990-kb-dq.png differ
diff --git a/docs/manual/docs/overview/change-log/img/400-histogram.png b/docs/manual/docs/overview/change-log/img/400-histogram.png
new file mode 100644
index 00000000000..86b6a655e6e
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/400-histogram.png differ
diff --git a/docs/manual/docs/overview/change-log/img/400-home-page-category-config.png b/docs/manual/docs/overview/change-log/img/400-home-page-category-config.png
new file mode 100644
index 00000000000..1c982580a34
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/400-home-page-category-config.png differ
diff --git a/docs/manual/docs/overview/change-log/img/400-record-event.png b/docs/manual/docs/overview/change-log/img/400-record-event.png
new file mode 100644
index 00000000000..bb49130536e
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/400-record-event.png differ
diff --git a/docs/manual/docs/overview/change-log/img/400-remote-record-support.png b/docs/manual/docs/overview/change-log/img/400-remote-record-support.png
new file mode 100644
index 00000000000..c78858732ef
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/400-remote-record-support.png differ
diff --git a/docs/manual/docs/overview/change-log/img/400-search-exactmatch.png b/docs/manual/docs/overview/change-log/img/400-search-exactmatch.png
new file mode 100644
index 00000000000..d5f9671de25
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/400-search-exactmatch.png differ
diff --git a/docs/manual/docs/overview/change-log/img/400-search-results.png b/docs/manual/docs/overview/change-log/img/400-search-results.png
new file mode 100644
index 00000000000..ee18e0f298f
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/400-search-results.png differ
diff --git a/docs/manual/docs/overview/change-log/img/401-wfs-scheduler.png b/docs/manual/docs/overview/change-log/img/401-wfs-scheduler.png
new file mode 100644
index 00000000000..f2fa52bc964
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/401-wfs-scheduler.png differ
diff --git a/docs/manual/docs/overview/change-log/img/403-monitoring.png b/docs/manual/docs/overview/change-log/img/403-monitoring.png
new file mode 100644
index 00000000000..47c67361cff
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/403-monitoring.png differ
diff --git a/docs/manual/docs/overview/change-log/img/421-previewdata.png b/docs/manual/docs/overview/change-log/img/421-previewdata.png
new file mode 100644
index 00000000000..a54a96be6d7
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/421-previewdata.png differ
diff --git a/docs/manual/docs/overview/change-log/img/424-pagesapi.png b/docs/manual/docs/overview/change-log/img/424-pagesapi.png
new file mode 100644
index 00000000000..0fba111c915
Binary files /dev/null and b/docs/manual/docs/overview/change-log/img/424-pagesapi.png differ
diff --git a/docs/manual/docs/overview/change-log/index.md b/docs/manual/docs/overview/change-log/index.md
new file mode 100644
index 00000000000..83a627c6074
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/index.md
@@ -0,0 +1,8 @@
+# Change log
+
+Notable changes made to GeoNetwork opensource including new features, migration instructions, and bug fixes.
+
+- [Latest](latest/index.md)
+- [Stable](stable/index.md)
+- [Maintenance](maintenance/index.md)
+- [Archive](archive/index.md)
diff --git a/docs/manual/docs/overview/change-log/latest/index.md b/docs/manual/docs/overview/change-log/latest/index.md
new file mode 100644
index 00000000000..6e78c807893
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/latest/index.md
@@ -0,0 +1,13 @@
+# Latest
+
+GeoNetwork 4.4.x is recommended for those enjoying the newest features from the GeoNetwork community.
+
+This series is under active development by our community, with new features, improvements, documentation updates, bug reports, fixes, and releases.
+
+## Latest
+
+- [Version 4.4.1](../version-4.4.1.md)
+
+## History
+
+- [Version 4.4.0](../version-4.4.0.md)
diff --git a/docs/manual/docs/overview/change-log/maintenance/index.md b/docs/manual/docs/overview/change-log/maintenance/index.md
new file mode 100644
index 00000000000..a7939f78428
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/maintenance/index.md
@@ -0,0 +1,22 @@
+# Maintenance
+
+The GeoNetwork 4.2.x series is stable and recommended for production use and new installations of GeoNetwork.
+This series is under active use by our community, with regular improvements, documentation updates, bug reports, fixes, and releases.
+
+## Latest
+
+* [Version 3.12.11](../version-3.12.11.md)
+
+## History
+
+* [Version 3.12.10](../version-3.12.10.md)
+* [Version 3.12.9](../version-3.12.9.md)
+* [Version 3.12.8](../version-3.12.8.md)
+* [Version 3.12.7](../version-3.12.7.md)
+* [Version 3.12.6](../version-3.12.6.md)
+* [Version 3.12.5](../version-3.12.5.md)
+* [Version 3.12.4](../version-3.12.4.md)
+* [Version 3.12.3](../version-3.12.3.md)
+* [Version 3.12.3](../version-3.12.2.md)
+* [Version 3.12.1](../version-3.12.1.md)
+* [Version 3.12.0](../version-3.12.0.md)
diff --git a/docs/manual/docs/overview/change-log/stable/index.md b/docs/manual/docs/overview/change-log/stable/index.md
new file mode 100644
index 00000000000..7dd249e7131
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/stable/index.md
@@ -0,0 +1,19 @@
+# Stable
+
+The GeoNetwork 4.2.x series is stable and recommended for production use and new installations of GeoNetwork.
+This series is under active use by our community, with regular improvements, documentation updates, bug reports, fixes, and releases.
+
+## Latest
+
+- [Version 4.2.7](../version-4.2.7.md)
+
+
+## History
+
+- [Version 4.2.6](../version-4.2.6.md)
+- [Version 4.2.5](../version-4.2.5.md)
+- [Version 4.2.4](../version-4.2.4.md)
+- [Version 4.2.3](../version-4.2.3.md)
+- [Version 4.2.2](../version-4.2.2.md)
+- [Version 4.2.1](../version-4.2.1.md)
+- [Version 4.2.0](../version-4.2.0.md)
diff --git a/docs/manual/docs/overview/change-log/version-3.0.0.md b/docs/manual/docs/overview/change-log/version-3.0.0.md
new file mode 100644
index 00000000000..3a35f9b542d
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.0.0.md
@@ -0,0 +1 @@
+# Version 3.0.0 {#version-300}
diff --git a/docs/manual/docs/overview/change-log/version-3.0.1.md b/docs/manual/docs/overview/change-log/version-3.0.1.md
new file mode 100644
index 00000000000..0b14e2b17ee
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.0.1.md
@@ -0,0 +1,20 @@
+# Version 3.0.1 {#version-301}
+
+## New features
+
+- [Map viewer provides now 3D mode](https://github.com/geonetwork/core-geonetwork/pull/1012) using [Cesiumjs](https://cesiumjs.org/)
+- Make your map in the visualization tools and [save your maps in the catalog](https://github.com/geonetwork/core-geonetwork/issues/1036)
+- [Spatial filter is now available on the minimap](https://github.com/geonetwork/core-geonetwork/issues/1051)
+- [Browse catalog by INSPIRE themes](https://github.com/geonetwork/core-geonetwork/issues/1054) and use the new [INSPIRE icon set](https://github.com/titellus/INSPIRE-themes-icons)
+- [Resource status is clearly displayed in search results](https://github.com/geonetwork/core-geonetwork/issues/1044)
+- Record view better displays links to local file on the network and database tables
+- Multiple bounding boxes are supported on bounding box map highlighter and record view
+- Sitemap is paginated
+
+## Bug Fixes
+
+- Fix map printing on Tomcat 8
+- Metadata editor now properly compute extent from geographic keyword
+- Properly upload thesaurus
+
+and more \... see [3.0.1 issues](https://github.com/geonetwork/core-geonetwork/issues?page=2&q=is%3Aissue+milestone%3A3.0.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.0.1+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.0.2.md b/docs/manual/docs/overview/change-log/version-3.0.2.md
new file mode 100644
index 00000000000..2cd7fa087c8
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.0.2.md
@@ -0,0 +1,16 @@
+# Version 3.0.2 {#version-302}
+
+## New features
+
+- Search / Add hierarchical facet support
+- Search / Add facet on source catalog and resolution
+- Metadata view / Better navigation between datasets and maps
+- Editor / Automatically enable workflow for records in a group
+- Thesaurus / Update region thesaurus based on Natural Earth and Sea Vox
+- Processing / Vacuum batch process help cleaning ISO19139 and Dublin Core records
+- Harvester / Filesystem harvester can harvest subtemplates
+- Administration / End of session notification (See [User session](../../administrator-guide/managing-users-and-groups/index.md#user-session))
+
+## Bug Fixes
+
+and more \... see [3.0.2 issues](https://github.com/geonetwork/core-geonetwork/issues?page=2&q=is%3Aissue+milestone%3A3.0.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.0.2+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.0.3.md b/docs/manual/docs/overview/change-log/version-3.0.3.md
new file mode 100644
index 00000000000..0dd9a54592a
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.0.3.md
@@ -0,0 +1,15 @@
+# Version 3.0.3 {#version-303}
+
+## New features
+
+- Search / Better support of INSPIRE themes in multilingual metadata records
+- Editor / Thesaurus broader/narrower/related concepts navigation (eg. GEMET)
+- Editor / Metadata identifier templates
+- CSW / Improved interoperability with other implementations
+- CSW / Pluggable output schema (required for ISO19115-3 support)
+- Administration / Define default and a set of category per group
+- Administration / Lock user account
+
+## Bug Fixes
+
+and more \... see [3.0.3 issues](https://github.com/geonetwork/core-geonetwork/issues?page=2&q=is%3Aissue+milestone%3A3.0.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.0.3+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.0.4.md b/docs/manual/docs/overview/change-log/version-3.0.4.md
new file mode 100644
index 00000000000..ca40a952ff1
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.0.4.md
@@ -0,0 +1,15 @@
+# Version 3.0.4 {#version-304}
+
+## New features
+
+- DCAT enhancements: CSW/OAI-PMH dcat outputs.
+- Allow user to change its user details and password.
+- Allows to set all datadir paths (not only geonetwork.dir) via overrides and bean properties.
+
+## Bug Fixes
+
+- Geopublisher fixes.
+- Privileges / RegisteredUser in group A MUST not be able to edit records.
+- Saving a metadata with an empty keyword value creates invalid metadata.
+
+and more \... see [3.0.4 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.0.4+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.0.4+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.0.md b/docs/manual/docs/overview/change-log/version-3.10.0.md
new file mode 100644
index 00000000000..ef78a34f2e8
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.0.md
@@ -0,0 +1,28 @@
+# Version 3.10.0 {#version-3100}
+
+## New features/fixes
+
+- Map
+
+> - [Openlayers update](https://github.com/geonetwork/core-geonetwork/pull/4236)
+> - [Reorganize map panel](https://github.com/geonetwork/core-geonetwork/pull/4338)
+> - ESRI Rest layer can be added to the map
+
+- Editor
+
+> - [Fix bounding polygon coordinates order](https://github.com/geonetwork/core-geonetwork/issues/4255)
+
+- Admin console
+
+> - [URL checker](https://github.com/geonetwork/core-geonetwork/pull/4284)
+
+- Standards
+
+> - INSPIRE / [Add support for batch validation](https://github.com/geonetwork/core-geonetwork/pull/4308)
+> - INSPIRE / [CSW capabilities is validated by ETF](https://github.com/geonetwork/core-geonetwork/pull/4291)
+
+- Installation
+
+> - [Data directory can be stored on S3](https://github.com/geonetwork/core-geonetwork/pull/4248)
+
+and more \... see [3.10.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.0+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.1.md b/docs/manual/docs/overview/change-log/version-3.10.1.md
new file mode 100644
index 00000000000..a7e17687ef4
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.1.md
@@ -0,0 +1,8 @@
+# Version 3.10.1 {#version-3101}
+
+## New features/fixes
+
+- MEF / Fix issues on ZIP export and harvesting using GeoNetwork protocol
+- CSW / Configuration of the capabilities is now done using a service metadata record [Configuring CSW](../../administrator-guide/configuring-the-catalog/csw-configuration.md)
+
+and more \... see [3.10.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.1+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.10.md b/docs/manual/docs/overview/change-log/version-3.10.10.md
new file mode 100644
index 00000000000..3d73147382c
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.10.md
@@ -0,0 +1,13 @@
+# Version 3.10.10 {#version-31010}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] Formatter / JSONLD [Fix coordinate order in jsonld GeoShape element](https://github.com/geonetwork/core-geonetwork/pull/6071)
+
+- Other
+
+> - [BP] [Update log4j2 from from 2.7 to 2.15.0 (CVE-2021-44228)](https://github.com/geonetwork/core-geonetwork/pull/6070)
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.10.9...3.10.10)
diff --git a/docs/manual/docs/overview/change-log/version-3.10.2.md b/docs/manual/docs/overview/change-log/version-3.10.2.md
new file mode 100644
index 00000000000..ef03d355d4d
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.2.md
@@ -0,0 +1,9 @@
+# Version 3.10.2 {#version-3102}
+
+## New features/fixes
+
+- Map / Background layer / Add support for WMS group layer
+- Add post processing xslt for CSW results
+- INSPIRE / Add example for a migration from TG1.3 to 2.0
+
+and more \... see [3.10.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.2+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.3.md b/docs/manual/docs/overview/change-log/version-3.10.3.md
new file mode 100644
index 00000000000..a4786b33539
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.3.md
@@ -0,0 +1,12 @@
+# Version 3.10.3 {#version-3103}
+
+## New features/fixes
+
+- ISO19139: improvements in language management
+- ISO19139: Associated resources / Support remote datasets for operatesOn and associated records origin
+- Link analysis improvements
+- Proxy / Limit to URL host registered in records
+- Improvements in UI to unify look and feel
+- Shibboleth improvements
+
+and more \... see [3.10.3 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.3+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.4.md b/docs/manual/docs/overview/change-log/version-3.10.4.md
new file mode 100644
index 00000000000..9fca6e36427
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.4.md
@@ -0,0 +1,31 @@
+# Version 3.10.4 {#version-3104}
+
+## New features/fixes
+
+- Map viewer
+
+> - [Enhance ESRI REST API support](https://github.com/geonetwork/core-geonetwork/pull/4784)
+> - [Show error when parsing WMTS options failed](https://github.com/geonetwork/core-geonetwork/pull/4809)
+
+- Metadata
+
+> - [Group reviewers should be able do publish a metadata in their groups, even if they can't edit the record](https://github.com/geonetwork/core-geonetwork/pull/4816)
+> - Editor / [Remove the 'geonet' namespace from the metadata](https://github.com/geonetwork/core-geonetwork/pull/4825)
+> - Editor / [Keywords / Group keywords by type when not part of a thesaurus](https://github.com/geonetwork/core-geonetwork/pull/4861)
+> - INSPIRE / [Remote INSPIRE Atom feeds improvements](https://github.com/geonetwork/core-geonetwork/pull/5043)
+> - Import / [Improve error message when uploading a mef zip file](https://github.com/geonetwork/core-geonetwork/pull/4838)
+
+- Harvester
+
+> - [OGC WxS / Add WMTS basic support](https://github.com/geonetwork/core-geonetwork/pull/4829)
+> - [CSW / Fix batch edit condition](https://github.com/geonetwork/core-geonetwork/pull/4857)
+
+- Security
+
+> - [LDAP improvements](https://github.com/geonetwork/core-geonetwork/pull/4938)
+
+- User interface
+
+> - [Improvements and accesibility fixes](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.4+is%3Aclosed+is%3Apr+%5Ba11y%5D)
+
+and more \... see [3.10.4 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.4+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.4+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.5.md b/docs/manual/docs/overview/change-log/version-3.10.5.md
new file mode 100644
index 00000000000..1e8d9671a82
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.5.md
@@ -0,0 +1,32 @@
+# Version 3.10.5 {#version-3105}
+
+## New features/fixes
+
+- Metadata
+
+> - [Add missing schema translation files to prevent 404 errors](https://github.com/geonetwork/core-geonetwork/pull/5093)
+> - [JSON-LD formatter / Avoid error on multiple hierarchyLevel](https://github.com/geonetwork/core-geonetwork/pull/5109)
+> - [HTML formatter / Return 404 when the metadata doesn't exist](https://github.com/geonetwork/core-geonetwork/pull/5129)
+> - [PDF formatter / Improvements in labeling](https://github.com/geonetwork/core-geonetwork/pull/5138)
+> - [PDF formatter / Improvements in layout](https://github.com/geonetwork/core-geonetwork/pull/5139)
+> - [Update the URL of map service used to display the metadata bounding box](https://github.com/geonetwork/core-geonetwork/pull/5154)
+
+- Harvesters
+
+> - [OGC WxS / Fix protocol element](https://github.com/geonetwork/core-geonetwork/pull/5146)
+
+- User interface
+
+> - [Allow the use of Thesaurus in search page fields](https://github.com/geonetwork/core-geonetwork/pull/5086)
+
+- Security
+
+> - [Encode username value in http error responses for password recovery to prevent potential XSS](https://github.com/geonetwork/core-geonetwork/pull/5164)
+> - [Configuration option to restrict in the map services supported in map extent API's the usage of non-predefined map services](https://github.com/geonetwork/core-geonetwork/pull/5166)
+
+- Other
+
+> - [Fixes in sitemap document](https://github.com/geonetwork/core-geonetwork/pull/5148)
+> - [API / Language / Delete / Add missing source translation table](https://github.com/geonetwork/core-geonetwork/pull/5111)
+
+and more \... see [3.10.5 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.5+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.5+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.6.md b/docs/manual/docs/overview/change-log/version-3.10.6.md
new file mode 100644
index 00000000000..f1ccc6825f4
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.6.md
@@ -0,0 +1,27 @@
+# Version 3.10.6 {#version-3106}
+
+## New features/fixes
+
+- Metadata
+
+> - Workflow / [Updated validation api so that it supports working copy and fixed other validation bugs](https://github.com/geonetwork/core-geonetwork/pull/5231)
+> - Workflow / [Fix some working copy merge issues](https://github.com/geonetwork/core-geonetwork/pull/5279)
+> - INSPIRE / [Update Remote INSPIRE Atom feeds to process dataset feeds from service feeds](https://github.com/geonetwork/core-geonetwork/pull/5239)
+> - ISO19139 / [Preserve locale codes in metadata](https://github.com/geonetwork/core-geonetwork/pull/5293)
+
+- Harvesters
+
+> - [Harvester / From folder / Unable to reset XSLT once set](https://github.com/geonetwork/core-geonetwork/pull/5281)
+
+- User interface
+
+> - Accessibility / [Make the subbar on the record view accessible (by keyboard)](https://github.com/geonetwork/core-geonetwork/pull/5067)
+> - Accessibility / [Accessibility improvements for the footer](https://github.com/geonetwork/core-geonetwork/pull/5073)
+> - Accessibility / [Change language picker into dropdown](https://github.com/geonetwork/core-geonetwork/pull/5136)
+> - [Fixed broken site logo image on fresh installation](https://github.com/geonetwork/core-geonetwork/pull/5342)
+
+- Other
+
+> - [Replace Travis by Github Actions](https://github.com/geonetwork/core-geonetwork/pull/5314)
+
+and more \... see [3.10.6 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.6+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.6+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.10.7.md b/docs/manual/docs/overview/change-log/version-3.10.7.md
new file mode 100644
index 00000000000..adb55f91948
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.7.md
@@ -0,0 +1,83 @@
+# Version 3.10.7 {#version-3107}
+
+## New features/fixes
+
+- Administration
+
+> - [Create user form issues 2 requests to userselection api that return status code 400.](https://github.com/geonetwork/core-geonetwork/pull/5804)
+> - [Fix parse of logo upload in groups management when the content type includes the charset encoding](https://github.com/geonetwork/core-geonetwork/pull/5460)
+> - [Update user - verify user groups when updating a user by a UserAdmin](https://github.com/geonetwork/core-geonetwork/pull/5560)
+> - [Users without groups assigned are listed in the users lists for any UserAdmin](https://github.com/geonetwork/core-geonetwork/pull/5798)
+
+- CSW
+
+> - [Record to CSW Capabilities - extract language iso2code with twoCharLangCode function, update in date element to use the text value](https://github.com/geonetwork/core-geonetwork/pull/5400)
+
+- Editor
+
+> - [Associated resource / Feature catalog / Missing list of values](https://github.com/geonetwork/core-geonetwork/pull/5083)
+> - [Fix issue using custom UUIDs](https://github.com/geonetwork/core-geonetwork/pull/5440)
+> - [Fix regression on "Compute extents from keywords" button](https://github.com/geonetwork/core-geonetwork/pull/5455)
+> - [Fix Thumbnail generator](https://github.com/geonetwork/core-geonetwork/pull/5757)
+> - [Fix unhandled error and its xsl regular expression and root element in Schematron title translation](https://github.com/geonetwork/core-geonetwork/pull/5220)
+> - [Fix xpath to match only the main citation title, not other titles](https://github.com/geonetwork/core-geonetwork/pull/5391)
+> - ISO19115-3 / [Add option for PNG images to mcc:fileType Recommended values](https://github.com/geonetwork/core-geonetwork/pull/5456)
+> - ISO19139 / [Fix Conformity checks in INSPIRE strict rules](https://github.com/geonetwork/core-geonetwork/pull/5335)
+> - [Option to disable OGC Capabilities layer processing in the online resource panel](https://github.com/geonetwork/core-geonetwork/pull/5763)
+> - [Remove non required data-translate directive usage in gnMetadataGroupUpdater directive](https://github.com/geonetwork/core-geonetwork/pull/5490)
+> - [Updated schematron name on error messages so that it does not overlap](https://github.com/geonetwork/core-geonetwork/pull/5521)
+
+- Harvesters
+
+> - CSW / [Enable preemptive for csw requests with credentials](https://github.com/geonetwork/core-geonetwork/pull/5497)
+> - [Don't allow empty group owner in harvesters.](https://github.com/geonetwork/core-geonetwork/pull/5370)
+
+- Map viewer
+
+> - [Add a WMTS error message when the URL can't be parsed](https://github.com/geonetwork/core-geonetwork/pull/5292)
+> - [Fix map height when there is no footer](https://github.com/geonetwork/core-geonetwork/pull/5696)
+
+- Metadata
+
+> - [Fix for too small privileges popup](https://github.com/geonetwork/core-geonetwork/pull/5591)
+> - [Fix logo in record view](https://github.com/geonetwork/core-geonetwork/pull/5337)
+> - Formatter / [Avoid request check not modified as unsupported on chrome and edge](https://github.com/geonetwork/core-geonetwork/pull/5406/files)
+> - Formatter / [Fixes some challenges in google-structured-data-test](https://github.com/geonetwork/core-geonetwork/pull/5508)
+> - Formatter / [Full view doesn't work in a draft version of a metadata record](https://github.com/geonetwork/core-geonetwork/pull/5433)
+> - Formatter / [iso19139 full view - codelist elements - display the codelistValue translation only if the element has a text also](https://github.com/geonetwork/core-geonetwork/pull/5793)
+> - Import / [Generic error message in 'Upload a file from URL'](https://github.com/geonetwork/core-geonetwork/pull/5553)
+> - [Index temporal extent period, fix multiple temporal extent display in the metadata detail page](https://github.com/geonetwork/core-geonetwork/pull/5485)
+> - INSPIRE / [Update the filter for INSPIRE Atom dataset feed to support the remote operatesOn indexing format](https://github.com/geonetwork/core-geonetwork/pull/5816)
+> - INSPIRE / [Retrieve INSPIRE Atom feed language from self link element instead of the feed language attribute that is optional](https://github.com/geonetwork/core-geonetwork/pull/5435)
+> - INSPIRE / [INSPIRE geometry fields lead to 0 results in opensearch](https://github.com/geonetwork/core-geonetwork/pull/5434)
+> - INSPIRE / [Atom fixes: filter metadata with schemas based on iso19139 and atom feed parse](https://github.com/geonetwork/core-geonetwork/pull/5472)
+> - INSPIRE / [Local INSPIRE Atom feed xslt fix for resource constraints with multiple gmd:otherConstraints elements](https://github.com/geonetwork/core-geonetwork/pull/5815)
+> - [Remove schema-org annotations from list pages](https://github.com/geonetwork/core-geonetwork/pull/5412)
+> - [Update getMdObjByUuid to use the draft information in the metadata when the workflow is enabled](https://github.com/geonetwork/core-geonetwork/pull/5344)
+> - [Update message if metadata is not found](https://github.com/geonetwork/core-geonetwork/pull/5384)
+> - [Update Thesaurus keywords to ISO19115-3.2018](https://github.com/geonetwork/core-geonetwork/pull/5458)
+> - [Use the configured CSW Service metadata to fill the meta headers for description / keywords for the html content](https://github.com/geonetwork/core-geonetwork/pull/5447)
+> - Workflow / [Bulk publish cancels working copy](https://github.com/geonetwork/core-geonetwork/pull/5420)
+> - Workflow / [Fix draft metadata manager update method to check if should be applied to the draft metadata or the published metadata](https://github.com/geonetwork/core-geonetwork/pull/5470)
+> - Workflow / [Fix for validation result gets lost when approving record and copy validation results when creating a draft.](https://github.com/geonetwork/core-geonetwork/pull/5418)
+> - Workflow / [Search results - metadata with a working copy display a label 'Working copy' if the metadata has a draft copy, even for public users.](https://github.com/geonetwork/core-geonetwork/pull/5805)
+
+- Other
+
+> - [Fixes embedded Cross-Site Scripting issues](https://github.com/geonetwork/core-geonetwork/pull/5551)
+> - [Kibana / Only allow access to authenticated users in the catalog](https://github.com/geonetwork/core-geonetwork/pull/5005)
+> - [Log transaction manager notification failures](https://github.com/geonetwork/core-geonetwork/pull/5408)
+> - [Manage url redirects with URL.openConnection](https://github.com/geonetwork/core-geonetwork/pull/5512)
+> - [Protect AccessManager code using user session](https://github.com/geonetwork/core-geonetwork/pull/5365)
+> - [Reset password service fixes/improvements](https://github.com/geonetwork/core-geonetwork/pull/5371)
+> - [Stream attachments to the browser without reading them first](https://github.com/geonetwork/core-geonetwork/pull/5462)
+> - Update doc url to point to 3.10.x documentation
+> - [Update ZipUtil.java to use tempFile configuration to avoid memory issue](https://github.com/geonetwork/core-geonetwork/pull/5526)
+> - [Use maven major, minor, patch, build, qualifier definition for version](https://github.com/geonetwork/core-geonetwork/pull/5451)
+> - [Use \$translateProvider.useSanitizeValueStrategy('escapeParameters') for encoding sanitizing](https://github.com/geonetwork/core-geonetwork/pull/5461)
+
+- User interface
+
+> - [Add confirm to delete Category and Cancel edits to metadata](https://github.com/geonetwork/core-geonetwork/pull/5813)
+> - One styling for all scrollbars and increase the width/height
+> - [Use button to recover the password](https://github.com/geonetwork/core-geonetwork/pull/5478)
diff --git a/docs/manual/docs/overview/change-log/version-3.10.8.md b/docs/manual/docs/overview/change-log/version-3.10.8.md
new file mode 100644
index 00000000000..105c9921ca8
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.8.md
@@ -0,0 +1,41 @@
+# Version 3.10.8 {#version-3108}
+
+## New features/fixes
+
+- Administration
+
+> - [BP] Admin / Users / [Fix the users that a UserAdmin can manage](https://github.com/geonetwork/core-geonetwork/pull/5886)
+
+- Editor
+
+> - Dublin core / Editor / [Fix autocomplete for subtemplates](https://github.com/geonetwork/core-geonetwork/pull/5965)
+> - [BP] [Fix for indenting the 'multientry combiner'](https://github.com/geonetwork/core-geonetwork/pull/5764)
+> - [BP] [Add a new directive for combining add online resource fields](https://github.com/geonetwork/core-geonetwork/pull/5559)
+> - [BP] [Fix editing of directory entries templates #5936](https://github.com/geonetwork/core-geonetwork/pull/5937)
+> - [BP] [Display topic categories tooltip in the metadata editor when tooltips are enabled](https://github.com/geonetwork/core-geonetwork/pull/5935)
+> - [BP] [Remove online resource - fix resource name comparison](https://github.com/geonetwork/core-geonetwork/pull/5934)
+
+- Metadata
+
+> - [BP] [Fix rdf export for iso19139 metadata with multilingual online resources name element](https://github.com/geonetwork/core-geonetwork/pull/5956)
+> - [BP] [Update iso19139 template for uuidref attribute to apply only for srv:operatesOn element](https://github.com/geonetwork/core-geonetwork/pull/5924)
+> - [BP] [Process data feed download links with multiple download files/links per datafeed entry](https://github.com/geonetwork/core-geonetwork/pull/5985)
+> - [BP] [Fix dates xpath in iso19139 export to jsonld](https://github.com/geonetwork/core-geonetwork/pull/5990)
+> - [BP] Fixes resource links if multilingual fixes feature-catalog indexing in iso19115-3
+> - [BP] [Fix duplicate string in normalize-space, if record both has a title as well as identifier has a citation with title](https://github.com/geonetwork/core-geonetwork/pull/5830)
+
+- User interface
+
+> - [BP] [Configure how to extract the WMS layer name from metadata online resources to add them to the map viewer](https://github.com/geonetwork/core-geonetwork/pull/5998)
+
+- Other
+
+> - [BP] [Updated default language so that is comes from common java location.](https://github.com/geonetwork/core-geonetwork/pull/5981)
+> - [BP] [Fix a bug when the url doesn't contain the ? sign](https://github.com/geonetwork/core-geonetwork/pull/5994)
+> - [BP] [Formatter / Datacite / Avoid empty elements.](https://github.com/geonetwork/core-geonetwork/pull/5500)
+> - [BP] Formatter / Datacite / Fix multiple geoLocations.
+> - [BP] Datacite / XSD validation / valueUri is valueURI.
+
+and more \... see [3.10.8 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.8+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.8+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.10.7...3.10.8)
diff --git a/docs/manual/docs/overview/change-log/version-3.10.9.md b/docs/manual/docs/overview/change-log/version-3.10.9.md
new file mode 100644
index 00000000000..45b0fbe9a18
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.10.9.md
@@ -0,0 +1,33 @@
+# Version 3.10.9 {#version-3109}
+
+## New features/fixes
+
+- Administration
+
+> - [BP] [Fix credentials autocomplete in harvesters](https://github.com/geonetwork/core-geonetwork/pull/6011)
+
+- Editor
+- Metadata
+
+> - [BP] [DOI improvements](https://github.com/geonetwork/core-geonetwork/pull/6034)
+> - [BP] [Reset search parameter after metadata status change to "approved"](https://github.com/geonetwork/core-geonetwork/pull/5970)
+> - [BP] [INSPIRE / Validation / Add API Key](https://github.com/geonetwork/core-geonetwork/pull/5978)
+
+- Map viewer
+
+> - [Fix for the print bug with annotations on map](https://github.com/geonetwork/core-geonetwork/pull/6008)
+> - [BP] [Fix check for layer already in map](https://github.com/geonetwork/core-geonetwork/pull/6031)
+
+- User interface
+
+> - [BP] [Remove the htmlEncode part for the label, this htmlEncode puts 'url safe' characters in the label. Fir instance 'Maps & graphics' turns into 'Maps & graphics'](https://github.com/geonetwork/core-geonetwork/pull/6038)
+
+- Other
+
+> - [BP] [Encode user interface view parameter](https://github.com/geonetwork/core-geonetwork/pull/6030)
+> - [BP] [Update Jsoup library](https://github.com/geonetwork/core-geonetwork/pull/6057)
+> - Update transifex translations
+
+and more \... see [3.10.8 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.10.9+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.10.9+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.10.8...3.10.9)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.0.md b/docs/manual/docs/overview/change-log/version-3.12.0.md
new file mode 100644
index 00000000000..8270fb436b8
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.0.md
@@ -0,0 +1,34 @@
+# Version 3.12.0 {#version-3120}
+
+## New features/fixes
+
+- Metadata
+
+> - Workflow / [Bulk metadata approval](https://github.com/geonetwork/core-geonetwork/pull/5430)
+> - [Allow to restore a metadata record from deleted records](https://github.com/geonetwork/core-geonetwork/pull/4817)
+> - [ISO19110 / View / Display feature cat in associated resources](https://github.com/geonetwork/core-geonetwork/pull/5584)
+
+- Harvesters
+
+> - [Harvester timezone setting](https://github.com/geonetwork/core-geonetwork/pull/4576)
+> - [Add a localized time format in harvester logs](https://github.com/geonetwork/core-geonetwork/pull/4900)
+> - [Support WAF with authentication](https://github.com/geonetwork/core-geonetwork/pull/5422)
+
+- User interface
+ - Accessibility / [Add a new accessible menubar: clickable and keyboard accessible](https://github.com/geonetwork/core-geonetwork/pull/5518)
+- Map viewer
+
+> - [Fix for polar extents](https://github.com/geonetwork/core-geonetwork/pull/5142)
+
+- Other
+
+> - Data directory / [Support for CMIS](https://github.com/geonetwork/core-geonetwork/pull/5118)
+> - Security / [Reset password service fixes/improvements](https://github.com/geonetwork/core-geonetwork/pull/5371)
+> - Security / [Support for Keycloak](https://github.com/geonetwork/core-geonetwork/pull/4931)
+> - Security / [Encrypt passwords stored in the database](https://github.com/geonetwork/core-geonetwork/pull/5476)
+> - Security / [Restrict username / group name characters enhancement](https://github.com/geonetwork/core-geonetwork/pull/5505)
+> - Memory / [Stream attachments to the browser without loading them in memory](https://github.com/geonetwork/core-geonetwork/pull/5462)
+> - Memory / [ServiceContext resource leak](https://github.com/geonetwork/core-geonetwork/pull/5260)
+> - [Upgrade to GeoTools 24.0 and JTS 1.17.1](https://github.com/geonetwork/core-geonetwork/pull/5007)
+
+and more \... see [3.12.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.0+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.12.1.md b/docs/manual/docs/overview/change-log/version-3.12.1.md
new file mode 100644
index 00000000000..ca2822fae9d
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.1.md
@@ -0,0 +1,38 @@
+# Version 3.12.1 {#version-3121}
+
+## New features/fixes
+
+- Metadata
+
+> - Editor / [Metadata editor - option to disable OGC Capabilities layer processing in the online resource panel](https://github.com/geonetwork/core-geonetwork/pull/5763)
+> - Editor / [Fix Thumbnail generator](https://github.com/geonetwork/core-geonetwork/pull/5757)
+> - Editor / [Overview / Removal / Do not delete attachment from other records](https://github.com/geonetwork/core-geonetwork/pull/5821)
+> - INSPIRE / [Update the filter for INSPIRE Atom dataset feed to support the remote operatesOn indexing format](https://github.com/geonetwork/core-geonetwork/pull/5816)
+> - [ISO19110 / View / Display feature cat in associated resources](https://github.com/geonetwork/core-geonetwork/pull/5584)
+> - Metadata status / [Add salutation to notification message](https://github.com/geonetwork/core-geonetwork/pull/5686)
+> - Privileges / [Fix replace privileges with editor users](https://github.com/geonetwork/core-geonetwork/pull/5828)
+> - Search / [Metadata with a working copy display a label 'Working copy' if the metadata has a draft copy for public users](https://github.com/geonetwork/core-geonetwork/pull/5805)
+
+- User interface
+
+> - [Add a Bootstrap layout and column to a static page](https://github.com/geonetwork/core-geonetwork/pull/5843)
+> - [Add a scrollbar to the privileges popup when group names are too long](https://github.com/geonetwork/core-geonetwork/pull/5799)
+> - [Add isoLang variable to Application URL setting](https://github.com/geonetwork/core-geonetwork/pull/5642)
+
+- Map viewer
+
+> - [Add settings and styling for the map height when there is no footer](https://github.com/geonetwork/core-geonetwork/pull/5696)
+
+- Administration
+
+> - [Add confirmation to delete Category and Cancel edits to metadata](https://github.com/geonetwork/core-geonetwork/pull/5813)
+> - [Users without groups assigned are listed in the users lists for any UserAdmin](https://github.com/geonetwork/core-geonetwork/pull/5798)
+
+- Other
+
+> - CMIS / [Add copy resource interface, implement cmis resource copy with additional properties](https://github.com/geonetwork/core-geonetwork/pull/5776)
+> - CMIS / [Fixed CMIS resource bug where the wrong key function was called causing an invalid key to be generated](https://github.com/geonetwork/core-geonetwork/pull/5775)
+> - Keycloak / [Fix csrf token when integrated with keycloak](https://github.com/geonetwork/core-geonetwork/pull/5672)
+> - Keycloak / [User Profile Readonly for keycloak users](https://github.com/geonetwork/core-geonetwork/pull/5769)
+
+and more \... see [3.12.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.1+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.12.10.md b/docs/manual/docs/overview/change-log/version-3.12.10.md
new file mode 100644
index 00000000000..50ea29d161b
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.10.md
@@ -0,0 +1,18 @@
+# Version 3.12.10 {#version-31210}
+
+## New features/fixes
+
+- Metadata
+ - [BP] [Metadata editor / fix disable link to parent button](https://github.com/geonetwork/core-geonetwork/pull/7045)
+ - [BP] [Metadata editor / Use created, modified, issued date from thesaurus when adding keywords](https://github.com/geonetwork/core-geonetwork/pull/6972)
+ - [BP] [Update publish link so that it is disabled if the metadata has not been approved](https://github.com/geonetwork/core-geonetwork/pull/7009)
+ - [BP] [Update validation report to include more information in the report](https://github.com/geonetwork/core-geonetwork/pull/6900)
+- Other
+ - [BP] [Cmis performance enhancements](https://github.com/geonetwork/core-geonetwork/pull/6893)
+ - [BP] [Update password min length check](https://github.com/geonetwork/core-geonetwork/pull/6953)
+ - [Update Geotools to v24.7](https://github.com/geonetwork/core-geonetwork/pull/6926)
+ - [reload4j drop-in replacement for Log4J 1.2 API](https://github.com/geonetwork/core-geonetwork/pull/6896)
+
+and more \... see [3.12.10 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.10+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.10+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.9...3.12.10)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.11.md b/docs/manual/docs/overview/change-log/version-3.12.11.md
new file mode 100644
index 00000000000..703c22d001e
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.11.md
@@ -0,0 +1,16 @@
+# Version 3.12.11 {#version-31211}
+
+## New features/fixes
+
+- Metadata
+ - [BP] [Fix working copy display so that links go to working copy](https://github.com/geonetwork/core-geonetwork/pull/7279)
+ - [BP] [Record view / Add support for emails with subdomains](https://github.com/geonetwork/core-geonetwork/pull/7314)
+ - [BP] [Batch Editing access level in general system settings](https://github.com/geonetwork/core-geonetwork/pull/7238)
+
+- Other
+ - [BP] [Fix `robots.txt` and sitemap 500 errors if no right content type is provided](https://github.com/geonetwork/core-geonetwork/pull/7327)
+
+
+and more \... see [3.12.11 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.11+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.11+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.10...3.12.11)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.2.md b/docs/manual/docs/overview/change-log/version-3.12.2.md
new file mode 100644
index 00000000000..075f99e28dd
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.2.md
@@ -0,0 +1,37 @@
+# Version 3.12.2 {#version-3122}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] Formatter / JSONLD [Fix coordinate order in jsonld GeoShape element](https://github.com/geonetwork/core-geonetwork/pull/6071)
+> - [BP] [INSPIRE / Validation / Add API Key](https://github.com/geonetwork/core-geonetwork/pull/5978)
+> - Workflow / [Improve workflow process facet in editor board](https://github.com/geonetwork/core-geonetwork/pull/5991)
+> - [BP] Workflow / [Metadata retired status support](https://github.com/geonetwork/core-geonetwork/pull/5943)
+> - [BP] [DOI improvements](https://github.com/geonetwork/core-geonetwork/pull/6034)
+> - [Fix editing of directory entries templates](https://github.com/geonetwork/core-geonetwork/pull/5937)
+
+- Map viewer
+
+> - [BP] [Configuration option to restrict the map services supported in map extent API (geom.png) the usage of non-predefined map services](https://github.com/geonetwork/core-geonetwork/pull/6045)
+> - [BP] [Configure how to extract the WMS layer name from metadata online resources to add them to the map viewer](https://github.com/geonetwork/core-geonetwork/pull/5998)
+> - [BP] [Fix check for layer already in map](https://github.com/geonetwork/core-geonetwork/pull/6031)
+
+- Administration
+
+> - [BP] [Confirm dialog when deleting users / groups](https://github.com/geonetwork/core-geonetwork/pull/6070)
+> - [BP] [Confirm dialog when deleting a logo](https://github.com/geonetwork/core-geonetwork/pull/6069)
+> - [BP] [Harvesters / Fix credentials autocomplete in harvesters](https://github.com/geonetwork/core-geonetwork/pull/6011)
+
+- Other
+
+> - [BP] [Encode user interface view parameter](https://github.com/geonetwork/core-geonetwork/pull/6030)
+> - [BP] [Encryption / Application fails to start if encryption error on harvester passwords](https://github.com/geonetwork/core-geonetwork/pull/5859)
+> - [Rollback exceptions handled in GlobalExceptionController](https://github.com/geonetwork/core-geonetwork/pull/5948)
+> - [BP] [Update Jsoup library](https://github.com/geonetwork/core-geonetwork/pull/6057)
+> - [BP] [Update log4j2 from from 2.7 to 2.15.0 (CVE-2021-44228)](https://github.com/geonetwork/core-geonetwork/pull/6070)
+> - [BP] [Use the Map projection Region API setting in Regions/geometry related services](https://github.com/geonetwork/core-geonetwork/pull/6050)
+
+and more \... see [3.12.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.2+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.1...3.12.2)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.3.md b/docs/manual/docs/overview/change-log/version-3.12.3.md
new file mode 100644
index 00000000000..b6e5e8c3f15
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.3.md
@@ -0,0 +1,31 @@
+# Version 3.12.3 {#version-3123}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] [DOI - add identifier / online resource url using the DOI proxy url](https://github.com/geonetwork/core-geonetwork/pull/6124)
+> - [BP] [Error message JSON path fixes in Editor Angular Controllers](https://github.com/geonetwork/core-geonetwork/pull/6029)
+> - [Metadata workflow - publish an approved record with a draft copy, publishes the draft copy](https://github.com/geonetwork/core-geonetwork/pull/5557)
+
+- Map viewer
+
+> - [BP] [Enable to display map in left column of search UI](https://github.com/geonetwork/core-geonetwork/pull/6080)
+
+- Administration
+
+> - [BP] [Confirmation dialog to delete an UI configuration](https://github.com/geonetwork/core-geonetwork/pull/6092)
+> - [BP] [Don't allow to delete a group if owns metadata](https://github.com/geonetwork/core-geonetwork/pull/6072)
+> - [BP] [Fix removal of sort by and hits per page elements in the UI configuration](https://github.com/geonetwork/core-geonetwork/pull/6091)
+> - [BP] [Sort groups and users in transfer ownership](https://github.com/geonetwork/core-geonetwork/pull/6093)
+
+- Other
+
+> - [BP] [Bump log4j2 2.17.1](https://github.com/geonetwork/core-geonetwork/pull/6110)
+> - [BP] [Formatter - remove debug mode](https://github.com/geonetwork/core-geonetwork/pull/6127)
+> - [BP] [Update libs reported by github security](https://github.com/geonetwork/core-geonetwork/pull/6120)`
+> - [Update translations](https://github.com/geonetwork/core-geonetwork/pull/6111)
+
+and more \... see [3.12.3 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.3+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.2...3.12.3)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.4.md b/docs/manual/docs/overview/change-log/version-3.12.4.md
new file mode 100644
index 00000000000..6433129b7da
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.4.md
@@ -0,0 +1,25 @@
+# Version 3.12.4 {#version-3124}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] [Don't allow transfer ownership to reserved groups](https://github.com/geonetwork/core-geonetwork/pull/6193)
+> - [BP] [Fix the thumbnail generator using the metadata view services for metadata working copies](https://github.com/geonetwork/core-geonetwork/pull/6179)
+> - [BP] [Use typeNames in the WFS URL when version is >= "2.0.0"](https://github.com/geonetwork/core-geonetwork/pull/6143)
+
+- Administration
+
+> - [BP] [Harvester of type Geonetwork using MEF format doesn't update the server in the online resource links for uploaded files/thumbnails](https://github.com/geonetwork/core-geonetwork/pull/6231)
+> - [BP] [Preserve harvester last run date when updating the harvester configuration](https://github.com/geonetwork/core-geonetwork/pull/6166)
+> - [Harvester / CSW / Add sortby option](https://github.com/geonetwork/core-geonetwork/pull/6223)
+
+- Other
+
+> - [BP] [Configure HttpOnly for session timeout cookies and fix the cookie path](https://github.com/geonetwork/core-geonetwork/pull/6163)
+> - [BP] [Fix issue with CMIS connection during startup](https://github.com/geonetwork/core-geonetwork/pull/6106)
+> - [BP] [Fix issue with getting keycloak token from upgraded security context](https://github.com/geonetwork/core-geonetwork/pull/6207)
+
+and more \... see [3.12.4 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.4+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.4+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.3...3.12.4)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.5.md b/docs/manual/docs/overview/change-log/version-3.12.5.md
new file mode 100644
index 00000000000..0714c32ce05
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.5.md
@@ -0,0 +1,24 @@
+# Version 3.12.5 {#version-3125}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] [Metadata workflow: metadata save and submit was displaying the metadata in a wrong status](https://github.com/geonetwork/core-geonetwork/pull/6299)
+> - [BP] [Metadata workflow: fix save and approve action in the metadata editor, that wasn't replacing the approved version with the working copy changes](https://github.com/geonetwork/core-geonetwork/pull/6313)
+> - [BP] [Remote ATOM feeds: fix atom describe output to remove a wrong empty namespace in some elements](https://github.com/geonetwork/core-geonetwork/pull/6288)
+> - [BP] [Metadata workflow: cancelling the metadata editor when editing a working copy always removes the working copy](https://github.com/geonetwork/core-geonetwork/pull/6295)
+> - [BP] [Cancelling from import or add new record results in a blank editor board](https://github.com/geonetwork/core-geonetwork/pull/6274)
+
+- Administration
+
+> - [BP] [Admin / Password reset by admin](https://github.com/geonetwork/core-geonetwork/pull/6235)
+> - [BP] [Configuration of the user profile authorized to import metadata.](https://github.com/geonetwork/core-geonetwork/pull/6200)
+
+- Other
+
+> - [BP] [Ensure that keycloak login redirects only go the current server](https://github.com/geonetwork/core-geonetwork/pull/6270)
+
+and more \... see [3.12.5 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.5+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.5+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.4...3.12.5)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.6.md b/docs/manual/docs/overview/change-log/version-3.12.6.md
new file mode 100644
index 00000000000..67d861b8dbd
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.6.md
@@ -0,0 +1,24 @@
+# Version 3.12.6 {#version-3126}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] [Support custom map configuration to generate map thumbnails](https://github.com/geonetwork/core-geonetwork/pull/6410)
+> - [BP] [Configure the user profile allowed to delete published metadata](https://github.com/geonetwork/core-geonetwork/pull/6398)
+
+- Map viewer
+
+> - [BP] [Support context map files per UI language](https://github.com/geonetwork/core-geonetwork/pull/6275)
+
+- Administration
+
+> - [BP] [Harvesters / GeoNetwork harvester / Re-add exiting files when re-harvesting](https://github.com/geonetwork/core-geonetwork/pull/6416)
+
+- Other
+
+> - [BP] [Switch from iText to OpenPDF for PDF map rendering](https://github.com/geonetwork/core-geonetwork/pull/6392)
+
+and more \... see [3.12.6 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.6+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.6+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.5...3.12.6)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.7.md b/docs/manual/docs/overview/change-log/version-3.12.7.md
new file mode 100644
index 00000000000..09f51329f41
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.7.md
@@ -0,0 +1,29 @@
+# Version 3.12.7 {#version-3127}
+
+## New features/fixes
+
+- Metadata
+
+> - [BP] [Fix inconsistent metadata status when requesting the DOI publication after the metadata approval and publication](https://github.com/geonetwork/core-geonetwork/pull/6505)
+> - [BP] [Metadata import - store the validation status when the validation option is selected](https://github.com/geonetwork/core-geonetwork/pull/6444)
+> - [BP] [Record view / Full / Display temporal range using gml:end/begin element](https://github.com/geonetwork/core-geonetwork/pull/6510)
+> - [BP] [Add OGC API protocols support for online resources](https://github.com/geonetwork/core-geonetwork/pull/6477)
+
+- User interface
+
+> - [BP] [Adjust side bar thickness to 12px](https://github.com/geonetwork/core-geonetwork/pull/6293)
+
+- Administration
+
+> - [BP] [Configuration option to display the application version and links to the About, GitHub and API pages in the footer](https://github.com/geonetwork/core-geonetwork/pull/6436)
+
+- Other
+
+> - [BP] [Keycloak client upgrade to 18.0.2](https://github.com/geonetwork/core-geonetwork/pull/6531)
+> - [BP] [Add validation status to cmis store and configuration](https://github.com/geonetwork/core-geonetwork/pull/6511)
+> - [BP] [Enable server hostname verification on this SSL/TLS connection](https://github.com/geonetwork/core-geonetwork/pull/6403)
+> - [BP] [Move messages property files to web module](https://github.com/geonetwork/core-geonetwork/pull/6508)
+
+and more \... see [3.12.7 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.7+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.7+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.6...3.12.7)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.8.md b/docs/manual/docs/overview/change-log/version-3.12.8.md
new file mode 100644
index 00000000000..24a7e2406dc
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.8.md
@@ -0,0 +1,30 @@
+# Version 3.12.8 {#version-3128}
+
+## New features/fixes
+
+- Metadata
+ - [BP] [Support for a process to update the metadata content when creating a duplicate](https://github.com/geonetwork/core-geonetwork/pull/6507)
+ - [BP] [Configuration to notify by mail about metadata publication / unpublication](https://github.com/geonetwork/core-geonetwork/pull/6457)
+ - [BP] [RDF export: Encode spaces in foaf:thumbnail urls and update geometry field](https://github.com/geonetwork/core-geonetwork/pull/6586)
+- User interface
+
+> - [BP] [Update bootstrap from 3.3.7 to 3.4.1](https://github.com/geonetwork/core-geonetwork/pull/6634)
+> - [BP] [Update bootstrap-table to v1.21.1](https://github.com/geonetwork/core-geonetwork/pull/6636)
+> - [BP] [Update moment to version 2.29.4](https://github.com/geonetwork/core-geonetwork/pull/6577)
+
+- Administration
+
+> - [BP] [Thesaurus / Import from Re3gistry failing](https://github.com/geonetwork/core-geonetwork/pull/6617)
+> - [BP] [Only allow Administrator users delete the UI settings for the default UI](https://github.com/geonetwork/core-geonetwork/pull/6639)
+> - [BP] [Harvesters - display the button to assign the harvested records to the local node only to 'Administrator' users](https://github.com/geonetwork/core-geonetwork/pull/6591)
+> - [BP] [Prevents browser from auto-completing proxy password in admin console](https://github.com/geonetwork/core-geonetwork/pull/6480)
+
+- Other
+
+> - [BP] [Check the signout redirect url](https://github.com/geonetwork/core-geonetwork/pull/6666)
+> - [BP] [Security / Update Site API](https://github.com/geonetwork/core-geonetwork/pull/6569)
+> - [BP] [Remove httpOnly from session timeout cookies](https://github.com/geonetwork/core-geonetwork/pull/6570)
+
+and more \... see [3.12.8 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.8+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.8+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.7...3.12.8)
diff --git a/docs/manual/docs/overview/change-log/version-3.12.9.md b/docs/manual/docs/overview/change-log/version-3.12.9.md
new file mode 100644
index 00000000000..68b456e29c0
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.12.9.md
@@ -0,0 +1,18 @@
+# Version 3.12.9 {#version-3129}
+
+## New features/fixes
+
+- Metadata
+ - [Fix indexing of resource date month / year in iso19139 and iso19115.3-2008 schemas](https://github.com/geonetwork/core-geonetwork/pull/6873)
+ - [BP] [ISO19115-3 / Metadata editor / Support gex:EX_BoundingPolygon with multiple gex:polygon elements](https://github.com/geonetwork/core-geonetwork/pull/6815)
+ - [BP] [API / User feedback only allowed on record user can view](https://github.com/geonetwork/core-geonetwork/pull/6781)
+- Map viewer
+ - [BP] [When identifying on a layer from a metadata with a linked feature catalog record, use case insensitive comparison between the feature catalog column definitions and the WMS FeatureInfo response](https://github.com/geonetwork/core-geonetwork/pull/6802)
+- Other
+ - [BP] [KeyCloak / set the user profile retrieved from KeyCloak only for new users or if the configuration option KEYCLOACK_UPDATEPROFILE is enabled](https://github.com/geonetwork/core-geonetwork/pull/6871)
+ - [BP] [Workflow / Restrict search by status to record that user can edit](https://github.com/geonetwork/core-geonetwork/pull/6889)
+ - [BP] [Update userapi so that it will allow administrators to pre-create/update user profile information when using service provider](https://github.com/geonetwork/core-geonetwork/pull/6712)
+
+and more \... see [3.12.9 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.12.9+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.12.9+is%3Aclosed+is%3Apr) for full details.
+
+**Full Changelog**: [here](https://github.com/geonetwork/core-geonetwork/compare/3.12.8...3.12.9)
diff --git a/docs/manual/docs/overview/change-log/version-3.2.0.md b/docs/manual/docs/overview/change-log/version-3.2.0.md
new file mode 100644
index 00000000000..177322705f9
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.2.0.md
@@ -0,0 +1,25 @@
+# Version 3.2.0 {#version-320}
+
+## New requirements
+
+- This release requires the use of Java 8, and is compatible with both Oracle JDK and Open JDK.
+
+## New features
+
+- WFS feature indexing (see [WFS GetFeature Harvesting](../../user-guide/harvesting/harvesting-wfs-features.md))
+- A new REST API (beta) is available. The documentation is available
+- User feedback form
+- Editor / Associated resources can be updated without the advanced view
+- Editor / Filter contact directory with facets
+- Editor / XML view provides code editing with syntax highlighting and more, \...
+- Directories can be populated from catalog content
+- Metadata import improved (import by URL, import multiple files at once, better error reports)
+- GeoServer updated to [version 2.9.0](https://geoserver.org/)
+- Added schema.org tags for better indexing by search engine
+
+## Removed features
+
+- ExtJS user interface removed
+- Z39.50 server removed (SRU support still available)
+
+and more \... see [3.2.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.2.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.2.0+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.2.1.md b/docs/manual/docs/overview/change-log/version-3.2.1.md
new file mode 100644
index 00000000000..431df9ab06e
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.2.1.md
@@ -0,0 +1,11 @@
+# Version 3.2.1 {#version-321}
+
+This is a maintenance release with [lots of bug fixed](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+is%3Aclosed+milestone%3A3.2.1) and some new features:
+
+- Add multiple parallel selection support
+- [Add CORS header configuration](https://github.com/geonetwork/core-geonetwork/pull/1748)
+- Editor / [User can configure table layout](https://github.com/geonetwork/core-geonetwork/pull/1635)
+- RDF / [URI prefix can be customized and records URI resolves](https://github.com/geonetwork/core-geonetwork/pull/1616)
+- Processing / Add capability to preview process results
+
+and more \... see [3.2.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.2.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.2.1+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.2.2.md b/docs/manual/docs/overview/change-log/version-3.2.2.md
new file mode 100644
index 00000000000..36a4d7c8251
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.2.2.md
@@ -0,0 +1,11 @@
+# Version 3.2.2 {#version-322}
+
+This is a maintenance release with [lots of bug fixed](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+is%3Aclosed+milestone%3A3.2.2) and some new features:
+
+- [CSRF token support](https://github.com/geonetwork/core-geonetwork/pull/1967)
+- [Fixes for Oracle DB](https://github.com/geonetwork/core-geonetwork/pull/1968)
+- Harvester / [Support for ArcSDE direct connection](https://github.com/geonetwork/core-geonetwork/pull/1945)
+- Remove duplicated postgres driver
+- HTTP requests / connection not released
+
+and more \... see [3.2.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.2.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.2.2+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.4.0.md b/docs/manual/docs/overview/change-log/version-3.4.0.md
new file mode 100644
index 00000000000..ff3ff9fd0ab
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.4.0.md
@@ -0,0 +1,23 @@
+# Version 3.4.0 {#version-340}
+
+## New features
+
+- User interface configuration in the admin page and [JS client API](https://github.com/geonetwork/core-geonetwork/pull/1848)
+- Multilingual support now available for [thesaurus admin](https://github.com/geonetwork/core-geonetwork/pull/2094), subtemplates and URL. Improved ISO19139 indexing.
+- [Catalogue your maps easily](https://github.com/geonetwork/core-geonetwork/pull/2081)
+- [Basket & user saved selection support](https://github.com/geonetwork/core-geonetwork/pull/1920)
+- Editor / Support for polygon encoding
+- Editor / Better local XLink support
+- Editor / Add a virtual all thesaurus to easily pick up keywords from all thesaurus
+- Editor / Support for extent and format subtemplate
+- Editor / Improved configuration (eg. sidepanel, embedded directive, \...)
+- Subtemplate / [Init extent subtemplate from shapefiles](https://github.com/geonetwork/core-geonetwork/pull/2096)
+- Subtemplate can now have a validation status
+- Dashboards and statistics are now using Elasticsearch & Kibana
+- [WFS feature indexing using Elasticsearch](https://github.com/geonetwork/core-geonetwork/pull/1981)
+- Fix sitemap memory issue
+- and lots of improvements in the user interface
+
+## Removed features
+
+and more \... see [3.4.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.4.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.4.0+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.4.1.md b/docs/manual/docs/overview/change-log/version-3.4.1.md
new file mode 100644
index 00000000000..a02b3854b05
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.4.1.md
@@ -0,0 +1,7 @@
+# Version 3.4.1 {#version-341}
+
+## New features
+
+## Removed features
+
+and more \... see [3.4.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.4.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.4.1+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.4.2.md b/docs/manual/docs/overview/change-log/version-3.4.2.md
new file mode 100644
index 00000000000..687f225c7c6
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.4.2.md
@@ -0,0 +1,16 @@
+# Version 3.4.2 {#version-342}
+
+## New features/fixes
+
+- User feedback () and additional improvements (, , )
+- Editor / [Topic category widget should look like keywords](https://github.com/geonetwork/core-geonetwork/pull/2615).
+- Editor / [INSPIRE JRC validation](https://github.com/geonetwork/core-geonetwork/pull/2444)
+- Editor / [INSPIRE view improvements](https://github.com/geonetwork/core-geonetwork/pull/2461)
+- XSL processing / [Preview mode / Return error report](https://github.com/geonetwork/core-geonetwork/pull/2620).
+- ISO19139 / [Improve feature catalogs in metadata](https://github.com/geonetwork/core-geonetwork/pull/2333)
+- [Fixes to WFS indexing & filtering](https://github.com/geonetwork/core-geonetwork/pull/2512)
+- Map viewer / [Allow to customize gazetteer](https://github.com/geonetwork/core-geonetwork/pull/2690)
+- [Support MEF in LocalFilesystemHarvester](https://github.com/geonetwork/core-geonetwork/pull/2667)
+- [Fix deadlock threads while indexing](https://github.com/geonetwork/core-geonetwork/pull/2740)
+
+and more \... see [3.4.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.4.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.4.2+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.4.3.md b/docs/manual/docs/overview/change-log/version-3.4.3.md
new file mode 100644
index 00000000000..91054e93b12
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.4.3.md
@@ -0,0 +1,14 @@
+# Version 3.4.3 {#version-343}
+
+## New features/fixes
+
+- INSPIRE / [INSPIRE / Add support to load codelists from Registry](https://github.com/geonetwork/core-geonetwork/pull/2741)
+- XSL processing / [Formatter / Schema resources are not properly loaded](https://github.com/geonetwork/core-geonetwork/pull/2979)
+- XSL processing / [Formatter / XSLT / Break work with some hardcoded rules](https://github.com/geonetwork/core-geonetwork/pull/2960)
+- Editor / [Topic categories widget doesn't work with schemas based in iso19139](https://github.com/geonetwork/core-geonetwork/pull/2954)
+- Editor / [ISO19110 / producer does not use directory](https://github.com/geonetwork/core-geonetwork/pull/2944).
+- Harvesters / [Harvesting wps2.0.0](https://github.com/geonetwork/core-geonetwork/pull/2718)
+- [Oracle compatibility](https://github.com/geonetwork/core-geonetwork/pull/2777)
+- [Avoid crawler to obtain a thread with a remanant context](https://github.com/geonetwork/core-geonetwork/pull/2859)
+
+and more \... see [3.4.3 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.4.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.4.3+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.4.4.md b/docs/manual/docs/overview/change-log/version-3.4.4.md
new file mode 100644
index 00000000000..1509a43c66b
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.4.4.md
@@ -0,0 +1,35 @@
+# Version 3.4.4 {#version-344}
+
+!!! warning
+
+ The migration from 3.4.3 and earlier to 3.4.4 may cause a reset of the *Template for advanced search form* setting in the UI configuration.
+
+
+## New features
+
+- Added Slovak language ([PR 3086](https://github.com/geonetwork/core-geonetwork/pull/3086))
+- Improved error message when a region was not found in a thesaurus ([PR 3069](https://github.com/geonetwork/core-geonetwork/pull/3069))
+- Improved batch editor labels in english ([PR 3000](https://github.com/geonetwork/core-geonetwork/pull/3000))
+- Excluded servlet-related dependencies ([PR 2287](https://github.com/geonetwork/core-geonetwork/pull/2287))
+
+## Fixes
+
+- Fixed issue with multiselect directive in users administration ([issue 3055](https://github.com/geonetwork/core-geonetwork/issues/3055))
+- Fixed issue where a record with user feedbacks could not be deleted ([issue 3122](https://github.com/geonetwork/core-geonetwork/issues/3122))
+- Fixed publication date for registries ([PR 3150](https://github.com/geonetwork/core-geonetwork/pull/3150))
+- Fixed CSW response when inserting records ([issue 3104](https://github.com/geonetwork/core-geonetwork/issues/3104))
+- Fixed WFS layer support in simple view ([issue 3116](https://github.com/geonetwork/core-geonetwork/issues/3116))
+- Fixed `hideTimeInCalendar` option for editor layout ([issue 3058](https://github.com/geonetwork/core-geonetwork/issues/3058))
+- Fixed an issue with MapServer password reset ([issue 3140](https://github.com/geonetwork/core-geonetwork/issues/3140))
+- Fixed thesaurus upload that would sometime give an unclear error ([issue 3131](https://github.com/geonetwork/core-geonetwork/issues/3131))
+- Fixed loading WMTS sometime failing in projections other than EPSG:3857 ([issue 3124](https://github.com/geonetwork/core-geonetwork/pull/3124))
+- Fixed an error related to thesaurus encoding when uploading from a registry
+- Fixed an issue when adding WMS layers with an url ending with `?` ([issue 3088](https://github.com/geonetwork/core-geonetwork/issues/3088))
+- Fixed temporal extent rendering in the editor ([PR 2868](https://github.com/geonetwork/core-geonetwork/pull/2868))
+- Fixed an `OutOfMemoryError` when listing groups using service admin.group.list ([PR 3079](https://github.com/geonetwork/core-geonetwork/pull/3079))
+- Fixed issue with INSPIRE related fields being indexed when the thesaurus was not present ([issue 2719](https://github.com/geonetwork/core-geonetwork/issues/2719))
+- Fixed adding a layer to the map when the URL contained extra parameters like GetCapabilities ([PR 2846](https://github.com/geonetwork/core-geonetwork/pull/2846))
+- Fixed rendering of the menubar on small screens ([issue 2934](https://github.com/geonetwork/core-geonetwork/issues/2934))
+- Fixed favicon uploading ([issue 2992](https://github.com/geonetwork/core-geonetwork/issues/2992))
+
+and more \... see [3.4.4 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.4.4+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.4.4+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.6.0.md b/docs/manual/docs/overview/change-log/version-3.6.0.md
new file mode 100644
index 00000000000..1413636e4d1
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.6.0.md
@@ -0,0 +1,30 @@
+# Version 3.6.0 {#version-360}
+
+## New features/fixes
+
+- [Web accessibility standards and guidelines improvements](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+is%3Aclosed+Accessibility+milestone%3A3.6.0)
+- Improved user interface and new design for the recent/popular homepage and admin console
+
+
+
+- [Social bar config via settings](https://github.com/geonetwork/core-geonetwork/pull/3180)
+- [Record history and tasks](https://github.com/geonetwork/core-geonetwork/pull/3209)
+
+
+
+- Map viewer improvements (eg. projection switcher, better WFS2 support, TMS support, HTTPs redirect support, WPS support, external lviewer support, legend panel)
+- [Digital Object Identifier creation](https://github.com/geonetwork/core-geonetwork/pull/3281)
+- [ISO19139 / DataCite output format](https://github.com/geonetwork/core-geonetwork/pull/3212)
+- [Editor board / Permalink](https://github.com/geonetwork/core-geonetwork/pull/3197)
+- [Editor / Inline validation](https://github.com/geonetwork/core-geonetwork/pull/3298)
+- [Editor / Use thesaurus for any fields](https://github.com/geonetwork/core-geonetwork/pull/3078)
+- [Thesaurus / Better Registry support](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+Registry+is%3Aclosed+milestone%3A3.6.0) and [GEMET update to version 4.1.2](https://github.com/geonetwork/util-gemet/pull/4)
+- [Standard / Add API to reload configuration](https://github.com/geonetwork/core-geonetwork/pull/3081)
+- [Formatter / Add support for JSON output](https://github.com/geonetwork/core-geonetwork/pull/3191)
+- [Harvesting / Add support for WPS2](https://github.com/geonetwork/core-geonetwork/pull/3257)
+- [Harvesting / WFS features improvements (eg. asynch indexing for better performances, precision model configuration, CDATA support, Elasticsearch 6.4.x support)](https://github.com/geonetwork/core-geonetwork/pull/3205)
+- Performance improvements on indexing and JS & LESS compilation
+- Better HTTPs support
+- Security fixes and library updates
+
+and more \... see [3.6.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.6.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.6.0+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.8.0.md b/docs/manual/docs/overview/change-log/version-3.8.0.md
new file mode 100644
index 00000000000..128d54844a0
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.8.0.md
@@ -0,0 +1,48 @@
+# Version 3.8.0 {#version-380}
+
+## New features/fixes
+
+- Search experience
+ - [Saved searches](https://github.com/geonetwork/core-geonetwork/pull/3778)
+
+
+
+ Saved user searches
+
+
+ - [Improve PDF output](https://github.com/geonetwork/core-geonetwork/pull/3912)
+
+ - [Add template to display related record as list](https://github.com/geonetwork/core-geonetwork/pull/3908)
+
+ >
+ >
+ > Add template
+ >
+
+ - [Add support for negative query on any fields](https://github.com/geonetwork/core-geonetwork/pull/3683)
+- Standards
+ - [ISO19115-3:2018 is now a default standard](https://github.com/metadata101/iso19115-3.2018)
+ - [ISO19139 / JSON-LD formatter](https://github.com/geonetwork/core-geonetwork/pull/3714)
+ - [ISO19139:2007 / Update schema](https://github.com/geonetwork/core-geonetwork/pull/3920)
+ - INSPIRE Technical guidance v2 support
+ - Add support for [etf-webapp validation with TG2 for datasets and sds](https://github.com/geonetwork/core-geonetwork/pull/3915) and also [support validating non ISO19139 records like ISO19115-3](https://github.com/geonetwork/core-geonetwork/pull/3766)
+ - [Improve support for gmx:Anchor encoding](https://github.com/geonetwork/core-geonetwork/pull/3911)
+ - [ISO19110 / Populate columns and codelist values from CSV](https://github.com/geonetwork/core-geonetwork/pull/3864)
+- Editor
+ - [Working copy support for approved records](https://github.com/geonetwork/core-geonetwork/pull/3592)
+
+ - [Associated resource can now be filtered, sorted](https://github.com/geonetwork/core-geonetwork/pull/3804), add [support for WFS and Atom services](https://github.com/geonetwork/core-geonetwork/pull/3817).
+
+ >
+ >
+ > Filtering associated resources
+ >
+- Harvester
+ - [GeoNetwork / Add paging for better support of large catalogues](https://github.com/geonetwork/core-geonetwork/pull/3916)
+ - [THREDDS / Modernise and simplify harvester](https://github.com/geonetwork/core-geonetwork/pull/3936)
+ - [WFS feature / Zoom to results](https://github.com/geonetwork/core-geonetwork/pull/3701), add support for CDATA, Update to Elasticsearch 7.2.
+- Administration
+ - New user interface settings for: humanizing date, enable user searches, enable saved selections, fluid or not container
+- Security fixes and library updates
+
+And more \... see [3.8.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.8.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.8.0+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.8.1.md b/docs/manual/docs/overview/change-log/version-3.8.1.md
new file mode 100644
index 00000000000..bd35bce414f
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.8.1.md
@@ -0,0 +1,27 @@
+# Version 3.8.1 {#version-381}
+
+## New features/fixes
+
+- User experience
+
+> - [Saved searches can be organize by group](https://github.com/geonetwork/core-geonetwork/pull/4033)
+> - [Improve CSS load](https://github.com/geonetwork/core-geonetwork/pull/4044)
+> - [Cache GetCapabilities for better performance](https://github.com/geonetwork/core-geonetwork/pull/3988)
+
+- Standards
+
+> - [Migrate easily from ISO19139 to ISO19115-3:2018](https://github.com/geonetwork/core-geonetwork/pull/3999)
+> - INSPIRE / [Fix INSPIRE ATOM endpoint](https://github.com/geonetwork/core-geonetwork/pull/4025)
+
+- Editor
+
+> - [Fix name editing in associated panel](https://github.com/geonetwork/core-geonetwork/pull/3983).
+> - [Add associated panel action can point to a type of resource](https://github.com/geonetwork/core-geonetwork/pull/3981).
+
+- Misc.
+
+> - [Add Portuguesa](https://github.com/geonetwork/core-geonetwork/pull/4024).
+> - [Fix GeoNetwork 2.x harvester](https://github.com/geonetwork/core-geonetwork/pull/4047).
+> - [Add portal home page](https://github.com/geonetwork/core-geonetwork/pull/4042).
+
+and more \... see [3.8.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.8.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.8.1+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.8.2.md b/docs/manual/docs/overview/change-log/version-3.8.2.md
new file mode 100644
index 00000000000..e016e9dd617
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.8.2.md
@@ -0,0 +1,15 @@
+# Version 3.8.2 {#version-382}
+
+## New features/fixes
+
+- Standards
+
+> - INSPIRE Technical Guidance version 2 (TG2) documentation [for describing resources (with valid example for ISO19139 and ISO19115-3)](https://geonetwork-opensource.org/manuals/3.8.x/en/user-guide/describing-information/inspire-editing.html) and [configuration instructions](https://geonetwork-opensource.org/manuals/3.8.x/en/administrator-guide/configuring-the-catalog/inspire-configuration.html)
+> - INSPIRE / [Fix INSPIRE validation behind a proxy](https://github.com/geonetwork/core-geonetwork/pull/4135)
+
+- Harvester
+
+> - [Harvester / CSW / Bbox filter](https://github.com/geonetwork/core-geonetwork/pull/4076)
+> - [Harvester / CSW / XPath filter](https://github.com/geonetwork/core-geonetwork/pull/4066)
+
+and more \... see [3.8.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.8.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.8.2+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-3.8.3.md b/docs/manual/docs/overview/change-log/version-3.8.3.md
new file mode 100644
index 00000000000..b85fd5fd462
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-3.8.3.md
@@ -0,0 +1,28 @@
+# Version 3.8.3 {#version-383}
+
+## New features/fixes
+
+- Standards
+
+> - ISO19139 / [Support for applicationProfile as anchor](https://github.com/geonetwork/core-geonetwork/pull/4194)
+
+- Harvester
+
+> - [Harvester / Add batch edit parameter.](https://github.com/geonetwork/core-geonetwork/pull/4172)
+
+- Editor/Import
+
+> - [Date picker directive - use moment timezone to process the date as UTC.](https://github.com/geonetwork/core-geonetwork/pull/4266)
+> - [MEF Export / Remove duplicates on each record](https://github.com/geonetwork/core-geonetwork/pull/4283)
+> - [Use projection axis order when writing gml for bounding polygon's](https://github.com/geonetwork/core-geonetwork/pull/4320)
+
+- Search/Map/Metadata detail page
+
+> - [Uniform view for related records in the Metadata view](https://github.com/geonetwork/core-geonetwork/pull/4384)
+> - [Map / Add ESRI ArcGIS Rest support](https://github.com/geonetwork/core-geonetwork/pull/3914)
+
+- General
+
+> - [Fix an error when GN is deployed as ROOT context ("/").](https://github.com/geonetwork/core-geonetwork/pull/4366)
+
+and more \... see [3.8.3 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A3.8.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=milestone%3A3.8.3+is%3Aclosed+is%3Apr) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.0-alpha.1.md b/docs/manual/docs/overview/change-log/version-4.0.0-alpha.1.md
new file mode 100644
index 00000000000..582ba9add4a
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.0-alpha.1.md
@@ -0,0 +1,126 @@
+# Version 4.0.0-alpha.1 {#version-400-alpha1}
+
+## Why 4.0.0-alpha.1?
+
+GeoNetwork 4.0.0-alpha.1 release is an alpha version of GeoNetwork using Elasticsearch as search engine (instead of the previous home made search based on Lucene). This version is a beta release made available for users who would like to test it.
+
+This version provides support of GeoNetwork main functionalities and user can search, edit records and manage the catalogue as usual. Only the searches (and all related protocols) are affected by the search engine change and the user search experience has been improved with the following:
+
+Some of the main goals of moving from Lucene to Elasticsearch are:
+
+- Be able to share index across catalogs (clustering)
+- Improve search experience (see below)
+- Improve performances for searches and indexing
+- Add dashboards with Kibana
+- Simplify code base
+
+## What's new?
+
+This release is all about user search experience:
+
+- Autocomplete support phrase query, does not return private terms, takes current search into account
+
+
+
+- Facets / OR query support
+
+
+
+- Facets / Negative query support
+
+
+
+- Facets / Nested aggregations support
+
+
+
+- Facets / Paging to collect more values
+
+
+
+- Facets / Histograms
+
+
+
+- Facets / Configuration from the admin --> Settings --> UI based on [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations.html)
+- Record view / More like this \...
+
+
+
+- Search / Custom scoring function
+- Search / Range field support eg. temporal coverage
+
+
+
+- Performances improved for search and indexing
+- Build your own dashboards to analyze content, improve quality, create data visualization in Kibana
+
+
+
+- Summary of indexing errors
+
+
+
+Regarding search protocols, only CSW has been migrated for now (ie. OAI-PMH, RDF, Z39.50/SRU, OpenSearch, \... are not available in this version). This means that a GeoNetwork 3.x can only harvest GeoNetwork 3.99 using CSW.
+
+More details can be found in .
+
+For the installation check [Installation guide](../../install-guide/index.md).
+
+For reporting any issues go to .
+
+## Some features now removed
+
+- CSW / Virtual CSW is replaced by sub-portal (see [Portal configuration](../../administrator-guide/configuring-the-catalog/portal-configuration.md))
+- CSW / results_with_summary custom GeoNetwork output schema is removed. To retrieve facets use the main search API.
+- Deprecated Jeeves services removed (ie. services not used by Angular application like harvester config). Use the swagger API instead (see [GeoNetwork API](../../api/the-geonetwork-api.md)).
+- Metadata notifier manager (can be replaced by event system)
+- Overrides mechanism of configuration file
+
+## What is next?
+
+This version is a beta version and needs testing and feedback from the community. As a roadmap for version 4, we have to find resources to move forward on the following topics:
+
+### Existing features not implemented
+
+- Transifex / Support multiple branches translation
+- Multilingual metadata / Records are indexed and displayed but no logic to display depending on user interface language or search on specific language
+
+
+
+Multilingual fields are stored as a JSON object with an optional link if using Anchor.
+
+
+- Indexing / Language specific analyzer (draft configuration made for French)
+- Indexing / Spatial / Support for bounding polygons
+- User interface / Search / Advanced search form
+- User interface / Search / Active filters
+- User interface / Search / Facet as tab
+- Search / Other protocols (ie. OAI-PMH, RDF, Z39.50/SRU, OpenSearch)
+- API / DirectoryUtils.search
+- API / ReportUploads
+- API / INSPIRE Atom Harvester
+- Search / Statistics and search stat dashboards
+
+### New features to develop
+
+- Search on records and WFS features
+- Search / Synonyms supports
+- Associated records / Use of multiple search API for better performance or Join query.
+- Harvester / GN4 protocol
+- Clustering
+- Large catalogs / Better support of batch operations (eg. privileges, new owner, validation) and large selection
+
+```
+":{"type":"too_many_clauses","reason":"maxClauseCount is set to 1024"}}}}]},"status":400}
+```
+
+- Large catalogs / Define strategy to speed up search and not use track_total_hits
+- Security / Elasticsearch and Kibana configuration (for now, do not expose Elasticsearch to the internet)
+- Java 11 support
+
+```
+future versions of Elasticsearch will require Java 11;
+your Java version from [/usr/lib/jvm/java-8-openjdk-amd64/jre]
+does not meet this requirement
+```
diff --git a/docs/manual/docs/overview/change-log/version-4.0.0-alpha.2.md b/docs/manual/docs/overview/change-log/version-4.0.0-alpha.2.md
new file mode 100644
index 00000000000..12d814faa04
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.0-alpha.2.md
@@ -0,0 +1,26 @@
+# Version 4.0.0-alpha.2 {#version-400-alpha2}
+
+- [Home page categories can now be configured from admin console](https://github.com/geonetwork/core-geonetwork/pull/4933)
+
+
+
+- [Improved search](https://github.com/geonetwork/core-geonetwork/pull/4881) eg. Full text search can now make exact phrase match using "version 17", base query can now be customized, score configuration, advanced querying using q(-status:obsolete)
+- [Add more like this configuration](https://github.com/geonetwork/core-geonetwork/pull/4687)
+- [Aggregation can now use histogram](https://github.com/geonetwork/core-geonetwork/pull/4683)
+
+
+
+- [Improved search results layout](https://github.com/geonetwork/core-geonetwork/pull/4929)
+
+
+
+- [Active filter is enabled by default and now support negative filter with better translations. Facet values can also be filtered.](https://github.com/geonetwork/core-geonetwork/pull/4877)
+- [Associated resources / Remote record support](https://github.com/geonetwork/core-geonetwork/pull/4899)
+
+
+
+- Security update: [Spring 5](https://github.com/geonetwork/core-geonetwork/pull/4749), [JPA 2](https://github.com/geonetwork/core-geonetwork/pull/4827), [Quartz, MySQL, Guava](https://github.com/geonetwork/core-geonetwork/pull/4834)
+- [OpenAPI support](https://github.com/geonetwork/core-geonetwork/pull/4749)
+- [Translation API](https://github.com/geonetwork/core-geonetwork/pull/4823) to override default translations.
+
+and more \... see [4.0.0-alpha.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.0-alpha.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.0-alpha.2+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.0.md b/docs/manual/docs/overview/change-log/version-4.0.0.md
new file mode 100644
index 00000000000..35fa9eba20a
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.0.md
@@ -0,0 +1,51 @@
+# Version 4.0.0 {#version-400}
+
+GeoNetwork 4.0.0 release is the first version of GeoNetwork using Elasticsearch as search engine!
+
+By moving from Lucene to Elasticsearch GeoNetwork 4.0.0 offers:
+
+- shared index across catalogs (clustering)
+- Improved search experience
+- Improved performance for searching and indexing
+- Opportunity to add dashboards with Kibana
+- Simplify the geonetwork codebase
+
+The Elasticsearch engine supports GeoNetwork core functionality: user can search, edit records and manage the catalogue as usual. Only the searches (and all related protocols) are affected by the change to Elasticsearch. The editor and admin application remains the same.
+
+There remains opportunities to help:
+
+- **A number of features that you enjoy in GeoNetwork 3 may not yet be available**.
+- Multilingual editing is the same, but multilingual search is not yet fully operational.
+- Read carefully the [list of missing features](https://github.com/geonetwork/core-geonetwork/issues/4727) before migrating.
+
+Before you start:
+
+- Installing the application require to install an Elasticsearch instance (see [Installing search platform](../../install-guide/installing-index.md)).
+
+Release highlights:
+
+- The GeoNetwork ``4.0.0`` release is aligned with GeoNetwork 3.10.4 (see [Version 3.10.4](version-3.10.4.md)).
+
+- The user search experience has been greatly improved.
+
+ For more infromation see the description in [Version 4.0.0-alpha.1](version-4.0.0-alpha.1.md) and [Version 4.0.0-alpha.2](version-4.0.0-alpha.2.md).
+
+- [Search / Exact match support](https://github.com/geonetwork/core-geonetwork/pull/5072)
+
+ 
+
+- [Record view / Use timeline to render resource events, temporal extent and vertical extent](https://github.com/geonetwork/core-geonetwork/pull/5065)
+
+ 
+
+- [Map / Add mouse position](https://github.com/geonetwork/core-geonetwork/pull/5030)
+
+- [Indexing / Improvements](https://github.com/geonetwork/core-geonetwork/pull/5064)
+
+- [API / Retrieve any extents](https://github.com/geonetwork/core-geonetwork/pull/4930)
+
+- [Improve ISO19110 support](https://github.com/geonetwork/core-geonetwork/pull/5059)
+
+- [Restrict access to Elasticsearch API](https://github.com/geonetwork/core-geonetwork/pull/5023)
+
+See [4.0.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.0+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.1.md b/docs/manual/docs/overview/change-log/version-4.0.1.md
new file mode 100644
index 00000000000..93bf59ceecc
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.1.md
@@ -0,0 +1,20 @@
+# Version 4.0.1 {#version-401}
+
+GeoNetwork 4.0.1 release is a minor release aligned with GeoNetwork 3.10.5 (see [Version 3.10.5](version-3.10.5.md)) with some changes:
+
+- [Search / Facet / Fix more action when collapse state is set](https://github.com/geonetwork/core-geonetwork/pull/5122)
+- [Search / Suggestion / Apply score](https://github.com/geonetwork/core-geonetwork/pull/5133)
+- [INSPIRE / Add conformance class 2b for monitoring](https://github.com/geonetwork/core-geonetwork/pull/5117)
+- [Record view / Fix extent image due to HTTPs change](https://github.com/geonetwork/core-geonetwork/pull/5154)
+- [Record view / More like this improvement](https://github.com/geonetwork/core-geonetwork/pull/5134)
+- [DOI / Stored as resource identifier instead of online resource](https://github.com/geonetwork/core-geonetwork/pull/5124)
+- [Map / Improvements](https://github.com/geonetwork/core-geonetwork/pull/5140)
+- [WFS feature harvester scheduler and QGIS server support](https://github.com/geonetwork/core-geonetwork/pull/5140)
+
+
+
+- [Indexing / Fix usage of custom indexing name](https://github.com/geonetwork/core-geonetwork/pull/5151)
+- [ISO19115-3 / ISO19139 conversion / Fix for multiple individuals in organization](https://github.com/geonetwork/core-geonetwork/pull/5150)
+- [CSW / Restore possibility to query any index fields](https://github.com/geonetwork/core-geonetwork/pull/5127)
+
+and more \... see [4.0.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.1+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.2.md b/docs/manual/docs/overview/change-log/version-4.0.2.md
new file mode 100644
index 00000000000..e6609dd481e
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.2.md
@@ -0,0 +1,92 @@
+# Version 4.0.2 {#version-402}
+
+GeoNetwork 4.0.2 release is a minor release but adds a better multilingual support which may require some changes in your installations:
+
+## Database migration
+
+With the possibility to [restore deleted record](https://github.com/geonetwork/core-geonetwork/pull/4817), catalog maintainer has to update the database with the [following migration SQL script](https://github.com/geonetwork/core-geonetwork/blob/master/web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v3110/migrate-default.sql#L10-L27).
+
+## Index migration
+
+Index migration is only required if you created custom facets configuration in the admin or created custom Kibana dashboards. Changes are related to name or structure changes in index fields due to the improvement made for multilingual record support. The changes affect the following type of fields:
+
+### Codelist
+
+`t_` is now `l_` and is an object composed of:
+
+So `et` was:
+
+``` js
+codelist_characterSet: [
+"utf8"
+],
+codelist_characterSet_text: [
+"UTF8"
+],
+codelist_characterSet_text_langeng: [
+"UTF8"
+],
+```
+
+and is now:
+
+``` js
+cl_characterSet: [{
+ key: "utf8",
+ default: "UTF8",
+ langeng: "UTF8",
+ link: "http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_CharacterSetCode"
+}]
+```
+
+So if using `xt` in a facet, use ``cl_characterSet.default`` with this new version.
+
+### Thesaurus
+
+The `ds` field is now only used for rendering (not for query) to limit the total number of field and avoid some errors on large catalogues.
+
+Use the per thesaurus fields which were named ``thesaurus_geonetwork+external/local+type+thesaurusid`` and are now `id`. The field is also an object composed of:
+
+``` js
+thesaurus_geonetworkthesaurusexternalthemeeeatopics: [
+ "Land use",
+ "http://www.eea.europa.eu/portal_vocabularies/themes/landuse",
+ "Biodiversity - Ecosystems",
+ "http://www.eea.europa.eu/portal_vocabularies/themes/biodiversity"
+],
+```
+
+and is now:
+
+``` js
+th_eea-topics: [{
+ default: "Biodiversity - Ecosystems",
+ langeng: "Biodiversity - Ecosystems",
+ link: "http://www.eea.europa.eu/portal_vocabularies/themes/biodiversity"
+},
+{
+ default: "Policy instruments",
+ langeng: "Policy instruments",
+ link: "http://www.eea.europa.eu/portal_vocabularies/themes/policy"
+}
+```
+
+### Topic category
+
+`ic` is renamed to `ic` and has the same structure as a codelist.
+
+### GeoTag
+
+`ag` is now stored in the ``template field for keyword types](https://github.com/geonetwork/core-geonetwork/pull/5243) ie. [keywordType-place``
+
+For more details check [Configuring search fields](../../customizing-application/configuring-search-fields.md) and [Configuring faceted search](../../customizing-application/configuring-faceted-search.md).
+
+## Main changes in version 4.0.2
+
+- [Multilingual support](https://github.com/geonetwork/core-geonetwork/pull/5193)
+- [Thesaurus / Import from Linked Data Registry](https://github.com/geonetwork/core-geonetwork/pull/5125)
+- [WFS indexing / More robust and add QGIS Server support](https://github.com/geonetwork/core-geonetwork/pull/5190)
+- [User searches / Add portals with filter in the list](https://github.com/geonetwork/core-geonetwork/pull/5181)
+- [Index / improvements](https://github.com/geonetwork/core-geonetwork/pull/5175)
+
+and more \... see [4.0.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.2+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.3.md b/docs/manual/docs/overview/change-log/version-4.0.3.md
new file mode 100644
index 00000000000..d5b3fc3b27a
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.3.md
@@ -0,0 +1,16 @@
+# Version 4.0.3 {#version-403}
+
+GeoNetwork 4.0.3 release is a minor release with some changes:
+
+- Interactive graphics for facets (See [Interactive graphics](../../customizing-application/configuring-faceted-search.md#configuring-facet-graphics))
+- [Map / WPS support improvements](https://github.com/geonetwork/core-geonetwork/pull/5362)
+- Indexing / [Improvements](https://github.com/geonetwork/core-geonetwork/pull/5425), [better multilingual support](https://github.com/geonetwork/core-geonetwork/pull/5436) and [more robust](https://github.com/geonetwork/core-geonetwork/pull/5398)
+- [Monitoring your catalogue usage using Kibana](https://github.com/geonetwork/docker-geonetwork/pull/60)
+
+
+
+- Translation pack builder for faster initialization of the client application.
+
+and more \... see [4.0.3 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.3+is%3Aclosed) for full details.
+
+Version 4.0.3 is also the version to use if [testing the draft OGC API Records service](https://github.com/geonetwork/geonetwork-microservices/tree/main/modules/services/ogc-api-records).
diff --git a/docs/manual/docs/overview/change-log/version-4.0.4.md b/docs/manual/docs/overview/change-log/version-4.0.4.md
new file mode 100644
index 00000000000..86784b91adf
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.4.md
@@ -0,0 +1,15 @@
+# Version 4.0.4 {#version-404}
+
+GeoNetwork 4.0.4 release is a minor release with some changes:
+
+- [Search results / Improve performance with overview as dataURL](https://github.com/geonetwork/core-geonetwork/pull/5467)
+- [Editor / List format as protocols](https://github.com/geonetwork/core-geonetwork/pull/5465)
+- [Editor / Fix compute extents from keywords](https://github.com/geonetwork/core-geonetwork/pull/5499)
+- [Filestore / Jcloud implementation](https://github.com/geonetwork/core-geonetwork/pull/4570)
+- [INSPIRE / Validation / Remove internal schematron](https://github.com/geonetwork/core-geonetwork/pull/5513). Use [INSPIRE validator instead](https://inspire.ec.europa.eu/validator/about/).
+- [DOI / Improve Datacite conversion](https://github.com/geonetwork/core-geonetwork/pull/5500)
+- [Security / Password enforcement](https://github.com/geonetwork/core-geonetwork/pull/5402)
+- [Index health check improvements](https://github.com/geonetwork/core-geonetwork/pull/5612)
+- [Add proxy for microservice eg. OGC API Records](https://github.com/geonetwork/core-geonetwork/pull/5604)
+
+and more \... see [4.0.4 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.4+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.4+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.5.md b/docs/manual/docs/overview/change-log/version-4.0.5.md
new file mode 100644
index 00000000000..d62b32b04e1
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.5.md
@@ -0,0 +1,10 @@
+# Version 4.0.5 {#version-405}
+
+GeoNetwork 4.0.5 release is a minor release with some changes:
+
+- [Harvester / Add visual summary](https://github.com/geonetwork/core-geonetwork/pull/5646)
+- [DOI / Update support and manage existing DOI from editor](https://github.com/geonetwork/core-geonetwork/pull/5734) (see [Digital Object Identifier (DOI)](../../user-guide/associating-resources/doi.md))
+- [DOI / Schematron validation to make DataCite XSD error reporting more comprehensive](https://github.com/geonetwork/core-geonetwork/pull/5671)
+- [Permalink to editor using a specific view or by UUID](https://github.com/geonetwork/core-geonetwork/pull/5705)
+
+and more \... see [4.0.5 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.5+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.5+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.0.6.md b/docs/manual/docs/overview/change-log/version-4.0.6.md
new file mode 100644
index 00000000000..50337f407fc
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.0.6.md
@@ -0,0 +1,243 @@
+# Version 4.0.6 {#version-406}
+
+This new release of GeoNetwork contains a *lot* of improvements and fixes made during the past 8 months that should make it much more easy to use and customizable. This version also benefited from most of the fixes and improvements made for the GeoNetwork 3.10 and 12 versions during the past months.
+
+## Highlights
+
+- Fix for the [log4shell CVE](https://en.wikipedia.org/wiki/Log4Shell)
+- A new flexible [JSON harvester](https://github.com/geonetwork/core-geonetwork/pull/5942) which currently supports CKAN, ODS and ESRI
+- Restyled [topics and categories](https://github.com/geonetwork/core-geonetwork/pull/5837) in the homepage
+- Better UI for the [harvester administration](https://github.com/geonetwork/core-geonetwork/pull/5926)
+- The possibility to [put the search map in the facets column](https://github.com/geonetwork/core-geonetwork/pull/6080)
+- Improvements to the search experience and facets
+- Improvements to the INSPIRE Atom feed
+- Improvements to the DOI creation process
+- Improvements to the Editor UI and Admin UI
+
+## Security
+
+- Bump log4j2 from 2.17.0 to 2.17.1 ([#6110](https://github.com/geonetwork/core-geonetwork/pull/6110))
+- Update log4j2 from 2.16.0 to 2.17.0 to address CVE-2021-45105 ([#6083](https://github.com/geonetwork/core-geonetwork/pull/6083))
+- Bump log4j-core and log4j-api from 2.15.0 to 2.16.0 ([#6079](https://github.com/geonetwork/core-geonetwork/pull/6079))
+- Update log4j2 from from 2.7 to 2.15.0 ([#6075](https://github.com/geonetwork/core-geonetwork/pull/6075))
+
+## Features and improvements
+
+- Display the alert message within the online resource popup ([#6109](https://github.com/geonetwork/core-geonetwork/pull/6109))
+- Updated keycloak to use the correct granted authority ([#6134](https://github.com/geonetwork/core-geonetwork/pull/6134))
+- DOI - add identifier / online resource url using the DOI proxy url ([#6124](https://github.com/geonetwork/core-geonetwork/pull/6124))
+- CSW Harvester / add typeahead support for filter field names ([#5796](https://github.com/geonetwork/core-geonetwork/pull/5796))
+- Sort groups and users in transfer ownership ([#6093](https://github.com/geonetwork/core-geonetwork/pull/6093))
+- Metadata update and internal reports updates ([#6082](https://github.com/geonetwork/core-geonetwork/pull/6082))
+- Service record for CSW capabilities - INSPIRE improvements ([#6081](https://github.com/geonetwork/core-geonetwork/pull/6081))
+- Update UI configuration selected by default: select the current node if defined in the configuration, otherwise the first one ([#6094](https://github.com/geonetwork/core-geonetwork/pull/6094))
+- Don't allow to delete a group if it owns metadata ([#6072](https://github.com/geonetwork/core-geonetwork/pull/6072))
+- Confirmation dialog to delete an UI configuration ([#6092](https://github.com/geonetwork/core-geonetwork/pull/6092))
+- Replace Travis badge by Github Actions Badge ([#6097](https://github.com/geonetwork/core-geonetwork/pull/6097))
+- Enable to display map in left column of search UI ([#6080](https://github.com/geonetwork/core-geonetwork/pull/6080))
+- Add maven caching to GraphQL analysis ([#6085](https://github.com/geonetwork/core-geonetwork/pull/6085))
+- Editor / Error message fixes ([#6029](https://github.com/geonetwork/core-geonetwork/pull/6029))
+- Add the doi-get query for ISO19115-3.2018 standard ([#6065](https://github.com/geonetwork/core-geonetwork/pull/6065))
+- Add proxy level security support for map services ([#5941](https://github.com/geonetwork/core-geonetwork/pull/5941))
+- INSPIRE Atom feed / Update retrieve dataset UUID to handle multiple atom feed entries for the same dataset ([#6078](https://github.com/geonetwork/core-geonetwork/pull/6078))
+- Metadata get status service - return the status change date for all types of statuses ([#6074](https://github.com/geonetwork/core-geonetwork/pull/6074))
+- User custom dialog to ask for users / groups delete confirmation ([#6070](https://github.com/geonetwork/core-geonetwork/pull/6070))
+- Add a confirm popup when deleting a logo ([#6067](https://github.com/geonetwork/core-geonetwork/pull/6067))
+- Misc. updates to Dutch translations
+- Upgrade jsoup library ([#6057](https://github.com/geonetwork/core-geonetwork/pull/6057))
+- Update label texts for workflow dialog / actions. Fixes [#4992](https://github.com/geonetwork/core-geonetwork/issues/4992) ([#5840](https://github.com/geonetwork/core-geonetwork/pull/5840))
+- Opendata harvesting / add a resource for the landing page ([#6062](https://github.com/geonetwork/core-geonetwork/pull/6062))
+- Configuration option to restrict the usage of non-predefined map services in the Regions API. Related to #5166 ([#6045](https://github.com/geonetwork/core-geonetwork/pull/6045))
+- Change the forgot password message ([#6015](https://github.com/geonetwork/core-geonetwork/pull/6015))
+- Don't display the delete button when creating a new group ([#6040](https://github.com/geonetwork/core-geonetwork/pull/6040))
+- Don't display the reset password button when creating a new user ([#6041](https://github.com/geonetwork/core-geonetwork/pull/6041))
+- Use the Map projection Region API setting in Regions/geometry related services ([#6050](https://github.com/geonetwork/core-geonetwork/pull/6050))
+- Metadata status migration - add FK for relatedMetadataStatusId ([#6010](https://github.com/geonetwork/core-geonetwork/pull/6010))
+- Encode view parameter in URL ([#6030](https://github.com/geonetwork/core-geonetwork/pull/6030))
+- Uses Java 8 in the code analysis
+- Add support for UI settings migrations. Migration for mods.header.isMenubarAccessible ([#6044](https://github.com/geonetwork/core-geonetwork/pull/6044))
+- Enable CodeQL analysis in CI workflow
+- Add mimetype in WWW:DOWNLOAD protocol on OpenDataSoft harvesting ([#6043](https://github.com/geonetwork/core-geonetwork/pull/6043))
+- Metadata retired status support ([#5943](https://github.com/geonetwork/core-geonetwork/pull/5943))
+- Allow to reset the users / groups filters ([#6042](https://github.com/geonetwork/core-geonetwork/pull/6042))
+- Datacite formatter - process for creators only point of contacts with roles pointOfContact and custodian ([#6039](https://github.com/geonetwork/core-geonetwork/pull/6039))
+- Map viewer / support to add layers from ESRI Rest services ([#5931](https://github.com/geonetwork/core-geonetwork/pull/5931))
+- JSON Harvester / Improve ESRI and OpenDataSoft harvesting ([#6023](https://github.com/geonetwork/core-geonetwork/pull/6023))
+- option for duplicate API to copy attachments or not ([#6009](https://github.com/geonetwork/core-geonetwork/pull/6009))
+- Added MetadataPreRemove event before backup operation ([#5954](https://github.com/geonetwork/core-geonetwork/pull/5954))
+- Remove username from forgot password service url ([#5993](https://github.com/geonetwork/core-geonetwork/pull/5993))
+- Unblock missing user/group information from user profile ([#6005](https://github.com/geonetwork/core-geonetwork/pull/6005))
+- Update XslProcessApi to process the draft copies for the metadata in a workflow ([#5811](https://github.com/geonetwork/core-geonetwork/pull/5811))
+- Add statusIds list to MetadataWorkflowApi.getStatusByType API ([#5984](https://github.com/geonetwork/core-geonetwork/pull/5984))
+- i18n / Add custom translations to the default language packages ([#5919](https://github.com/geonetwork/core-geonetwork/pull/5919))
+- Configure how to extract the WMS layer name from metadata online resources to add them to the map viewer ([#5987](https://github.com/geonetwork/core-geonetwork/pull/5987))
+- Validation / INSPIRE / Return message when quota exceeded. ([#5995](https://github.com/geonetwork/core-geonetwork/pull/5995))
+- Add index folder information in the catalog information table (admin
+ - statistics and status) ([#5976](https://github.com/geonetwork/core-geonetwork/pull/5976))
+- Add logic to only run encryptor once on password during the migration. ([#5865](https://github.com/geonetwork/core-geonetwork/pull/5865))
+- Used nv-i18n library to add better support for iso639-2/T iso639-2/B support ([#5982](https://github.com/geonetwork/core-geonetwork/pull/5982))
+- Update iso19139 template for uuidref attribute to apply only for srv:operatesOn element ([#5924](https://github.com/geonetwork/core-geonetwork/pull/5924))
+- INSPIRE Atom feed / Process data feed download links with multiple download files/links per datafeed entry ([#5985](https://github.com/geonetwork/core-geonetwork/pull/5985))
+- ISO19115-3 - jsonld formatter - support online resources multilingual for name and description ([#5989](https://github.com/geonetwork/core-geonetwork/pull/5989))
+- ISO19139 - jsonld formatter - support online resources multilingual for name and description ([#5955](https://github.com/geonetwork/core-geonetwork/pull/5955))
+- Add a split button for `Validate` in the 'edit' toolbar so the label is always displayed (whether the submenu is there or not). ([#5966](https://github.com/geonetwork/core-geonetwork/pull/5966))
+- Add a new Json harvester ([#5942](https://github.com/geonetwork/core-geonetwork/pull/5942))
+- Remove secure port setting ([#5569](https://github.com/geonetwork/core-geonetwork/pull/5569))
+- Avoid loading Recaptcha API by angular-recaptcha if Recaptcha is disabled in the settings ([#5562](https://github.com/geonetwork/core-geonetwork/pull/5562))
+- Small UI improvements for the Harvester Settings page ([#5926](https://github.com/geonetwork/core-geonetwork/pull/5926))
+- Display topic categories tooltip in the metadata editor when tooltips are enabled ([#5935](https://github.com/geonetwork/core-geonetwork/pull/5935))
+- Editor / ISO / Compute extent from one keyword or add one extent from all keywords ([#5917](https://github.com/geonetwork/core-geonetwork/pull/5917))
+- Record view / ISO / Temporal range details support. ([#5918](https://github.com/geonetwork/core-geonetwork/pull/5918))
+- Homepage / Add a title to info block ([#5922](https://github.com/geonetwork/core-geonetwork/pull/5922))
+- Map list / Open map in the viewer, not the record view ([#5921](https://github.com/geonetwork/core-geonetwork/pull/5921))
+- Add localizedException logic so that errors can be displayed in multiple languages ([#5323](https://github.com/geonetwork/core-geonetwork/pull/5323))
+- Search / Facet / Remove count if undefined ([#5915](https://github.com/geonetwork/core-geonetwork/pull/5915))
+- Search / Add search options (eg. titleonly) to permalink ([#5914](https://github.com/geonetwork/core-geonetwork/pull/5914))
+- Record status / Highlight superseded record like obsolete one. ([#5898](https://github.com/geonetwork/core-geonetwork/pull/5898))
+- Formatter / Admin API / Migrate to Spring. ([#5905](https://github.com/geonetwork/core-geonetwork/pull/5905))
+- Update search options of the editor (harmonisation of the search functions between search page and editor) ([#5907](https://github.com/geonetwork/core-geonetwork/pull/5907))
+- Search / Active filter / Misc improvements. ([#5903](https://github.com/geonetwork/core-geonetwork/pull/5903))
+- INSPIRE / Validation from a portal endpoint. ([#5899](https://github.com/geonetwork/core-geonetwork/pull/5899))
+- Data / WFS harvester / Don't diplay widget if WFS is down ([#5898](https://github.com/geonetwork/core-geonetwork/pull/5898))
+- Admin / Reports / Consistent CSV format with other exports. ([#5897](https://github.com/geonetwork/core-geonetwork/pull/5897))
+- Resources / Load using relative path. ([#5902](https://github.com/geonetwork/core-geonetwork/pull/5902))
+- Only extractTitles for type METADATA ([#5892](https://github.com/geonetwork/core-geonetwork/pull/5892))
+- Small UI improvements to the (advanced) search on the search page ([#5877](https://github.com/geonetwork/core-geonetwork/pull/5877))
+- Record view / Preserve debug mode in links ([#5894](https://github.com/geonetwork/core-geonetwork/pull/5894))
+- Dublin core / Improvements ([#5893](https://github.com/geonetwork/core-geonetwork/pull/5893))
+- Editor / ISO topic category / Return list corresponding to schema plugins. ([#5887](https://github.com/geonetwork/core-geonetwork/pull/5887))
+- Editor / Avoid error if records contains multiple all thesaurus block ([#5885](https://github.com/geonetwork/core-geonetwork/pull/5885))
+- Editor board / Validation filter translations. ([#5884](https://github.com/geonetwork/core-geonetwork/pull/5884))
+- Break words in table on the record view page ([#5879](https://github.com/geonetwork/core-geonetwork/pull/5879))
+- Plugin / SchemaLocation is removed on save in ISO19139 (not in other plugins). ([#5878](https://github.com/geonetwork/core-geonetwork/pull/5878))
+- Record view / More like this improvements. ([#5858](https://github.com/geonetwork/core-geonetwork/pull/5858))
+- Record view / Add conditional formatter support ([#5820](https://github.com/geonetwork/core-geonetwork/pull/5820))
+- Facet / Translation / Distinction between zip code and ZIP format ([#5876](https://github.com/geonetwork/core-geonetwork/pull/5876))
+- MetadataManager / Add utility to check if record is valid. (5875)
+- Setting / Integer / Get with default value. ([#5874](https://github.com/geonetwork/core-geonetwork/pull/5874))
+- Editor / Associated resource / Check null protocol or url ([#5880](https://github.com/geonetwork/core-geonetwork/pull/5880))
+- Home page / Facet / Add CSS class ([#5869](https://github.com/geonetwork/core-geonetwork/pull/5869))
+- GML / Add required id attribute to TimePeriod ([#5867](https://github.com/geonetwork/core-geonetwork/pull/5867))
+- Restyle the logo list in the Settings ([#5855](https://github.com/geonetwork/core-geonetwork/pull/5855))
+- Refactor sql to use binding ([#5868](https://github.com/geonetwork/core-geonetwork/pull/5868))
+- Facet / Add translation sort and filtering support. ([#5852](https://github.com/geonetwork/core-geonetwork/pull/5852))
+- CSW / Restore possibility to store by any index fields ([#5849](https://github.com/geonetwork/core-geonetwork/pull/5849))
+- Map / Service list / Add UI configuration filter if any ([#5854](https://github.com/geonetwork/core-geonetwork/pull/5854))
+- ISO19139 / Formatter / Support isoType in template match for plugins ([#5853](https://github.com/geonetwork/core-geonetwork/pull/5853))
+- Remove deleteAllByMetadataIdExceptGroupId from custom implementation and use the repository @query instead. ([#5828](https://github.com/geonetwork/core-geonetwork/pull/5828))
+- Small adjustments to UI settings in the Admin ([#5839](https://github.com/geonetwork/core-geonetwork/pull/5839))
+- Restyle topics on the Home page ([#5837](https://github.com/geonetwork/core-geonetwork/pull/5837))
+- Escape login redirect url ([#5829](https://github.com/geonetwork/core-geonetwork/pull/5829))
+- Add a Bootstrap layout and column to a static page ([#5843](https://github.com/geonetwork/core-geonetwork/pull/5843))
+- Aggregation / Add terms script support ([#5745](https://github.com/geonetwork/core-geonetwork/pull/5745))
+- Editor / Associated resources / Do not add wildcard on all search ([#5792](https://github.com/geonetwork/core-geonetwork/pull/5792))
+- Admin / Tools / Add action to drop data index. ([#5812](https://github.com/geonetwork/core-geonetwork/pull/5812))
+- Add exact match and title only search options ([#5783](https://github.com/geonetwork/core-geonetwork/pull/5783))
+- Add copy resource interface, implement cmis resource copy with additional properties ([#5776](https://github.com/geonetwork/core-geonetwork/pull/5776))
+- Make the editor menu scrollable on small screens ([#5795](https://github.com/geonetwork/core-geonetwork/pull/5795))
+- User Profile Readonly for keycloak users ([#5769](https://github.com/geonetwork/core-geonetwork/pull/5769))
+- Add confirm to delete Category and Cancel edits to metadata ([#5813](https://github.com/geonetwork/core-geonetwork/pull/5813))
+- Editor / Online source / Check URL with a HEAD call ([#5741](https://github.com/geonetwork/core-geonetwork/pull/5741))
+- Map / Apply filter to layer search ([#5803](https://github.com/geonetwork/core-geonetwork/pull/5803))
+- iso19139 full view - codelist elements - display the codelistValue translation only if the element has a text also ([#5793](https://github.com/geonetwork/core-geonetwork/pull/5793))
+- Add a scrollbar to the privileges popup when group names are too long ([#5799](https://github.com/geonetwork/core-geonetwork/pull/5799))
+- Display the facet filter on a single row ([#5762](https://github.com/geonetwork/core-geonetwork/pull/5762))
+- History / Display close task only when it applies ([#5786](https://github.com/geonetwork/core-geonetwork/pull/5786))
+- Revise security policy with example of email list and issue tracker as public forums ([#5754](https://github.com/geonetwork/core-geonetwork/pull/5754))
+- Update instructions for local development ([#5627](https://github.com/geonetwork/core-geonetwork/pull/5627))
+- Search / Add all title's translations in the default search ([#5750](https://github.com/geonetwork/core-geonetwork/pull/5750))
+- Indexing / Temporal extent / Add support for now in range upper bound. ([#5784](https://github.com/geonetwork/core-geonetwork/pull/5784))
+- Add new styling options to display the status of metadata records ([#5759](https://github.com/geonetwork/core-geonetwork/pull/5759))
+- Move release build properties to separate file ([#5348](https://github.com/geonetwork/core-geonetwork/pull/5348))
+- Add `register` and `lost password` option to accessible login menu ([#5571](https://github.com/geonetwork/core-geonetwork/pull/5571))
+- Styling and multiple columns for the language list in the `Create Thesaurus Window` ([#5572](https://github.com/geonetwork/core-geonetwork/pull/5572))
+- Add a new accessible menubar (clickable and keyboard accessible): ([#5518](https://github.com/geonetwork/core-geonetwork/pull/5518))
+- Modify spring security so that it can be set at runtime startup ([#5312](https://github.com/geonetwork/core-geonetwork/pull/5312))
+- Add salutation to notification message. ([#5686](https://github.com/geonetwork/core-geonetwork/pull/5686))
+- Refactor - autowire settingManager bean to make code cleaner. ([#5773](https://github.com/geonetwork/core-geonetwork/pull/5773))
+- Editor / option to disable OGC Capabilities layer processing in the online resource panel. ([#5763](https://github.com/geonetwork/core-geonetwork/pull/5763))
+
+## Fixes
+
+- Use typeNames in the WFS URL when version is >= "2.0.0" ([#6143](https://github.com/geonetwork/core-geonetwork/pull/6143))
+- URL rewrite / Make "/geonetwork?uuid=..." links work again ([#6139](https://github.com/geonetwork/core-geonetwork/pull/6139))
+- Fix the cron expression for the INSPIRE ATOM harvester ([#6131](https://github.com/geonetwork/core-geonetwork/pull/6131))
+- Fix issue with CMIS connection during startup ([#6106](https://github.com/geonetwork/core-geonetwork/pull/6106))
+- Fix removal of sort by and hits per page elements in the UI configuration ([#6091](https://github.com/geonetwork/core-geonetwork/pull/6091))
+- Fix to display the role translation instead of the role code in the iso19139 full view formatter ([#6123](https://github.com/geonetwork/core-geonetwork/pull/6123))
+- XSLT formatter / remove debug mode ([#6127](https://github.com/geonetwork/core-geonetwork/pull/6127))
+- Fix default URL for the metadata full view ([#6125](https://github.com/geonetwork/core-geonetwork/pull/6125))
+- Metadata view / correctly escape quotes in links title to avoid runtime error ([#6095](https://github.com/geonetwork/core-geonetwork/pull/6095))
+- Fix for the height of a Modal popup in the Editor ([#6098](https://github.com/geonetwork/core-geonetwork/pull/6098))
+- Fix check for layer already in map - case insensitive check of the url ([#6090](https://github.com/geonetwork/core-geonetwork/pull/6090))
+- Fix coordinate order in jsonld GeoShape element ([#6071](https://github.com/geonetwork/core-geonetwork/pull/6071))
+- Add styles and classes to fix the button bars not really fitting inside the headers on admin pages ([#6061](https://github.com/geonetwork/core-geonetwork/pull/6061))
+- Fix the registration of the `surname` and `country` for the 'self' registration process ([#6060](https://github.com/geonetwork/core-geonetwork/pull/6060))
+- Fix the list of elements to process in CSW ElementSet strategy 'context' ([#6017](https://github.com/geonetwork/core-geonetwork/pull/6017))
+- Fix the display of the service metadata title for CSW and portals ([#6026](https://github.com/geonetwork/core-geonetwork/pull/6026))
+- Fix check for layer already in map ([#6031](https://github.com/geonetwork/core-geonetwork/pull/6031))
+- Fix feedback email with multiple recipients ([#6033](https://github.com/geonetwork/core-geonetwork/pull/6033))
+- Fixed issue with missing keycloakSecurityContextRequestFilter that was causing keycloak not to refresh the token correctly. ([#6035](https://github.com/geonetwork/core-geonetwork/pull/6035))
+- DOI creation / Change the links to buttons so that they become actually disabled when clicked ([#6037](https://github.com/geonetwork/core-geonetwork/pull/6037))
+- Convert iso639_2T to iso639_2B language codes in form-builder ([#6024](https://github.com/geonetwork/core-geonetwork/pull/6024))
+- Reset search parameter after metadata status change to "approved" ([#5970](https://github.com/geonetwork/core-geonetwork/pull/5970))
+- Fix gn-fn-index:is-isoDate - invalid dates like 2021-04-207 match, causing indexing errors ([#6022](https://github.com/geonetwork/core-geonetwork/pull/6022))
+- Fix credentials autocomplete in harvesters ([#6011](https://github.com/geonetwork/core-geonetwork/pull/6011))
+- Admin / better handle harvester types translation ([#6006](https://github.com/geonetwork/core-geonetwork/pull/6006))
+- Add missing 3.12.x upgrade steps ([#5866](https://github.com/geonetwork/core-geonetwork/pull/5866))
+- Admin / Users / Fix the users that a UserAdmin can manage ([#5886](https://github.com/geonetwork/core-geonetwork/pull/5886))
+- Validation / INSPIRE / Fix when setting is 'null' ([#5973](https://github.com/geonetwork/core-geonetwork/pull/5973))
+- Fix a bug when the url doesn't contain the ? sign ([#5994](https://github.com/geonetwork/core-geonetwork/pull/5994))
+- Fixes some challenges in google-structured-data-test ([#5988](https://github.com/geonetwork/core-geonetwork/pull/5988))
+- Remove duplicated dependency ([#5986](https://github.com/geonetwork/core-geonetwork/pull/5986))
+- Updated default language so that is comes from common java location. ([#5981](https://github.com/geonetwork/core-geonetwork/pull/5981))
+- INSPIRE / Validation / Add API Key. ([#5975](https://github.com/geonetwork/core-geonetwork/pull/5975))
+- Fix workflow mail notifications for metadata with a working copy ([#5971](https://github.com/geonetwork/core-geonetwork/pull/5971))
+- Small fix for long titles on Topic blocks ([#5960](https://github.com/geonetwork/core-geonetwork/pull/5960))
+- Editor / Avoid hiding part of the Add Resource dropdown in sidebar. ([#5916](https://github.com/geonetwork/core-geonetwork/pull/5916))
+- External viewer / Fix error when adding layer ([#5959](https://github.com/geonetwork/core-geonetwork/pull/5959))
+- Rollback exceptions handled in GlobalExceptionController. Fixes [#5944](https://github.com/geonetwork/core-geonetwork/issues/5944) ([#5948](https://github.com/geonetwork/core-geonetwork/pull/5948))
+- Remove online resource - fix resource name comparison ([#5934](https://github.com/geonetwork/core-geonetwork/pull/5934))
+- Fix CSW ES mapping for sortBy and bbox ([#5927](https://github.com/geonetwork/core-geonetwork/pull/5927))
+- Handle CSW BBOX Filter correctly ([#5913](https://github.com/geonetwork/core-geonetwork/pull/5913))
+- Encryptor env variable should be uppercase as this it the general standard otherwise it will not find the variable on unix ([#5873](https://github.com/geonetwork/core-geonetwork/pull/5873))
+- Fix issue with localized exception where with* functions were returning LocalizedException instead of the class. i.e. ResourceNotFoundException ([#5531](https://github.com/geonetwork/core-geonetwork/pull/5531))
+- API / Avoid browser cache issue when the same API Path serving various formats. ([#5901](https://github.com/geonetwork/core-geonetwork/pull/5901))
+- ISO19139 / CRS indexing fails on multilingual records ([#5900](https://github.com/geonetwork/core-geonetwork/pull/5900))
+- HTML / Page tab title empty ([#5895](https://github.com/geonetwork/core-geonetwork/pull/5895))
+- Record view / Refactor getFormatterForRecord / Fix default url
+- Record view / Fix display of topic category. ([#5891](https://github.com/geonetwork/core-geonetwork/pull/5891))
+- Search results / PDF / Missing title in TOC ([#5888](https://github.com/geonetwork/core-geonetwork/pull/5888))
+- Fit view to exact extent (fixes issue #5791) ([#5847](https://github.com/geonetwork/core-geonetwork/pull/5847))
+- Fix ops for public metadata inserted with CSW-T ([#5202](https://github.com/geonetwork/core-geonetwork/pull/5202))
+- Record view / Fix display of CRS label. ([#5883](https://github.com/geonetwork/core-geonetwork/pull/5883))
+- Record view / Group not set in prod mode ([#5851](https://github.com/geonetwork/core-geonetwork/pull/5851))
+- Fix empty metadata list with -1 count in user profile. Fixes [#5871](https://github.com/geonetwork/core-geonetwork/issues/5871). ([#5872](https://github.com/geonetwork/core-geonetwork/pull/5872))
+- Encryption / Application fails to start if encryption error on harvester passwords ([#5859](https://github.com/geonetwork/core-geonetwork/pull/5859))
+- Admin / Status / Fix facet more ([#5848](https://github.com/geonetwork/core-geonetwork/pull/5848))
+- Record view / Advanced / Fix search by keyword links ([#5832](https://github.com/geonetwork/core-geonetwork/pull/5832))
+- Indexing / documentStandard is not an array. ([#5834](https://github.com/geonetwork/core-geonetwork/pull/5834))
+- Indexing / Do not add twice indexingDate field ([#5823](https://github.com/geonetwork/core-geonetwork/pull/5823))
+- User \$translateProvider.useSanitizeValueStrategy('escapeParameters') for encoding sanitizing ([#5461](https://github.com/geonetwork/core-geonetwork/pull/5461))
+- Fix for validation result gets lost when approving record and copy validation results when creating a draft. Fixes [#5209](https://github.com/geonetwork/core-geonetwork/issues/5209) ([#5418](https://github.com/geonetwork/core-geonetwork/pull/5418))
+- Overview / Removal / Do not delete attachment from other records ([#5821](https://github.com/geonetwork/core-geonetwork/pull/5821))
+- INSPIRE Atom feed xslt fix for resource constraints with multiple gmd:otherConstraints elements ([#5815](https://github.com/geonetwork/core-geonetwork/pull/5815))
+- Index / Avoid error on multiple results in DQ conformance. ([#5814](https://github.com/geonetwork/core-geonetwork/pull/5814))
+- Correct the OpenAPI document so that it does not generate errors that were identified in #5431 ([#5809](https://github.com/geonetwork/core-geonetwork/pull/5809))
+- Fix Thumbnail generator ([#5757](https://github.com/geonetwork/core-geonetwork/pull/5757))
+- OpenAPI / Restore missing method. ([#5752](https://github.com/geonetwork/core-geonetwork/pull/5752))
+- Locale loader: fix to load translation files using the format `relativepath|type`, like `../../catalog/views/myview/locales/|core` ([#5710](https://github.com/geonetwork/core-geonetwork/pull/5710))
+- Search results - metadata with a working copy display a label 'Working copy' if the metadata has a draft copy, even for public users. Fixes [#5580](https://github.com/geonetwork/core-geonetwork/issues/5580) ([#5805](https://github.com/geonetwork/core-geonetwork/pull/5805))
+- Create user form issues 2 requests to userselection api that return status code 400. Fixes [#4545](https://github.com/geonetwork/core-geonetwork/issues/4545) ([#5804](https://github.com/geonetwork/core-geonetwork/pull/5804))
+- Users without groups assigned are listed in the users lists for any UserAdmin ([#5798](https://github.com/geonetwork/core-geonetwork/pull/5798))
+- Selection / PDF / Fix errors due to index schema changes ([#5787](https://github.com/geonetwork/core-geonetwork/pull/5787))
+- Fix editor overview manager. Fixes [#5806](https://github.com/geonetwork/core-geonetwork/issues/5806) ([#5807](https://github.com/geonetwork/core-geonetwork/pull/5807))
+- Self-register option doesn't work. Fixes [#5778](https://github.com/geonetwork/core-geonetwork/issues/5778) ([#5779](https://github.com/geonetwork/core-geonetwork/pull/5779))
+- Updated the index fieldname to match the es index names. ([#5772](https://github.com/geonetwork/core-geonetwork/pull/5772))
+- Fix bug in signin link - regression cause by #5518 which used older variable. ([#5782](https://github.com/geonetwork/core-geonetwork/pull/5782))
+- Fixed CMIS resource bug where the wrong key function was called causing an invalid key to be generated. ([#5775](https://github.com/geonetwork/core-geonetwork/pull/5775))
+- 3.12.x cmis jcloud updates cherry pick ([#5767](https://github.com/geonetwork/core-geonetwork/pull/5767))
+
+A huge thanks to all contributors and maintainers alike!
+
+See [4.0.6 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.0.6+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.0.6+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.0.md b/docs/manual/docs/overview/change-log/version-4.2.0.md
new file mode 100644
index 00000000000..28801a59253
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.0.md
@@ -0,0 +1,45 @@
+# Version 4.2.0 {#version-420}
+
+GeoNetwork 4.2.0 release is a major release.
+
+## Migration instructions
+
+Due to H2 database major update, when migrating from a previous version drop the following database caches:
+
+- JS/CSS cache database in \$DATA_DIR/wro4j-cache.mv.db
+- Formatter cache database in \$DATA_DIR/data/resources/htmlcache/formatter-cache/info-store.mv.db
+
+If using H2 as the main database consider migrating to an external database (see [Configuring the database](../../install-guide/configuring-database.md)) or read [H2 migration guide](https://www.h2database.com/html/migration-to-v2.html) and migrate the database to version 2 format.
+
+Then start the application.
+
+If using GeoNetwork 4.2.0 with an H2 version 1 database, the following error will be reported by H2 driver:
+
+```
+General error: "The write format 1 is smaller than the supported format 2 [2.1.212/5]" [50000-212]
+```
+
+## List of changes
+
+Major changes:
+
+- [Library updates](https://github.com/geonetwork/core-geonetwork/pull/6244) including the move to H2 version 2 (not compatible with H2 version 1)
+- [Search / Multilingual support](https://github.com/geonetwork/core-geonetwork/pull/6188)
+- [Search / Display results as table](https://github.com/geonetwork/core-geonetwork/pull/6170)
+- [Search / Associated resources can now be part of the search response API](https://github.com/geonetwork/core-geonetwork/pull/6269)
+- [Record view / Improved navigation](https://github.com/geonetwork/core-geonetwork/pull/6188)
+- [Record view / Dataset citation formatter](https://github.com/geonetwork/core-geonetwork/pull/6188)
+- [Toolbar / Add menu to switch portals](https://github.com/geonetwork/core-geonetwork/pull/6256)
+- [Editing / Define preferred template and group](https://github.com/geonetwork/core-geonetwork/pull/6128) to easily create new records
+- [Editing / Database search and replace](https://github.com/geonetwork/core-geonetwork/pull/6188)
+- [Editing / Batch editing examples and copy/paste facilities](https://github.com/geonetwork/core-geonetwork/pull/6239)
+- [Editing / Use directories for ISO19115-3 records](https://github.com/geonetwork/core-geonetwork/pull/6292) [Managing directories](../../administrator-guide/managing-classification-systems/managing-directories.md)
+- [Editing / Easily register service in Spatineo monitor for ISO19115-3](https://github.com/geonetwork/core-geonetwork/pull/6298)
+- [INSPIRE / Configure API endpoint and gateway URL](https://github.com/geonetwork/core-geonetwork/pull/6146)
+- [Admin / Languages / Easily remove unneeded languages](https://github.com/geonetwork/core-geonetwork/pull/5923) to keep admin form as simple as possible
+- [Admin / Harvesting / Order options according to processing](https://github.com/geonetwork/core-geonetwork/pull/6221) to better understand the harvesting steps
+- [Admin / Harvesting / JSON file support](https://github.com/geonetwork/core-geonetwork/pull/6251)
+- [Admin / Thesaurus / Improved form and add support for description](https://github.com/geonetwork/core-geonetwork/pull/6283)
+- [Admin / Link analysis / Filter by HTTP status.](https://github.com/geonetwork/core-geonetwork/pull/6255) Those status gives more details, a link could be valid with an authorization required status.
+
+and more \... see [4.2.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.2.0+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.1.md b/docs/manual/docs/overview/change-log/version-4.2.1.md
new file mode 100644
index 00000000000..35ed2b8b0a6
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.1.md
@@ -0,0 +1,39 @@
+# Version 4.2.1 {#version-421}
+
+GeoNetwork 4.2.1 release is a minor release.
+
+## List of changes
+
+Major changes:
+
+- Accessibility improvements on [map tools](https://github.com/geonetwork/core-geonetwork/pull/6211), [top tool bar skip link](https://github.com/geonetwork/core-geonetwork/pull/6217)
+
+- [Search / Aggregation / Add support for terms missing value](https://github.com/geonetwork/core-geonetwork/pull/6335)
+
+- [Record view / Group associated resources by type](https://github.com/geonetwork/core-geonetwork/pull/6328)
+
+- [Record view / More like this / Suggest records of same type](https://github.com/geonetwork/core-geonetwork/pull/6452)
+
+- [Record view / Preview tabular data](https://github.com/geonetwork/core-geonetwork/pull/6440)
+
+ 
+
+- DOI improvements: [Fix on published records](https://github.com/geonetwork/core-geonetwork/pull/6338), [Configure DOI URL pattern](https://github.com/geonetwork/core-geonetwork/pull/6347), [Disabled for metadata workflow](https://github.com/geonetwork/core-geonetwork/pull/6367), [Multilingual exception](https://github.com/geonetwork/core-geonetwork/pull/6472)
+
+- [Editing / Upload file or overview from main form](https://github.com/geonetwork/core-geonetwork/pull/6371)
+
+- [Editor configuration / Use condition on any elements](https://github.com/geonetwork/core-geonetwork/pull/6355)
+
+- [API / Batch editing / Add support for attribute](https://github.com/geonetwork/core-geonetwork/pull/6423)
+
+- [INSPIRE / Atom service migrated to Elasticsearch and Spring](https://github.com/geonetwork/core-geonetwork/pull/6395)
+
+- [Admin / Settings / Configure profile allowed to delete published metadata](https://github.com/geonetwork/core-geonetwork/pull/6398)
+
+- [Admin / Indexing error improvements](https://github.com/geonetwork/core-geonetwork/pull/6432)
+
+- [Print / Improve styling](https://github.com/geonetwork/core-geonetwork/pull/6517)
+
+- Library update: [Switch to OpenPDF](https://github.com/geonetwork/core-geonetwork/pull/6343), [Keycloak](https://github.com/geonetwork/core-geonetwork/pull/6531), [Log4j2](https://github.com/geonetwork/core-geonetwork/pull/6397)
+
+and more \... see [4.2.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.1+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.2.md b/docs/manual/docs/overview/change-log/version-4.2.2.md
new file mode 100644
index 00000000000..63df8c445ab
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.2.md
@@ -0,0 +1,21 @@
+# Version 4.2.2 {#version-422}
+
+GeoNetwork 4.2.2 release is a minor release.
+
+## List of changes
+
+Major changes:
+
+- [Authentication / OAuth2 OpenId Connect Single Sign-on and also support for OIDC Bearer tokens](https://github.com/geonetwork/core-geonetwork/pull/6494)
+- [Search / Aggregations / Add icon decorator](https://github.com/geonetwork/core-geonetwork/pull/6556)
+- [Search / Autocomplete improvements](https://github.com/geonetwork/core-geonetwork/pull/6555)
+- [Indexing / Add analyzer for Dutch](https://github.com/geonetwork/core-geonetwork/pull/6646)
+- [Indexing / Improve performance](https://github.com/geonetwork/core-geonetwork/pull/6632)
+- [Editor / Easier configuration for custom editor](https://github.com/geonetwork/core-geonetwork/pull/6629)
+- Feature catalogue now provides [a table of content](https://github.com/geonetwork/core-geonetwork/pull/6679) when multiple tables are described.
+- [Feature catalogue / Use ISO19115-3 instead of ISO19110](https://github.com/geonetwork/core-geonetwork/pull/6545)
+- [Admin / Improve layout for settings](https://github.com/geonetwork/core-geonetwork/pull/6600)
+- [CSW / Improve DCAT support](https://github.com/geonetwork/core-geonetwork/pull/6635)
+- [INSPIRE / Fix import from Re3gistry](https://github.com/geonetwork/core-geonetwork/pull/6617)
+
+and more \... see [4.2.2 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.2+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.2+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.3.md b/docs/manual/docs/overview/change-log/version-4.2.3.md
new file mode 100644
index 00000000000..cfc8aa74eac
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.3.md
@@ -0,0 +1,24 @@
+# Version 4.2.3 {#version-423}
+
+GeoNetwork 4.2.3 release is a minor release.
+
+After update, don't forget to go to admin console --> tools --> Delete index and reindex.
+
+## List of changes
+
+Major changes:
+
+- [Search / Multilingual support for contact, links and overview label](https://github.com/geonetwork/core-geonetwork/pull/6588)
+- [Search / CSW / Improve search on multilingual content](https://github.com/geonetwork/core-geonetwork/pull/6736)
+- [Search / Aggregations / Add support for filter aggregation on home page, better translations of database fields](https://github.com/geonetwork/core-geonetwork/pull/6737)
+- [SEO / Add sitemap configuration](https://github.com/geonetwork/core-geonetwork/pull/5579) and [permalink configuration](https://github.com/geonetwork/core-geonetwork/pull/6792) with DOI support.
+- [Record view / Series statistics improvements](https://github.com/geonetwork/core-geonetwork/pull/6743)
+- [Editor / Geopublication support geopackage and zipped geopackage](https://github.com/geonetwork/core-geonetwork/pull/6490)
+- [Harvester / Simple URL harvester now support XML document, multiple URLs, XSL conversion configuration](https://github.com/geonetwork/core-geonetwork/pull/6677)
+- [Harvester / Simple URL harvester now support RDF DCAT](https://github.com/geonetwork/core-geonetwork/pull/6771)
+- [Schema plugin / XSL conversions are dispatched in each schemas](https://github.com/geonetwork/core-geonetwork/pull/6772)
+- [Resources / Improve temporary file management](https://github.com/geonetwork/core-geonetwork/pull/6686)
+- [Javascript / Update to AngularJS 1.8.2](https://github.com/geonetwork/core-geonetwork/pull/6693)
+- [Javascript / WRO4J cache can be built at build time](https://github.com/geonetwork/core-geonetwork/pull/6774)
+
+and more \... see [4.2.3 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.3+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.3+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.4.md b/docs/manual/docs/overview/change-log/version-4.2.4.md
new file mode 100644
index 00000000000..f5e4092ed85
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.4.md
@@ -0,0 +1,38 @@
+# Version 4.2.4 {#version-424}
+
+GeoNetwork 4.2.4 release is a minor release.
+
+## Migration notes
+
+### Database changes
+
+- If using the pages API, consider checking the `spg_page` database table ([More information](https://github.com/geonetwork/core-geonetwork/pull/7005)) during migration.
+
+### API changes
+
+- API for link analysis
+ - `POST /links` is now `POST /links/analyze` to analyze all links in a set of records.
+ - `POST /links/analyze` to `POST /links/analyzeurl` to analyze a URL.
+ - `POST /links` allows now queries with large filter which was not supported using GET ([More information](https://github.com/geonetwork/core-geonetwork/pull/7022)).
+- API on pages is now more consistent ([More information](https://github.com/geonetwork/core-geonetwork/pull/6788)). Use `GET pages` to retrieve list of pages (instead of `GET pages/list`). Use `PUT` operation to create a new page or `POST` to upload a file for the page. Section and status can now updated when updating the page. A page label can now be defined. Format, sections and status can now be retrieved using the API.
+
+
+
+## List of changes
+
+Major changes:
+
+- Security / Library updates: [Spring](https://github.com/geonetwork/core-geonetwork/pull/7023), [SVN kit](https://github.com/geonetwork/core-geonetwork/pull/7017), [GeoTools](https://github.com/geonetwork/core-geonetwork/pull/6925), [Logging bridge](https://github.com/geonetwork/core-geonetwork/pull/6904)
+- [Languages / Fix loading of ICE, KOR and CZE language code](https://github.com/geonetwork/core-geonetwork/pull/7055) and [Danish added](https://github.com/geonetwork/core-geonetwork/pull/6933)
+- [Sharing / Configure profile allowed to publish/unpublish records](https://github.com/geonetwork/core-geonetwork/pull/6956)
+- [Sharing / Improve definition of the Intranet group](https://github.com/geonetwork/core-geonetwork/pull/6894)
+- [Portal / Check that portal exist and if not redirect to main one](https://github.com/geonetwork/core-geonetwork/pull/7034)
+- [Map / WMS Time and elevation support](https://github.com/geonetwork/core-geonetwork/pull/6820)
+- CSW / Transactions: [Record history of transactions](https://github.com/geonetwork/core-geonetwork/pull/7016) and [consistently apply update fixed info](https://github.com/geonetwork/core-geonetwork/pull/7004)
+- [Authentication / Easier extension of OpenID mode](https://github.com/geonetwork/core-geonetwork/pull/6965)
+- [Search / Improve performances for catalogs containing lot of overviews](https://github.com/geonetwork/core-geonetwork/pull/6895)
+- [CMIS / Performance improvements](https://github.com/geonetwork/core-geonetwork/pull/6893)
+- [Admin console / Pages manager](https://github.com/geonetwork/core-geonetwork/pull/6788)
+- [Editor configuration / Add for each support](https://github.com/geonetwork/core-geonetwork/pull/6907)
+
+and more \... see [4.2.4 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.4+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.4+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.5.md b/docs/manual/docs/overview/change-log/version-4.2.5.md
new file mode 100644
index 00000000000..6ae51bd48ff
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.5.md
@@ -0,0 +1,41 @@
+# Version 4.2.5 {#version-425}
+
+GeoNetwork 4.2.5 release is a minor release.
+
+## Migration notes
+
+### Database changes
+
+- Remove Language table isdefault column ([More information](https://github.com/geonetwork/core-geonetwork/pull/7169)).
+
+### API changes
+
+- API for link analysis
+ - `PUT /records` when using OVERWRITE mode only the XML of the metadata is updated. Use REMOVE_AND_REPLACE for previous mechanism which remove the existing metadata and inserting the new one. When workflow is enabled, OVERWRITE is not allowed ([More information](https://github.com/geonetwork/core-geonetwork/pull/7178)).
+
+### Index changes
+
+After update, don't forget to go to admin console --> tools --> Delete index and reindex.
+
+### Thesaurus changes
+
+If using the default regions thesaurus, [update the thesaurus dates before starting the application](https://github.com/geonetwork/core-geonetwork/pull/7208/files) ([More information](https://github.com/geonetwork/core-geonetwork/issues/7207)).
+
+## List of changes
+
+Major changes:
+
+- [Full text search / Add search by individual name and email](https://github.com/geonetwork/core-geonetwork/pull/7167)
+- [Map / Layer manager / Add support for multilingual layer title](https://github.com/geonetwork/core-geonetwork/pull/7121)
+- [RSS / Display RSS links when OGC API Records is installed](https://github.com/geonetwork/core-geonetwork/pull/7094)
+- [Workflow improvements](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.2.5+is%3Aclosed+workflow)
+- [CSW / DCAT / Fix for multilingual records](https://github.com/geonetwork/core-geonetwork/pull/7161)
+- [ATOM feeds / Support elements using anchor](https://github.com/geonetwork/core-geonetwork/pull/7156)
+- [SEO / Set HTML head title and description](https://github.com/geonetwork/core-geonetwork/pull/7080)
+- [DOI / Support European Union Publication Office format](https://github.com/geonetwork/core-geonetwork/pull/6979)
+- [User interface / Update Font-awesome icon library](https://github.com/geonetwork/core-geonetwork/pull/7007)
+- [Admin / Harvester / Fix log file access](https://github.com/geonetwork/core-geonetwork/pull/7127)
+- [Admin / Pages / Add support for submenu](https://github.com/geonetwork/core-geonetwork/pull/7138)
+- [Installation / Database / Add config property to turn off database creation/migration on startup](https://github.com/geonetwork/core-geonetwork/pull/7100)
+
+and more \... see [4.2.5 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.5+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.5+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.6.md b/docs/manual/docs/overview/change-log/version-4.2.6.md
new file mode 100644
index 00000000000..a6bbd571914
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.6.md
@@ -0,0 +1,19 @@
+# Version 4.2.6 {#version-426}
+
+GeoNetwork 4.2.6 release is a minor release.
+
+## Migration notes
+
+### Index changes
+
+After update, don't forget to go to admin console --> tools --> Delete index and reindex.
+
+## List of changes
+
+Major changes:
+
+- [API / CSV export / Add support for custom export](https://github.com/geonetwork/core-geonetwork/pull/7132)
+- [Map / WFS Features / Improvements](https://github.com/geonetwork/core-geonetwork/pull/7000)
+
+
+and more \... see [4.2.6 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.6+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.6+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.2.7.md b/docs/manual/docs/overview/change-log/version-4.2.7.md
new file mode 100644
index 00000000000..251365aeb4e
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.2.7.md
@@ -0,0 +1,14 @@
+# Version 4.2.7 {#version-427}
+
+GeoNetwork 4.2.7 release is a minor release.
+
+## List of changes
+
+Release highlights:
+
+- [Add more db information to the site information page](https://github.com/geonetwork/core-geonetwork/pull/7403)
+- [Fix cookies path when deployed on root "/" context](https://github.com/geonetwork/core-geonetwork/pull/7446)
+- [Security / Jolokia update](https://github.com/geonetwork/core-geonetwork/pull/7501)
+
+
+and more \... see [4.2.7 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.2.6+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.2.7+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.4.0.md b/docs/manual/docs/overview/change-log/version-4.4.0.md
new file mode 100644
index 00000000000..f2142230d3a
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.4.0.md
@@ -0,0 +1,37 @@
+# Version 4.4.0 {#version-440}
+
+GeoNetwork 4.4.0 release is a major release.
+
+## Migration notes
+
+### Java
+
+**Version 4.4 only works on Java 11.**
+
+### API changes
+
+- Groovy formatter support is removed. ([More information](https://github.com/geonetwork/core-geonetwork/pull/7346)).
+
+### Installation changes
+
+- Datastore / [To use CMIS, JCloud or S3 download the corresponding package](https://sourceforge.net/projects/geonetwork/files/GeoNetwork_opensource/v4.4.0/).
+
+### Index changes
+
+After update, don't forget to go to admin console --> tools --> Delete index and reindex.
+
+## List of changes
+
+Major changes:
+
+- [Java 11 support](https://github.com/geonetwork/core-geonetwork/pull/7186)
+- [Move datastorage providers to maven modules and include them in the build on demand](https://github.com/geonetwork/core-geonetwork/pull/7302)
+- [Docker configuration improvements](https://github.com/geonetwork/docker-geonetwork/pull/107)
+- [Improvements to allow future deployment of multiple instances](https://github.com/geonetwork/core-geonetwork/pull/7337)
+- [API / CSV export / Add support for custom export](https://github.com/geonetwork/core-geonetwork/pull/7132)
+- [INSPIRE / Validator / Add API usage information](https://github.com/geonetwork/core-geonetwork/pull/7284)
+- [Map / WMS / Add support for time dimension](https://github.com/geonetwork/core-geonetwork/pulls?q=is%3Apr+milestone%3A4.4.0+is%3Aclosed+WMS)
+- [Map / WFS Features / Improvements](https://github.com/geonetwork/core-geonetwork/pull/7000)
+
+
+and more \... see [4.4.0 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.4.0+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.4.0+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/change-log/version-4.4.1.md b/docs/manual/docs/overview/change-log/version-4.4.1.md
new file mode 100644
index 00000000000..46a226dad58
--- /dev/null
+++ b/docs/manual/docs/overview/change-log/version-4.4.1.md
@@ -0,0 +1,23 @@
+# Version 4.4.1 {#version-441}
+
+GeoNetwork 4.4.1 release is a minor release.
+
+## Migration notes
+
+### Java
+
+**Version 4.4 only works on Java 11.**
+
+### Index changes
+
+After update, don't forget to go to admin console --> tools --> Delete index and reindex.
+
+## List of changes
+
+Release highlights:
+
+- [Add more db information to the site information page](https://github.com/geonetwork/core-geonetwork/pull/7403)
+- [Fix cookies path when deployed on root "/" context](https://github.com/geonetwork/core-geonetwork/pull/7446)
+- [Security / Jolokia update](https://github.com/geonetwork/core-geonetwork/pull/7501)
+
+See [4.4.1 issues](https://github.com/geonetwork/core-geonetwork/issues?q=is%3Aissue+milestone%3A4.4.1+is%3Aclosed) and [pull requests](https://github.com/geonetwork/core-geonetwork/pulls?page=3&q=is%3Apr+milestone%3A4.4.1+is%3Aclosed) for full details.
diff --git a/docs/manual/docs/overview/index.md b/docs/manual/docs/overview/index.md
new file mode 100644
index 00000000000..cd91b9f0ac7
--- /dev/null
+++ b/docs/manual/docs/overview/index.md
@@ -0,0 +1,7 @@
+# Overview
+
+The GeoNetwork project started out in year 2001 as a Spatial Data Catalogue System for the Food and Agriculture organisation of the United Nations ([FAO](https://www.fao.org)), the United Nations World Food Programme ([WFP](https://www.wfp.org)) and the United Nations Environmental Programme ([UNEP](https://www.unep.org)).
+
+The project is widely used as the foundation of Spatial Data Infrastructures world wide (See [gallery](../annexes/gallery/index.md)).
+
+The GeoNetwork project is part of the Open Source Geospatial Foundation ([OSGeo](https://www.osgeo.org)) and can be found at [GeoNetwork opensource](https://geonetwork-opensource.org).
diff --git a/docs/manual/docs/overview/license/GPL.md b/docs/manual/docs/overview/license/GPL.md
new file mode 100644
index 00000000000..28fbecabf5c
--- /dev/null
+++ b/docs/manual/docs/overview/license/GPL.md
@@ -0,0 +1,361 @@
+### GNU GENERAL PUBLIC LICENSE
+
+Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+### Preamble
+
+The licenses for most software are designed to take away your freedom
+to share and change it. By contrast, the GNU General Public License is
+intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if
+you distribute copies of the software, or if you modify it.
+
+For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on,
+we want its recipients to know that what they have is not the
+original, so that any problems introduced by others will not reflect
+on the original authors' reputations.
+
+Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at
+all.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
+### TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+**0.** This License applies to any program or other work which
+contains a notice placed by the copyright holder saying it may be
+distributed under the terms of this General Public License. The
+"Program", below, refers to any such program or work, and a "work
+based on the Program" means either the Program or any derivative work
+under copyright law: that is to say, a work containing the Program or
+a portion of it, either verbatim or with modifications and/or
+translated into another language. (Hereinafter, translation is
+included without limitation in the term "modification".) Each licensee
+is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the Program
+(independent of having been made by running the Program). Whether that
+is true depends on what the Program does.
+
+**1.** You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a
+fee.
+
+**2.** You may modify your copy or copies of the Program or any
+portion of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+
+**a)** You must cause the modified files to carry prominent notices
+stating that you changed the files and the date of any change.
+
+
+**b)** You must cause any work that you distribute or publish, that in
+whole or in part contains or is derived from the Program or any part
+thereof, to be licensed as a whole at no charge to all third parties
+under the terms of this License.
+
+
+**c)** If the modified program normally reads commands interactively
+when run, you must cause it, when started running for such interactive
+use in the most ordinary way, to print or display an announcement
+including an appropriate copyright notice and a notice that there is
+no warranty (or else, saying that you provide a warranty) and that
+users may redistribute the program under these conditions, and telling
+the user how to view a copy of this License. (Exception: if the
+Program itself is interactive but does not normally print such an
+announcement, your work based on the Program is not required to print
+an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+**3.** You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+
+**a)** Accompany it with the complete corresponding machine-readable
+source code, which must be distributed under the terms of Sections 1
+and 2 above on a medium customarily used for software interchange; or,
+
+
+**b)** Accompany it with a written offer, valid for at least three
+years, to give any third party, for a charge no more than your cost of
+physically performing source distribution, a complete machine-readable
+copy of the corresponding source code, to be distributed under the
+terms of Sections 1 and 2 above on a medium customarily used for
+software interchange; or,
+
+
+**c)** Accompany it with the information you received as to the offer
+to distribute corresponding source code. (This alternative is allowed
+only for noncommercial distribution and only if you received the
+program in object code or executable form with such an offer, in
+accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+**4.** You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt otherwise
+to copy, modify, sublicense or distribute the Program is void, and
+will automatically terminate your rights under this License. However,
+parties who have received copies, or rights, from you under this
+License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+**5.** You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+**6.** Each time you redistribute the Program (or any work based on
+the Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+**7.** If, as a consequence of a court judgment or allegation of
+patent infringement or for any other reason (not limited to patent
+issues), conditions are imposed on you (whether by court order,
+agreement or otherwise) that contradict the conditions of this
+License, they do not excuse you from the conditions of this License.
+If you cannot distribute so as to satisfy simultaneously your
+obligations under this License and any other pertinent obligations,
+then as a consequence you may not distribute the Program at all. For
+example, if a patent license would not permit royalty-free
+redistribution of the Program by all those who receive copies directly
+or indirectly through you, then the only way you could satisfy both it
+and this License would be to refrain entirely from distribution of the
+Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+**8.** If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+**9.** The Free Software Foundation may publish revised and/or new
+versions of the General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Program does not specify a
+version number of this License, you may choose any version ever
+published by the Free Software Foundation.
+
+**10.** If you wish to incorporate parts of the Program into other
+free programs whose distribution conditions are different, write to
+the author to ask for permission. For software which is copyrighted by
+the Free Software Foundation, write to the Free Software Foundation;
+we sometimes make exceptions for this. Our decision will be guided by
+the two goals of preserving the free status of all derivatives of our
+free software and of promoting the sharing and reuse of software
+generally.
+
+**NO WARRANTY**
+
+**11.** BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+**12.** IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+### END OF TERMS AND CONDITIONS
+
+### How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these
+terms.
+
+To do so, attach the following notices to the program. It is safest to
+attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ one line to give the program's name and an idea of what it does.
+ Copyright (C) yyyy name of author
+
+ This program is free software; you can redistribute it and/or
+ modify it under the terms of the GNU General Public License
+ as published by the Free Software Foundation; either version 2
+ of the License, or (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+
+Also add information on how to contact you by electronic and paper
+mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+ type `show w'. This is free software, and you are welcome
+ to redistribute it under certain conditions; type `show c'
+ for details.
+
+The hypothetical commands \`show w' and \`show c' should show the
+appropriate parts of the General Public License. Of course, the
+commands you use may be called something other than \`show w' and
+\`show c'; they could even be mouse-clicks or menu items--whatever
+suits your program.
+
+You should also get your employer (if you work as a programmer) or
+your school, if any, to sign a "copyright disclaimer" for the program,
+if necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright
+ interest in the program `Gnomovision'
+ (which makes passes at compilers) written
+ by James Hacker.
+
+ signature of Ty Coon, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library,
+you may consider it more useful to permit linking proprietary
+applications with the library. If this is what you want to do, use the
+[GNU Lesser General Public
+License](https://www.gnu.org/licenses/lgpl.html) instead of this
+License.
diff --git a/docs/manual/docs/overview/license/index.md b/docs/manual/docs/overview/license/index.md
new file mode 100644
index 00000000000..192dc4d1872
--- /dev/null
+++ b/docs/manual/docs/overview/license/index.md
@@ -0,0 +1,3 @@
+# License
+
+The GeoNetwork opensource software is released under the [GPL v2 license](GPL.md) and can be used and modified free of charge.
diff --git a/docs/manual/docs/tutorials/customui/index.md b/docs/manual/docs/tutorials/customui/index.md
new file mode 100644
index 00000000000..29e5e76c028
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/index.md
@@ -0,0 +1,6 @@
+# Customize your GeoNetwork UI {#tuto-customui}
+
+- [Search page](search/index.md)
+- [Formatter](view/index.md)
+
+For editor customization see [Customizing editor](../../customizing-application/editor-ui/creating-custom-editor.md):.
diff --git a/docs/manual/docs/tutorials/customui/search/customview.md b/docs/manual/docs/tutorials/customui/search/customview.md
new file mode 100644
index 00000000000..316e5b51afb
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/search/customview.md
@@ -0,0 +1,23 @@
+# Customizing default view {#tuto-search-customview}
+
+Follow [instructions](../../../customizing-application/search-ui/customview.md) and create your first custom view.
+
+## Exercices
+
+1. Create a new view with almost no content
+2. Make your new view looks like the default one
+3. Create your own result list template
+4. Make main templates url customizable.
+5. Put the search map upon facets
+6. Let's build a new search page quickly
+
+## Corrections
+
+Go to
+
+1. step-1
+2. step-2
+3. step-3
+4. step-4
+5. step-5
+6. step-6
diff --git a/docs/manual/docs/tutorials/customui/search/defaultview.md b/docs/manual/docs/tutorials/customui/search/defaultview.md
new file mode 100644
index 00000000000..6d9de9e456c
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/search/defaultview.md
@@ -0,0 +1,34 @@
+# Customizing default view {#tuto-search-defaultview}
+
+## Objectives
+
+Read instructions about [default view customization](../../../customizing-application/search-ui/configdefault.md).
+
+- Understand view settings.
+- Be able to customize the default view.
+
+## Exercices
+
+- Propose 4 hits per page options for search result list : 2, 5, 10, 20.
+
+- Propose to sort only by change date and title.
+
+- Use Stamen layer source for search map background.
+
+- Recenter search map on Seoul
+
+-
+
+ Change full map configuration
+
+ : - play with initial extent
+ - change brackground layer list
+ - add WMS layers to the default map
+
+- Change default location for map search
+
+- Change WMS/WMTS default services
+
+- Customize full map without OWS Context
+
+- Disable map viewer
diff --git a/docs/manual/docs/tutorials/customui/search/index.md b/docs/manual/docs/tutorials/customui/search/index.md
new file mode 100644
index 00000000000..0beb8cbb438
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/search/index.md
@@ -0,0 +1,5 @@
+# Search page {#tuto-customui-search}
+
+- [Understand loading page mechanisms](loadpage.md)
+- [Customizing default view](defaultview.md)
+- [Customizing default view](customview.md)
diff --git a/docs/manual/docs/tutorials/customui/search/loadpage.md b/docs/manual/docs/tutorials/customui/search/loadpage.md
new file mode 100644
index 00000000000..ddfa51fbdf2
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/search/loadpage.md
@@ -0,0 +1,29 @@
+# Understand loading page mechanisms {#tuto-search-loadpage}
+
+## Objectives
+
+Read instructions in [customization section](../../../customizing-application/search-ui/loadview.md).
+
+- understand the XSL service output
+- look at the `view` parameter
+- understand main template loading
+- understand javascript modules bootstrap
+
+## Resources
+
+- XSLT files
+ - [base layout](https://github.com/geonetwork/core-geonetwork/blob/main/web/src/main/webapp/xslt/base-layout.xsl).
+ - [js and css loader](https://github.com/geonetwork/core-geonetwork/blob/main/web/src/main/webapp/xslt/base-layout-cssjs-loader.xsl).
+ - [variables](https://github.com/geonetwork/core-geonetwork/blob/main/web/src/main/webapp/xslt/common/base-variables.xsl).
+ - [search page](https://github.com/geonetwork/core-geonetwork/blob/main/web/src/main/webapp/xslt/ui-search/search.xsl).
+- Template files
+
+
+
+- AngularJS module
+
+
+
+- Less file
+
+
diff --git a/docs/manual/docs/tutorials/customui/view/formatter.md b/docs/manual/docs/tutorials/customui/view/formatter.md
new file mode 100644
index 00000000000..dde5d94ca6d
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/view/formatter.md
@@ -0,0 +1,225 @@
+# Create a new formatter {#tuto-formatter}
+
+## Objectives
+
+- oversee groovy formatter mechnism
+- understand handlers, matchers concepts
+- create a small formatter
+
+## Exercices
+
+1. Add a new formatter that display all text information of the metadata in basic layout.
+2. Update previous formatter to display labels of the text fields.
+3. Use formatter templating system to render the handler's view
+4. Add styling to your formatter view.
+5. Create a tree for rendering elements
+6. Use translation of iso elements
+7. Use default tree styling
+8. Use all default view formatter elements
+9. Customise default formatter view
+10. Overload handlers methods
+
+## Corrections
+
+Go to
+
+1. Create a new formatter
+
+ - create a new folder named 'foss4g" in /schemas/iso19139/src/main/plugin/iso19139/formatter
+
+ - create a new groovy file in this new folder
+
+ - text information are stored in `gco:CharacterString`
+
+ ``` groovy
+ handlers.add 'gco:CharacterString', {el -> "
${el.text()}
"}
+ ```
+
+2. Add a matcher and play with `name` and `text` properties.
+
+ ``` groovy
+ handlers.add select: {el -> !el.'gco:CharacterString'.text().isEmpty()}, {el ->
+ "
'
+ }
+
+ def isoHandlers = new iso19139.Handlers(handlers, f, env)
+
+ handlers.add select: isoHandlers.matchers.isTextEl, isoHandlers.isoTextEl
+ handlers.add name: 'Container Elements',
+ select: isoHandlers.matchers.isContainerEl,
+ priority: -1,
+ isoHandlers.commonHandlers.entryEl(f.&nodeLabel,
+ isoHandlers.addPackageViewClass)
+ isoHandlers.addExtentHandlers()
+ ```
+
+8. See `SummaryFactory` class.
+
+ - view.groovy
+
+ ``` groovy
+ import iso19139.SummaryFactory
+
+ def isoHandlers = new iso19139.Handlers(handlers, f, env)
+
+ SummaryFactory.summaryHandler({it.parent() is it.parent()}, isoHandlers)
+
+ isoHandlers.addDefaultHandlers()
+ ```
+
+9. Add custom option to the `SummaryFactory`
+
+ - view.groovy
+
+ ``` groovy
+ import iso19139.SummaryFactory
+
+ def isoHandlers = new iso19139.Handlers(handlers, f, env)
+
+ def factory = new SummaryFactory(isoHandlers, {summary ->
+ summary.title = "My Title"
+ summary.addCompleteNavItem = false
+ summary.addOverviewNavItem = false
+ summary.associated.clear()
+ })
+
+
+ handlers.add name: "Summary Handler",
+ select: {it.parent() is it.parent()},
+ {factory.create(it).getResult()}
+ isoHandlers.addDefaultHandlers()
+ ```
+
+10. Add custom behavior to `iso19139.Handlers` constructor
+
+ - view.groovy
+
+ ``` groovy
+ def isoHandlers = new iso19139.Handlers(handlers, f, env) {
+ {
+ def oldImpl = super.isoTextEl
+ isoTextEl = { el ->
+ "----------- ${oldImpl(el)}"
+ }
+ }
+ }
+ ```
diff --git a/docs/manual/docs/tutorials/customui/view/index.md b/docs/manual/docs/tutorials/customui/view/index.md
new file mode 100644
index 00000000000..d7b04aebd9a
--- /dev/null
+++ b/docs/manual/docs/tutorials/customui/view/index.md
@@ -0,0 +1,3 @@
+# Formatter {#tuto-customui-viw}
+
+- [Create a new formatter](formatter.md)
diff --git a/docs/manual/docs/tutorials/hookcustomizations/events/index.md b/docs/manual/docs/tutorials/hookcustomizations/events/index.md
new file mode 100644
index 00000000000..07886cda8a2
--- /dev/null
+++ b/docs/manual/docs/tutorials/hookcustomizations/events/index.md
@@ -0,0 +1,73 @@
+# Using Events {#tuto-hookcustomizations-events}
+
+From GeoNetwork 3.0.x on, there are a number of events you can listen to on your Java code.
+
+## Enabling Event Listeners
+
+To enable this on your Maven project, you have to add the event dependencies. Edit the file **`custom/pom.xml`** and add the dependencies tag:
+
+``` xml
+
+
+ ${project.groupId}
+ events
+ ${project.version}
+
+
+ ${project.groupId}
+ core
+ ${project.version}
+
+
+```
+
+Then create the file custom/src/main/resources/config-spring-geonetwork.xml to tell Spring to load your custom beans adding the following content:
+
+``` xml
+
+
+
+
+```
+
+This file should contain a list of all the classes that listen to events inside GeoNetwork scope.
+
+## Simple Example
+
+We can add a simple example listener like this one, which will print a string every time a metadata gets removed.
+
+``` java
+package org.fao.geonet.events.listeners;
+
+import org.fao.geonet.domain.*;
+
+import org.fao.geonet.events.md.MetadataRemove;
+
+import org.springframework.context.ApplicationListener;
+
+import org.springframework.stereotype.Component;
+
+@Component
+public class MyCustomListener implements ApplicationListener {
+ @Override
+ public void onApplicationEvent(MetadataRemove event) {
+ System.out.println("REMOVED");
+ }
+}
+```
+
+For example, we can call an external REST API that gets triggered every time a Metadata gets removed or updated.
+
+## GeoNetwork API
+
+There is also a new API you can use to interact with GeoNetwork from an external script. See more on [API Guide](../../../api/index.md).
diff --git a/docs/manual/docs/tutorials/hookcustomizations/index.md b/docs/manual/docs/tutorials/hookcustomizations/index.md
new file mode 100644
index 00000000000..96c1838a3e0
--- /dev/null
+++ b/docs/manual/docs/tutorials/hookcustomizations/index.md
@@ -0,0 +1,11 @@
+# Hook your own code {#tuto-hookcustomizations}
+
+At the end of this tutorial, you should be able to customize your own code into GeoNetwork on a clean and easy to upgrade way. You should start with the [GeoNetwork Orientation](../introduction/index.md) tutorial first.
+
+- [Separate your code](newproject/index.md)
+- [Using Events](events/index.md)
+- [Adding new User Interface](ui/index.md)
+- [Schema Plugins](schemaplugins/index.md)
+- [Search Fields](searchfields/index.md)
+
+For ui customization see [Customize your GeoNetwork UI](../customui/index.md).
diff --git a/docs/manual/docs/tutorials/hookcustomizations/newproject/img/listprojects.png b/docs/manual/docs/tutorials/hookcustomizations/newproject/img/listprojects.png
new file mode 100644
index 00000000000..87960aa1d6d
Binary files /dev/null and b/docs/manual/docs/tutorials/hookcustomizations/newproject/img/listprojects.png differ
diff --git a/docs/manual/docs/tutorials/hookcustomizations/newproject/index.md b/docs/manual/docs/tutorials/hookcustomizations/newproject/index.md
new file mode 100644
index 00000000000..2a2aaaaece1
--- /dev/null
+++ b/docs/manual/docs/tutorials/hookcustomizations/newproject/index.md
@@ -0,0 +1,104 @@
+# Separate your code {#tuto-hookcustomizations-newproject}
+
+GeoNetwork is built using Maven. This means, there are several folders inside the source code and each of them is a different Maven project that can be built separately.
+
+
+
+## Create your own project
+
+The best way to work with GeoNetwork and easily upgrade later is add your own Maven project(s) to the Maven build stack, so GeoNetwork code remains unaltered and your changes are decoupled.
+
+To do this, go to the root folder of the source code and create a new folder. This can be done on a GNU/Linux terminal using the following command:
+
+``` shell
+cd core-geonetwork
+mkdir custom
+```
+
+Then we have to tell Maven this is a new project that can be built. So we add a new file called pom.xml on this "custom" folder and add the following:
+
+``` xml
+
+
+ 4.0.0
+
+
+ org.geonetwork-opensource
+ geonetwork
+ 3.1.0-SNAPSHOT
+
+
+ org.geonetwork-opensource
+ custom
+ jar
+ Hook your customizations tutorial
+
+
+
+
+ General Public License (GPL)
+ http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
+ repo
+
+
+
+
+ ${project.build.directory}/${project.build.finalName}
+
+
+
+
+ tests-and-static-analysis
+
+ !skipTests
+
+
+
+
+```
+
+## Add your project
+
+Then you should add it to the list of projects Maven will automatically build. On the root folder of the source code, edit the file pom.xml and add your own project:
+
+``` xml
+
+ schemas-test
+ web-ui
+ custom
+ web-ui-docs
+ web-client
+ web
+
+```
+
+The idea is that not only we build the project, but also add it to the war file that is being generated. To do this, we edit the file web/pom.xml and add our project as a new dependency inside the tag dependencies:
+
+``` xml
+
+ ${project.groupId}
+ custom
+ ${project.version}
+
+```
+
+And on the same file, we should also add our resources folder to the build (if we are going to modify the UI, which we will on this tutorial):
+
+``` xml
+
+ ${project.basedir}/../custom/src/main/resources
+
+```
+
+``` xml
+
+ ${project.basedir}/src/main/webapp,
+ ${rootProjectDir}/web-ui/src/main/resources/,
+ ${rootProjectDir}/custom/src/main/resources/,
+ ${build.webapp.resources}
+
+```
+
+Now, if we build GeoNetwork, it will also build and add our project.
diff --git a/docs/manual/docs/tutorials/hookcustomizations/schemaplugins/index.md b/docs/manual/docs/tutorials/hookcustomizations/schemaplugins/index.md
new file mode 100644
index 00000000000..315cb09973c
--- /dev/null
+++ b/docs/manual/docs/tutorials/hookcustomizations/schemaplugins/index.md
@@ -0,0 +1,3 @@
+# Schema Plugins {#tuto-hookcustomizations-schemaplugins}
+
+See [Implementing schema plugins](../../../customizing-application/implementing-a-schema-plugin.md)
diff --git a/docs/manual/docs/tutorials/hookcustomizations/searchfields/index.md b/docs/manual/docs/tutorials/hookcustomizations/searchfields/index.md
new file mode 100644
index 00000000000..7cfa53e4cd0
--- /dev/null
+++ b/docs/manual/docs/tutorials/hookcustomizations/searchfields/index.md
@@ -0,0 +1,50 @@
+# Search Fields {#tuto-hookcustomizations-searchfields}
+
+Lucene is the search engine used by GeoNetwork. All Lucene configuration is defined in WEB-INF/config-lucene.xml.
+
+In some cases it's relevant to modify or extend the search fields of the metadata index. For example to add a field (which is then searchable or can be used in a default view) or change the content of the field is created from the metadata (indexation).
+
+## Adding a new field
+
+Each schema contains a file index-fields/default.xsl where the fields stored on the index are defined. This is an xslt that runs over the xml of the metadata and creates the different field tags that Lucene will recognize and process.
+
+``` xml
+
+
+
+```
+
+This fields can then be used as parameters on the Q service, to search by that field.
+
+Remember that after every change on the index configuration, a new index should be rebuilt.
+
+## Summaries
+
+The Q service returns the list of search results, but also can return a summary of the results returned with the parameters "buildSummary=true" and "summaryType=\$summary".
+
+This summary is a list of the most common values for certain fields. This summaries are defined on web/src/main/webapp/WEB-INF/config-summary.xml:
+
+``` xml
+
+
+
+```
+
+The items used on this summaries have to be defined on the upper tag called "facets".
+
+## Boost fields
+
+Sometimes we want some field to be more relevant on the search than others. We can boost those fields inside the tag fieldBoosting .The boost is a positive or negative float value.
+
+``` xml
+
+
+
+
+
+
+
+
+```
+
+See more on [Configuring search fields](../../../customizing-application/configuring-search-fields.md)
diff --git a/docs/manual/docs/tutorials/hookcustomizations/ui/index.md b/docs/manual/docs/tutorials/hookcustomizations/ui/index.md
new file mode 100644
index 00000000000..f014d42a6b0
--- /dev/null
+++ b/docs/manual/docs/tutorials/hookcustomizations/ui/index.md
@@ -0,0 +1,114 @@
+# Adding new User Interface {#tuto-hookcustomizations-ui}
+
+To completely understand this part of the tutorial, it would be good to be familiarized with the [Customize your GeoNetwork UI](../../customui/index.md) tutorial first.
+
+In GeoNetwork you can have more than one style installed on the same deployment. You can select which style to use on the Settings manager. Also, you can use the parameter "?view=\$name" to force a specific style on a page request.
+
+## Create an empty style
+
+Now, we are going to create our custom style on the separated Maven project we created before. First we define the minimal user interface customization so we can test that our style is being generated and used.
+
+We need an empty file on the custom/src/main/resources/catalog/views/custom/less/gn_search_custom.less path
+
+Then we need to define the basic Angular module that will be used on this style. Create a file on custom/src/main/resources/catalog/views/custom/module.js and add the following content:
+
+``` javascript
+( function() {
+ goog.provide('gn_search_custom');
+ goog.require('gn_search');
+ var module = angular.module('gn_search_custom', ['gn_search']);
+})();
+```
+
+Next we create a new file on custom/src/main/resources/catalog/views/custom/templates/index.html and add the following content:
+
+``` html
+
This is my custom GeoNetwork
+```
+
+Finally we have to tell the wro4j library where our files will be. Edit the file web-ui/src/main/resources/WEB-INF/classes/web-ui-wro-sources.xml and add our folders:
+
+``` xml
+
+
+
+
+
+
+
+
+
+
+```
+
+Now, if we build, deploy and enter GeoNetwork, we can use this new style called "custom":
+
+## Import default style
+
+You can import the default style to have an easy start on your new style.
+
+Edit custom/src/main/resources/catalog/views/custom/less/gn_search_custom.less and add the following line:
+
+``` less
+@import "gn_search_default.css";
+```
+
+Then make the Angular module dependant of the default Angular UI module. Edit custom/src/main/resources/catalog/views/custom/module.js and replace the contents with:
+
+``` javascript
+( function() {
+ goog.provide('gn_search_custom');
+ goog.require('gn_search_default');
+ var module = angular.module('gn_search_custom', ['gn_search_default']);
+})();
+```
+
+Finally, replace the file custom/src/main/resources/catalog/views/custom/templates/index.html with the contents of the file web-ui/src/main/resources/catalog/views/default/templates/index.html
+
+You have now a duplicate of the default style you can improve with your own customizations.
+
+One of the main advantages of having your code decoupled is that you can override some of the files that comes by default on the GeoNetwork user interface and this overriding will not collide with future upgrades of the code.
+
+## Modify Search Results
+
+One of the most common customizations on the styling of GeoNetwork is to modify the appearance of the search result list. We can point to a different template on the config.js file. Edit the file custom/src/main/resources/catalog/views/custom/config.js and modify the property searchSettings.resultViewTpls.
+
+``` javascript
+searchSettings.resultViewTpls = [{
+ tplUrl: '../../catalog/views/custom/resultsview/' +
+ 'partials/viewtemplates/grid.html',
+ tooltip: 'Grid',
+ icon: 'fa-th'
+}];
+```
+
+And now we have to create the referenced file web-ui/src/main/resources/catalog/views/custom/resultsview/partials/viewtemplates/grid.html and use the template we want, like:
+
+``` html
+
+
+
+
+
+
+
+
+
+
{{md.status_text[0]}}
+
+
+
+
+
+```
+
+We can define any class we want and reference it on the gn_search_default.css file to give it some styling.
diff --git a/docs/manual/docs/tutorials/index.md b/docs/manual/docs/tutorials/index.md
new file mode 100644
index 00000000000..7c4e95fab4e
--- /dev/null
+++ b/docs/manual/docs/tutorials/index.md
@@ -0,0 +1,6 @@
+# Tutorials
+
+- [GeoNetwork Orientation](introduction/index.md)
+- [Customize your GeoNetwork UI](customui/index.md)
+- [Hook your own code](hookcustomizations/index.md)
+- [Tutorials](inspire/index.md)
diff --git a/docs/manual/docs/tutorials/inspire/download-atom.md b/docs/manual/docs/tutorials/inspire/download-atom.md
new file mode 100644
index 00000000000..41eeaa735fd
--- /dev/null
+++ b/docs/manual/docs/tutorials/inspire/download-atom.md
@@ -0,0 +1,65 @@
+# Setting up an Atom/OpenSearch based INSPIRE download service {#tuto-download-atom}
+
+This tutorial shows how one can set up GeoNetwork to provide download services following [technical guidelines for download services](https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-download-services).
+
+Note that the technical guidelines allow both Atom/OpenSearch as well as [WFS](https://www.opengeospatial.org/standards/wfs). This tutorial describes how to set up a download service using Atom/Opensearch.
+
+The basics of Atom/OpenSearch is that for each dataset a number of file-downloads in various flavours (language/projection/format) is available. These flavours are advertised in a "Dataset Atom Feed" document. A set of "Dataset Atom Feed" documents is grouped into a "Service Atom Feed" document. For each "Service Atom Feed" document an OpenSearchDescription document is available. A website can refer to this OpenSearchDescription document, which enables searching through the download service using the browser search bar (OpenSearch).
+
+See:
+
+- [Linking data using ATOM feeds](../../user-guide/associating-resources/linking-online-resources.md#linking-data-using-atom-feed)
+- [OpenSearch and INSPIRE ATOM](../../api/opensearch.md)
+
+## External mode implementation
+
+GeoNetwork implements OpenSearch on a set of Dataset- and Service Atom feeds. An OpenSearch Description document is generated for each Service Atom Feed.
+
+GeoNetwork will soon support an internal- and external mode.
+
+- in internal mode GeoNetwork will generate Atom files dynamically from metadata content.
+- in external mode GeoNetwork will ingest Atom files that are linked to metadata records.
+
+Currently only the external mode is fully supported. Atom files can be generated in any text or xml editor following the technical guidelines. To optimise the Atom support GeoNetwork uses a convention, which is currently not mandated by the technical guidelines. The convention is that any gmd:MD_Distribution having a link to an Atom file requires the protocol field to contain a defined value to indicate the distribution as being an Atom document. Default value for this protocol is INSPIRE-ATOM, but you can change it using Admin --> Settings. The benefit of this approach is that GeoNetwork doesn't need to open any file-link to determine if it is an Atom File. We've seen various member states mandate this convention in localised INSPIRE Technical Guidelines.
+
+``` xml
+
+
+
+
+ http://www.broinspireservices.nl/atom/awp.atom
+
+
+ INSPIRE-ATOM
+
+
+ gdn.Aardwarmtepotentie
+
+
+
+
+```
+
+When deploying Geonetwork, make sure the GEMET thesauri are loaded and activate the INSPIRE editor as described in [inspire configuration](../../administrator-guide/configuring-the-catalog/inspire-configuration.md). In this file "schemas/iso19139/src/main/plugin/iso19139/loc/eng/labels.xml " (and the same file in other languages in use in the catalogue) in the gmd:protocol helper (around line 2000) add the "INSPIRE-ATOM" protocol which is used to indicate links that link to an Atom file (only links having that protocol value will be ingested).
+
+In Admin --> Settings activate the INSPIRE extension and activate Atom harvesting (at certain interval). The settings page facilitates to set a protocol which is used in metadata to indicate an Atom link.
+
+
+
+For each dataset that you are going to publish create an iso19115 record using the INSPIRE template. Link each record to the related atom file (or upload an atom file)
+
+
+
+Make sure the metadata contains the same gmd:code as used in the Atom file.
+
+Now create a service metadata using the INSPIRE template and link it to the service Atom and the individual datasets (using srv:operatesOn).
+
+Before you validate the implementation, run the Atom harvester in admin --> settings manually. A panel will display the number of processed Atom feeds and any errors that may have occurred while processing (more details in log file).
+
+## Validate the implementation
+
+If you are running the above setup online, you can use the [INSPIRE validator](https://inspire.ec.europa.eu/validator/). If the above setup is running locally, you can use [Esdin Test Framework](https://github.com/Geonovum/etf-test-projects-inspire) to validate the INSPIRE setup.
+
+
+
+Running the test frequently during development helps to identify issues in an early stage.
diff --git a/docs/manual/docs/tutorials/inspire/download-geoserver.md b/docs/manual/docs/tutorials/inspire/download-geoserver.md
new file mode 100644
index 00000000000..a90a5ec13c7
--- /dev/null
+++ b/docs/manual/docs/tutorials/inspire/download-geoserver.md
@@ -0,0 +1,49 @@
+# Setting up a WFS based INSPIRE download service with GeoServer {#tuto-download-geoserver}
+
+This tutorial shows how one can set up a combination of GeoNetwork and GeoServer to provide download services following [technical guidelines for download services](https://inspire.ec.europa.eu/documents/technical-guidance-implementation-inspire-download-services).
+
+Note that the technical guidelines allow both Atom/OpenSearch as well as [WFS](https://www.opengeospatial.org/standards/wfs). This tutorial describes how to set up a download service using WFS.
+
+## GeoServer
+
+To support the INSPIRE data models the geoserver ["appschema" plugin](https://docs.geoserver.org/stable/en/user/data/app-schema/) needs to be installed. Configuring appschema support in GeoServer is not the goal of this tutorial. Appschema support for INSPIRE is nicely documented by [Marcus Sen](https://data.gov.uk/sites/default/files/library/INSPIREWFSCookbook_v1.0.pdf). Another valuable resource is available at [geosolutions](https://www.geo-solutions.it/blog/inspire-support-in-geoserver-made-easy-with-hale/). In this tutorial we'll focus on metadata aspects of a WFS download service.
+
+Download and install GeoServer INSPIRE extension as documented in [installing inspire extension](https://docs.geoserver.org/latest/en/user/extensions/inspire/using.html)
+
+Create at least one workspace per data model. On workspace properties activate "Settings" and set the selected service type (WFS).
+
+
+
+On WFS settings, select the new workspace and fill out the form (keep service metadata url empty for now) as described in [using inspire extension](https://docs.geoserver.org/latest/en/user/extensions/inspire/using.html). If the new workspace is not in the pull down, return to previous step and make sure "Settings" is activated for the workspace. If the INSPIRE fields are not visible, make sure the INSPIRE extension is correctly installed.
+
+
+
+Create featuretypes according to the appschema documentation.
+
+## GeoNetwork
+
+When deploying GeoNetwork, make sure the GEMET thesauri are loaded and activate the INSPIRE editor as described in [inspire documentation](../../administrator-guide/configuring-the-catalog/inspire-configuration.md).
+
+In Admin --> Settings activate the INSPIRE extension.
+
+
+
+For each dataset that you are going to publish create an iso19115 record using the INSPIRE template. Link each record to a download service as created in geoserver: eg
+
+
+
+Create an OGC harvester that is able to extract a metadata for service (iso19119) record from the WFS. Run the harvester and note down the identifier of the created service metadata.
+
+## Return to GeoServer
+
+For each layer add a metadata url to the layer configuration of type application/vnd.ogc.csw.GetRecordByIdResponse_xml.
+
+On the WFS-settings --> INSPIRE workspace add the link to the service metadata. In contradiction to WMS does WFS not link from a featuretype (layer) to metadata, instead the links to dataset metadata have to be added as part of the extende INSPIRE capabilities.
+
+## Validate the implementation
+
+If you are running the above setup online, you can use the [pilot JRC INSPIRE validator](https://inspire-geoportal.ec.europa.eu/validator2/). If the above setup is running locally, you can use [Esdin Test Framework](https://github.com/Geonovum/etf-test-projects-inspire) to validate the INSPIRE setup.
+
+
+
+Running the test frequently during development helps to identify issues in an early stage.
diff --git a/docs/manual/docs/tutorials/inspire/img/image_0.png b/docs/manual/docs/tutorials/inspire/img/image_0.png
new file mode 100644
index 00000000000..b689ddaa382
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_0.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_1.png b/docs/manual/docs/tutorials/inspire/img/image_1.png
new file mode 100644
index 00000000000..0b755f3f9c4
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_1.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_2.png b/docs/manual/docs/tutorials/inspire/img/image_2.png
new file mode 100644
index 00000000000..46ec1fcd87d
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_2.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_3.png b/docs/manual/docs/tutorials/inspire/img/image_3.png
new file mode 100644
index 00000000000..bf55c5b17ce
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_3.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_4.png b/docs/manual/docs/tutorials/inspire/img/image_4.png
new file mode 100644
index 00000000000..162e4a1df3d
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_4.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_5.png b/docs/manual/docs/tutorials/inspire/img/image_5.png
new file mode 100644
index 00000000000..1cefd07d900
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_5.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_6.png b/docs/manual/docs/tutorials/inspire/img/image_6.png
new file mode 100644
index 00000000000..163c2986ded
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_6.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_7.png b/docs/manual/docs/tutorials/inspire/img/image_7.png
new file mode 100644
index 00000000000..5408bd804ec
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_7.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_8.png b/docs/manual/docs/tutorials/inspire/img/image_8.png
new file mode 100644
index 00000000000..2d7e7e087a1
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_8.png differ
diff --git a/docs/manual/docs/tutorials/inspire/img/image_9.png b/docs/manual/docs/tutorials/inspire/img/image_9.png
new file mode 100644
index 00000000000..f84449b7a1a
Binary files /dev/null and b/docs/manual/docs/tutorials/inspire/img/image_9.png differ
diff --git a/docs/manual/docs/tutorials/inspire/index.md b/docs/manual/docs/tutorials/inspire/index.md
new file mode 100644
index 00000000000..ba501e95d2a
--- /dev/null
+++ b/docs/manual/docs/tutorials/inspire/index.md
@@ -0,0 +1,8 @@
+# Tutorials {#tutorials_inspire}
+
+The tutorials in this section target specific GeoNetwork implementation scenarios related to the [European INSPIRE Directive](https://inspire.ec.europa.eu/). INSPIRE mandates European organisations to set up view- and download services and to describe them using metadata in discovery services. To respond to all aspects of the technical guidelines requires to compose an infrastructure of various components. For now we provide tutorials for view services in [mapserver](view-mapserver.md) and [geoserver](view-geoserver.md) and download services using [Atom](download-atom.md) and [Tutorial setting up a WFS based INSPIRE download service with GeoServer](download-geoserver.md).
+
+- [Setting up INSPIRE view service with GeoNetwork and GeoServer](view-geoserver.md)
+- [Setting up INSPIRE view service with GeoNetwork and Mapserver](view-mapserver.md)
+- [Setting up an Atom/OpenSearch based INSPIRE download service](download-atom.md)
+- [Setting up a WFS based INSPIRE download service with GeoServer](download-geoserver.md)
diff --git a/docs/manual/docs/tutorials/inspire/view-geoserver.md b/docs/manual/docs/tutorials/inspire/view-geoserver.md
new file mode 100644
index 00000000000..49b560fc55f
--- /dev/null
+++ b/docs/manual/docs/tutorials/inspire/view-geoserver.md
@@ -0,0 +1,55 @@
+# Setting up INSPIRE view service with GeoNetwork and GeoServer {#tuto-view-geoserver}
+
+This tutorial shows how one can set up a combination of GeoServer and GeoNetwork to provide view services following [technical guidelines for view services](https://inspire.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.1.pdf).
+
+Note that the technical guidelines allow both [WMS](https://www.opengeospatial.org/standards/wms) as well as [WMTS](https://www.opengeospatial.org/standards/wmts). Select the service type which matches your use case or both. WMTS is generally the preferred choice for bigger datasets (facilitates to meet the quality of service requirements). WMS is generally the better choice for datasets with a high update frequency. GeoServer has improved its WMTS support in recent versions (2.10+). Older versions can not be used for providing WMTS according to INSPIRE technical guidelines.
+
+## GeoServer
+
+Download and install GeoServer INSPIRE extension as documented in [installing inspire extension](https://docs.geoserver.org/latest/en/user/extensions/inspire/installing.html)
+
+Create a workspace from which the INSPIRE layers will be hosted. On workspace properties activate "Settings" and set the selected services (WMS/WMTS). Limit the number of projections to the required INSPIRE projections. Keeping all default geoserver projections will cause serious performance issues.
+
+
+
+On WMS/WMTS settings, select the INSPIRE workspace and fill out the form (keep service metadata url empty for now) as described in [using inspire extension](https://docs.geoserver.org/latest/en/user/extensions/inspire/using.html#inspire-using). If the INSPIRE workspace is not in the pull down, return to previous step and make sure "Settings" is activated for the workspace. If the INSPIRE fields are not visible, make sure the INSPIRE extension is correctly installed.
+
+
+
+Create layers as described in [layer management](https://docs.geoserver.org/latest/en/user/data/webadmin/layers.html)
+
+
+
+## GeoNetwork
+
+When deploying Geonetwork, make sure the GEMET thesauri are loaded and activate the INSPIRE editor as described in [inspire documentation](../../administrator-guide/configuring-the-catalog/inspire-configuration.md).
+
+In Admin --> Settings activate the INSPIRE extension.
+
+
+
+For each dataset that you are going to publish create an iso19115 record using the INSPIRE template. Link each record to the view service as created in geoserver: eg
+
+
+
+Make sure the metadata contains the same gmd:code (and authority) as used in WMS getcapabilities.
+
+Create an OGC harvester that is able to extract a metadata for service (iso19119) record from the WM(T)S. Run the harvester and note down the identifier of the created service metadata.
+
+## Return to GeoServer
+
+For each layer add a link to the metadata of type application/vnd.ogc.csw.GetRecordByIdResponse_xml.
+
+On the WM(T)S-settings --> INSPIRE workspace add a link to the service metadata
+
+## Validate the implementation
+
+If you are running the above setup online, you can use the [pilot JRC INSPIRE validator](https://inspire-geoportal.ec.europa.eu/validator2/). If the above setup is running locally, you can use [Esdin Test Framework](https://github.com/Geonovum/etf-test-projects-inspire) to validate the INSPIRE setup.
+
+
+
+Running the test frequently during development helps to identify issues in an early stage.
+
+## Known issues
+
+There is a known issue in the capabilities to metadata linkage. The JRC validator requires a gmd:RS_Identifier inside gmd:code having the authority and dataset identifier modeled separately. However the technical guidelines suggest a gmd:MD_Identifier inside gmd:code, the authority can then be included as a prefix, eg < gmd:MD_Identifier >{authority}#{uuid}< gmd:MD_Identifier >
diff --git a/docs/manual/docs/tutorials/inspire/view-mapserver.md b/docs/manual/docs/tutorials/inspire/view-mapserver.md
new file mode 100644
index 00000000000..30ac0fee8e8
--- /dev/null
+++ b/docs/manual/docs/tutorials/inspire/view-mapserver.md
@@ -0,0 +1,75 @@
+# Setting up INSPIRE view service with GeoNetwork and Mapserver {#tuto-view-mapserver}
+
+This tutorial shows how one can set up a combination of [MapServer](https://mapserver.org) and GeoNetwork to provide view services following [technical guidelines for view services](https://inspire.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.1.pdf).
+
+## MapServer
+
+How to set up an INSPIRE view service in Mapserver is documented in [mapserver documentation](https://www.mapserver.org/ogc/inspire.html). In this tutorial we use the reference service metadata approach:
+
+``` text
+WEB
+ METADATA
+ "wms_inspire_capabilities" "url"
+ END
+END
+```
+
+## GeoNetwork
+
+When deploying Geonetwork, make sure the GEMET thesauri are loaded and activate the INSPIRE editor as described in [Geonetwork documentation](../../administrator-guide/configuring-the-catalog/inspire-configuration.md).
+
+In Admin --> Settings activate the INSPIRE extension.
+
+
+
+For each dataset that you are going to publish create an iso19115 record using the INSPIRE template. Link each record to the view service as created in mapserver: eg ``https://{url}/cgi-bin/mapserv?map={mapfile}&request=getcapabilities&service=wms&version=1.3.0``
+
+
+
+Make sure the metadata contains the same gmd:code (and authority) as available in WMS getcapabilities.
+
+Create an OGC harvester that is able to extract a metadata for service (iso19119) record from the WMS. Run the harvester and note down the identifier of the created service metadata.
+
+## Return to MapServer Mapfile
+
+For each layer configuration add a metadata url of type text/xml. Other relevant parameters are the authority element and the dataset identifier.
+
+``` text
+LAYER
+ NAME "mylayer"
+ METADATA
+ wms_dataurl_format "application/vnd.ogc.csw.GetRecordByIdResponse_xml"
+ wms_dataurl_href "http://geonetwork/srv/api/records/f4f137aa-a2bf-4033-91ef-2cfdbe500690"
+ wms_authorityurl_name "inspire"
+ wms_authorityurl_href "http://inspire.ec.europa.eu/"
+ wms_identifier_authority "inspire"
+ wms_identifier_value "0a636f43-016c-474a-ab28-1f3d75e9fcae"
+ END
+END
+```
+
+For the service definition add a link to the service metadata
+
+``` text
+WEB
+ METADATA
+ "wms_inspire_capabilities" "url"
+ "wms_languages" "eng"
+ "wms_inspire_metadataurl_href" "http://geonetwork/srv/api/records/d461302e-5ec8-415d-9a6d-05de37184b03"
+ "wms_inspire_metadataurl_format" "application/vnd.ogc.csw.GetRecordByIdResponse_xml"
+ "wms_keywordlist_ISO_items" "infoMapAccessService"
+ END
+END
+```
+
+## Validate the implementation
+
+If you are running the above setup online, you can use the [pilot JRC INSPIRE validator](https://inspire-geoportal.ec.europa.eu/validator2/). If the above setup is running locally, you can use [Esdin Test Framework](https://github.com/Geonovum/etf-test-projects-inspire) to validate the INSPIRE setup.
+
+
+
+Running the test frequently during development helps to identify issues in an early stage.
+
+## Known issues
+
+There is a known issue in the capabilities to metadata linkage. The JRC validator requires a gmd:RS_Identifier inside gmd:code having the authority and dataset identifier modeled separately. However the technical guidelines suggest a gmd:MD_Identifier inside gmd:code, the authority can then be included as a prefix, eg ``{authority}#{uuid}``
diff --git a/docs/manual/docs/tutorials/introduction/deployment/build.md b/docs/manual/docs/tutorials/introduction/deployment/build.md
new file mode 100644
index 00000000000..12e65cd653c
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/deployment/build.md
@@ -0,0 +1,103 @@
+# Build from source code {#tuto-introduction-deployment-build}
+
+In this paragraph some guidance will be provided to build GeoNetwork from source code. This is relevant in case you want to extend the application to your needs.
+
+The source code of GeoNetwork is available at [Github](https://github.com/geonetwork/core-geonetwork). This means that you can clone, fork and propose pushes of your custom changes. If you are not familiar with repositories of code or git, you should check [this quick manual](https://try.github.io/levels/1/challenges/1).
+
+GeoNetwork 4.4 is a java project using [Maven version 3+](https://Maven.apache.org/). It is written on **Java 11**. It works both with OpenJDK or the Oracle version. There are several ways to install this on your local machine; for example if you have a Debian based OS (like Ubuntu), you can install them with just this command:
+
+``` bash
+$ sudo apt-get install maven git
+```
+
+Make sure you installed maven version 3!!
+
+``` bash
+$ mvn --version
+Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00)
+Maven home: ....
+```
+
+Remember that this will also install Java on your system. You can check that the version is the right one with the following command:
+
+``` bash
+$ java -version
+```
+
+So, the very first step once you have your environment set up is clone the GeoNetwork repository on your local machine. That can be done on the command line using the following command inside an empty folder where the source code will be populated:
+
+``` bash
+$ cd yourEmptyFolder
+$ git clone https://github.com/geonetwork/core-geonetwork.git
+$ cd core-geonetwork
+$ git submodule init
+$ git submodule update
+```
+
+As you can see, all the source code shown on github is also available on your local machine now.
+
+The source code of GeoNetwork is split on several smaller Maven projects. To run GeoNetwork, you have to build all of them and run the project named **"web"**.
+
+If you are familiar to Maven, you will probably have guessed that you have to run a package install command on the root folder of GeoNetwork source code. But if you try that, Maven will warn you that for building GeoNetwork you need more memory than the default memory provided to Maven. This means, you will have to export the Maven options to increase the memory like this:
+
+``` bash
+$ export MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=256M"
+```
+
+At this point we are not interested in running the tests, so you can skip them using the parameter *-DskipTests*:
+
+``` bash
+$ mvn package install -DskipTests
+```
+
+At the end of this build (which can take long, depending on your network connection, as it has many third party libraries), you will see something like this:
+
+``` bash
+[INFO] ------------------------------------------------------------------------
+[INFO] Reactor Summary:
+[INFO]
+[INFO] GeoNetwork opensource ............................. SUCCESS [ 3.111 s]
+[INFO] common utils ...................................... SUCCESS [ 13.678 s]
+[INFO] Caching xslt module ............................... SUCCESS [ 7.607 s]
+[INFO] ArcSDE module (dummy-api) ......................... SUCCESS [ 7.860 s]
+[INFO] GeoNetwork domain ................................. SUCCESS [ 33.785 s]
+[INFO] Oaipmh modules .................................... SUCCESS [ 0.833 s]
+[INFO] GeoNetwork Events ................................. SUCCESS [ 0.654 s]
+[INFO] GeoNetwork schema plugins ......................... SUCCESS [ 4.646 s]
+[INFO] GeoNetwork schema plugins core .................... SUCCESS [ 5.338 s]
+[INFO] GeoNetwork schema plugin for ISO19139/119 standards SUCCESS [ 8.432 s]
+[INFO] GeoNetwork core ................................... SUCCESS [ 16.304 s]
+[INFO] GeoNetwork schema plugin for Dublin Core records retrieved by CSW SUCCESS [ 5.031 s]
+[INFO] GeoNetwork schema plugin for Dublin Core standard . SUCCESS [ 8.419 s]
+[INFO] GeoNetwork schema plugin for ISO19110 standard .... SUCCESS [ 3.627 s]
+[INFO] GeoNetwork CSW server ............................. SUCCESS [ 5.546 s]
+[INFO] GeoNetwork harvesters ............................. SUCCESS [ 3.888 s]
+[INFO] GeoNetwork health monitor ......................... SUCCESS [ 2.489 s]
+[INFO] GeoNetwork services ............................... SUCCESS [ 8.597 s]
+[INFO] Geonetwork Web Resources 4 Java ................... SUCCESS [ 5.261 s]
+[INFO] Cobweb Customizations ............................. SUCCESS [ 4.226 s]
+[INFO] GeoNetwork INSPIRE Atom ........................... SUCCESS [ 3.990 s]
+[INFO] Tests for schema plugins .......................... SUCCESS [ 2.334 s]
+[INFO] GeoNetwork user interface module .................. SUCCESS [ 35.356 s]
+[INFO] JS API and Service documentation .................. SUCCESS [ 21.203 s]
+[INFO] GeoNetwork web client module ...................... SUCCESS [ 47.484 s]
+[INFO] GeoNetwork Web module ............................. SUCCESS [ 48.490 s]
+[INFO] GeoNetwork E2E Javascript Tests ................... SUCCESS [ 1.645 s]
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 02:19 min (Wall Clock)
+[INFO] Finished at: 2015-07-17T10:36:43+01:00
+[INFO] Final Memory: 232M/441M
+[INFO] ------------------------------------------------------------------------
+```
+
+This will generate a war file, which you can use in any Java Application Container (server) like Tomcat, on web/target/geonetwork.war
+
+Congratulations! You are ready to run GeoNetwork. To do this, just go to the web folder and run Jetty in there:
+
+``` bash
+$ cd web; mvn jetty:run
+```
+
+After Jetty starts, you can see your running GeoNetwork by opening a browser and enter to http://localhost:8080/geonetwork
diff --git a/docs/manual/docs/tutorials/introduction/deployment/deploy.md b/docs/manual/docs/tutorials/introduction/deployment/deploy.md
new file mode 100644
index 00000000000..0a327c6ba77
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/deployment/deploy.md
@@ -0,0 +1,38 @@
+# Local deployment {#tuto-introduction-deployment-deploy}
+
+Before deploying **GeoNetwork** you first need to set up an Elasticsearch instance. lists the various options for deployment, such as via the installer, a package manager such as yum, apt, brew or docker. Ensure you use a version of Elasticsearch compatible with the version of GeoNetwork. For GeoNetwork 4.x this is Elasticsearch 7.x.
+
+GeoNetwork itself can be downloaded from [sourceforge](https://sourceforge.net/projects/geonetwork/files/GeoNetwork_opensource). The zip distribution includes a jetty container ready to run GeoNetwork.
+
+Verify that a java 1.8 run time (JRE/JDK) is available and active. Else download and install from . Or activate via the \$JAVA_HOME environment variable.
+
+``` bash
+$ java --version
+```
+
+The war distribution can be deployed in a container such as Tomcat.
+
+To install Tomcat on a debian-based operation system, you can use the apt-get tool like:
+
+``` bash
+$ sudo apt-get install tomcat7
+```
+
+For windows, download the installer from .
+
+Once you have Tomcat installed on your system, locate the webapps folder and place the geonetwork.war file there. This will deploy GeoNetwork on your system.
+
+!!! note
+
+ You need to ensure Tomcat is configured with enough memory for GeoNetwork to launch. This can be be configured via the `setenv` script in tomcat with the appropriate memory for the JAVA_OPTS property)
+
+
+Open the file /geonetwork/WEB-INF/config.properties and alter the elasticsearch connection
+
+``` bash
+$ es.url=http://localhost:9200
+```
+
+Then (re)start Jetty/Tomcat.
+
+You can make sure GeoNetwork is deployed via the following url:
diff --git a/docs/manual/docs/tutorials/introduction/deployment/docker.md b/docs/manual/docs/tutorials/introduction/deployment/docker.md
new file mode 100644
index 00000000000..ab665eb8755
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/deployment/docker.md
@@ -0,0 +1,43 @@
+# Pull from docker hub {#tuto-docker}
+
+This paragraph describes how you can deploy **GeoNetwork** and its dependencies as a docker orchestration using prepared images from [Docker hub](https://hub.docker.com/_/geonetwork).
+
+Ensure the system on which you will install the software has a recent [Docker engine](https://docs.docker.com/engine/install) and [Docker Compose](https://docs.docker.com/compose/install/) installed. [Docker Desktop](https://www.docker.com/products/docker-desktop), including both, is a good option for local installation.
+
+Open a command-line panel verify that docker engine is running:
+
+``` bash
+$ docker --version
+```
+
+Clone or download as a zip file the repository . The relevant folder in that repository is the latest 4.2.x.
+
+Navigate with command-line to that folder (e.g. ``cd \~docker-geonetwork\4.2.6``). The folder has a file ``docker-compose.yml`` which defines the orchestration. The orchestration will download and deploy the following
+
+- nginx; manages routing within the orchestration
+- postgis; used for database persistence
+- geonetwork; the main application
+- elasticsearch; the search index
+- kibana; the dashboard for elasticsearch
+
+It is important to verify if the ports used in that orchestration (80, 8080, 9200) are available on the local system. Alternatively you can change the port mappings in this file.
+
+Spin up the orchestration with:
+
+``` bash
+$ docker-compose up
+```
+
+After a while, the application should be available via .
+
+On console to see a list of running containers type:
+
+``` bash
+$ docker ps
+```
+
+You can verify logs of the geonetwork container with:
+
+``` bash
+$ docker logs geonetwork
+```
diff --git a/docs/manual/docs/tutorials/introduction/deployment/index.md b/docs/manual/docs/tutorials/introduction/deployment/index.md
new file mode 100644
index 00000000000..e26395184b7
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/deployment/index.md
@@ -0,0 +1,11 @@
+# Deployment {#tuto-introduction-deployment}
+
+On this chapter, we will learn how to make GeoNetwork run on your machine or in the cloud.
+
+Up to version 3 GeoNetwork could easily be deployed locally, there is even a [Windows installer](https://my.geocat.net/download/category/6/GeoNetwork.html). But with the arrival of version 4, GeoNetwork has a number of dependencies that need to be deployed separately, which makes the deployment locally more challenging. Instead the GeoNetwork community provides `es` for automated deployment using Docker. [Docker](https://docker.com) is a virtualisation technology which facilitates deployment of a `on` of prepackaged `es` locally or in the cloud.
+
+For this workshop we will focus on the use of docker, but we also provide some guidance on how to set up the environment without docker, or even build the application from sources.
+
+- [Pull from docker hub](docker.md)
+- [Local deployment](deploy.md)
+- [Build from source code](build.md)
diff --git a/docs/manual/docs/tutorials/introduction/edit/edit.md b/docs/manual/docs/tutorials/introduction/edit/edit.md
new file mode 100644
index 00000000000..c709925928a
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/edit/edit.md
@@ -0,0 +1,23 @@
+# Edit {#tuto-introduction-edit}
+
+To add new metadata, you should enter the editor dashboard:
+
+
+
+There, you can click on the blue "Add new record" button at the right to create a new metadata. Depending on the schema selected on previous steps, you will be offered different templates to start a new metadata.
+
+
+
+After selecting a template and clicking on the green "Create" button at the right, the editor will be opened with your newly created metadata. You can complete and change the values you need to and then click on the blue save icon.
+
+
+
+After saving and closing the editor, you metadata is already on your catalog. You can search for it on the home page or the editor dashboard.
+
+If you want your metadata to be publicly available, you should also modify the privileges so the "All" group, which represents the anonymous users, can see it. To do this, go back to the editor dashboard:
+
+
+
+Select the metadata you want to publish and, on the top menu, select the "Publish" option. Now your metadata is publicly available on your catalog. If you access with an anonymous tab, your metadata is visible.
+
+See more on [Editing metadata](../../../user-guide/describing-information/editing-metadata.md).
diff --git a/docs/manual/docs/tutorials/introduction/edit/editor.md b/docs/manual/docs/tutorials/introduction/edit/editor.md
new file mode 100644
index 00000000000..c1c36168220
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/edit/editor.md
@@ -0,0 +1,62 @@
+# Customize Editor (Optional) {#tuto-introduction-editor}
+
+Each schema can configure different editor views. This configurations can be found on the file layout/config-editor.xml of each schema.
+
+This file has four main blocks:
+
+Fields:
+
+``` xml
+
+
+
+
+
+
+
+
+```
+
+This defines for each XSD defined type, which type of input to use. As with gmd:onLine, a customized angular input type can be defined.
+
+After defining all the simple fields, we define a list of fieldsets, which the editor will recognize as something to put together:
+
+``` xml
+
+ gmd:MD_Metadata
+ gmd:identificationInfo
+
+```
+
+Now we define what fields are multilingual. Usually most of the fields are multilingual, so we can just define which ones to exclude.
+
+``` xml
+
+
+
+ gmd:title
+ gmd:abstract
+
+
+ gmd:identifier
+
+
+```
+
+Finally, we define the views, which will customize which fields will be shown when editing the metadata. We can define more than one view per schema, so the editor user can select which one to use when editing the metadata.
+
+When a non-final field is defined on a view, the editor will automatically generate all the input fields inside it. So, you don't have to explicitly define all the fields you want to show. The simplest view is the one based on the XSD of the schema.
+
+The xml view can also be easily defined:
+
+``` xml
+
+
+
+```
+
+If the view is too big, we can also define a set of tabs inside the editor, so not all fields are shown at the same time. Remember that when the user changes the tab, the content will be saved. So we should place related fields inside the same tab.
+
+Remember that you have to restart the application container (Tomcat) every time you modify this file.
+
+See more on [Customizing editor](../../../customizing-application/editor-ui/creating-custom-editor.md).
diff --git a/docs/manual/docs/tutorials/introduction/edit/img/addNewRecord.png b/docs/manual/docs/tutorials/introduction/edit/img/addNewRecord.png
new file mode 100644
index 00000000000..65ec2442cdb
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/edit/img/addNewRecord.png differ
diff --git a/docs/manual/docs/tutorials/introduction/edit/img/editor.png b/docs/manual/docs/tutorials/introduction/edit/img/editor.png
new file mode 100644
index 00000000000..7c91f1bd55e
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/edit/img/editor.png differ
diff --git a/docs/manual/docs/tutorials/introduction/edit/img/editorDashboard.png b/docs/manual/docs/tutorials/introduction/edit/img/editorDashboard.png
new file mode 100644
index 00000000000..a3a5c0610e8
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/edit/img/editorDashboard.png differ
diff --git a/docs/manual/docs/tutorials/introduction/edit/img/editorDashboard2.png b/docs/manual/docs/tutorials/introduction/edit/img/editorDashboard2.png
new file mode 100644
index 00000000000..1538d494ecd
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/edit/img/editorDashboard2.png differ
diff --git a/docs/manual/docs/tutorials/introduction/edit/index.md b/docs/manual/docs/tutorials/introduction/edit/index.md
new file mode 100644
index 00000000000..a7f0588b5c6
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/edit/index.md
@@ -0,0 +1,6 @@
+# Editing Metadata {#tuto-introduction-edit-index}
+
+On this step we will learn how to edit metadata and configure the editor.
+
+- [Edit](edit.md)
+- [Customize Editor (Optional)](editor.md)
diff --git a/docs/manual/docs/tutorials/introduction/extra/img/apidoc.png b/docs/manual/docs/tutorials/introduction/extra/img/apidoc.png
new file mode 100644
index 00000000000..6bae6396bd4
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/extra/img/apidoc.png differ
diff --git a/docs/manual/docs/tutorials/introduction/extra/index.md b/docs/manual/docs/tutorials/introduction/extra/index.md
new file mode 100644
index 00000000000..dac53f29025
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/extra/index.md
@@ -0,0 +1,25 @@
+# Advanced topics {#extra}
+
+## GeoNetwork API
+
+In recent releases most of GeoNetworks functionality is exposed via a centralised API based on OpenApi. An optimal approach to get started with the API is via the Interactive documentation page provided by OpenAPI. This page is accessibly via .
+
+{width="400px"}
+
+The page describes each of the methods and its properties, but also offers the capability to try out any operation via a web form.
+
+## Kibana Dashboard
+
+Kibana is an optional component which can be installed with Elastic Search. Kibana offers a dynamic way to create visualisations of the contentn of the Elastc Search index.
+
+The GeoNetwork community has prepared some sample visualisations. Load the samples from via the 'Saved objects --> Import' option in Kibana.
+
+If installed, you can access kibana from the GeoNetwork admin interface. To access the Kibana interface you need to be logged in as administrator.
+
+Read more about the usage of kibana at
+
+## Search engines
+
+Search engines provide a good mechanism for wide data discovery for public portals. The process of having catalogue content ingested by search engine crawlers requires some attention. The search engine expects to find robots.txt, at the root of the domain. Robots.txt contains a reference to the sitemap /srv/api/sitemap. Alternatively you can register the sitemap manually at individual search engines.
+
+GeoNetwork includes on any html representation of a metadata record a representation of that record in schema.org encoded as json-ld. This enables the search engine to extract the information in a structured way.
diff --git a/docs/manual/docs/tutorials/introduction/harvesting/img/harvest1.png b/docs/manual/docs/tutorials/introduction/harvesting/img/harvest1.png
new file mode 100644
index 00000000000..5b026a1b037
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/harvesting/img/harvest1.png differ
diff --git a/docs/manual/docs/tutorials/introduction/harvesting/img/harvester1.png b/docs/manual/docs/tutorials/introduction/harvesting/img/harvester1.png
new file mode 100644
index 00000000000..304517b82ae
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/harvesting/img/harvester1.png differ
diff --git a/docs/manual/docs/tutorials/introduction/harvesting/img/harvester2.png b/docs/manual/docs/tutorials/introduction/harvesting/img/harvester2.png
new file mode 100644
index 00000000000..afc3c87e77a
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/harvesting/img/harvester2.png differ
diff --git a/docs/manual/docs/tutorials/introduction/harvesting/index.md b/docs/manual/docs/tutorials/introduction/harvesting/index.md
new file mode 100644
index 00000000000..d86e477f06b
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/harvesting/index.md
@@ -0,0 +1,31 @@
+# Harvesting {#tuto-introduction-harvesting}
+
+The quickest way to add relevant data to your catalog is by harvesting. This means, copying data from other catalos in your own catalog. There are many protocols that can be used for harvesting.
+
+## GeoNetwork
+
+GeoNetwork can harvest from other GeoNetwork catalogs. For this tutorial, we are going to use this catalog:
+
+To add a new harvester, we have to enter the administration console:
+
+
+
+We select the **GeoNetwork** option on the *Harvest from* dropdown. This will open a harvester editor at the right. We enter a *Node name* and the *Catalog URL* and we can already save it.
+
+All harvesters can be run manually at will with the *Harvest* button. This means, it will run just once every time an authorized user runs it.
+
+But the most interesting feature of harvesters is the scheduler. You can define a frequency of running.
+
+
+
+## CSW
+
+GeoNetwork can also harvest from CSW catalogs. The process is quite similar, but instead of choosing the GeoNetwork type of harvester, we chose the **OGC CSW 2.0.2** harvester type.
+
+For this tutorial, we are going to use the following catalog:
+
+While the harvester is running, there will be an animated circle. Once the harvester has finished, the number of records harvested will be shown.
+
+
+
+See more on [Harvesting](../../../user-guide/harvesting/index.md).
diff --git a/docs/manual/docs/tutorials/introduction/img/geonetwork_opensource.png b/docs/manual/docs/tutorials/introduction/img/geonetwork_opensource.png
new file mode 100644
index 00000000000..9031dcf45cb
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/img/geonetwork_opensource.png differ
diff --git a/docs/manual/docs/tutorials/introduction/img/metadata_example.png b/docs/manual/docs/tutorials/introduction/img/metadata_example.png
new file mode 100644
index 00000000000..b44f9e88a66
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/img/metadata_example.png differ
diff --git a/docs/manual/docs/tutorials/introduction/index.md b/docs/manual/docs/tutorials/introduction/index.md
new file mode 100644
index 00000000000..a6b1518f9eb
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/index.md
@@ -0,0 +1,29 @@
+# GeoNetwork Orientation {#tuto-introduction}
+
+In this workshop you are introduced to the main features of the GeoNetwork system from a usage and data curation perspective. The tutorial contains information and hands-on exercises explaining how to use the GeoNetwork system.
+
+## GeoNetwork opensource
+
+GeoNetwork opensource is a standards based and decentralised spatial information management system, designed to enable access to spatial databases and cartographic products from a variety of data providers through descriptive metadata, enhancing the spatial information exchange and sharing between organisations and their audience, using the capacities and the power of the Internet.
+
+The system provides a broad community of users with easy and timely access to available spatial data and thematic maps from multidisciplinary sources, that may in the end support informed decision making.
+
+The main goal of the software is to increase collaboration within and between organisations for reducing duplication and enhancing information consistency and quality and to improve the accessibility of a wide variety of geographic information along with the associated information, organised and documented in a standardised and consistent way.
+
+{width="800px"}
+
+The tutorial starts with an introduction on cataloguing concepts and then continues with installation, configuration and usage of the GeoNetwork software.
+
+At various points references are made to the product documentation to find more details on a certain topic.
+
+## Tutorial contents
+
+- [Metadata and Catalogues](introduction/index.md)
+- [Discovering information](introduction/discover.md)
+- [Maps and dataset visualisation](introduction/map.md)
+- [Multi schema support](introduction/schema.md)
+- [Deployment](deployment/index.md)
+- [Setup](setup/index.md)
+- [Editing Metadata](edit/index.md)
+- [Harvesting](harvesting/index.md)
+- [Advanced topics](extra/index.md)
diff --git a/docs/manual/docs/tutorials/introduction/introduction/discover.md b/docs/manual/docs/tutorials/introduction/introduction/discover.md
new file mode 100644
index 00000000000..7968d596977
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/introduction/discover.md
@@ -0,0 +1,38 @@
+# Discovering information
+
+We start our tour through GeoNetwork with an introduction to the search mechanism. For this tour you need to access a preconfigured and populated GeoNetwork instance. Use for example , , or alternatively continue with the next chapters of the tutorial first, in which you will install, configure and populate a local instance of GeoNetwork.
+
+The process of discovery includes searching by keyword, location, organisation or others, filtering the results and the evaluation of individual records. GeoNetwork provides various ways of searching for records in the catalogue:
+
+- A full text search box provides suggestions as you type. This options queries all elements of the metadata, so you can use keywords, organisations names, filenames, etc. Use * to match partial search terms. If you want to search only on a specific field, such as title, use the advanced search.
+
+{width="600px"}
+
+- To use a spatial filter, draw a polygon in the map-filter widget. You can switch the mode of the widget from "intersect" to "within" so you only receive records that are within the bounding box you defined.
+
+{width="400px"}
+
+## Search results
+
+The search results show the main information of each resource: title, abstract, schema, thumbnail, download links.
+
+{width="600px"}
+
+You can use the facets in the left sidebar to further filter the search result. Facets provice a summary of common elements in the current search result.
+
+To get more information, click the title of the record, this will bring you to the index-view, a view of the metadata that displays a subset of the metadata, directly from the search index.
+
+{width="600px"}
+
+The view menu displays the available view modes. In a default configuration are available "Default" and "Full". The "Full" view displays all metadata elements by applying an XML to HTML transformation.
+
+## View data on map
+
+From the results or the record view, you can add linked WMS and WFS layers to the map viewer by clicking the *Interactive map* url of the *Online resource* element in the *Distribution* section.
+
+{width="600px"}
+
+!!! abstract "Explore"
+
+ Find a record that has a linked WMS layer and add it to the map.
+
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/OWSContext.png b/docs/manual/docs/tutorials/introduction/introduction/img/OWSContext.png
new file mode 100644
index 00000000000..c409a387688
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/OWSContext.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/a-record.png b/docs/manual/docs/tutorials/introduction/introduction/img/a-record.png
new file mode 100644
index 00000000000..9b99a98a760
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/a-record.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/a-result.png b/docs/manual/docs/tutorials/introduction/introduction/img/a-result.png
new file mode 100644
index 00000000000..905bd1091fc
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/a-result.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/addLayers.png b/docs/manual/docs/tutorials/introduction/introduction/img/addLayers.png
new file mode 100644
index 00000000000..f89a2752d57
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/addLayers.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/advanced.png b/docs/manual/docs/tutorials/introduction/introduction/img/advanced.png
new file mode 100644
index 00000000000..6b02f083df7
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/advanced.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/facets.png b/docs/manual/docs/tutorials/introduction/introduction/img/facets.png
new file mode 100644
index 00000000000..4690617927b
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/facets.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/full-text.png b/docs/manual/docs/tutorials/introduction/introduction/img/full-text.png
new file mode 100644
index 00000000000..3acd15ab41a
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/full-text.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/geonetwork_opensource.png b/docs/manual/docs/tutorials/introduction/introduction/img/geonetwork_opensource.png
new file mode 100644
index 00000000000..b6e4c09373a
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/geonetwork_opensource.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/map-africa-basin.png b/docs/manual/docs/tutorials/introduction/introduction/img/map-africa-basin.png
new file mode 100644
index 00000000000..cd2d32d6712
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/map-africa-basin.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/metadata_example.png b/docs/manual/docs/tutorials/introduction/introduction/img/metadata_example.png
new file mode 100644
index 00000000000..b44f9e88a66
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/metadata_example.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/metasearch.png b/docs/manual/docs/tutorials/introduction/introduction/img/metasearch.png
new file mode 100644
index 00000000000..d9920b77c24
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/metasearch.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/spatial-filter.png b/docs/manual/docs/tutorials/introduction/introduction/img/spatial-filter.png
new file mode 100644
index 00000000000..e523eae5f65
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/spatial-filter.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/img/view-menu.png b/docs/manual/docs/tutorials/introduction/introduction/img/view-menu.png
new file mode 100644
index 00000000000..f10f45c9568
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/introduction/img/view-menu.png differ
diff --git a/docs/manual/docs/tutorials/introduction/introduction/index.md b/docs/manual/docs/tutorials/introduction/introduction/index.md
new file mode 100644
index 00000000000..cd602aaede9
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/introduction/index.md
@@ -0,0 +1,36 @@
+# Metadata and Catalogues {#introduction.rst}
+
+This paragraph introduces metadata and catalogues. In the process of registering an asset in a catalog, one typically describes properties of the asset. This results in a metadata record being created. Metadata, or 'data about data', is used in a variety of contexts. In the spatial domain the term is generally used for documents that describe spatial assets, such as datasets, web services/processes, maps, scientific articles, sensors, documents, etc.
+
+In order to faciliate sharing of metadata between organisations, common metadata models, such as Dublin Core, DCAT and ISO19115 have been adopted. These models are generally tailored for a specific organisational or domain context in 'metadata profiles'.
+
+## Metadata in the spatial domain
+
+{width="400px"}
+
+In the above image you see the rendering of a spatial dataset. Based on the image itself it is hard to tell what type of data is represented in the image. It could be roads or rivers, but considering the symbology of the dataset this seems unlikely. Most likely this dataset contains boundaries, but because we do not have any metadata describing the dataset we can only guess. Metadata defines what a dataset is about, so everyone who receives the datasets knows what the data represents.
+
+## Catalogue purposes
+
+Metadata serves three main purposes; discovery, identification and assessment.
+
+- Catalogues are able to let users query through large amounts of records, created locally or imported from other catalogues, so users are able to **discover** resources that may be of interest to them.
+- When you're looking at a map or dataset you want to verify what it is you're looking at. Metadata supports the **identification** of the asset.
+- Users are enabled to assess if a dataset is relevant for their use case by checking its metadata. Important attributes for **assessment** are location, scale, legal constraints (data license), date of modification, accuracy and lineage information.
+
+## Populating a catalogue
+
+Catalogues can be populated in three ways:
+
+- A catalogue can have functionality so users can register assets inside the catalogue.
+- Catalogues can 'harvest' (import) records from other catalogues at intervals, thus reaching a wider audience for the information.
+- Catalogues can create records from external assets in an automated way.
+
+!!! abstract "Exercise"
+
+ Open a browser and visit a common spatial catalogue like . Answer the following questons:
+
+ - What type of assets do the records in this catalogue describe (imagery, vector data, web services, maps, etc)
+ - Try to locate some records that describe data in your area for a topic of your interest.
+ - For a map like , try to find out what is the data license of the data represented in the map. What suggestions would you make to the map administrator to improve this aspect.
+
diff --git a/docs/manual/docs/tutorials/introduction/introduction/map.md b/docs/manual/docs/tutorials/introduction/introduction/map.md
new file mode 100644
index 00000000000..2a4d480edf9
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/introduction/map.md
@@ -0,0 +1,70 @@
+# Maps and dataset visualisation {#customizing-the-map}
+
+The map component in GeoNetwork serves two goals:
+
+- As part of the evaluation of relevance users can visualise a resource discovered in the catalogue in an interactive map viewer to preview the contents.
+- GeoNetwork can be used as a mapping application to create maps that can be printed or shared with others. The maps itself can even be registered in the catalogue as assets.
+
+!!! note
+
+ Instead of using the embedded map viewer, GeoNetwork offers functionality to use an external map viewer (for example an existing WebGIS framework in your organisation). An administrator can configure GeoNetwork in such a way that it is connected to an external web map application. In such a configuration all map interaction is delegated to the external application.
+
+
+## Map viewer
+
+From the Search tab, click on the card for *Hydrological Basins in Africa* to view the metadata. Move down the results page until the *Download and links* section is visible.
+
+The Download and links section shows external resources associated with the metadata record, such as:
+
+- A file download of the data,
+- Further information such as a web page,
+- A Web Mapping Service (WMS) or Web Feature Service (WFS) link to the data.
+
+!!! abstract "Exercise"
+
+ Locate the link labelled as *This dataset is published to the view service (WMS) available at http://data.fao.org/maps/wms with layer name GEONETWORK:basins_296* and select *Add to map*. This step will switch you to the Map tab in the catalog, and after a short delay the WMS layer will be added to the map.
+
+
+Tools for using the Map are arranged in two groups in the right-hand side of the map. The top group looks like this:
+
+- Add new layers to the map. You can search the catalog, add layers from web services, or kml.
+- Manage existing layers or change the background map (the default is openstreetmap).
+- Filter layers on the map (if configured).
+- Manage the Map, by setting it back to default settings, loading a new map definition, downloading the current map, or saving the map configuration as a layer in the catalog.
+- Print the map.
+- Synchronise layers with the small map on the Search tab.
+- Measure distances on the map.
+- Draw annotations on the map.
+
+Additionally there is a geographic search tool in the top left.
+
+!!! abstract "Exercise"
+
+ Use the Add Layers tool and type *Physiographic* in the Search box. Three results will be returned, for the three Physiographic records in the catalog. Click the + button next to the Physiography of North and Central Eurasia Landform result to add it to the map.
+
+ Using the Manage Layers tool, select the cog symbol next to Physiography of North and Central Eurasia Landform and select Zoom to layer. The map will zoom to the extent of this layer. Select the paintbrush tool next to this layer to see the legend, showing you the classification used for the display.
+
+
+Layers in the map viewer can be managed from the layer panel: Reorder, change opacity, show legend and set alternative style. The map viewer has some advanced features such as map printing, distance measure and red lining.
+
+The map viewer supports Featureinfo, to retrieve information by clicking on a location in the map. An administrator can activate WFS-indexing. If activated, users can filter the contents of a dataset.
+
+It is possible to add directly WMS, WFS or WMTS layers by entering the endpoint and selecting the layer from the capabilities response.
+
+{width="300px"}
+
+The default projection of maps in GeoNetwork is EPSG:3857 pseudo mercator. However the administrator can add a projection switcher that allows alternative projections.
+
+## Store and share maps
+
+A map consists of a background layer and a number of thematic overlays. A format to combine layers, projection and bounds (area of interest) has been adopted by OGC as the OWS Context standard. Besides GeoNetwork there are a number of other applications supporting this standard.
+
+GeoNetwork uses OWSContext to store, share and load maps:
+
+- Export a context to a local file, to restore the map later or share by email.
+- The administrator can introduce a context file as default configuration for the catalog.
+- Open a local context file by dragging it on to the map viewer (or open from context menu).
+- Register a context as asset in the catalogue, the context itself will be added as attachement.
+- Records that have an OWS context file attached will display a button to open the context file.
+
+{width="400px"}
diff --git a/docs/manual/docs/tutorials/introduction/introduction/schema.md b/docs/manual/docs/tutorials/introduction/introduction/schema.md
new file mode 100644
index 00000000000..0e133de9779
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/introduction/schema.md
@@ -0,0 +1,35 @@
+# Multi schema support {#internals.rst}
+
+This paragraph explains how GeoNetwork leverages metadata records formatted in various schemas (metadata models). Over time various communities adopted a number of metadata standards and profiles for metadata records.
+
+Metadata models define which properties can be registered for an asset, such as title, author, creation date. In the spatial domain TC211 together with OGC are the standardisation bodies which define the standards. In 2005 TC211 released ISO19139, a standard for metadata to describe spatial assets which is still widely used. In 2014 TC211 released a big update to this standard, named ISO19115-1. GeoNetwork is able to manage records in either schema (and other schemas, such as Dublin Core, DCAT).
+
+## Indexing records
+
+In GeoNetwork records in various schemas are stored as XML-documents in the database. To manage records that follow a certain schema a series of "schema-plugins" is available, which define rules how to manage records formatted according to that schema. One aspect of a schema-plugin is that it defines which parts of the xml document contain relevant information for the search mechanism. The process of extracting this information and storing it in a unified search index is called 'indexing'. This process is triggered when a record is updated or imported in the database.
+
+!!! note
+
+ The search index of GeoNetwork is based on an external component, called "Elastic Search".
+
+
+## Authoring Records
+
+GeoNetwork provides an option to create and modify records in an advanced web form. The web form is created and validated from rules that are defined in the relevant "schema-plugin". Saving the form results in an updated xml-document in the database. Read more on this topic on the next page.
+
+## Transforming Records
+
+GeoNetwork has functionality to extract from or insert a record into the catalogue using an alternative schema. GeoNetwork will then perform a transformation from the source schema to the target schema. These transformations are defined using a technique called XSLT and are available in the relevant schema-plugin.
+
+## Standardised exchange of records
+
+To facilitate exchange of catalogue records between applications TC211 and OGC have defined a standard for metedata exchange. The standard "Catalogue Service for the web" (CSW) is a standardised protocol to exchange and query records over the web. This standard facilitated the development of multiple catalogue clients which nowedays allow to query any spatial catalogue from a range of GIS clients, such as OpenLayers, ArcGIS and QGIS. These days OGC is working on a successor of CSW, called OGC API-Records. An experimental implementation of OGC API-Records for GeoNetwork is available via github.
+
+Other communities do have similar standards for metadata exchange, such as OpenSearch (Earth Observation), OAI-PMH (libraries), schema.org (search engines). GeoNetwork allows to set up these alternative endpoints to facilitate data consumption by these communities.
+
+!!! abstract "Exercise"
+
+ In this exercise you'll query a spatial catalogue from within a desktop GIS using CSW. If you have QGIS installed, open QGIS and look under "web" menu for a plugin called "metasearch" (else install it from plugins). In the metasearch configuration add a new server with this url: . Use the plugin to search through the catalogue, and visualise some data in the map. As soon as you've set up your own GoNetwork instance you can try it in metasearch, add it as:
+
+
+{width="500px"}
diff --git a/docs/manual/docs/tutorials/introduction/setup/img/catalogServer.png b/docs/manual/docs/tutorials/introduction/setup/img/catalogServer.png
new file mode 100644
index 00000000000..6a742823585
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/setup/img/catalogServer.png differ
diff --git a/docs/manual/docs/tutorials/introduction/setup/img/createuser.png b/docs/manual/docs/tutorials/introduction/setup/img/createuser.png
new file mode 100644
index 00000000000..fe07265f3d1
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/setup/img/createuser.png differ
diff --git a/docs/manual/docs/tutorials/introduction/setup/img/hostandname.png b/docs/manual/docs/tutorials/introduction/setup/img/hostandname.png
new file mode 100644
index 00000000000..a0524f0d699
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/setup/img/hostandname.png differ
diff --git a/docs/manual/docs/tutorials/introduction/setup/img/password.png b/docs/manual/docs/tutorials/introduction/setup/img/password.png
new file mode 100644
index 00000000000..c1870af46a6
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/setup/img/password.png differ
diff --git a/docs/manual/docs/tutorials/introduction/setup/img/roles.png b/docs/manual/docs/tutorials/introduction/setup/img/roles.png
new file mode 100644
index 00000000000..25de8035a1e
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/setup/img/roles.png differ
diff --git a/docs/manual/docs/tutorials/introduction/setup/img/schemas.png b/docs/manual/docs/tutorials/introduction/setup/img/schemas.png
new file mode 100644
index 00000000000..2fd647d2908
Binary files /dev/null and b/docs/manual/docs/tutorials/introduction/setup/img/schemas.png differ
diff --git a/docs/manual/docs/tutorials/introduction/setup/index.md b/docs/manual/docs/tutorials/introduction/setup/index.md
new file mode 100644
index 00000000000..d4b1e7ce115
--- /dev/null
+++ b/docs/manual/docs/tutorials/introduction/setup/index.md
@@ -0,0 +1,87 @@
+# Setup {#tuto-introduction-setup}
+
+## Change Administrator Password
+
+The first step you should do after deploying GeoNetwork is login with the administrator user and change the administrator password. The default administrator user is called *admin* and the password is *admin*. Once you have logged in, you have to enter the administration console to configure the basics.
+
+Change your admin password here:
+
+
+
+
+
+## Basic Settings
+
+Then, go to the settings page:
+
+
+
+There are a few configuration values here that should be changed like the url domain for your catalog, if it is going to use https or the title for your catalog.
+
+
+
+Make sure you use the hostname, port and protocol that your users will use to access the geoportal as this settings will be used to generate default urls like the ones shown on the sitemap.
+
+Preferred protocol should be https as that will mean a secure navigation for your users but http is the default one for easy deployment and development. **No login should be made outside the https protocol** for security reasons. Using https protocol on a strict browser policy like on Firefox may mean that some http map services will be blocked and display an error if trying to be loaded on the map. This can be solved by using only https map services. As http is a deprecated protocol, this problem will be solved in time. Check with your map service provider to use https with a valid certificate for the map services.
+
+
+
+The Catalogue Identifier should be a unique name on the whole internet. The default identifier is generated automatically by GeoNetwork and should be safe to use. Unless you have a better identifier, you can leave the one generated by default.
+
+## Loading Schemas
+
+The last important thing to configure is what schemas are we going to use in our catalog. By default, GeoNetwork has already installed some of the most used schemas. These schemas have usually samples and templates you can easily add to your catalog on the administration console:
+
+
+
+
+
+Sample data has no use on real world catalogues, it is just used to show how the metadata should be filled in and how it will look like once the data is inserted on the catalog.
+
+Templates, on the other hand, are needed if you want to edit metadata. Instead of using empty xml files for the metadata creation, a template is used when creating a new record. You can always import or harvest already created metadata instead of using the editor to create manually records if that fits your usecase.
+
+One you add some templates, your catalog is ready to be used.
+
+## Creating Users
+
+Although you can enable user self-registration, it is more usual to create the users manually, so you control exactly who have access to what. The catalog uses the concept of Users, Groups and User Profiles.
+
+- A User can be part of one or more Groups.
+- A User has a Role in a Group.
+- The Administrator Role is not related to a Group as it relates to the whole platform.
+
+Users can have different roles in different groups. A role defines what tasks the user can perform:
+
+- Guest is a user that can see records on the group, but cannot modify them.
+- Editor is a user that can create or edit records on the group.
+- Reviewer is a user that can edit and publish records on the group.
+- UserAdmin is a user that has administrative privileges over the records and users on the group.
+
+To add a new user to the GeoNetwork system you do the following:
+
+- Select the Administration button in the menu
+- On the Administration page, select User management
+- Click the button Add a new user
+- Provide the information required for the new user
+- Assign the correct profile
+- Assign the user to a group
+- Click on Save
+
+
+
+For each possible role, there is a list of groups. This way, a user can have different roles for different groups, allowing a user being a readonly guest on some group while being able to edit and review records on another group.
+
+
+
+## Creating Groups
+
+To create new groups you should be logged on with an account that has Administrative privileges.
+
+- Select the Administration button in the menu. On the Administration page, select Group management.
+- Select Add a new group. You may want to remove the Sample group;
+- Fill out the details. The email address will be used to send feedback on data downloads when they occur for resources that are part of the Group.
+- Click on Save
+
+Access privileges can be set per metadata record. You can define privileges on a per Group basis.
+
+See more on [Configuring the catalog](../../../administrator-guide/configuring-the-catalog/index.md).
diff --git a/docs/manual/docs/user-guide/analyzing/data.md b/docs/manual/docs/user-guide/analyzing/data.md
new file mode 100644
index 00000000000..53089faabde
--- /dev/null
+++ b/docs/manual/docs/user-guide/analyzing/data.md
@@ -0,0 +1,76 @@
+# Analyze and visualize data {#analyzing_data}
+
+## Data accessible using download services (WFS)
+
+All datasets described in metadata records and accessible through a download services (ie WFS) can be analyzed to improve search and data visualization. The catalog collect WFS features and index them.
+
+
+
+Elasticsearch needs to be installed and configured (See [Installing search platform](../../install-guide/installing-index.md)).
+
+Once collected, filtering is available in the map viewer for this layer. The filter interface provides faceting and export capabilities. The map viewer tries to connect to a WFS service by substituting WMS by WFS in the service URL. If a WFS service is responding with a feature type having the same name as the WMS, the filter panel provides the option to index the features. User needs to be identified to run the indexing task.
+
+
+
+Once indexed, all users can access the filtering menu providing:
+
+- a full text search on all fields
+- a control to display or not the heatmap
+- facets on all fields (computing automatically range facet for numbers)
+- table action display all values
+- filter action apply the filters to the WMS layers using SLD
+
+
+
+Click on the table menu to display the attributes. Double click a row in the table to zoom to a feature.
+
+
+
+Spatial filters can also be applied.
+
+
+
+## Feature type customization
+
+By default, the filter panel is generated from Elasticsearch index. But you customise it for a specific WFS Feature Type.
+
+The customisation is done by a JSON config inserted in the gmd:applicationProfile section of the online resource in the metadata.
+
+Here the options:
+
+``` json
+{
+ "fields": [{
+ "name": "PNT_PROF",
+ // non disponible actuellement
+ "type": "double",
+ "fq" : {
+ "facet.interval": "PNT_PROF_d",
+ "facet.interval.set": ["[0,10]", "(10,10000]"],
+ or
+ "facet.range": "PNT_PROF_d",
+ "facet.range.start": "0",
+ "facet.range.end": "10000",
+ "facet.range.gap": "300"
+ or
+ "facet.range": "PNT_PROF_d",
+ "facet.range.classes": "5" // Get min, max and compute gap on 5 classes
+ }
+ }, {
+ "name": "GRIDCODE"
+ }, {
+ "name": "LABEL",
+ "label" : {"fr": "monLabel", "en": "myLabel"}
+ }],
+ "tokenize": {"GRIDCODE": ",", "PARCELLE": "/"},
+ "heatmap": true
+}
+```
+
+You can
+
+- restrict the fields used for filter
+- specify your own ranges for numeric values
+- set your label
+- manage tokenized fields
+- enable heatmap
diff --git a/docs/manual/docs/user-guide/analyzing/img/filtering.png b/docs/manual/docs/user-guide/analyzing/img/filtering.png
new file mode 100644
index 00000000000..27e39444dcb
Binary files /dev/null and b/docs/manual/docs/user-guide/analyzing/img/filtering.png differ
diff --git a/docs/manual/docs/user-guide/analyzing/img/filteringlayer.png b/docs/manual/docs/user-guide/analyzing/img/filteringlayer.png
new file mode 100644
index 00000000000..dad7d97ba87
Binary files /dev/null and b/docs/manual/docs/user-guide/analyzing/img/filteringlayer.png differ
diff --git a/docs/manual/docs/user-guide/analyzing/img/layernotindexed.png b/docs/manual/docs/user-guide/analyzing/img/layernotindexed.png
new file mode 100644
index 00000000000..b986ae1a263
Binary files /dev/null and b/docs/manual/docs/user-guide/analyzing/img/layernotindexed.png differ
diff --git a/docs/manual/docs/user-guide/analyzing/img/mechanism.png b/docs/manual/docs/user-guide/analyzing/img/mechanism.png
new file mode 100644
index 00000000000..111464c9c6c
Binary files /dev/null and b/docs/manual/docs/user-guide/analyzing/img/mechanism.png differ
diff --git a/docs/manual/docs/user-guide/analyzing/img/tableview.png b/docs/manual/docs/user-guide/analyzing/img/tableview.png
new file mode 100644
index 00000000000..fbd14d48021
Binary files /dev/null and b/docs/manual/docs/user-guide/analyzing/img/tableview.png differ
diff --git a/docs/manual/docs/user-guide/analyzing/index.md b/docs/manual/docs/user-guide/analyzing/index.md
new file mode 100644
index 00000000000..b89f398e3f1
--- /dev/null
+++ b/docs/manual/docs/user-guide/analyzing/index.md
@@ -0,0 +1,4 @@
+# Analyzing data {#analyzing}
+
+- [Statistics on catalog content](metadata.md)
+- [Analyze and visualize data](data.md)
diff --git a/docs/manual/docs/user-guide/analyzing/metadata.md b/docs/manual/docs/user-guide/analyzing/metadata.md
new file mode 100644
index 00000000000..2ab3127cf93
--- /dev/null
+++ b/docs/manual/docs/user-guide/analyzing/metadata.md
@@ -0,0 +1,3 @@
+# Statistics on catalog content {#analyzing_metadata}
+
+The administration panel provides statistics on search and on records in the catalog.
diff --git a/docs/manual/docs/user-guide/associating-resources/cite.md b/docs/manual/docs/user-guide/associating-resources/cite.md
new file mode 100644
index 00000000000..378c1540fcd
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/cite.md
@@ -0,0 +1,46 @@
+# Cite a resource {#cite}
+
+The catalogue can provide an automatic citation based on information provided in the metadata record.
+
+
+
+The citation can be use to cite a dataset in publications.
+
+## Citation text
+
+The citation generated by default follows general conventions on how to cite a dataset but can be customized.
+
+The default is: * list of authors (and organisation) * publication year * title * list of publisher * DOI URL or landing page URL.
+
+These are the data needed to create DOI (see [Digital Object Identifier (DOI)](doi.md)).
+
+Customization of the citation can be done in `schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/formatter/citation/common.xsl`.
+
+An additional text may be stored in an online resource description with protocol `WWW:LINK-1.0-http--publication-URL`.
+
+
+
+Example:
+
+## Configuration
+
+The citation can be displayed or not in the record view. Check the user interface configuration to customize it:
+
+
+
+## Format
+
+Citation can be provided in various formats:
+
+- HTML
+- Plain text
+- RIS
+- BibTex
+
+## API
+
+The citation can be displayed in the default XSL formatter used for the full view using:
+
+The formatter producing the citation can be accessed directly using:
+
+To list available formats use: ?
diff --git a/docs/manual/docs/user-guide/associating-resources/doi.md b/docs/manual/docs/user-guide/associating-resources/doi.md
new file mode 100644
index 00000000000..31434831688
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/doi.md
@@ -0,0 +1,116 @@
+# Digital Object Identifier (DOI) {#doi}
+
+## Configuration
+
+The catalogue support DOI creation using:
+
+- [DataCite API](https://support.datacite.org/docs/mds-api-guide).
+- EU publication office API
+
+Configure the API access point in the `admin console --> settings`:
+
+
+
+A record can be downloaded using the DataCite format from the API using:
+
+## Creating the DOI
+
+Once configured, DOI can be created using the interface. DOI is created on demand. It means that a user must ask for creation of a DOI. When created, the task is notified by email to the reviewer of the group (by default, can be configured for administrator only using the notification level of the task).
+
+
+
+The task is assigned to a specific user. An optional due date and comment can be defined:
+
+
+
+After submission of the task, the task owner is notified by email (if the mail server is configured, see admin console --> settings). The task can then be resolved in the admin console ---> information --> versioning section.
+
+If the configuration is missing or wrong, the error is reported:
+
+
+
+For DOI creation, the task is a 2 steps actions:
+
+- First check if all prerequisite are covered (below the record is not valid in DataCite format).
+
+The DataCite format requires some mandatory fields:
+
+- Identifier (with mandatory type sub-property)
+- Creator (with optional given name, family name, name identifier and affiliation sub-properties)
+- Title (with optional type sub-properties)
+- Publisher
+- PublicationYear
+- ResourceType (with mandatory general type description subproperty)
+
+The mapping with ISO standards is the following:
+
+| Property | ISO 19139 | ISO 19115-3 |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
+| Identifier | ``gmd:MD_Metadata/gmd:fileIdentifier/*/text()`` | ``mdb:MD_Metadata/mdb:metadataIdentifier/*/mcc:code/*/text()`` |
+| Creator | ``gmd:identificationInfo/*/gmd:pointOfContact`` with role 'pointOfContact' or 'custodian' | ``mdb:identificationInfo/*/mri:pointOfContact`` with role 'pointOfContact' or 'custodian' |
+| Title | ``gmd:identificationInfo/*/gmd:citation/*/gmd:title`` | ``mdb:identificationInfo/*/mri:citation/*/cit:title`` |
+| Publisher | ``gmd:distributorContact[1]/*/gmd:organisationName/gco:CharacterString`` | ``mrd:distributorContact[1]/*/cit:party/*/cit:organisationName/gco:CharacterString`` |
+| PublicationYear | ``gmd:identificationInfo/*/gmd:citation/*/gmd:date/*[gmd:dateType/*/@codeListValue = 'publication'`` | ``mdb:identificationInfo/*/mri:citation/*/cit:date/*[cit:dateType/*/@codeListValue = 'publication'`` |
+| ResourceType | ``gmd:hierarchyLevel/*/@codeListValue`` ` | mdb:metadataScope/*/mdb:resourceScope/*/@codeListValue` |
+
+The mapping can be customized in:
+
+- ISO19139 `schemas/iso19139/src/main/plugin/iso19139/formatter/datacite/view.xsl`
+- ISO19115-3.2018 `schemas/iso19139/src/main/plugin/iso19139/formatter/datacite/view.xsl`
+
+See for more details on the format.
+
+DataCite API return XSD validation error.
+
+
+
+The catalogue also allow to apply DataCite validation in the editor:
+
+
+
+A DOI may already be assigned for a record:
+
+
+
+In such case the DOI can be updated. If the DOI is already assigned in a metadata record, editors can also update the DOI from the editor:
+
+
+
+After validation, create the DOI
+
+
+
+Once created, a link to the DOI and to the DataCite document is available:
+
+
+
+The DOI is then added to the metadata record:
+
+
+
+## DOI API
+
+The REST API allows to access the DOI related operations:
+
+
+
+The check preconditions API returns exception if one of the pre requisite is not met:
+
+- DataCite API is not configured
+- Record is not public
+- Record already has a DOI
+- Record is not valid for DataCite (ie. XSD errors returned by DataCite XSD validation)
+
+
+
+When a DOI is created, the response return the following details:
+
+
+
+The DOI is added to the metadata record using the following encoding:
+
+
+
+## Examples
+
+- [Comment créer un DOI à partir de l'outil de catalogage Geonetwork, Annick Battais](https://sist19.sciencesconf.org/data/pages/SIST19_A_BATTAIS.pdf)
diff --git a/docs/manual/docs/user-guide/associating-resources/img/addonlinesrc.png b/docs/manual/docs/user-guide/associating-resources/img/addonlinesrc.png
new file mode 100644
index 00000000000..1d92c9d914d
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/addonlinesrc.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/addonlinesrcup.png b/docs/manual/docs/user-guide/associating-resources/img/addonlinesrcup.png
new file mode 100644
index 00000000000..dfba69ce9e0
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/addonlinesrcup.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/addonlinesrcwms.png b/docs/manual/docs/user-guide/associating-resources/img/addonlinesrcwms.png
new file mode 100644
index 00000000000..4cfffa414f0
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/addonlinesrcwms.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/addresources.png b/docs/manual/docs/user-guide/associating-resources/img/addresources.png
new file mode 100644
index 00000000000..90138925c6a
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/addresources.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/atom-choose-dataset.png b/docs/manual/docs/user-guide/associating-resources/img/atom-choose-dataset.png
new file mode 100644
index 00000000000..58d9fa34185
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/atom-choose-dataset.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/atom-choose-feed.png b/docs/manual/docs/user-guide/associating-resources/img/atom-choose-feed.png
new file mode 100644
index 00000000000..6be82deb229
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/atom-choose-feed.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/citation-ui-config.png b/docs/manual/docs/user-guide/associating-resources/img/citation-ui-config.png
new file mode 100644
index 00000000000..33a811193b6
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/citation-ui-config.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/citation-with-addition.png b/docs/manual/docs/user-guide/associating-resources/img/citation-with-addition.png
new file mode 100644
index 00000000000..aa344222696
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/citation-with-addition.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/citation.png b/docs/manual/docs/user-guide/associating-resources/img/citation.png
new file mode 100644
index 00000000000..cc3221459f1
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/citation.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/dataset.png b/docs/manual/docs/user-guide/associating-resources/img/dataset.png
new file mode 100644
index 00000000000..23997fe7961
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/dataset.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-admin-console.png b/docs/manual/docs/user-guide/associating-resources/img/doi-admin-console.png
new file mode 100644
index 00000000000..f13c098ac17
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-admin-console.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-api-check-already-exist.png b/docs/manual/docs/user-guide/associating-resources/img/doi-api-check-already-exist.png
new file mode 100644
index 00000000000..27d6988fbf0
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-api-check-already-exist.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-api-check.png b/docs/manual/docs/user-guide/associating-resources/img/doi-api-check.png
new file mode 100644
index 00000000000..5a83293416e
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-api-check.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-api-done.png b/docs/manual/docs/user-guide/associating-resources/img/doi-api-done.png
new file mode 100644
index 00000000000..99b10f1b73f
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-api-done.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-api.png b/docs/manual/docs/user-guide/associating-resources/img/doi-api.png
new file mode 100644
index 00000000000..04d08223cb9
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-api.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-config-wrong.png b/docs/manual/docs/user-guide/associating-resources/img/doi-config-wrong.png
new file mode 100644
index 00000000000..d17b189ce0c
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-config-wrong.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-created.png b/docs/manual/docs/user-guide/associating-resources/img/doi-created.png
new file mode 100644
index 00000000000..4de9a6b7c36
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-created.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-exists.png b/docs/manual/docs/user-guide/associating-resources/img/doi-exists.png
new file mode 100644
index 00000000000..5d4931c2c64
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-exists.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-in-xml.png b/docs/manual/docs/user-guide/associating-resources/img/doi-in-xml.png
new file mode 100644
index 00000000000..0a36cfea8f2
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-in-xml.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-request-check-ok.png b/docs/manual/docs/user-guide/associating-resources/img/doi-request-check-ok.png
new file mode 100644
index 00000000000..d633f4f1549
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-request-check-ok.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-request-check.png b/docs/manual/docs/user-guide/associating-resources/img/doi-request-check.png
new file mode 100644
index 00000000000..85a5e2342c6
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-request-check.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-request-menu.png b/docs/manual/docs/user-guide/associating-resources/img/doi-request-menu.png
new file mode 100644
index 00000000000..e69c5168407
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-request-menu.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-request-popup.png b/docs/manual/docs/user-guide/associating-resources/img/doi-request-popup.png
new file mode 100644
index 00000000000..3c3078b22b5
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-request-popup.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-tocheck.png b/docs/manual/docs/user-guide/associating-resources/img/doi-tocheck.png
new file mode 100644
index 00000000000..50eacfb4985
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-tocheck.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-update-in-editor.png b/docs/manual/docs/user-guide/associating-resources/img/doi-update-in-editor.png
new file mode 100644
index 00000000000..02ec8648138
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-update-in-editor.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/doi-validation.png b/docs/manual/docs/user-guide/associating-resources/img/doi-validation.png
new file mode 100644
index 00000000000..07319ab1f32
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/doi-validation.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/feature.png b/docs/manual/docs/user-guide/associating-resources/img/feature.png
new file mode 100644
index 00000000000..d773ef47143
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/feature.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/filestore.png b/docs/manual/docs/user-guide/associating-resources/img/filestore.png
new file mode 100644
index 00000000000..9524410c235
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/filestore.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/link-remote-editor.png b/docs/manual/docs/user-guide/associating-resources/img/link-remote-editor.png
new file mode 100644
index 00000000000..1083719d038
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/link-remote-editor.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/link-remote-sibling.png b/docs/manual/docs/user-guide/associating-resources/img/link-remote-sibling.png
new file mode 100644
index 00000000000..4ac95486c08
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/link-remote-sibling.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/link-remote-view.png b/docs/manual/docs/user-guide/associating-resources/img/link-remote-view.png
new file mode 100644
index 00000000000..b83f578a5f7
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/link-remote-view.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/link-remote.png b/docs/manual/docs/user-guide/associating-resources/img/link-remote.png
new file mode 100644
index 00000000000..c78858732ef
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/link-remote.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/nav-series.png b/docs/manual/docs/user-guide/associating-resources/img/nav-series.png
new file mode 100644
index 00000000000..f2267acf37d
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/nav-series.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/onlinesrc.png b/docs/manual/docs/user-guide/associating-resources/img/onlinesrc.png
new file mode 100644
index 00000000000..23c37f09ad8
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/onlinesrc.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/parent.png b/docs/manual/docs/user-guide/associating-resources/img/parent.png
new file mode 100644
index 00000000000..28be6e5919c
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/parent.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/service.png b/docs/manual/docs/user-guide/associating-resources/img/service.png
new file mode 100644
index 00000000000..a60ef12f2e3
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/service.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/sources.png b/docs/manual/docs/user-guide/associating-resources/img/sources.png
new file mode 100644
index 00000000000..1639ee5542f
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/sources.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/thumb-from-filestore.png b/docs/manual/docs/user-guide/associating-resources/img/thumb-from-filestore.png
new file mode 100644
index 00000000000..1ef2f73291c
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/thumb-from-filestore.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/thumb-from-url.png b/docs/manual/docs/user-guide/associating-resources/img/thumb-from-url.png
new file mode 100644
index 00000000000..e9bd58311bd
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/thumb-from-url.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/thumb-in-editor.png b/docs/manual/docs/user-guide/associating-resources/img/thumb-in-editor.png
new file mode 100644
index 00000000000..7138b3a8078
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/thumb-in-editor.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/thumb-in-search-results.png b/docs/manual/docs/user-guide/associating-resources/img/thumb-in-search-results.png
new file mode 100644
index 00000000000..14f17ee4957
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/thumb-in-search-results.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/thumb.png b/docs/manual/docs/user-guide/associating-resources/img/thumb.png
new file mode 100644
index 00000000000..f7c6d5342b1
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/thumb.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/img/thumbprint.png b/docs/manual/docs/user-guide/associating-resources/img/thumbprint.png
new file mode 100644
index 00000000000..7beea06630c
Binary files /dev/null and b/docs/manual/docs/user-guide/associating-resources/img/thumbprint.png differ
diff --git a/docs/manual/docs/user-guide/associating-resources/index.md b/docs/manual/docs/user-guide/associating-resources/index.md
new file mode 100644
index 00000000000..fa4296170b7
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/index.md
@@ -0,0 +1,20 @@
+# Associating resources {#associating_resources}
+
+You can associate a record with different types of resources using the **Associated resources** panel. This topic describes how to associate resources.
+
+- To add or edit associated resources, open the editor, and click Associate Resources to view the wizard panel.
+
+
+
+Use the wizard panel to create or delete associated resources. A list of currently attached resources grouped by types is also provided.
+
+- To add a new online resource, click on the top + caret.
+
+
+
+You can associate different types of resources:
+
+- [Associating documents](linking-documents.md)
+- [Associating another record](linking-records.md)
+- [Digital Object Identifier (DOI)](doi.md)
+- [Cite a resource](cite.md)
diff --git a/docs/manual/docs/user-guide/associating-resources/linking-dataset-or-service.md b/docs/manual/docs/user-guide/associating-resources/linking-dataset-or-service.md
new file mode 100644
index 00000000000..4fd977ccd6a
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/linking-dataset-or-service.md
@@ -0,0 +1,23 @@
+# Linking a dataset with a service {#linking-dataset-or-service}
+
+Metadata on dataset can be associated to metadata on services.
+
+!!! info "Todo"
+
+ Add more details on how/why/encoding
+
+
+``` xml
+
+```
+
+In a service metadata record, click the `Link to a dataset` button to open the record selector which list all datasets in the catalog. Optionally, the layer name may be define manually or from the list of the layers retrieved from the service (using the GetCapabilities).
+
+
+
+In a dataset metadata record, click the `Link to a service` button to open the record selector which list all services in the catalog.
+
+
+
+When confirming the association, both records will be affected by the change (depending on user privileges - ie. current user may not be allowed to modify the target record).
diff --git a/docs/manual/docs/user-guide/associating-resources/linking-documents.md b/docs/manual/docs/user-guide/associating-resources/linking-documents.md
new file mode 100644
index 00000000000..10bbacece64
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/linking-documents.md
@@ -0,0 +1,9 @@
+# Associating documents {#associating_resources_doc}
+
+You can associate a record with documents using a URL.
+
+A document could be an overview, a quality report, a website available in different formats (eg. png, jpg, pdf, html) on the web.
+
+- [Uploading attachments](using-filestore.md)
+- [Illustrating with an overview](linking-thumbnail.md)
+- [Linking website, web services, \... using URL](linking-online-resources.md)
diff --git a/docs/manual/docs/user-guide/associating-resources/linking-feature-catalog.md b/docs/manual/docs/user-guide/associating-resources/linking-feature-catalog.md
new file mode 100644
index 00000000000..e35f317dd8e
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/linking-feature-catalog.md
@@ -0,0 +1,17 @@
+# Describing attributes table in a feature Catalog {#linking-feature-catalog}
+
+A feature catalog describes the data model of the dataset with the list of tables, attributes, definitions, list of values, \... Feature catalogs could be described:
+
+- as a document (eg. PDF) and linked to the metadata record (see [Linking a document](linking-online-resources.md#linking-online-resources-doc))
+- as a record and described using the ISO19110 standards.
+
+Click on `Link to a feature catalog` to open the record selector listing all feature catalog described in the catalog. Choose one and submit to associate the 2 documents.
+
+
+
+In ISO19115-3, the feature catalog can also be described directly in the metadata record in the `content` section.
+
+!!! info "Todo"
+
+ Add encoding
+
diff --git a/docs/manual/docs/user-guide/associating-resources/linking-online-resources.md b/docs/manual/docs/user-guide/associating-resources/linking-online-resources.md
new file mode 100644
index 00000000000..09cf9ccbd4d
--- /dev/null
+++ b/docs/manual/docs/user-guide/associating-resources/linking-online-resources.md
@@ -0,0 +1,169 @@
+# Linking website, web services, \... using URL {#linking-online-resources}
+
+This section applies mainly to ISO19139 records and partially to Dublin Core (ie. only documents can be associated in Dublin Core) standards.
+
+## Linking a document {#linking-online-resources-doc}
+
+2 approaches can be used to link documents:
+
+- by providing a URL
+- by uploading a document
+
+To add a new one, click on the + caret button then `Add an online resource` button or, if already one exists, just click on the title of the `Online resources`.
+
+
+
+To link a URL, set the following properties:
+
+- `Protocol` to describe the type of document attached (`Web address (URL)` is the default)
+- `Linkage` to point to the target document. It can be any type of links like , , , \...
+- `Name` is optional and provides a label for making an hyperlink
+- `Description` is optional and provides more details about the link
+
+To upload a document, switch to the `Upload` tab and choose a document, or drag and drop it in the pop up. In that case, the protocol is hidden and is set to `WWW:DOWNLOAD`.
+
+
+
+Depending on your needs, more specific links could be added and will be associated to different actions and display in the applications.
+
+## Linking a WMS layer {#linking-wms-layer}
+
+To be able to view a record on the map viewer, it may be relevant to add a reference to one or more WMS services publishing the dataset. An online resource is encoded using the following in ISO19139:
+
+``` xml
+
+
+
+ https://download.data.grandlyon.com/wms/grandlyon
+
+
+ OGC:WMS
+
+
+ cad_cadastre.cadsubdivisionsection
+
+
+ Subdivision de section cadastrale (Plan cadastral informatisé du Grand Lyon)(OGC:WMS)
+
+
+
+```
+
+To add a WMS layer:
+
+- choose the protocol `OGC:WMS Web Map Service`,
+- set the URL of the service,
+- then the wizard query the service to retrieve the list of layers
+- choose one or more layer in the list or set it manually.
+
+
+
+## Linking a database table or a GIS file on the network {#linking-online-resources-georesource}
+
+To reference a GIS file or a database table, user can upload or link to a that resource (see [Linking a document](linking-online-resources.md#linking-online-resources-doc)). The type of protocol depends on the type of resource associated:
+
+| Type of resource | Vector file uploaded (eg. zipped Shapefile) |
+|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
+| URL | File URL created after upload on the catalog. eg. |
+| Protocol | WWW:DOWNLOAD |
+| Name | File name (readonly) |
+
+| Type of resource | Vector file on the network |
+|------------------|--------------------------------------------------------------------|
+| URL | File path. eg. |
+| Protocol | or |
+| Name | File description |
+
+| Type of resource | Vector (Table PostGIS) |
+|------------------|------------------------------------------------------|
+| URL | jdbc:postgresql://localhost:5432/login: |
+| Protocol | DB:POSTGIS |
+| Name | Table name |
+
+When having information about the database or file on the local network, it may be relevant to hide those informations for public users (see [Restricting information to metadata sections](../publishing/restricting-information-to-metadata-sections.md)).
+
+!!! info "Todo"
+
+ Add doc & link to geopublisher
+
+
+## Linking data using ATOM feeds {#linking-data-using-atom-feed}
+
+If your organisation provides ATOM feeds to facilitate access to the data, metadata records can link to these feeds. Users can link to a service feed in a service record and to a dataset feed in a dataset record.
+
+``` xml
+
+
+
+ 
+ > 
+ > 
+