Co-authored-by: archaeogeek <jo.k.cook@gmail.com>

Instead of having display above facets true/false options, user can now set the map placement with:
* results
* facets
* or not displayed.

Follow geonetwork/core-geonetwork#7007

The target/geonetwork folder contains the font awesome update but not the WAR due to packagingExcludes.

Currently HTML head description is set to an empty value. Google is
indexing the cookie warning in GeoNetwork case when no HTML head is found (probably because it is the first HTML text content found).

Use the service metadata configured for the main node (see admin >
settings > record to use for GetCapabilities) and same for portal.

If no service metadata record configured, default title and description
to node name (or site name for the main portal).

Follow up of:
* geonetwork/core-geonetwork@611be2a
* geonetwork/core-geonetwork#4758

…d (#7094)

* Display footer rss endpoint(s) when OGC API Records service is enabled

* Update rss endpoint in page head section

* Update rss opensearch endpoint in page head section

---------

Co-authored-by: François Prunayre <fx.prunayre@gmail.com>

Follow up of geonetwork/core-geonetwork#6954

Change `hibernate.hbm2ddl.auto` to `update` that was the value previously set when using `generateDdl=true` in Spring JPA.

* Workflow / Clarity each steps in the workflow and simplify extension

Define a configuration to define on a per profile basis which workflow
steps can be followed by other steps.

This makes easier to read the workflow menu setup and allows to extend
it more easily when adding new workflow steps.

* (core) Prevent approval of invalid records from editor if settings

* Workflow / Report status change type

Can be
* UPDATED
* UNCHANGED
* DELETED

Add placeholder method to apply side effect or check if user can
actually trigger the requested status change.

Co-authored-by: CMath04 <chaussier.mathieu@gmail.com>

* Refactored deletion/backup procedure, introduced purge instead

* Workflow / API / Return if status was modified or not. This can be useful client side to trigger action when the workflow did nothing or removed a record.

* Workflow / More precise error reporting so that user knows what to do exactly.

* Formatting.

* Formatting.

* Workflow / Avoid double validation on terminating editing session. Reindex record if status change

* Javadoc.

---------

Co-authored-by: CMath04 <chaussier.mathieu@gmail.com>
Co-authored-by: Joachim Nielandt <joachim.nielandt@vlaanderen.be>

…e to DRAFT when doing a rejection, not when creating a working copy

Follow-up of geonetwork/core-geonetwork#7094.

The targetUri property can be configured using multiple methods, not only as init parameter
in web.xml servlet's config but also as environment variable, system property or config.properties
entry. This change saves the targetUri value in a ServletContext attribute so it can be retrieved
from other servlets to check its value. Changed the value of <load-on-startup> servlet property
to init the attribute on server start.

Fix Sonarcloud warnings.

Follow up of geonetwork/core-geonetwork#5006

Test.
* enable workflow
* create a record
* publish (and approve)
* edit will create a draft
* cancel
* open record view
http://localhost:8080/srv/eng/catalog.search#/metadata/5692d7a3-949e-4f27-8fe0-0fa9efd3584e
* open draft view (even if not displayed in record view)
http://localhost:8080/srv/eng/catalog.search#/metadraf/5692d7a3-949e-4f27-8fe0-0fa9efd3584e
show a records which does not exist in db anymore (due to cancel) but was not properly removed from index.

Also note that if you save the new draft, the cancel will not remove it (looks to be expected in 5006).

…iguration of the online resources. Fixes #7103

…r information.

This allows to display a sort by a field in ascending and descending order, for example the metadata title

…pattern

… templates

* Fix selection / filter Only my records

* Fix selection / filter Only my records: use setting to enable Only my records in the editor application, not in the search application

…h the case where no port is set in the settings manager

… value

… that we can see the real error in the logs. (#7119)

…alues

* Allow multiple request matchers to decide if require CSRF token
* Fix a problem with the Keycloak configuration that was making the server
to require CSRF tokens for GN URLs that shouldn't be protected by CSRF.
To do this, now the GeonetworkCsrfSecurityRequestMatcher allows to be configured
with additional RequestMatchers, for example the KeycloakCsrfRequestMatcher.
If Keycloak security is enabled, then the KeycloakCsrfRequestMatcher is added to the
original GeoNetwork patterns listed in `config-security-core.xml`

The link for 'Installing from source code' is broken.  The label of Maintainer Guide is also incorrect and should be Installation Guide.

…ustom status (#7104)

* Core cleanup translation.

* Workflow / Remove magic numbers in label and avoid issue when using
custom status.

The status workflow index field contains 2 numbers concatenated - status of the record + status of the draft.
If using custom status, the concatenation of the number can match other status number eg. 111 can be 1+11 or 11+1 so we can't always get a label from that value.
Use status name instead of ids and rely on db translation as much as
possible (there is still room for improvements when custom status are
used).

Co-authored-by: Joachim Nielandt <joachim.nielandt@vlaanderen.be>

* Workflow / Add configuration for the list of status for which to start a
draft.

Co-authored-by: Joachim Nielandt <joachim.nielandt@vlaanderen.be>

* Workflow / Better build label.

Co-authored-by: Joachim Nielandt <joachim.nielandt@vlaanderen.be>

* Workflow / Record view / Use db translations.

* Workflow / Label improvement.

---------

Co-authored-by: Joachim Nielandt <joachim.nielandt@vlaanderen.be>

…abel in German (#7122)

…se insensitive and ignore accents

Replace geonetwork/core-geonetwork#7134 and follow up of geonetwork/core-geonetwork#7104

…ved (#7074)

When a metadata is published / un-published it can be configured a mail notification.

When the metadata workflow is enabled, published metadata can be edited and re-approved. 
This change request expands the email notifications in this case, to send an email to let you know 
that a published metadata has been re-approved, with a new version published.

Related to #6457

---------

Co-authored-by: Juan Luis Rodríguez <juanluisrp@gmail.com>

…ual URL

Avoid error on multilingual URL. Can be tested with https://ecoscope.svc.groupcls.com/geonetwork/srv/api/records/19b09201-c9a5-42e7-ac18-8e48c95dec38/formatters/xml

…nd labels (#7076)

* UI / Language picker / Display all entries on focus. Search by code and english.

* Prettier.

* Map / Layer manager / Add support for multilingual layer title.

Metadata may be multilingual and provide multilingual layer name in the
online source description field. GetCapabilities document do not provide
multilingual support, so this adds the possibility to translate layer
name in maps.

A multilingual description in a link:

```xml
<gmd:onLine>
  <gmd:CI_OnlineResource>
    <gmd:linkage>
      <gmd:URL>https://data.apps.fao.org/map/gsrv/gsrv1/geonetwork/ows?SERVICE=WMS&amp;</gmd:URL>
    </gmd:linkage>
    <gmd:protocol>
      <gmx:MimeFileType type="">OGC:WMS</gmx:MimeFileType>
    </gmd:protocol>
    <gmd:name xsi:type="gmd:PT_FreeText_PropertyType">
      <gco:CharacterString>geonetwork:basins_296</gco:CharacterString>
      <gmd:PT_FreeText>
        <gmd:textGroup>
          <gmd:LocalisedCharacterString locale="#EN">geonetwork:basins_296</gmd:LocalisedCharacterString>
        </gmd:textGroup>
        <gmd:textGroup>
          <gmd:LocalisedCharacterString locale="#FR" />
        </gmd:textGroup>
      </gmd:PT_FreeText>
    </gmd:name>
    <gmd:description xsi:type="gmd:PT_FreeText_PropertyType">
      <gco:CharacterString>Hydrological basins in Africa</gco:CharacterString>
      <gmd:PT_FreeText>
        <gmd:textGroup>
          <gmd:LocalisedCharacterString locale="#EN">Hydrological basins in Africa</gmd:LocalisedCharacterString>
        </gmd:textGroup>
        <gmd:textGroup>
          <gmd:LocalisedCharacterString locale="#FR">Bassins versants en Afrique</gmd:LocalisedCharacterString>
        </gmd:textGroup>
      </gmd:PT_FreeText>
    </gmd:description>
  </gmd:CI_OnlineResource>
</gmd:onLine>
```

The description is retrieved from the metadata on load from the metadata
UUID which is attached to the layer (and saved in the OWS context
extension of the layer) using the service URL and the layer name.

This also allows to override layer name when a group of layer (eg.
`a,b,c`) is used in the online source name.

* Map / When loading a map, switch to layer tool panel.

* Map / Layer manager / Add support for multilingual layer title / Layer search.

* Map / Layer manager / Add support for multilingual layer title / Layer filter.

* Remove openTool after map load.

Configuration done in geonetwork/core-geonetwork#7126

* Map / Background layer / Fix active layer on load.

Test:
* Open the map
* Reload page
* Active background is not enabled.

This was related to the fact that the search map is also affecting bgLayers.

Only the main map viewer is defining the bgLayers which is used for the base switcher directive.
In case of the context has no active background, use the first one (and log a warning).
Reset default map :
* may fail if no context defined. Add a fallback to the default one (and log a warning).
* tried to use the map layer config if no context defined as it was ignored (but not working - require more work or removal of those unused ? settings)

* Map / Avoid JSON parse error on context having layer with filter. Clear
queue on context load.

Context layer can contain a JSON extension which could be formatted and
XML formatting may add extra space which needs to be clean up for proper
JSON string:

```xml
       <ows-context:Layer name="surval_parametre_point" group="/Human Activities" hidden="false" opacity="1"
                           showLayerInfo="true">
            <ows:Title>Surval données par paramètre (point)</ows:Title>
            <ows-context:Server service="urn:ogc:serviceType:WMS" version="1.3.0">
                <ows-context:OnlineResource xlink:href="https://sextant.ifremer.fr/services/wms/environnement_marin"/>
            </ows-context:Server>
            <ows-context:Extension>{"uuid":"cf5048f6-5bbf-4e44-ba74-e6f429af51ea","label":"Surval données par paramètre
                (point)","filters":{"qParams":{"ft_LIEU_LIBELLE_s":{"type":"terms","values":{"001-P-003 - Zuydcoote
                filière":true}}}},"wfsUrl":"https://sextant.ifremer.fr/services/wfs/environnement_marin"}
            </ows-context:Extension>
        </ows-context:Layer>
```

Clear map queue on load - may have side effect when loading differents
maps quickly.

Avoid JS error if server layer is not defined (which should not be the
case unless custom context with new layer types was created).

* Update OwsContextDirective.js

* Map / Add option to configure default active tool and default active tool after map load.

* Update OwsContextService.js

* missed file in geonetwork/core-geonetwork#6494

* jose feedback

Co-authored-by: Jose García <josegar74@gmail.com>

---------

Co-authored-by: david.blasby <david.blasby@geocat.net>
Co-authored-by: Jose García <josegar74@gmail.com>

* Support customising the metadata publication options

* Support customising the metadata publication options - javascript cleanup and support of additionalPublications information in the UI

* Support customising the metadata publication options - Fix batch publication UI

* Support customising the metadata publication options - rename endpoint to retrieve the publication options

* Support customising the metadata publication options - code refactor for to check if a metadata is published in a group

* Support customising the metadata publication options - use publication type in batch publication / un-publication

* Support customising the metadata publication options - fix integration tests

* Move tooltip from reccusive input field to the label field

* description field multiple tool tips

* multi lang field tool tips

* Revert "multi lang field tool tips"

This reverts commit f54e6451

* Move all tool tips to label level

…ords (#7170)

When using template field, the label may not be retrieved from translation files.

eg. configuration
```xml
 <section>

          <field name="sextant-temporalRangeSection"
                 templateModeOnly="true"
                 notDisplayedIfMissing="true"
                 xpath="/mdb:MD_Metadata/mdb:identificationInfo/*/mri:extent/*/gex:temporalElement">
            <template>
              <values>
                <key label="beginPosition"
                     xpath="gex:EX_TemporalExtent/mri:extent/gml:TimePeriod/*/gml:beginPosition"
                     use="gn-date-picker"
                     tooltip="mri:extent|gex:EX_TemporalExtent">
                  <directiveAttributes data-tag-name="gml:beginPosition"/>
                </key>
                <key label="endPosition"
                     xpath="gex:EX_TemporalExtent/mri:extent/gml:TimePeriod/*/gml:endPosition"
                     use="gn-date-picker"
                     tooltip="mri:extent|gex:EX_TemporalExtent"
                >
                  <directiveAttributes
                    data-tag-name="gml:endPosition"
                    data-indeterminate-position="eval#gex:EX_TemporalExtent/mri:extent/gml:TimePeriod/*/gml:endPosition/@indeterminatePosition"/>
                </key>
              </values>
              <snippet>
                <gex:temporalElement>
                  <gex:EX_TemporalExtent>
                    <gex:extent>
                      <gml:TimePeriod gml:id="">
                        {{beginPosition}}
                        {{endPosition}}
                      </gml:TimePeriod>
                    </gex:extent>
                  </gex:EX_TemporalExtent>
                </gex:temporalElement>
              </snippet>
            </template>
          </field>
```

Translation in loc/eng/strings.xml
```xml
  <sextant-temporalRangeSection>Temporal extent</sextant-temporalRangeSection>
````

…epresentation namespace (#7172)

Backport of ISO-TC211/XML#228

Only define the language id once it is defined. 

If not, we can have wrong multilingual widget.

Test:
* create new 115-3 record
* set default language to spanish
* add other language to english
* set title in both languages
* add other language without lang code (it will get the EN id) - and editor do not display title properly.
 

Set language id to empty as far as lang code is not set.

When updating a metadata record using CSW, revision date could have invalid date type.
GeoNetwork always write revision date as dateTime type (to properly order records by change date) but if using the API, user insert records using date type for dates, the wrong type may be introduced.

SONAR was complaining about possible SQL Injections.

2 strategies here:
*Using prepared statements instead of string concatenation.
* Using //NOSONAR where concat seems to be safely

Co-authored-by: Thomas Junk <thomas.junk@intevation.de>

…nstead

* CSW / DCAT output / Fix for multilingual records

RDF about creation on Distribution class can fail on some multilingual records.

eg https://sextant.ifremer.fr/geonetwork/srv/api/records/8c8c52b3-4b00-4d11-9dad-37edf6395d82/formatters/xml

* Update tpl-rdf.xsl

Clarify link pointing to keyword URL with an info icon and a better label.

* Test / Fix for default language.

Follow up of geonetwork/core-geonetwork#7169.

* Test / Fix for default language.

    Follow up of geonetwork/core-geonetwork#7169.

---------

Co-authored-by: Jose García <josegar74@gmail.com>

Add the possibility to configure Kibana URL using env variables

eg.
```
 -Dgeonetwork.HttpDashboardProxy.targetUri=http://kibana:5601

```
Follow up of geonetwork/core-geonetwork#6356

…(#7153)

* Standard / Translations / Load contact role codelist from the schema

Make more consistent translations for contact role which are defined in ISO schema. If a user override or extend contact role, then it will be automatically available in editor and angular app.

* Contact / Role / Rely on ISO schema for translations

Fix geonetwork/core-geonetwork#7048

…goutSuccessHandler and BaseMetadataManager to get around compilation error about not referring to a non-static method from a static context

Co-authored-by: Jose García <josegar74@gmail.com>

…MetadataManager.java

Co-authored-by: Jose García <josegar74@gmail.com>

…outSuccessHandler.java

Co-authored-by: Jose García <josegar74@gmail.com>

…name

* Pages / Top toolbar / Add support for submenu

Sample configuration:

```
topCustomMenu: [
              "page1",
              { "Quick search": ["search1", "search2"] },
              { Dashboards: ["page2", "page3"] },
              { "About us": ["page1"] }
            ]
```

* Pages / API / Fix label update.

* Pages / API / Increase link column length. Page with a long link was not saved.

* UI / Toolbar / Create directive for each menu (to make them easier to reorder). Remove non accessible toolbar.

* UI / Move top toolbar to a directive. Move pages utility in a service.

* UI / Toolbar / Add support for custom toolbar.

* UI / Toolbar / Default config.

* UI / Toolbar / By default list all pages (as before).

* Update web-ui/src/main/resources/catalog/components/toolbar/ToolbarDirective.js

Co-authored-by: Jose García <josegar74@gmail.com>

* Update web-ui/src/main/resources/catalog/components/toolbar/ToolbarModule.js

Co-authored-by: Jose García <josegar74@gmail.com>

* Pages / Configuration is JSON.

* Pages / Move dependency to top to have it available for all apps.

* UI config / Fix JSON edit of array type.

---------

Co-authored-by: Jose García <josegar74@gmail.com>

…-to-map

External map viewer / Fix add WFS to map empty variable

…to #6970 (#7196)

…scribe service (#7189)

Code optimisations to retrieve the atom feeds. Tested in 3.12.x and somehow retrieveDatasetUuidFromIdentifier 
causes that the call to findByMetadataId takes long time. In main doesn't seem so, maybe due to the 
JPA/Hibernate version.

The change does some cleanup of the code and avoids to retrieve the same information several times.

…, publishes the draft copy. Fixes #5556 (#5557)

* Metadata workflow - publish an approved record with a draft copy, publishes the draft copy. Fixes #5556

* Metadata workflow - publish an approved record with a draft copy, publishes the draft copy - update bulk publish. Fixes #5556

…version, not to the working copy version.

…ort-fix

Added some logic into JeevesNodeAwareLogoutSuccessHandler to deal with the case where no port is set in the settings manager

Follow up of geonetwork/core-geonetwork#6770

When requesting keywords in ISO formats, populate the thesaurus title
using the proper multilingual title based on record language.

Test:
* create a local thesaurus with a title in UI language
* add keywords
* create a metadata record and add those keywords = title is wrong.

Sample API call: http://localhost:8080/srv/api/registries/vocabularies/keyword?thesaurus=local.theme.demo&id=https:%2F%2Fregistry.geonetwork-opensource.org%2Ftheme%2Fdemo%2387aa1156-b91e-405c-92c3-5c7063a5ce68&transformation=to-iso19115-3.2018-keyword&langMap=%7B%22fre%22:%22%23FR%22%7D&lang=fre&textgroupOnly=false

If thesaurus is defined in config-editor use this config.
If not, check in all catalogue thesaurus and find a match by key (which is always available in GeoNetwork metadata records) and then fallback with a match on the title.

…uplication (#7200)

* Additional code refactor related to #7124 to avoid code duplication

* Update core/src/main/java/org/fao/geonet/kernel/setting/SettingManager.java

Co-authored-by: François Prunayre <fx.prunayre@gmail.com>

---------

Co-authored-by: François Prunayre <fx.prunayre@gmail.com>

* API / Import record / Overwrite mode improvement.

Currently `OVERWRITE` mode is not really overwriting the record
but remove it (including status, privileges, ...) and then replace it
with the new XML and import parameters.

Users expect that overwrite is only updating the XML of the metadata
record.

Change `OVERWRITE` mode to only update the XML and
add a `REMOVE_AND_REPLACE` mode to keep existing mechanism.

* API / Import record / Overwrite mode not allowed when workflow is enabled.

… grouped by translation

* Static pages / Fix links to load html pages content.

Initialise gnActiveTbItem directive with pageId, page.pageId is not yet available when the directive is initialised.

* Pages / Ensure page is initialized before creating active-tb-item (#79)

* Pages / Ensure page is initialized before creating active-tb-item

* Pages / Add more doc about ui config

---------

Co-authored-by: François Prunayre <fx.prunayre@gmail.com>

Related to geonetwork/core-geonetwork#7207

In ISO19139, `gfc:cardinality` is a multiplicity element with
lower/upper properties. In ISO19115-3, cardinality is a
`CharacterString`.

Store it as text in the index with `lower..upper` value for ISO19139.

Display cardinality next to the type.