Deployed 9e5d8fb to 4.4 with MkDocs 1.5.3 and mike 2.0.0

4.4/administrator-guide/managing-users-and-groups/authentication-mode/index.html

@@ -2900,7 +2900,7 @@ <h3 id="configuring-ldap-beans-hierarchy">Configuring LDAP Beans (Hierarchy)</h3
 <p>There are currently two ways to convert an LDAP group to GeoNetwork Groups/Profiles.</p>
 <ul>
 <li>
-<p>The <code>LDAPRoleConverterGroupNameParser</code>, 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 <code>OR</code> into the GeoNetwork group <code>AL</code> with Profile <code>r.</code></p>
+<p>The <code>LDAPRoleConverterGroupNameParser</code>, 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 <code>GCAT_GENERAL_EDITOR</code> into the GeoNetwork group <code>GENERAL</code> with Profile <code>Editor</code>.</p>
 <div class="language-xml highlight"><pre><span></span><code><span id="__span-21-1"><a id="__codelineno-21-1" name="__codelineno-21-1" href="#__codelineno-21-1"></a><span class="nt">&lt;bean</span><span class="w"> </span><span class="na">id=</span><span class="s">&quot;ldapRoleConverterGroupNameParser&quot;</span><span class="w">  </span><span class="na">class=</span><span class="s">&quot;LDAPRoleConverterGroupNameParser&quot;</span><span class="nt">&gt;</span>
 </span><span id="__span-21-2"><a id="__codelineno-21-2" name="__codelineno-21-2" href="#__codelineno-21-2"></a>
 </span><span id="__span-21-3"><a id="__codelineno-21-3" name="__codelineno-21-3" href="#__codelineno-21-3"></a><span class="w">    </span><span class="nt">&lt;property</span><span class="w"> </span><span class="na">name=</span><span class="s">&quot;ldapMembershipQueryParser&quot;</span><span class="w"> </span><span class="na">value=</span><span class="s">&quot;GCAT_(.*)_(.*)&quot;</span><span class="nt">/&gt;</span>

4.4/administrator-guide/managing-users-and-groups/creating-group/index.html

@@ -1951,7 +1951,7 @@
 
 
 <h1 id="creating-group">Creating group</h1>
-<p>The administrator can create new groups of users. User groups could correspond to logical units within an organisation, for example <code>es</code>, <code>re</code>, <code>nd</code>, <code>er</code>, <code>th</code> and so on.</p>
+<p>The administrator can create new groups of users. User groups could correspond to logical units within an organisation, for example <code>Fisheries</code>, <code>Agriculture</code>, <code>Land</code>, <code>Water</code>, <code>Health</code> and so on.</p>
 <p>To create new groups you should be logged on with an account that has administrative privileges.</p>
 <ol>
 <li>

4.4/customizing-application/search-ui/enrichview/index.html

@@ -1810,7 +1810,7 @@ <h1 id="enrichsearchview">Enrich your custom view</h1>
 <p>Now we created our structure with basic content, we want to create a real catalog page.</p>
 <p>For that, you can include default view content, or build your own application on top of core GeoNetwork components.</p>
 <h2 id="geonetwork-components">GeoNetwork components</h2>
-<p>UI design is based on shared widgets, logic and components. In AngularJS terms, we talk about <code>es</code> and <code>es</code>.</p>
+<p>UI design is based on shared widgets, logic and components. In AngularJS terms, we talk about <code>services</code> and <code>directives</code>.</p>
 <p>All components are stored in the folder <a href="https://github.com/geonetwork/core-geonetwork/tree/develop/web-ui/src/main/resources/catalog/components">components</a></p>
 <h3 id="main-page-components">Main page components</h3>
 <p>Main search input</p>

4.4/customizing-application/search-ui/loadview/index.html

