Configuration du système

La plupart des paramètres de configuration du système peuvent être modifiés par les utilisateurs administrateurs à l’aide de l’interface Web dans `` Console d’administration``> `` Paramètres``.

Important

La configuration de ces paramètres est essentielle pour le catalogue dans un contexte opérationnel. Une mauvaise compréhension de certains paramètres peut provoquer des dysfonctionnements imprévus du système. Par exemple, les téléchargements peuvent ne pas être correctement traités ou la collecte de métadonnées à partir d’autres serveurs peut ne pas fonctionner.

../../_images/settings.png

Étant donné que le formulaire de configuration est long, le bouton “Enregistrer” est répété entre les sections et sauvegardera tous les paramètres.

Description du Catalogue

  • Nom du catalogue Le nom du nœud. Informations qui aident à identifier le catalogue pour un utilisateur humain. Le nom est affiché sur la bannière, dans le CSW GetCapabilities.

  • Identifiant du catalogue Un identificateur universellement unique (uuid) qui distingue votre catalogue de tout autre catalogue. C’est un identifiant unique pour votre catalogue et il vaut mieux le laisser comme uuid. Il sera utilisé par harvester en utilisant le protocole GeoNetwork pour identifier le catalogue source.

  • Organisation L’organisation à laquelle appartient le nœud. Encore une fois, il s’agit d’informations qui aident à identifier le catalogue pour un utilisateur humain.

  • 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.

Catalogue

  • Version La version du catalogue (en lecture seule, version de la base de données)

  • Version mineure Version mineure du catalogue (en lecture seule, version de la base de données)

