process reference links using anchors_txt index

docs/manual/docs/administrator-guide/configuring-the-catalog/csw-configuration.md

@@ -41,7 +41,7 @@ If an error occurred while building the capabilities document from the service r
 
 ## CSW Configuration for INSPIRE {#csw-configuration_inspire}
 
-If your catalogue also focus on INSPIRE (see [inspire-configuration](inspire-configuration.md)), it may be relevant to also populate the following to properly configure your discovery service:
+If your catalogue also focus on INSPIRE (see [Configuring for the INSPIRE Directive](/administrator-guide/configuring-the-catalog/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

docs/manual/docs/administrator-guide/configuring-the-catalog/inspire-configuration.md

@@ -6,11 +6,11 @@ From the **Admin console --> Settings** user can configure INSPIRE directive sup
 
 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-thesaurus.md)).
+-   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](/administrator-guide/managing-classification-systems/managing-thesaurus.md)).
 
     ![image](img/inspire-configuration.png)
 
-To configure the discovery service, a dedicated service metadata record MUST be created in order to provide a complete GetCapabilities document ([csw-configuration_inspire](csw-configuration_inspire.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](/administrator-guide/configuring-the-catalog/csw-configuration.rst#csw-configuration_inspire)).
 
 ## Loading INSPIRE codelists
 

docs/manual/docs/administrator-guide/configuring-the-catalog/map-server-configuration.md

@@ -18,4 +18,4 @@ The following parameters are required:
 -   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 [geopublication-usage](geopublication-usage.md).
+See [Publishing GIS data in a map server](/user-guide/workflow/geopublication.md).

docs/manual/docs/administrator-guide/configuring-the-catalog/portal-configuration.md

@@ -14,7 +14,7 @@ There are 3 types of sources:
 
 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 (:[mef_format](mef_format.md)) which contain the source catalogue information.
+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.
 
@@ -54,7 +54,7 @@ Some organizations need to open the catalogue to a set of partners. In such case
 
 ![](img/portal-geocatch.png)
 
-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)).
+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](/administrator-guide/configuring-the-catalog/user-interface-configuration.md)).
 
 To setup this kind of configuration, the basic principle is to have:
 
@@ -63,8 +63,8 @@ To setup this kind of configuration, the basic principle is to have:
 
 To configure this, apply the following steps:
 