@@ -1812,7 +1812,7 @@ <h2 id="loading-the-javascript">Loading the javascript</h2>
 <p>To init AngularJS main module you have to use the directive <code>ng-app</code> and point on your main AngularJS module.</p>
 <div class="language-xml highlight"><pre><span></span><code><span id="__span-1-1"><a id="__codelineno-1-1" name="__codelineno-1-1" href="#__codelineno-1-1"></a><span class="nt">&lt;html</span><span class="w"> </span><span class="na">ng-app=</span><span class="s">&quot;{$angularModule}&quot;</span><span class="w"> </span><span class="na">lang=</span><span class="s">&quot;{$lang}&quot;</span><span class="w"> </span><span class="na">id=</span><span class="s">&quot;ng-app&quot;</span><span class="nt">&gt;</span>
 </span></code></pre></div>
-<p>In the case of the search page (<code>catalog.search</code>), the <code>$angularApp</code> variable equals <code>gn_search</code>. And for the <code>lt</code> view the <code>$angularModule</code> equals <code>gn_search_default</code>.</p>
+<p>In the case of the search page (<code>catalog.search</code>), the <code>$angularApp</code> variable equals <code>gn_search</code>. And for the <code>default</code> view the <code>$angularModule</code> equals <code>gn_search_default</code>.</p>
 <p>So, by default, the main AngularJS module is loaded here from <code>gn_search_default</code> module declared here (See <code>web-ui/src/main/resources/catalog/views/default/module.js</code>.</p>
 <p>From here, you can build your AngularJS module dependency tree and load your application.</p>
 <h2 id="css-files">CSS files</h2>

4.4/fr/administrator-guide/managing-users-and-groups/authentication-mode/index.html

@@ -2900,7 +2900,7 @@ <h3 id="configuring-ldap-beans-hierarchy">Configuring LDAP Beans (Hierarchy)</h3
 <p>There are currently two ways to convert an LDAP group to GeoNetwork Groups/Profiles.</p>
 <ul>
 <li>
-<p>The <code>LDAPRoleConverterGroupNameParser</code>, 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 <code>OR</code> into the GeoNetwork group <code>AL</code> with Profile <code>r.</code></p>
+<p>The <code>LDAPRoleConverterGroupNameParser</code>, 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 <code>GCAT_GENERAL_EDITOR</code> into the GeoNetwork group <code>GENERAL</code> with Profile <code>Editor</code>.</p>
 <div class="language-xml highlight"><pre><span></span><code><span id="__span-21-1"><a id="__codelineno-21-1" name="__codelineno-21-1" href="#__codelineno-21-1"></a><span class="nt">&lt;bean</span><span class="w"> </span><span class="na">id=</span><span class="s">&quot;ldapRoleConverterGroupNameParser&quot;</span><span class="w">  </span><span class="na">class=</span><span class="s">&quot;LDAPRoleConverterGroupNameParser&quot;</span><span class="nt">&gt;</span>
 </span><span id="__span-21-2"><a id="__codelineno-21-2" name="__codelineno-21-2" href="#__codelineno-21-2"></a>
 </span><span id="__span-21-3"><a id="__codelineno-21-3" name="__codelineno-21-3" href="#__codelineno-21-3"></a><span class="w">    </span><span class="nt">&lt;property</span><span class="w"> </span><span class="na">name=</span><span class="s">&quot;ldapMembershipQueryParser&quot;</span><span class="w"> </span><span class="na">value=</span><span class="s">&quot;GCAT_(.*)_(.*)&quot;</span><span class="nt">/&gt;</span>

4.4/fr/administrator-guide/managing-users-and-groups/creating-group/index.html

@@ -1951,7 +1951,7 @@
 
 
 <h1 id="creating-group">Creating group</h1>
-<p>The administrator can create new groups of users. User groups could correspond to logical units within an organisation, for example <code>es</code>, <code>re</code>, <code>nd</code>, <code>er</code>, <code>th</code> and so on.</p>
+<p>The administrator can create new groups of users. User groups could correspond to logical units within an organisation, for example <code>Fisheries</code>, <code>Agriculture</code>, <code>Land</code>, <code>Water</code>, <code>Health</code> and so on.</p>
 <p>To create new groups you should be logged on with an account that has administrative privileges.</p>
 <ol>
 <li>

4.4/fr/customizing-application/search-ui/enrichview/index.html

@@ -1810,7 +1810,7 @@ <h1 id="enrichsearchview">Enrich your custom view</h1>
 <p>Now we created our structure with basic content, we want to create a real catalog page.</p>
 <p>For that, you can include default view content, or build your own application on top of core GeoNetwork components.</p>
 <h2 id="geonetwork-components">GeoNetwork components</h2>
-<p>UI design is based on shared widgets, logic and components. In AngularJS terms, we talk about <code>es</code> and <code>es</code>.</p>
+<p>UI design is based on shared widgets, logic and components. In AngularJS terms, we talk about <code>services</code> and <code>directives</code>.</p>
 <p>All components are stored in the folder <a href="https://github.com/geonetwork/core-geonetwork/tree/develop/web-ui/src/main/resources/catalog/components">components</a></p>
 <h3 id="main-page-components">Main page components</h3>
 <p>Main search input</p>

4.4/fr/customizing-application/search-ui/loadview/index.html

@@ -1812,7 +1812,7 @@ <h2 id="loading-the-javascript">Loading the javascript</h2>
 <p>To init AngularJS main module you have to use the directive <code>ng-app</code> and point on your main AngularJS module.</p>
 <div class="language-xml highlight"><pre><span></span><code><span id="__span-1-1"><a id="__codelineno-1-1" name="__codelineno-1-1" href="#__codelineno-1-1"></a><span class="nt">&lt;html</span><span class="w"> </span><span class="na">ng-app=</span><span class="s">&quot;{$angularModule}&quot;</span><span class="w"> </span><span class="na">lang=</span><span class="s">&quot;{$lang}&quot;</span><span class="w"> </span><span class="na">id=</span><span class="s">&quot;ng-app&quot;</span><span class="nt">&gt;</span>
 </span></code></pre></div>
-<p>In the case of the search page (<code>catalog.search</code>), the <code>$angularApp</code> variable equals <code>gn_search</code>. And for the <code>lt</code> view the <code>$angularModule</code> equals <code>gn_search_default</code>.</p>
+<p>In the case of the search page (<code>catalog.search</code>), the <code>$angularApp</code> variable equals <code>gn_search</code>. And for the <code>default</code> view the <code>$angularModule</code> equals <code>gn_search_default</code>.</p>
 <p>So, by default, the main AngularJS module is loaded here from <code>gn_search_default</code> module declared here (See <code>web-ui/src/main/resources/catalog/views/default/module.js</code>.</p>
 <p>From here, you can build your AngularJS module dependency tree and load your application.</p>
 <h2 id="css-files">CSS files</h2>

4.4/fr/install-guide/configuring-database/index.html

@@ -1593,7 +1593,7 @@ <h2 id="configuring-a-database-via-environment">Configuring a database via envir
 </span></code></pre></div>
 </li>
 </ol>
-<p>Within PostgreSQL it is possible to configure <code>es</code> or <code>is</code>. 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.</p>
+<p>Within PostgreSQL it is possible to configure <code>postgres</code> or <code>postgis</code>. 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.</p>
 <h2 id="logging">Logging</h2>
 <p>To see more details about the database connection and queries, the log can be switched to DEBUG level in <code>web/src/main/webapp/WEB-INF/classes/log4j.xml</code> (or see <a href="../../administrator-guide/configuring-the-catalog/system-configuration/#system-config-server">Catalog Server</a> &rarr; Log level).</p>
 <div class="language-xml highlight"><pre><span></span><code><span id="__span-3-1"><a id="__codelineno-3-1" name="__codelineno-3-1" href="#__codelineno-3-1"></a><span class="nt">&lt;logger</span><span class="w"> </span><span class="na">name=</span><span class="s">&quot;org.hibernate.SQL&quot;</span><span class="w"> </span><span class="na">additivity=</span><span class="s">&quot;false&quot;</span><span class="nt">&gt;</span>

4.4/fr/install-guide/installing-from-war-file/index.html

@@ -1427,7 +1427,7 @@ <h1 id="installing-from-war-file">Installing from WAR file</h1>
 </span><span id="__span-2-4"><a id="__codelineno-2-4" name="__codelineno-2-4" href="#__codelineno-2-4"></a>./elasticsearch
 </span></code></pre></div>
 <p>Open <a href="http://localhost:9200">http://localhost:9200</a> in your web browser to check that Elasticsearch is running.</p>
-<p>To use an existing instance check <code>on</code> in <a href="../installing-index/">Installing search platform</a>.</p>
+<p>To use an existing instance check Configure connection in <a href="../installing-index/">Installing search platform</a>.</p>
 </li>
 <li>
 <p>Up and running?</p>

4.4/fr/install-guide/map-print-setup/index.html

@@ -1369,14 +1369,14 @@
 
 <h1 id="" map-print-setup="map-print-setup">Configuring printing of the map</h1>
 <p>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.</p>
-<p>GeoNetwork needs to be able to access the external resource. Set up a webproxy in <code>gs</code> if your network requires a webproxy to be set up to access the internet.</p>
+<p>GeoNetwork needs to be able to access the external resource. Set up a webproxy in <code>system settings</code> if your network requires a webproxy to be set up to access the internet.</p>
 <p>Locate the file <code>WEB-INF/config-print/print-config.yaml</code>, this configuration file has a lot of options to customise the print options. Read more about the various parameters at <a href="http://www.mapfish.org/doc/print/configuration.html">http://www.mapfish.org/doc/print/configuration.html</a></p>
 <p>The folder contains 3 template files:</p>
 <ul>
 <li><code>template.pdf</code> and <code>template-landscape.pdf</code> which are used to generate the map viewer pdf</li>
 <li><code>template-thumbnail.pdf</code> which is used to build a thumbnail in the metadata editor (see <a href="../../user-guide/associating-resources/linking-thumbnail/#linking-thumbnail-from-wms">Generating a thumbnail using WMS layers</a>).</li>
 </ul>
-<p>These templates are created by exporting pdf from the included <code>template.odf</code> file in the folder.</p>
+<p>These templates are created by exporting pdf from the included <code>template.pdf</code> file in the folder.</p>
 
 
 

4.4/fr/overview/change-log/version-4.0.2/index.html

@@ -2524,12 +2524,12 @@
 <h1 id="version-402">Version 4.0.2</h1>
 <p>GeoNetwork 4.0.2 release is a minor release but adds a better multilingual support which may require some changes in your installations:</p>
 <h2 id="database-migration">Database migration</h2>
-<p>With the possibility to <a href="https://github.com/geonetwork/core-geonetwork/pull/4817">restore deleted record</a>, catalog maintainer has to update the database with the <a href="https://github.com/geonetwork/core-geonetwork/blob/master/web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v3110/migrate-default.sql#L10-L27">following migration SQL script</a>.</p>
+<p>With the possibility to <a href="https://github.com/geonetwork/core-geonetwork/pull/4817">restore deleted records</a>, the catalog maintainer has to update the database with the <a href="https://github.com/geonetwork/core-geonetwork/blob/master/web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v3110/migrate-default.sql#L10-L27">following migration SQL script</a>.</p>
 <h2 id="index-migration">Index migration</h2>
 <p>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:</p>
 <h3 id="codelist">Codelist</h3>
-<p><code>t_</code> is now <code>l_</code> and is an object composed of:</p>
-<p>So <code>et</code> was:</p>
+<p><code>codelist</code> is now <code>cl_</code> and is an object composed of:</p>
+<p>characterSet was:</p>
 <div class="language-js highlight"><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a><span class="nx">codelist_characterSet</span><span class="o">:</span><span class="w"> </span><span class="p">[</span>
 </span><span id="__span-0-2"><a id="__codelineno-0-2" name="__codelineno-0-2" href="#__codelineno-0-2"></a><span class="s2">&quot;utf8&quot;</span>
 </span><span id="__span-0-3"><a id="__codelineno-0-3" name="__codelineno-0-3" href="#__codelineno-0-3"></a><span class="p">],</span>
@@ -2548,10 +2548,10 @@ <h3 id="codelist">Codelist</h3>
 </span><span id="__span-1-5"><a id="__codelineno-1-5" name="__codelineno-1-5" href="#__codelineno-1-5"></a><span class="w">  </span><span class="nx">link</span><span class="o">:</span><span class="w"> </span><span class="s2">&quot;http://standards.iso.org/iso/19139/resources/gmxCodelists.xml#MD_CharacterSetCode&quot;</span>
 </span><span id="__span-1-6"><a id="__codelineno-1-6" name="__codelineno-1-6" href="#__codelineno-1-6"></a><span class="p">}]</span>
 </span></code></pre></div>