Serveur de catalogue

  • Hôte Nom ou adresse IP du nœud (sans http: //). Par exemple, c’est utilisé lors de l’édition des métadonnées pour créer des liens de ressources et lors du retour des Capabilities du serveur lors d’une requête CSW.

  • Si votre noeud est accessible au public depuis Internet, vous devez utiliser le nom de domaine.

  • Si votre nœud est caché dans votre réseau privé et que vous avez un pare-feu ou un serveur Web qui redirige les demandes entrantes vers le nœud, vous devez entrer l’adresse publique du pare-feu ou du serveur Web. Une configuration typique consiste à avoir un serveur Web Apache sur l’adresse A qui est accessible au public et redirige les demandes vers un serveur Tomcat sur une adresse privée B. Dans ce cas, vous devez entrer A dans le paramètre hôte.

  • Port Le numéro de port du serveur (généralement 80 ou 8080). Si vous utilisez HTTP, réglez-le sur 80.

  • Protocole préféré Défini le protocole pour accéder au catalogue. Le protocole HTTP utilisé pour accéder au serveur. Le choix de http signifie que toute communication avec le catalogue sera visible par toute personne captant le protocole. Comme cela inclut les noms d’utilisateur et les mots de passe, cela n’est pas sécurisé. Choisir https signifie que toute communication avec le catalogue sera cryptée et donc beaucoup plus difficile à décoder en cas d’interception.

  • ** Port sécurisé ** Le numéro de port sécurisé.

  • Niveau de journalisation Définir le niveau de journalisation de l’application. Après modification, le journal peut être vérifié dans la section Statistiques & status sous Activité.

../../_images/log-view.png

Paramètres de l’intranet

Un besoin courant pour une organisation est de discriminer automatiquement les utilisateurs internes anonymes qui accèdent au nœud à partir d’une organisation (Intranet) et les utilisateurs externes anonymes d’Internet. Le catalogue définit les utilisateurs anonymes de l’intérieur de l’organisation comme appartenant au groupe Intranet, tandis que les utilisateurs anonymes de l’extérieur de l’organisation sont définis par le groupe Tous. Pour distinguer automatiquement les utilisateurs appartenant au groupe Intranet, vous devez indiquer au catalogue l’adresse IP intranet et le masque de réseau.

  • Masque de réseau Le masque de réseau intranet (par exemple 255.255.255.0).

  • Réseau* L’adresse intranet sous forme IP (par exemple, 147.109.100.0).

Z39.50

  • Activer le serveur Z39.50 Activer le serveur Z39.50. Redémarrez le catalogue pour activer cette modification.

  • ** Port ** Modifier le port d’écoute Z39.50. Redémarrez le catalogue pour activer cette modification.

Serveur proxy

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.

  • Utiliser un proxy Activer le proxy dans le cas où le catalogue est derrière un proxy et doit l’utiliser pour accéder à des ressources distantes.

  • Hôte proxy L’adresse IP ou le nom du proxy

  • Port Le port proxy

  • Nom d’utilisateur du proxy Le nom d’utilisateur

  • Mot de passe de l’utilisateur proxy Mot de passe de l’utilisateur

  • *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.

Des paramètres proxy pour la JVM (Java Virtual Machine) pourraient être nécessaires à la configuration du proxy pour tous les accès à distance.

Commentaire

Un courriel peut être envoyé par le catalogue.

  • vous utilisez le système d’inscription d’utilisateurs externes

  • you are using the metadata status workflow (See Life cycle)

  • a file uploaded with a metadata record is downloaded and notify privilege is selected

Cette section permet de configurer le serveur de mails à utiliser.

  • 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.

CSW

See Configuration du CSW.

Shibboleth

See Configuration de Shibboleth.

Inscription d’utilisateurs externes

Enable the self registration form. See User Self-Registration.

system/userFeedback

Obsolète depuis la version 3.0.0.

Évaluation des métadonnées

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.

Download Service

The metadata editor supports uploading one or more files that can be stored with the metadata record. When such a record is displayed in the search results, a “Download” button is provided which will allow the user to select which file they want to download. This option group determines how that download will occur.

  • Use GeoNetwork simple file download service Clicking on any file stored with the metadata record will deliver that file directly to the user via the browser.

  • Use GeoNetwork disclaimer and constraints service Clicking on any file stored with the metadata record will deliver a zip archive to the user (via the browser) that contains the data file, the metadata record itself and a summary of the resource constraint metadata as an html document. In addition, the user will need to provide some details (name, organisation, email and optional comment) and view the resource constraints before they can download the zip archive.

Enregistrement des fiches

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.

Search Statistics

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.

Optimisation de l’index

Configuration settings in this group determine when the Lucene Index Optimizer is run. By default, this takes place at midnight each day. With recent upgrades to Lucene, particularly Lucene 3.6.1, the optimizer is becoming less useful, so this configuration group will very likely be removed in future versions.

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.

Directive INSPIRE

See Configuring for the INSPIRE Directive.

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:

  • 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:

    <gmd:transferOptions>
        <gmd:MD_DigitalTransferOptions>
          <gmd:onLine>
            <gmd:CI_OnlineResource>
              <gmd:linkage>
                <gmd:URL>http://geodata.nationaalgeoregister.nl/atom/index.xml</gmd:URL>
              </gmd:linkage>
              <gmd:protocol>
                <gco:CharacterString>INSPIRE Atom</gco:CharacterString>
              </gmd:protocol>
            </gmd:CI_OnlineResource>
          </gmd:onLine>
        </gmd:MD_DigitalTransferOptions>
      </gmd:transferOptions>
    

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:

<link rel="search" href="http://SERVER/geonetwork/opensearch/eng/{uuid}/OpenSearchDescription.xml"
type="application/opensearchdescription+xml" title="Open Search document for INSPIRE Download service"/>

The INSPIRE Atom/OpenSearch implementation can be verified with the Atom tests in Esdin Test Framework (http://elfproject.eu/documentation/geotool/etf) or INSPIRE metadata validator (http://inspire-geoportal.ec.europa.eu/validator2).

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.

Multilingual Settings

Options in this group determine how GeoNetwork will search metadata in multiple languages.

Enable auto-detecting search request language: If this option is selected, GeoNetwork will analyse the search query and attempt to detect the language that is used before defaulting to the GUI language.

Search results in requested language sorted on top: If this option is selected, a sort clause will be added to each query to ensure that results in the current language are always sorted on top. This is different from increasing priority of the language in that it overrides the relevance of the result. For example, if a german result has very high relevance but the search language is french then the french results will all come before the german result.

Search only in requested language The options in this section determines how documents are sorted/prioritised relative to the language in the document compared to the search language.

  • All documents in all languages (No preferences) - The search language is ignored and will have no effect on the ordering of the results

  • Prefer documents with translations requested language - Documents with a translation in the search language (anywhere in the document) will be prioritized over documents without any elements in the search language

  • Prefer documents whose language is the requested language - Documents that are the same language as the search language (ie. the documents that are specified as being in the same language as the search language) are prioritized over documents that are not.

  • Translations in requested language - The search results will only contain documents that have some translations in the search language.

  • Document language is the requested language - The search results will contain documents whose metadata language is specified as being the in search language

Metadata Views

Options in this section enable/disable metadata element groups in the metadata editor/viewer.

Enable simple view: The simple view in the metadata editor/viewer: - removes much of the hierarchy from nested metadata records (such as ISO19115/19139) - will not let the user add metadata elements that are not already in the metadata record It is intended to provide a flat, simple view of the metadata record. A disadvantage of the simple view is that some of the context information supplied by the nesting in the metadata record is lost. Enable ISO view: The ISO19115/19139 metadata standard defines three groups of elements: - Minimum: those elements that are mandatory - Core: the elements that should be present in any metadata record describing a geographic dataset - All: all the elements Enable INSPIRE view: Enables the metadata element groups defined in the EU INSPIRE directive. Enable XML view: This is a raw text edit view of the XML record. You can disable this if (for example), you don’t want inexperienced users to be confused by the XML presentation provided by this view.

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.

Moissonnage

Allow editing on harvested records: Enables/Disables editing of harvested records in the catalogue. By default, harvested records cannot be edited.