--   Create a group for the partner eg. `oca` (see [creating-group](creating-group.md)).
--   Create at least one user for the partner (see [creating-user](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 group for the partner eg. `oca` (see [Creating group](/administrator-guide/managing-users-and-groups/creating-group.md)).
+-   Create at least one user for the partner (see [Creating user](/administrator-guide/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 <http://localhost:8080/geonetwork/oca>.
 -   (Optional) Link the sub-portal to a user admin group to allow `UserAdmin` to configure their sub-portal.
 

docs/manual/docs/administrator-guide/configuring-the-catalog/system-configuration.md

@@ -61,7 +61,7 @@ JVM proxy parameters may also be required to properly set the proxy for all remo
 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](life-cycle.md))
+-   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.
@@ -81,15 +81,15 @@ Configuration settings in this group determine what the limits are on user inter
 
 ## Catalog Service for the Web (CSW)
 
-See [csw-configuration](csw-configuration.md).
+See [Configuring CSW](/administrator-guide/configuring-the-catalog/csw-configuration.md).
 
 ## Shibboleth
 
-See [authentication-shibboleth](authentication-shibboleth.md).
+See [Configuring Shibboleth](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-shibboleth).
 
 ## User self-registration
 
-Enable the self registration form. See [user_self_registration](user_self_registration.md).
+Enable the self registration form. See [User Self-Registration](/administrator-guide/managing-users-and-groups/user-self-registration.md).
 
 ## system/userFeedback
 
@@ -147,7 +147,7 @@ Restart the catalog to take all OAI settings into account.
 
 ## INSPIRE Directive configuration
 
-See [inspire-configuration](inspire-configuration.md).
+See [Configuring for the INSPIRE Directive](/administrator-guide/configuring-the-catalog/inspire-configuration.md).
 
 ## INSPIRE Atom Feed
 

docs/manual/docs/administrator-guide/configuring-the-catalog/user-interface-configuration.md

@@ -11,7 +11,7 @@ Most of the configuration parameters for the user interface can be changed by an
 
 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.
+To add a new configuration, such as for a sub-portal (see [Portal configuration](/administrator-guide/configuring-the-catalog/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
 
@@ -77,7 +77,7 @@ To add a new configuration, such as for a sub-portal (see [portal-configuration]
 ![](img/ui-settings-searchpage3.png)
 
 -   **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 [creating-custom-view](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.
+-   **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.
 
 ![](img/ui-settings-searchpage3.png)
 
@@ -116,7 +116,7 @@ This section describes how an administrator can configure the different maps in
 ### 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](quick_start.md)).
+-   **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.
 
@@ -205,11 +205,11 @@ This WMS layer will be shown but only when the map is on `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 [user-interface-config-viewermap](user-interface-config-viewermap.md).
+This section defines the configuration for the mini map shown on the search page. It uses the same options as in [Viewer Map Configuration](/administrator-guide/configuring-the-catalog/user-interface-configuration.rst#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 [user-interface-config-viewermap](user-interface-config-viewermap.md).
+This section defines the configuration for the map shown when editing a record. It uses the same options as in [Viewer Map Configuration](/administrator-guide/configuring-the-catalog/user-interface-configuration.rst#user-interface-config-viewermap).
 
 ## Gazetteer
 

docs/manual/docs/administrator-guide/managing-classification-systems/managing-directories.md

@@ -26,11 +26,11 @@ Metadata fragments that are saved in the catalogue database are called subtempla
 Fragments can be inserted in metadata record in 2 modes:
 
 -   by copy/paste
--   by link (if xlink support is enabled. See [xlink_config](xlink_config.md))
+-   by link (if xlink support is enabled. See [Metadata XLink](/administrator-guide/configuring-the-catalog/system-configuration.rst#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](harvesting_fragments.md)) or imported using the metadata import page.
+Fragments may be created by harvesting (see [Harvesting Fragments of Metadata to support re-use](/user-guide/harvesting/index.rst#harvesting_fragments)) or imported using the metadata import page.
 
 This section of the manual describes:
 

docs/manual/docs/administrator-guide/managing-metadata-standards/configure-validation.md

@@ -1,6 +1,6 @@
 # Configuring validation levels {#configure-validation}
 
-Each standard defines validation levels (using schematron - see [implementing-a-schema-plugin](implementing-a-schema-plugin.md)). By default, ISO19139 proposes validation using:
+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)

docs/manual/docs/administrator-guide/managing-users-and-groups/authentication-mode.md

@@ -2,12 +2,12 @@
 
 By default the catalog uses the internal database for user management and authentication. However there are some other authentication mechanisms available:
 
--   [authentication-ldap](authentication-ldap.md)
--   [authentication-ldap-hierarchy](authentication-ldap-hierarchy.md)
--   [authentication-cas](authentication-cas.md)
--   [authentication-openid](authentication-openid.md)
--   [authentication-keycloak](authentication-keycloak.md)
--   [authentication-shibboleth](authentication-shibboleth.md)
+-   [Configuring LDAP](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-ldap)
+-   [Configuring LDAP - Hierarchy](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-ldap-hierarchy)
+-   [Configuring CAS](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-cas)
+-   [Configuring OAUTH2 OpenID Connect](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-openid)
+-   [Configuring Keycloak](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-keycloak)
+-   [Configuring Shibboleth](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-shibboleth)
 
 Which mode to use is configured in **`WEB-INF/config-security/config-security.xml`** or via an environment variable `geonetwork.security.type`.
 
@@ -21,7 +21,7 @@ Uncomment the relevant line in **`WEB-INF/config-security/config-security.xml`**
 
 [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 [authentication-ldap-hierarchy](authentication-ldap-hierarchy.md).
+GeoNetwork currently has 2 approaches to configure LDAP. Verify also the alternative approach in [Configuring LDAP - Hierarchy](/administrator-guide/managing-users-and-groups/authentication-mode.rst#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`.
 
@@ -728,10 +728,10 @@ Authorization: Bearer:  <JWT token>
 
 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 [authentication-openid](authentication-openid.md))
-2.  Setup the OIDC Bearer token configuration (see [bearer_token_configuration](bearer_token_configuration.md))
+1.  Setup your OIDC configuration (see [Configuring OAUTH2 OpenID Connect](/administrator-guide/managing-users-and-groups/authentication-mode.rst#authentication-openid))
+2.  Setup the OIDC Bearer token configuration (see [Configuration](/administrator-guide/managing-users-and-groups/authentication-mode.rst#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](oidc_bearer_tokens.md))
+4.  Attach it to your request headers (see [OIDC Bearer Tokens](/administrator-guide/managing-users-and-groups/authentication-mode.rst#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.

docs/manual/docs/administrator-guide/managing-users-and-groups/creating-user.md

@@ -5,6 +5,6 @@ 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 [user_profiles](user_profiles.md));
-5.  Assign the user to a *group* (see [creating-group](creating-group.md));
+4.  Assign the correct *profile* (see [Users, Groups and Roles](/administrator-guide/managing-users-and-groups/index.rst#user_profiles));
+5.  Assign the user to a *group* (see [Creating group](/administrator-guide/managing-users-and-groups/creating-group.md));
 6.  Click *Save*.

docs/manual/docs/administrator-guide/managing-users-and-groups/index.md

@@ -11,7 +11,7 @@ Upon installation a default user with name `admin` and password `admin` is creat
 
 ## 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 [session-timeout-configuration](session-timeout-configuration.md) for details).
+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.rst#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:
 

docs/manual/docs/administrator-guide/managing-users-and-groups/user-self-registration.md

@@ -1,6 +1,6 @@
 # User Self-Registration {#user_self_registration}
 
-To enable the self-registration functions, see [system-configuration](system-configuration.md). When self-registration is enabled, for users that are not logged in, an additional link is shown on the login page:
+To enable the self-registration functions, see [System configuration](/administrator-guide/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:
 
 ![](img/selfregistration-start.png)
 
@@ -39,7 +39,7 @@ When a user self-registration occurs, the user receives an email with the new ac
     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 [system-config-feedback](system-config-feedback.md)) section of the `System Administration` menu which looks something like the following:
+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](/administrator-guide/configuring-the-catalog/system-configuration.rst#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.