-<p>So if using <code>xt</code> in a facet, use <code>cl_characterSet.default</code> with this new version.</p>
+<p>So if using <code>codelist_characterSet_text</code> in a facet, use <code>cl_characterSet.default</code> with this new version.</p>
 <h3 id="thesaurus">Thesaurus</h3>
-<p>The <code>ds</code> field is now only used for rendering (not for query) to limit the total number of field and avoid some errors on large catalogues.</p>
-<p>Use the per thesaurus fields which were named <code>thesaurus_geonetwork+external/local+type+thesaurusid</code> and are now <code>id</code>. The field is also an object composed of:</p>
+<p>The <code>allKeywords</code> field is now only used for rendering (not for query) to limit the total number of field and avoid some errors on large catalogues.</p>
+<p>Use the per thesaurus fields, which were named <code>thesaurus_geonetwork+external/local+type+thesaurusid</code> and are now <code>th_thesaurusid</code>. The field is also an object composed of:</p>
 <div class="language-js highlight"><pre><span></span><code><span id="__span-2-1"><a id="__codelineno-2-1" name="__codelineno-2-1" href="#__codelineno-2-1"></a><span class="nx">thesaurus_geonetworkthesaurusexternalthemeeeatopics</span><span class="o">:</span><span class="w"> </span><span class="p">[</span>
 </span><span id="__span-2-2"><a id="__codelineno-2-2" name="__codelineno-2-2" href="#__codelineno-2-2"></a><span class="w">  </span><span class="s2">&quot;Land use&quot;</span><span class="p">,</span>
 </span><span id="__span-2-3"><a id="__codelineno-2-3" name="__codelineno-2-3" href="#__codelineno-2-3"></a><span class="w">  </span><span class="s2">&quot;http://www.eea.europa.eu/portal_vocabularies/themes/landuse&quot;</span><span class="p">,</span>
@@ -2572,9 +2572,9 @@ <h3 id="thesaurus">Thesaurus</h3>
 </span><span id="__span-3-10"><a id="__codelineno-3-10" name="__codelineno-3-10" href="#__codelineno-3-10"></a><span class="p">}</span>
 </span></code></pre></div>
 <h3 id="topic-category">Topic category</h3>
-<p><code>ic</code> is renamed to <code>ic</code> and has the same structure as a codelist.</p>
+<p><code>topic</code> is renamed to <code>cl_topic</code> and has the same structure as a codelist.</p>
 <h3 id="geotag">GeoTag</h3>
-<p><code>ag</code> is now stored in the <code>template field for keyword types](https://github.com/geonetwork/core-geonetwork/pull/5243) ie. [keywordType-place</code></p>
+<p><code>geotag</code> is now stored in the <a href="https://github.com/geonetwork/core-geonetwork/pull/5243">template field for keyword types</a> ie. <code>keywordType-place</code></p>
 <p>For more details check <a href="../../../customizing-application/configuring-search-fields/">Configuring search fields</a> and <a href="../../../customizing-application/configuring-faceted-search/">Configuring faceted search</a>.</p>
 <h2 id="main-changes-in-version-402">Main changes in version 4.0.2</h2>
 <ul>