[GeoNetwork-users] GeoNetwork 3.10.6 ERDDAP WAF harvesting fails with "Skipping metadata with unknown schema"

Dear all,

I am trying to harvest the native WAF endpoint of an ERDDAP instance from GeoNetwork 3.10.6.
The harvesting finishes without error but in the log file clearly states that no metadata have been imported because of missing schemas:

- - - - - - - -

2022-02-26T12:58:00,907+0000 INFO [ERDDAP] - Starting harvesting of ERDDAP
2022-02-26T12:58:00,907+0000 DEBUG [ERDDAP] - AbstractHarvester login: ownerId = 116
2022-02-26T12:58:01,075+0000 INFO [ERDDAP] - Started harvesting from node : ERDDAP (WebDavHarvester)
2022-02-26T12:58:01,076+0000 INFO [ERDDAP] - WebDav doHarvest start
2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Retrieving remote metadata information for : ERDDAP
2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Scanning resource : https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/
2022-02-26T12:58:01,132+0000 DEBUG [ERDDAP] - Remote files found : 1
2022-02-26T12:58:01,132+0000 INFO [ERDDAP] - Start of alignment for : ERDDAP
2022-02-26T12:58:01,162+0000 DEBUG [ERDDAP] - Getting remote file : https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
2022-02-26T12:58:01,170+0000 DEBUG [ERDDAP] - Record got:
<gmi:MI_Metadata xmlns:gmi="http://www.isotc211.org/2005/gmi&quot; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:xlink="http://www.w3.org/1999/xlink&quot; xmlns:gco="http://www.isotc211.org/2005/gco&quot; xmlns:gmd="http://www.isotc211.org/2005/gmd&quot; xmlns:gmx="http://www.isotc211.org/2005/gmx&quot; xmlns:gml="http://www.opengis.net/gml/3.2&quot; xmlns:gss="http://www.isotc211.org/2005/gss&quot; xmlns:gts="http://www.isotc211.org/2005/gts&quot; xmlns:gsr="http://www.isotc211.org/2005/gsr&quot; xmlns:srv="http://www.isotc211.org/2005/srv&quot; xsi:schemaLocation="https://www.isotc211.org/2005/gmi https://data.noaa.gov/resources/iso19139/schema.xsd&quot;&gt;
   <gmd:fileIdentifier>
     <gco:CharacterString>cnr_ismar_b37f_8e81_db5d</gco:CharacterString>
   </gmd:fileIdentifier>

   ### OMITTED FOR BREVITY ###

</gmi:MI_Metadata>
2022-02-26T12:58:01,172+0000 WARN [ERDDAP] - Skipping metadata with unknown schema. Path is : https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - End of alignment for : ERDDAP
2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - WebDav doHarvest end
2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - Ended harvesting from node : ERDDAP (WebDavHarvester)

- - - - - - - -

Here's the json repsonse to the query to the GeoNetwork API exposing the loaded schemas (https://geonetwork.ve.ismar.cnr.it/geonetwork/doc/api/index.html#/identifiers/getIdentifiers):

- - - - -

[
   {
     "name": "iso19115-3.2018",
     "titles": {
       "en": "Geographic information -- Metadata",
       "fr": "Information géographique -- Métadonnées"
     },
     "descriptions": {
       "en": "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 <http://cnig.gouv.fr/wp-content/uploads/2015/06/titellus_fx_prunayre_iso19115-3_inspire2015.pdf&gt;\`\_ This standard is maintained on https://github.com/metadata101/iso19115-3.2018 and is available by default in GeoNetwork 3.8+. The TC211 is maintaining the XSD for this standard on https://github.com/ISO-TC211/XML. Example of catalogues using this standard: - `Metawal - Catalogue pour l'information géographique de Wallonie <http://metawal.wallonie.be/&gt;\`\_ 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. .. figure:: img/metawal-tramedesaxes.png - `Sextant - Checkpoints <https://sextant.ifremer.fr/&gt;\`\_ is using ISO19115-3 for data quality description of Specification / Products and upstream data. .. figure:: img/sextant-checkpoint.png",
       "fr": "L’objectif de l’ISO 19115 est de fournir un modèle destiné à décrire des informations ou des ressources pouvant avoir des étendues géographiques. Cette partie de l’ISO 19115 est destinée à être utilisée, entre autres, par des analystes de systèmes d’informations, des planificateurs de programmes et des développeurs de systèmes d’informations, dans le but de définir des principes de base et des exigences permettant d’établir une description normalisée des ressources d’informations. Cette partie de l’ISO 19115 définit les éléments de métadonnées, leurs propriétés et les relations entre les éléments et établit un ensemble commun de terminologies, de définitions et de procédures d’extension concernant les métadonnées.  Bien que cette partie de l’ISO 19115 ait pour but principal de décrire les informations numériques qui ont une étendue géographique, elle peut être utilisée pour décrire tous les types de ressources, y compris les documents textuels, les initiatives, les logiciels, les informations non géographiques, les spécifications de produit et les entrepôts de données, c’est-à-dire qu’elle peut même être utilisée pour décrire des ressources d’informations n’ayant aucune étendue géographique. Certains domaines ont leurs propres normes de métadonnées, telles que celles du Dublin Core pour les bibliothèques. Si besoin, des profils de telles normes et de cette partie de l’ISO 19115 pourraient être développés pour créer un Schéma Communautaire. Ce schéma est également composé des normes : - ISO19110 pour les modèles de données - ISO19115-2 pour l'imagerie - ISO19157 pour la qualité des données"
     },
     "standardUrl": "http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32579&quot;,
     "targetNamespace": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
     "namespaces": {
       "dqm": "http://standards.iso.org/iso/19157/-2/dqm/1.0&quot;,
       "gml": "http://www.opengis.net/gml/3.2&quot;,
       "fcc": "http://standards.iso.org/iso/19110/fcc/1.0&quot;,
       "mmi": "http://standards.iso.org/iso/19115/-3/mmi/1.0&quot;,
       "mcc": "http://standards.iso.org/iso/19115/-3/mcc/1.0&quot;,
       "msr": "http://standards.iso.org/iso/19115/-3/msr/2.0&quot;,
       "mac": "http://standards.iso.org/iso/19115/-3/mac/2.0&quot;,
       "cit": "http://standards.iso.org/iso/19115/-3/cit/2.0&quot;,
       "gmw": "http://standards.iso.org/iso/19115/-3/gmw/1.0&quot;,
       "gco": "http://standards.iso.org/iso/19115/-3/gco/1.0&quot;,
       "reg": "http://standards.iso.org/iso/19135/-2/reg/1.0&quot;,
       "xml": "http://www.w3.org/XML/1998/namespace&quot;,
       "cat": "http://standards.iso.org/iso/19115/-3/cat/1.0&quot;,
       "mco": "http://standards.iso.org/iso/19115/-3/mco/1.0&quot;,
       "lan": "http://standards.iso.org/iso/19115/-3/lan/1.0&quot;,
       "gex": "http://standards.iso.org/iso/19115/-3/gex/1.0&quot;,
       "gcx": "http://standards.iso.org/iso/19115/-3/gcx/1.0&quot;,
       "mas": "http://standards.iso.org/iso/19115/-3/mas/1.0&quot;,
       "mrd": "http://standards.iso.org/iso/19115/-3/mrd/1.0&quot;,
       "mrc": "http://standards.iso.org/iso/19115/-3/mrc/2.0&quot;,
       "mpc": "http://standards.iso.org/iso/19115/-3/mpc/1.0&quot;,
       "mex": "http://standards.iso.org/iso/19115/-3/mex/1.0&quot;,
       "pre": "http://standards.iso.org/iso/19135/-2/pre/1.0&quot;,
       "mri": "http://standards.iso.org/iso/19115/-3/mri/1.0&quot;,
       "gfc": "http://standards.iso.org/iso/19110/gfc/1.1&quot;,
       "mrl": "http://standards.iso.org/iso/19115/-3/mrl/2.0&quot;,
       "mdb": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
       "mrs": "http://standards.iso.org/iso/19115/-3/mrs/1.0&quot;,
       "srv": "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;,
       "dqc": "http://standards.iso.org/iso/19157/-2/dqc/1.0&quot;,
       "mdq": "http://standards.iso.org/iso/19157/-2/mdq/1.0&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": [
       "schematron-rules-inspire.xsl",
       "schematron-rules-iso.xsl"
     ],
     "version": "1.0",
     "appMinorVersionSupported": "3.5.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "iso19139",
     "titles": {
       "en": "Geographic information -- Metadata (iso19139:2007)",
       "fr": "Information géographique -- Métadonnées (iso19139:2007)"
     },
     "descriptions": {
       "en": "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."
     },
     "standardUrl": "https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798\\n ",
     "targetNamespace": "http://www.isotc211.org/2005/gmd&quot;,
     "namespaces": {
       "gco": "http://www.isotc211.org/2005/gco&quot;,
       "gmx": "http://www.isotc211.org/2005/gmx&quot;,
       "xml": "http://www.w3.org/XML/1998/namespace&quot;,
       "gss": "http://www.isotc211.org/2005/gss&quot;,
       "srv": "http://www.isotc211.org/2005/srv&quot;,
       "gts": "http://www.isotc211.org/2005/gts&quot;,
       "gsr": "http://www.isotc211.org/2005/gsr&quot;,
       "gml": "http://www.opengis.net/gml/3.2&quot;,
       "gmd": "http://www.isotc211.org/2005/gmd&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": [
       "schematron-rules-url-check.xsl",
       "schematron-rules-inspire-sds.xsl",
       "schematron-rules-geonetwork.xsl",
       "schematron-rules-inspire.xsl",
       "schematron-rules-iso.xsl",
       "schematron-rules-inspire-strict.xsl"
     ],
     "version": "1.0",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "dublin-core",
     "titles": {
       "en": "Dublin core"
     },
     "descriptions": {},
     "standardUrl": "http://dublincore.org/documents/dces/&quot;,
     "targetNamespace": null,
     "namespaces": {
       "": "http://purl.org/dc/dcmitype/&quot;,
       "dct": "http://purl.org/dc/terms/&quot;,
       "xml": "http://www.w3.org/XML/1998/namespace&quot;,
       "dc": "http://purl.org/dc/elements/1.1/&quot;
     },
     "readwriteUUID": false,
     "schematronRules": ,
     "version": "1.0",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "csw-record",
     "titles": {
       "en": "Dublin core (for CSW only)"
     },
     "descriptions": {},
     "standardUrl": null,
     "targetNamespace": "http://www.opengis.net/cat/csw/2.0.2&quot;,
     "namespaces": {
       "dct": "http://purl.org/dc/terms/&quot;,
       "csw": "http://www.opengis.net/cat/csw/2.0.2&quot;,
       "ows": "http://www.opengis.net/ows&quot;,
       "dc": "http://purl.org/dc/elements/1.1/&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": ,
     "version": "2.0.2",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "iso19110",
     "titles": {
       "en": "Geographic information -- Methodology for feature cataloguing",
       "fr": "Information géographique -- Méthodologie de catalogage des entités"
     },
     "descriptions": {},
     "standardUrl": "\n http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965\\n ",
     "targetNamespace": "http://www.isotc211.org/2005/gfc&quot;,
     "namespaces": {
       "": "http://www.isotc211.org/2005/gss&quot;,
       "gco": "http://www.isotc211.org/2005/gco&quot;,
       "gmx": "http://www.isotc211.org/2005/gmx&quot;,
       "gfc": "http://www.isotc211.org/2005/gfc&quot;,
       "gml": "http://www.opengis.net/gml&quot;,
       "gts": "http://www.isotc211.org/2005/gts&quot;,
       "gsr": "http://www.isotc211.org/2005/gsr&quot;,
       "gmd": "http://www.isotc211.org/2005/gmd&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": ,
     "version": "1.0",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": "iso19139"
   }
]

- - - - - - -

Do I have to load the missing schemas on GeoNetwork or do I have to perform some post processing on ERDDAP WAF endpoint in order to let GeoNetwork perform a smooth harvesting?

With Best Regards,
Pierpaolo Culurciello

(attachments)

harvester_webdav_ERDDAP_202202261258.log (54.8 KB)
Geonetwork_metadata_standards.txt (11.7 KB)

Hi Pierpaolo

The metadata starts with this element gmi:MI_Metadata, that doesn't
correspond to any metadata schema bundled in GeoNetwork.

Regards,
Jose García

On Sat, Feb 26, 2022 at 4:53 PM Pierpaolo Culurciello via GeoNetwork-users <
geonetwork-users@lists.sourceforge.net> wrote:

Dear all,

I am trying to harvest the native WAF endpoint of an ERDDAP instance
from GeoNetwork 3.10.6.
The harvesting finishes without error but in the log file clearly
states that no metadata have been imported because of missing schemas:

- - - - - - - -

2022-02-26T12:58:00,907+0000 INFO [ERDDAP] - Starting harvesting of ERDDAP
2022-02-26T12:58:00,907+0000 DEBUG [ERDDAP] - AbstractHarvester login:
ownerId = 116
2022-02-26T12:58:01,075+0000 INFO [ERDDAP] - Started harvesting from
node : ERDDAP (WebDavHarvester)
2022-02-26T12:58:01,076+0000 INFO [ERDDAP] - WebDav doHarvest start
2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Retrieving remote
metadata information for : ERDDAP
2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Scanning resource :
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/
2022-02-26T12:58:01,132+0000 DEBUG [ERDDAP] - Remote files found : 1
2022-02-26T12:58:01,132+0000 INFO [ERDDAP] - Start of alignment for :
ERDDAP
2022-02-26T12:58:01,162+0000 DEBUG [ERDDAP] - Getting remote file :

https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
2022-02-26T12:58:01,170+0000 DEBUG [ERDDAP] - Record got:
<gmi:MI_Metadata xmlns:gmi="http://www.isotc211.org/2005/gmi&quot;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
xmlns:xlink="http://www.w3.org/1999/xlink&quot;
xmlns:gco="http://www.isotc211.org/2005/gco&quot;
xmlns:gmd="http://www.isotc211.org/2005/gmd&quot;
xmlns:gmx="http://www.isotc211.org/2005/gmx&quot;
xmlns:gml="http://www.opengis.net/gml/3.2&quot;
xmlns:gss="http://www.isotc211.org/2005/gss&quot;
xmlns:gts="http://www.isotc211.org/2005/gts&quot;
xmlns:gsr="http://www.isotc211.org/2005/gsr&quot;
xmlns:srv="http://www.isotc211.org/2005/srv&quot;
xsi:schemaLocation="https://www.isotc211.org/2005/gmi
https://data.noaa.gov/resources/iso19139/schema.xsd&quot;&gt;
   <gmd:fileIdentifier>
     <gco:CharacterString>cnr_ismar_b37f_8e81_db5d</gco:CharacterString>
   </gmd:fileIdentifier>

   ### OMITTED FOR BREVITY ###

</gmi:MI_Metadata>
2022-02-26T12:58:01,172+0000 WARN [ERDDAP] - Skipping metadata with
unknown schema. Path is :

https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - End of alignment for : ERDDAP
2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - WebDav doHarvest end
2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - Ended harvesting from
node : ERDDAP (WebDavHarvester)

- - - - - - - -

Here's the json repsonse to the query to the GeoNetwork API exposing
the loaded schemas
(
https://geonetwork.ve.ismar.cnr.it/geonetwork/doc/api/index.html#/identifiers/getIdentifiers
):

- - - - -

[
   {
     "name": "iso19115-3.2018",
     "titles": {
       "en": "Geographic information -- Metadata",
       "fr": "Information géographique -- Métadonnées"
     },
     "descriptions": {
       "en": "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
<
http://cnig.gouv.fr/wp-content/uploads/2015/06/titellus_fx_prunayre_iso19115-3_inspire2015.pdf&gt;\`\_
This standard is maintained on
https://github.com/metadata101/iso19115-3.2018 and is available by
default in GeoNetwork 3.8+. The TC211 is maintaining the XSD for this
standard on https://github.com/ISO-TC211/XML. Example of catalogues using
this standard: - `Metawal - Catalogue pour l'information géographique de
Wallonie <http://metawal.wallonie.be/&gt;\`\_ 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.
.. figure:: img/metawal-tramedesaxes.png - `Sextant - Checkpoints <
https://sextant.ifremer.fr/&gt;\`\_ is using ISO19115-3 for data quality
description of Specification / Products and upstream data. .. figure::
img/sextant-checkpoint.png",
       "fr": "L’objectif de l’ISO 19115 est de fournir un modèle
destiné à décrire des informations ou des ressources pouvant avoir des
étendues géographiques. Cette partie de l’ISO 19115 est destinée à
être utilisée, entre autres, par des analystes de systèmes
d’informations, des planificateurs de programmes et des développeurs
de systèmes d’informations, dans le but de définir des principes de
base et des exigences permettant d’établir une description normalisée
des ressources d’informations. Cette partie de l’ISO 19115 définit les
éléments de métadonnées, leurs propriétés et les relations entre les
éléments et établit un ensemble commun de terminologies, de
définitions et de procédures d’extension concernant les métadonnées. 
Bien que cette partie de l’ISO 19115 ait pour but principal de décrire
les informations numériques qui ont une étendue géographique, elle
peut être utilisée pour décrire tous les types de ressources, y
compris les documents textuels, les initiatives, les logiciels, les
informations non géographiques, les spécifications de produit et les
entrepôts de données, c’est-à-dire qu’elle peut même être utilisée
pour décrire des ressources d’informations n’ayant aucune étendue
géographique. Certains domaines ont leurs propres normes de
métadonnées, telles que celles du Dublin Core pour les bibliothèques.
Si besoin, des profils de telles normes et de cette partie de l’ISO
19115 pourraient être développés pour créer un Schéma Communautaire.
Ce schéma est également composé des normes : - ISO19110 pour les
modèles de données - ISO19115-2 pour l'imagerie - ISO19157 pour la
qualité des données"
     },
     "standardUrl":
"
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32579
",
     "targetNamespace": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
     "namespaces": {
       "dqm": "http://standards.iso.org/iso/19157/-2/dqm/1.0&quot;,
       "gml": "http://www.opengis.net/gml/3.2&quot;,
       "fcc": "http://standards.iso.org/iso/19110/fcc/1.0&quot;,
       "mmi": "http://standards.iso.org/iso/19115/-3/mmi/1.0&quot;,
       "mcc": "http://standards.iso.org/iso/19115/-3/mcc/1.0&quot;,
       "msr": "http://standards.iso.org/iso/19115/-3/msr/2.0&quot;,
       "mac": "http://standards.iso.org/iso/19115/-3/mac/2.0&quot;,
       "cit": "http://standards.iso.org/iso/19115/-3/cit/2.0&quot;,
       "gmw": "http://standards.iso.org/iso/19115/-3/gmw/1.0&quot;,
       "gco": "http://standards.iso.org/iso/19115/-3/gco/1.0&quot;,
       "reg": "http://standards.iso.org/iso/19135/-2/reg/1.0&quot;,
       "xml": "http://www.w3.org/XML/1998/namespace&quot;,
       "cat": "http://standards.iso.org/iso/19115/-3/cat/1.0&quot;,
       "mco": "http://standards.iso.org/iso/19115/-3/mco/1.0&quot;,
       "lan": "http://standards.iso.org/iso/19115/-3/lan/1.0&quot;,
       "gex": "http://standards.iso.org/iso/19115/-3/gex/1.0&quot;,
       "gcx": "http://standards.iso.org/iso/19115/-3/gcx/1.0&quot;,
       "mas": "http://standards.iso.org/iso/19115/-3/mas/1.0&quot;,
       "mrd": "http://standards.iso.org/iso/19115/-3/mrd/1.0&quot;,
       "mrc": "http://standards.iso.org/iso/19115/-3/mrc/2.0&quot;,
       "mpc": "http://standards.iso.org/iso/19115/-3/mpc/1.0&quot;,
       "mex": "http://standards.iso.org/iso/19115/-3/mex/1.0&quot;,
       "pre": "http://standards.iso.org/iso/19135/-2/pre/1.0&quot;,
       "mri": "http://standards.iso.org/iso/19115/-3/mri/1.0&quot;,
       "gfc": "http://standards.iso.org/iso/19110/gfc/1.1&quot;,
       "mrl": "http://standards.iso.org/iso/19115/-3/mrl/2.0&quot;,
       "mdb": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
       "mrs": "http://standards.iso.org/iso/19115/-3/mrs/1.0&quot;,
       "srv": "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;,
       "dqc": "http://standards.iso.org/iso/19157/-2/dqc/1.0&quot;,
       "mdq": "http://standards.iso.org/iso/19157/-2/mdq/1.0&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": [
       "schematron-rules-inspire.xsl",
       "schematron-rules-iso.xsl"
     ],
     "version": "1.0",
     "appMinorVersionSupported": "3.5.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "iso19139",
     "titles": {
       "en": "Geographic information -- Metadata (iso19139:2007)",
       "fr": "Information géographique -- Métadonnées (iso19139:2007)"
     },
     "descriptions": {
       "en": "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."
     },
     "standardUrl":
"
https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798\\n

",
     "targetNamespace": "http://www.isotc211.org/2005/gmd&quot;,
     "namespaces": {
       "gco": "http://www.isotc211.org/2005/gco&quot;,
       "gmx": "http://www.isotc211.org/2005/gmx&quot;,
       "xml": "http://www.w3.org/XML/1998/namespace&quot;,
       "gss": "http://www.isotc211.org/2005/gss&quot;,
       "srv": "http://www.isotc211.org/2005/srv&quot;,
       "gts": "http://www.isotc211.org/2005/gts&quot;,
       "gsr": "http://www.isotc211.org/2005/gsr&quot;,
       "gml": "http://www.opengis.net/gml/3.2&quot;,
       "gmd": "http://www.isotc211.org/2005/gmd&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": [
       "schematron-rules-url-check.xsl",
       "schematron-rules-inspire-sds.xsl",
       "schematron-rules-geonetwork.xsl",
       "schematron-rules-inspire.xsl",
       "schematron-rules-iso.xsl",
       "schematron-rules-inspire-strict.xsl"
     ],
     "version": "1.0",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "dublin-core",
     "titles": {
       "en": "Dublin core"
     },
     "descriptions": {},
     "standardUrl": "http://dublincore.org/documents/dces/&quot;,
     "targetNamespace": null,
     "namespaces": {
       "": "http://purl.org/dc/dcmitype/&quot;,
       "dct": "http://purl.org/dc/terms/&quot;,
       "xml": "http://www.w3.org/XML/1998/namespace&quot;,
       "dc": "http://purl.org/dc/elements/1.1/&quot;
     },
     "readwriteUUID": false,
     "schematronRules": ,
     "version": "1.0",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "csw-record",
     "titles": {
       "en": "Dublin core (for CSW only)"
     },
     "descriptions": {},
     "standardUrl": null,
     "targetNamespace": "http://www.opengis.net/cat/csw/2.0.2&quot;,
     "namespaces": {
       "dct": "http://purl.org/dc/terms/&quot;,
       "csw": "http://www.opengis.net/cat/csw/2.0.2&quot;,
       "ows": "http://www.opengis.net/ows&quot;,
       "dc": "http://purl.org/dc/elements/1.1/&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": ,
     "version": "2.0.2",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": null
   },
   {
     "name": "iso19110",
     "titles": {
       "en": "Geographic information -- Methodology for feature
cataloguing",
       "fr": "Information géographique -- Méthodologie de catalogage
des entités"
     },
     "descriptions": {},
     "standardUrl": "\n

http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965\\n

",
     "targetNamespace": "http://www.isotc211.org/2005/gfc&quot;,
     "namespaces": {
       "": "http://www.isotc211.org/2005/gss&quot;,
       "gco": "http://www.isotc211.org/2005/gco&quot;,
       "gmx": "http://www.isotc211.org/2005/gmx&quot;,
       "gfc": "http://www.isotc211.org/2005/gfc&quot;,
       "gml": "http://www.opengis.net/gml&quot;,
       "gts": "http://www.isotc211.org/2005/gts&quot;,
       "gsr": "http://www.isotc211.org/2005/gsr&quot;,
       "gmd": "http://www.isotc211.org/2005/gmd&quot;,
       "xlink": "http://www.w3.org/1999/xlink&quot;
     },
     "readwriteUUID": false,
     "schematronRules": ,
     "version": "1.0",
     "appMinorVersionSupported": "3.4.0",
     "appMajorVersionSupported": null,
     "dependsOn": "iso19139"
   }
]

- - - - - - -

Do I have to load the missing schemas on GeoNetwork or do I have to
perform some post processing on ERDDAP WAF endpoint in order to let
GeoNetwork perform a smooth harvesting?

With Best Regards,
Pierpaolo Culurciello

_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--

*Vriendelijke groeten / Kind regards,Jose García
<http://www.geocat.net/&gt;Veenderweg 136721 WD BennekomThe NetherlandsT: +31
(0)318 416664 <+31318416664>Please consider the environment before printing
this email.*

Hi, so those records are using ISO19115-2 for imagery dataset. This is only
supported using ISO19115-3 in GeoNetwork. So using a transformation
"ISO19139-to-ISO19115-3-2018" could have worked but unfortunately is not an
option of the WAF harvester.

You can first give a try importing manually one record with that conversion
to see if it works.

Cheers.
Francois

Le lun. 28 févr. 2022 à 12:26, Jose Garcia via GeoNetwork-users <
geonetwork-users@lists.sourceforge.net> a écrit :

Hi Pierpaolo

The metadata starts with this element gmi:MI_Metadata, that doesn't
correspond to any metadata schema bundled in GeoNetwork.

Regards,
Jose García

On Sat, Feb 26, 2022 at 4:53 PM Pierpaolo Culurciello via GeoNetwork-users
<
geonetwork-users@lists.sourceforge.net> wrote:

>
>
> Dear all,
>
> I am trying to harvest the native WAF endpoint of an ERDDAP instance
> from GeoNetwork 3.10.6.
> The harvesting finishes without error but in the log file clearly
> states that no metadata have been imported because of missing schemas:
>
> - - - - - - - -
>
> 2022-02-26T12:58:00,907+0000 INFO [ERDDAP] - Starting harvesting of
ERDDAP
> 2022-02-26T12:58:00,907+0000 DEBUG [ERDDAP] - AbstractHarvester login:
> ownerId = 116
> 2022-02-26T12:58:01,075+0000 INFO [ERDDAP] - Started harvesting from
> node : ERDDAP (WebDavHarvester)
> 2022-02-26T12:58:01,076+0000 INFO [ERDDAP] - WebDav doHarvest start
> 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Retrieving remote
> metadata information for : ERDDAP
> 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Scanning resource :
> https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/
> 2022-02-26T12:58:01,132+0000 DEBUG [ERDDAP] - Remote files found : 1
> 2022-02-26T12:58:01,132+0000 INFO [ERDDAP] - Start of alignment for :
> ERDDAP
> 2022-02-26T12:58:01,162+0000 DEBUG [ERDDAP] - Getting remote file :
>
>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
> 2022-02-26T12:58:01,170+0000 DEBUG [ERDDAP] - Record got:
> <gmi:MI_Metadata xmlns:gmi="http://www.isotc211.org/2005/gmi&quot;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
> xmlns:xlink="http://www.w3.org/1999/xlink&quot;
> xmlns:gco="http://www.isotc211.org/2005/gco&quot;
> xmlns:gmd="http://www.isotc211.org/2005/gmd&quot;
> xmlns:gmx="http://www.isotc211.org/2005/gmx&quot;
> xmlns:gml="http://www.opengis.net/gml/3.2&quot;
> xmlns:gss="http://www.isotc211.org/2005/gss&quot;
> xmlns:gts="http://www.isotc211.org/2005/gts&quot;
> xmlns:gsr="http://www.isotc211.org/2005/gsr&quot;
> xmlns:srv="http://www.isotc211.org/2005/srv&quot;
> xsi:schemaLocation="https://www.isotc211.org/2005/gmi
> https://data.noaa.gov/resources/iso19139/schema.xsd&quot;&gt;
> <gmd:fileIdentifier>
> <gco:CharacterString>cnr_ismar_b37f_8e81_db5d</gco:CharacterString>
> </gmd:fileIdentifier>
>
> ### OMITTED FOR BREVITY ###
>
> </gmi:MI_Metadata>
> 2022-02-26T12:58:01,172+0000 WARN [ERDDAP] - Skipping metadata with
> unknown schema. Path is :
>
>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
> 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - End of alignment for :
ERDDAP
> 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - WebDav doHarvest end
> 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - Ended harvesting from
> node : ERDDAP (WebDavHarvester)
>
> - - - - - - - -
>
> Here's the json repsonse to the query to the GeoNetwork API exposing
> the loaded schemas
> (
>
https://geonetwork.ve.ismar.cnr.it/geonetwork/doc/api/index.html#/identifiers/getIdentifiers
> ):
>
> - - - - -
>
> [
> {
> "name": "iso19115-3.2018",
> "titles": {
> "en": "Geographic information -- Metadata",
> "fr": "Information géographique -- Métadonnées"
> },
> "descriptions": {
> "en": "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
> <
>
http://cnig.gouv.fr/wp-content/uploads/2015/06/titellus_fx_prunayre_iso19115-3_inspire2015.pdf
>`_
> This standard is maintained on
> https://github.com/metadata101/iso19115-3.2018 and is available by
> default in GeoNetwork 3.8+. The TC211 is maintaining the XSD for this
> standard on https://github.com/ISO-TC211/XML. Example of catalogues
using
> this standard: - `Metawal - Catalogue pour l'information géographique de
> Wallonie <http://metawal.wallonie.be/&gt;\`\_ 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.
> .. figure:: img/metawal-tramedesaxes.png - `Sextant - Checkpoints <
> https://sextant.ifremer.fr/&gt;\`\_ is using ISO19115-3 for data quality
> description of Specification / Products and upstream data. .. figure::
> img/sextant-checkpoint.png",
> "fr": "L’objectif de l’ISO 19115 est de fournir un modèle
> destiné à décrire des informations ou des ressources pouvant avoir des
> étendues géographiques. Cette partie de l’ISO 19115 est destinée à
> être utilisée, entre autres, par des analystes de systèmes
> d’informations, des planificateurs de programmes et des développeurs
> de systèmes d’informations, dans le but de définir des principes de
> base et des exigences permettant d’établir une description normalisée
> des ressources d’informations. Cette partie de l’ISO 19115 définit les
> éléments de métadonnées, leurs propriétés et les relations entre les
> éléments et établit un ensemble commun de terminologies, de
> définitions et de procédures d’extension concernant les métadonnées. 
> Bien que cette partie de l’ISO 19115 ait pour but principal de décrire
> les informations numériques qui ont une étendue géographique, elle
> peut être utilisée pour décrire tous les types de ressources, y
> compris les documents textuels, les initiatives, les logiciels, les
> informations non géographiques, les spécifications de produit et les
> entrepôts de données, c’est-à-dire qu’elle peut même être utilisée
> pour décrire des ressources d’informations n’ayant aucune étendue
> géographique. Certains domaines ont leurs propres normes de
> métadonnées, telles que celles du Dublin Core pour les bibliothèques.
> Si besoin, des profils de telles normes et de cette partie de l’ISO
> 19115 pourraient être développés pour créer un Schéma Communautaire.
> Ce schéma est également composé des normes : - ISO19110 pour les
> modèles de données - ISO19115-2 pour l'imagerie - ISO19157 pour la
> qualité des données"
> },
> "standardUrl":
> "
>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32579
> ",
> "targetNamespace": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
> "namespaces": {
> "dqm": "http://standards.iso.org/iso/19157/-2/dqm/1.0&quot;,
> "gml": "http://www.opengis.net/gml/3.2&quot;,
> "fcc": "http://standards.iso.org/iso/19110/fcc/1.0&quot;,
> "mmi": "http://standards.iso.org/iso/19115/-3/mmi/1.0&quot;,
> "mcc": "http://standards.iso.org/iso/19115/-3/mcc/1.0&quot;,
> "msr": "http://standards.iso.org/iso/19115/-3/msr/2.0&quot;,
> "mac": "http://standards.iso.org/iso/19115/-3/mac/2.0&quot;,
> "cit": "http://standards.iso.org/iso/19115/-3/cit/2.0&quot;,
> "gmw": "http://standards.iso.org/iso/19115/-3/gmw/1.0&quot;,
> "gco": "http://standards.iso.org/iso/19115/-3/gco/1.0&quot;,
> "reg": "http://standards.iso.org/iso/19135/-2/reg/1.0&quot;,
> "xml": "http://www.w3.org/XML/1998/namespace&quot;,
> "cat": "http://standards.iso.org/iso/19115/-3/cat/1.0&quot;,
> "mco": "http://standards.iso.org/iso/19115/-3/mco/1.0&quot;,
> "lan": "http://standards.iso.org/iso/19115/-3/lan/1.0&quot;,
> "gex": "http://standards.iso.org/iso/19115/-3/gex/1.0&quot;,
> "gcx": "http://standards.iso.org/iso/19115/-3/gcx/1.0&quot;,
> "mas": "http://standards.iso.org/iso/19115/-3/mas/1.0&quot;,
> "mrd": "http://standards.iso.org/iso/19115/-3/mrd/1.0&quot;,
> "mrc": "http://standards.iso.org/iso/19115/-3/mrc/2.0&quot;,
> "mpc": "http://standards.iso.org/iso/19115/-3/mpc/1.0&quot;,
> "mex": "http://standards.iso.org/iso/19115/-3/mex/1.0&quot;,
> "pre": "http://standards.iso.org/iso/19135/-2/pre/1.0&quot;,
> "mri": "http://standards.iso.org/iso/19115/-3/mri/1.0&quot;,
> "gfc": "http://standards.iso.org/iso/19110/gfc/1.1&quot;,
> "mrl": "http://standards.iso.org/iso/19115/-3/mrl/2.0&quot;,
> "mdb": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
> "mrs": "http://standards.iso.org/iso/19115/-3/mrs/1.0&quot;,
> "srv": "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;,
> "dqc": "http://standards.iso.org/iso/19157/-2/dqc/1.0&quot;,
> "mdq": "http://standards.iso.org/iso/19157/-2/mdq/1.0&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": [
> "schematron-rules-inspire.xsl",
> "schematron-rules-iso.xsl"
> ],
> "version": "1.0",
> "appMinorVersionSupported": "3.5.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "iso19139",
> "titles": {
> "en": "Geographic information -- Metadata (iso19139:2007)",
> "fr": "Information géographique -- Métadonnées (iso19139:2007)"
> },
> "descriptions": {
> "en": "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."
> },
> "standardUrl":
> "
>
https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798\\n
>
> ",
> "targetNamespace": "http://www.isotc211.org/2005/gmd&quot;,
> "namespaces": {
> "gco": "http://www.isotc211.org/2005/gco&quot;,
> "gmx": "http://www.isotc211.org/2005/gmx&quot;,
> "xml": "http://www.w3.org/XML/1998/namespace&quot;,
> "gss": "http://www.isotc211.org/2005/gss&quot;,
> "srv": "http://www.isotc211.org/2005/srv&quot;,
> "gts": "http://www.isotc211.org/2005/gts&quot;,
> "gsr": "http://www.isotc211.org/2005/gsr&quot;,
> "gml": "http://www.opengis.net/gml/3.2&quot;,
> "gmd": "http://www.isotc211.org/2005/gmd&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": [
> "schematron-rules-url-check.xsl",
> "schematron-rules-inspire-sds.xsl",
> "schematron-rules-geonetwork.xsl",
> "schematron-rules-inspire.xsl",
> "schematron-rules-iso.xsl",
> "schematron-rules-inspire-strict.xsl"
> ],
> "version": "1.0",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "dublin-core",
> "titles": {
> "en": "Dublin core"
> },
> "descriptions": {},
> "standardUrl": "http://dublincore.org/documents/dces/&quot;,
> "targetNamespace": null,
> "namespaces": {
> "": "http://purl.org/dc/dcmitype/&quot;,
> "dct": "http://purl.org/dc/terms/&quot;,
> "xml": "http://www.w3.org/XML/1998/namespace&quot;,
> "dc": "http://purl.org/dc/elements/1.1/&quot;
> },
> "readwriteUUID": false,
> "schematronRules": ,
> "version": "1.0",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "csw-record",
> "titles": {
> "en": "Dublin core (for CSW only)"
> },
> "descriptions": {},
> "standardUrl": null,
> "targetNamespace": "http://www.opengis.net/cat/csw/2.0.2&quot;,
> "namespaces": {
> "dct": "http://purl.org/dc/terms/&quot;,
> "csw": "http://www.opengis.net/cat/csw/2.0.2&quot;,
> "ows": "http://www.opengis.net/ows&quot;,
> "dc": "http://purl.org/dc/elements/1.1/&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": ,
> "version": "2.0.2",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "iso19110",
> "titles": {
> "en": "Geographic information -- Methodology for feature
> cataloguing",
> "fr": "Information géographique -- Méthodologie de catalogage
> des entités"
> },
> "descriptions": {},
> "standardUrl": "\n
>
>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965\\n
>
> ",
> "targetNamespace": "http://www.isotc211.org/2005/gfc&quot;,
> "namespaces": {
> "": "http://www.isotc211.org/2005/gss&quot;,
> "gco": "http://www.isotc211.org/2005/gco&quot;,
> "gmx": "http://www.isotc211.org/2005/gmx&quot;,
> "gfc": "http://www.isotc211.org/2005/gfc&quot;,
> "gml": "http://www.opengis.net/gml&quot;,
> "gts": "http://www.isotc211.org/2005/gts&quot;,
> "gsr": "http://www.isotc211.org/2005/gsr&quot;,
> "gmd": "http://www.isotc211.org/2005/gmd&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": ,
> "version": "1.0",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": "iso19139"
> }
> ]
>
> - - - - - - -
>
> Do I have to load the missing schemas on GeoNetwork or do I have to
> perform some post processing on ERDDAP WAF endpoint in order to let
> GeoNetwork perform a smooth harvesting?
>
> With Best Regards,
> Pierpaolo Culurciello
>
>
>
>
>
>
>
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>

--

*Vriendelijke groeten / Kind regards,Jose García
<http://www.geocat.net/&gt;Veenderweg 136721 WD BennekomThe NetherlandsT: +31
(0)318 416664 <+31318416664>Please consider the environment before printing
this email.*

_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Hello Francois and Jose,

and thanks for your quick replies!
I was on holiday and so I beg your pardon for answering only a few days later.
I am not very familiar with metadata schemas, I am trying to publish scientific datasets originally on THREDDS and ERDDAP servers from a central catalogue (GeoNetwork) and I am exploring the available alternatives.
WAF harvesting seemed to me a good choice because ERDDAP automatically builds the WAF endpoint URL for all the datasets (in my case it is https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/) and I thought it worked "out of the box".
Anyway this can became a good opportunity to dig further into metadata schemas and so if you could give me a couple of advices on how to perform the ISO19139-to-ISO19115-3-2018 transformation I'd really appreciate it.
I found on my GeoNetwork instance a mapping file:

/usr/local/tomcat/webapps/geonetwork/WEB-INF/data/config/schema_plugins/iso19115-3.2018/convert/ISO19139/fromISO19139.xsl

but I honestly don't know how to use it to perform the conversion and I was neither able to find some guides on the web.

With Best Regards,
Pierpaolo Culurciello

Quoting Francois Prunayre <fx.prunayre@anonymised.com>:

Hi, so those records are using ISO19115-2 for imagery dataset. This is only
supported using ISO19115-3 in GeoNetwork. So using a transformation
"ISO19139-to-ISO19115-3-2018" could have worked but unfortunately is not an
option of the WAF harvester.

You can first give a try importing manually one record with that conversion
to see if it works.

Cheers.
Francois

Le lun. 28 févr. 2022 à 12:26, Jose Garcia via GeoNetwork-users <
geonetwork-users@lists.sourceforge.net> a écrit :

Hi Pierpaolo

The metadata starts with this element gmi:MI_Metadata, that doesn't
correspond to any metadata schema bundled in GeoNetwork.

Regards,
Jose García

On Sat, Feb 26, 2022 at 4:53 PM Pierpaolo Culurciello via GeoNetwork-users
<
geonetwork-users@lists.sourceforge.net> wrote:

>
> Dear all,
>
> I am trying to harvest the native WAF endpoint of an ERDDAP instance
> from GeoNetwork 3.10.6.
> The harvesting finishes without error but in the log file clearly
> states that no metadata have been imported because of missing schemas:
>
> - - - - - - - -
>
> 2022-02-26T12:58:00,907+0000 INFO [ERDDAP] - Starting harvesting of
ERDDAP
> 2022-02-26T12:58:00,907+0000 DEBUG [ERDDAP] - AbstractHarvester login:
> ownerId = 116
> 2022-02-26T12:58:01,075+0000 INFO [ERDDAP] - Started harvesting from
> node : ERDDAP (WebDavHarvester)
> 2022-02-26T12:58:01,076+0000 INFO [ERDDAP] - WebDav doHarvest start
> 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Retrieving remote
> metadata information for : ERDDAP
> 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Scanning resource :
> https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/
> 2022-02-26T12:58:01,132+0000 DEBUG [ERDDAP] - Remote files found : 1
> 2022-02-26T12:58:01,132+0000 INFO [ERDDAP] - Start of alignment for :
> ERDDAP
> 2022-02-26T12:58:01,162+0000 DEBUG [ERDDAP] - Getting remote file :
>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
> 2022-02-26T12:58:01,170+0000 DEBUG [ERDDAP] - Record got:
> <gmi:MI_Metadata xmlns:gmi="http://www.isotc211.org/2005/gmi&quot;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
> xmlns:xlink="http://www.w3.org/1999/xlink&quot;
> xmlns:gco="http://www.isotc211.org/2005/gco&quot;
> xmlns:gmd="http://www.isotc211.org/2005/gmd&quot;
> xmlns:gmx="http://www.isotc211.org/2005/gmx&quot;
> xmlns:gml="http://www.opengis.net/gml/3.2&quot;
> xmlns:gss="http://www.isotc211.org/2005/gss&quot;
> xmlns:gts="http://www.isotc211.org/2005/gts&quot;
> xmlns:gsr="http://www.isotc211.org/2005/gsr&quot;
> xmlns:srv="http://www.isotc211.org/2005/srv&quot;
> xsi:schemaLocation="https://www.isotc211.org/2005/gmi
> https://data.noaa.gov/resources/iso19139/schema.xsd&quot;&gt;
> <gmd:fileIdentifier>
> <gco:CharacterString>cnr_ismar_b37f_8e81_db5d</gco:CharacterString>
> </gmd:fileIdentifier>
>
> ### OMITTED FOR BREVITY ###
>
> </gmi:MI_Metadata>
> 2022-02-26T12:58:01,172+0000 WARN [ERDDAP] - Skipping metadata with
> unknown schema. Path is :
>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
> 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - End of alignment for :
ERDDAP
> 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - WebDav doHarvest end
> 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - Ended harvesting from
> node : ERDDAP (WebDavHarvester)
>
> - - - - - - - -
>
> Here's the json repsonse to the query to the GeoNetwork API exposing
> the loaded schemas
> (
>
https://geonetwork.ve.ismar.cnr.it/geonetwork/doc/api/index.html#/identifiers/getIdentifiers
> ):
>
> - - - - -
>
> [
> {
> "name": "iso19115-3.2018",
> "titles": {
> "en": "Geographic information -- Metadata",
> "fr": "Information géographique -- Métadonnées"
> },
> "descriptions": {
> "en": "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
> <
>
http://cnig.gouv.fr/wp-content/uploads/2015/06/titellus_fx_prunayre_iso19115-3_inspire2015.pdf
>`_
> This standard is maintained on
> https://github.com/metadata101/iso19115-3.2018 and is available by
> default in GeoNetwork 3.8+. The TC211 is maintaining the XSD for this
> standard on https://github.com/ISO-TC211/XML. Example of catalogues
using
> this standard: - `Metawal - Catalogue pour l'information géographique de
> Wallonie <http://metawal.wallonie.be/&gt;\`\_ 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.
> .. figure:: img/metawal-tramedesaxes.png - `Sextant - Checkpoints <
> https://sextant.ifremer.fr/&gt;\`\_ is using ISO19115-3 for data quality
> description of Specification / Products and upstream data. .. figure::
> img/sextant-checkpoint.png",
> "fr": "L’objectif de l’ISO 19115 est de fournir un modèle
> destiné à décrire des informations ou des ressources pouvant avoir des
> étendues géographiques. Cette partie de l’ISO 19115 est destinée à
> être utilisée, entre autres, par des analystes de systèmes
> d’informations, des planificateurs de programmes et des développeurs
> de systèmes d’informations, dans le but de définir des principes de
> base et des exigences permettant d’établir une description normalisée
> des ressources d’informations. Cette partie de l’ISO 19115 définit les
> éléments de métadonnées, leurs propriétés et les relations entre les
> éléments et établit un ensemble commun de terminologies, de
> définitions et de procédures d’extension concernant les métadonnées. 
> Bien que cette partie de l’ISO 19115 ait pour but principal de décrire
> les informations numériques qui ont une étendue géographique, elle
> peut être utilisée pour décrire tous les types de ressources, y
> compris les documents textuels, les initiatives, les logiciels, les
> informations non géographiques, les spécifications de produit et les
> entrepôts de données, c’est-à-dire qu’elle peut même être utilisée
> pour décrire des ressources d’informations n’ayant aucune étendue
> géographique. Certains domaines ont leurs propres normes de
> métadonnées, telles que celles du Dublin Core pour les bibliothèques.
> Si besoin, des profils de telles normes et de cette partie de l’ISO
> 19115 pourraient être développés pour créer un Schéma Communautaire.
> Ce schéma est également composé des normes : - ISO19110 pour les
> modèles de données - ISO19115-2 pour l'imagerie - ISO19157 pour la
> qualité des données"
> },
> "standardUrl":
> "
>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32579
> ",
> "targetNamespace": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
> "namespaces": {
> "dqm": "http://standards.iso.org/iso/19157/-2/dqm/1.0&quot;,
> "gml": "http://www.opengis.net/gml/3.2&quot;,
> "fcc": "http://standards.iso.org/iso/19110/fcc/1.0&quot;,
> "mmi": "http://standards.iso.org/iso/19115/-3/mmi/1.0&quot;,
> "mcc": "http://standards.iso.org/iso/19115/-3/mcc/1.0&quot;,
> "msr": "http://standards.iso.org/iso/19115/-3/msr/2.0&quot;,
> "mac": "http://standards.iso.org/iso/19115/-3/mac/2.0&quot;,
> "cit": "http://standards.iso.org/iso/19115/-3/cit/2.0&quot;,
> "gmw": "http://standards.iso.org/iso/19115/-3/gmw/1.0&quot;,
> "gco": "http://standards.iso.org/iso/19115/-3/gco/1.0&quot;,
> "reg": "http://standards.iso.org/iso/19135/-2/reg/1.0&quot;,
> "xml": "http://www.w3.org/XML/1998/namespace&quot;,
> "cat": "http://standards.iso.org/iso/19115/-3/cat/1.0&quot;,
> "mco": "http://standards.iso.org/iso/19115/-3/mco/1.0&quot;,
> "lan": "http://standards.iso.org/iso/19115/-3/lan/1.0&quot;,
> "gex": "http://standards.iso.org/iso/19115/-3/gex/1.0&quot;,
> "gcx": "http://standards.iso.org/iso/19115/-3/gcx/1.0&quot;,
> "mas": "http://standards.iso.org/iso/19115/-3/mas/1.0&quot;,
> "mrd": "http://standards.iso.org/iso/19115/-3/mrd/1.0&quot;,
> "mrc": "http://standards.iso.org/iso/19115/-3/mrc/2.0&quot;,
> "mpc": "http://standards.iso.org/iso/19115/-3/mpc/1.0&quot;,
> "mex": "http://standards.iso.org/iso/19115/-3/mex/1.0&quot;,
> "pre": "http://standards.iso.org/iso/19135/-2/pre/1.0&quot;,
> "mri": "http://standards.iso.org/iso/19115/-3/mri/1.0&quot;,
> "gfc": "http://standards.iso.org/iso/19110/gfc/1.1&quot;,
> "mrl": "http://standards.iso.org/iso/19115/-3/mrl/2.0&quot;,
> "mdb": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
> "mrs": "http://standards.iso.org/iso/19115/-3/mrs/1.0&quot;,
> "srv": "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;,
> "dqc": "http://standards.iso.org/iso/19157/-2/dqc/1.0&quot;,
> "mdq": "http://standards.iso.org/iso/19157/-2/mdq/1.0&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": [
> "schematron-rules-inspire.xsl",
> "schematron-rules-iso.xsl"
> ],
> "version": "1.0",
> "appMinorVersionSupported": "3.5.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "iso19139",
> "titles": {
> "en": "Geographic information -- Metadata (iso19139:2007)",
> "fr": "Information géographique -- Métadonnées (iso19139:2007)"
> },
> "descriptions": {
> "en": "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."
> },
> "standardUrl":
> "
>
https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798\\n
>
> ",
> "targetNamespace": "http://www.isotc211.org/2005/gmd&quot;,
> "namespaces": {
> "gco": "http://www.isotc211.org/2005/gco&quot;,
> "gmx": "http://www.isotc211.org/2005/gmx&quot;,
> "xml": "http://www.w3.org/XML/1998/namespace&quot;,
> "gss": "http://www.isotc211.org/2005/gss&quot;,
> "srv": "http://www.isotc211.org/2005/srv&quot;,
> "gts": "http://www.isotc211.org/2005/gts&quot;,
> "gsr": "http://www.isotc211.org/2005/gsr&quot;,
> "gml": "http://www.opengis.net/gml/3.2&quot;,
> "gmd": "http://www.isotc211.org/2005/gmd&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": [
> "schematron-rules-url-check.xsl",
> "schematron-rules-inspire-sds.xsl",
> "schematron-rules-geonetwork.xsl",
> "schematron-rules-inspire.xsl",
> "schematron-rules-iso.xsl",
> "schematron-rules-inspire-strict.xsl"
> ],
> "version": "1.0",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "dublin-core",
> "titles": {
> "en": "Dublin core"
> },
> "descriptions": {},
> "standardUrl": "http://dublincore.org/documents/dces/&quot;,
> "targetNamespace": null,
> "namespaces": {
> "": "http://purl.org/dc/dcmitype/&quot;,
> "dct": "http://purl.org/dc/terms/&quot;,
> "xml": "http://www.w3.org/XML/1998/namespace&quot;,
> "dc": "http://purl.org/dc/elements/1.1/&quot;
> },
> "readwriteUUID": false,
> "schematronRules": ,
> "version": "1.0",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "csw-record",
> "titles": {
> "en": "Dublin core (for CSW only)"
> },
> "descriptions": {},
> "standardUrl": null,
> "targetNamespace": "http://www.opengis.net/cat/csw/2.0.2&quot;,
> "namespaces": {
> "dct": "http://purl.org/dc/terms/&quot;,
> "csw": "http://www.opengis.net/cat/csw/2.0.2&quot;,
> "ows": "http://www.opengis.net/ows&quot;,
> "dc": "http://purl.org/dc/elements/1.1/&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": ,
> "version": "2.0.2",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": null
> },
> {
> "name": "iso19110",
> "titles": {
> "en": "Geographic information -- Methodology for feature
> cataloguing",
> "fr": "Information géographique -- Méthodologie de catalogage
> des entités"
> },
> "descriptions": {},
> "standardUrl": "\n
>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965\\n
>
> ",
> "targetNamespace": "http://www.isotc211.org/2005/gfc&quot;,
> "namespaces": {
> "": "http://www.isotc211.org/2005/gss&quot;,
> "gco": "http://www.isotc211.org/2005/gco&quot;,
> "gmx": "http://www.isotc211.org/2005/gmx&quot;,
> "gfc": "http://www.isotc211.org/2005/gfc&quot;,
> "gml": "http://www.opengis.net/gml&quot;,
> "gts": "http://www.isotc211.org/2005/gts&quot;,
> "gsr": "http://www.isotc211.org/2005/gsr&quot;,
> "gmd": "http://www.isotc211.org/2005/gmd&quot;,
> "xlink": "http://www.w3.org/1999/xlink&quot;
> },
> "readwriteUUID": false,
> "schematronRules": ,
> "version": "1.0",
> "appMinorVersionSupported": "3.4.0",
> "appMajorVersionSupported": null,
> "dependsOn": "iso19139"
> }
> ]
>
> - - - - - - -
>
> Do I have to load the missing schemas on GeoNetwork or do I have to
> perform some post processing on ERDDAP WAF endpoint in order to let
> GeoNetwork perform a smooth harvesting?
>
> With Best Regards,
> Pierpaolo Culurciello
>
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>

--

*Vriendelijke groeten / Kind regards,Jose García
<http://www.geocat.net/&gt;Veenderweg 136721 WD BennekomThe NetherlandsT: +31
(0)318 416664 <+31318416664>Please consider the environment before printing
this email.*

_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Hi Pierpaolo

Open the import panel, select your XML and choose the conversion in the list
https://geonetwork-opensource.org/manuals/4.0.x/en/user-guide/describing-information/importing-metadata.html
so you can first test that you can import this type of record.

It looks to be ok eg.
https://apps.titellus.net/geonetwork/srv/eng/catalog.search#/metadata/cnr_ismar_b37f_8e81_db5d

Cheers.
Francois

Le mer. 2 mars 2022 à 18:49, Pierpaolo Culurciello <
pierpaolo.culurciello@anonymised.com> a écrit :

Hello Francois and Jose,

and thanks for your quick replies!
I was on holiday and so I beg your pardon for answering only a few days
later.
I am not very familiar with metadata schemas, I am trying to publish
scientific datasets originally on THREDDS and ERDDAP servers from a
central catalogue (GeoNetwork) and I am exploring the available
alternatives.
WAF harvesting seemed to me a good choice because ERDDAP automatically
builds the WAF endpoint URL for all the datasets (in my case it is
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/) and I
thought it worked "out of the box".
Anyway this can became a good opportunity to dig further into metadata
schemas and so if you could give me a couple of advices on how to
perform the ISO19139-to-ISO19115-3-2018 transformation I'd really
appreciate it.
I found on my GeoNetwork instance a mapping file:

/usr/local/tomcat/webapps/geonetwork/WEB-INF/data/config/schema_plugins/iso19115-3.2018/convert/ISO19139/fromISO19139.xsl

but I honestly don't know how to use it to perform the conversion and
I was neither able to find some guides on the web.

With Best Regards,
Pierpaolo Culurciello

Quoting Francois Prunayre <fx.prunayre@anonymised.com>:

> Hi, so those records are using ISO19115-2 for imagery dataset. This is
only
> supported using ISO19115-3 in GeoNetwork. So using a transformation
> "ISO19139-to-ISO19115-3-2018" could have worked but unfortunately is not
an
> option of the WAF harvester.
>
> You can first give a try importing manually one record with that
conversion
> to see if it works.
>
> Cheers.
> Francois
>
>
>
> Le lun. 28 févr. 2022 à 12:26, Jose Garcia via GeoNetwork-users <
> geonetwork-users@lists.sourceforge.net> a écrit :
>
>> Hi Pierpaolo
>>
>> The metadata starts with this element gmi:MI_Metadata, that doesn't
>> correspond to any metadata schema bundled in GeoNetwork.
>>
>> Regards,
>> Jose García
>>
>> On Sat, Feb 26, 2022 at 4:53 PM Pierpaolo Culurciello via
GeoNetwork-users
>> <
>> geonetwork-users@lists.sourceforge.net> wrote:
>>
>> >
>> >
>> > Dear all,
>> >
>> > I am trying to harvest the native WAF endpoint of an ERDDAP instance
>> > from GeoNetwork 3.10.6.
>> > The harvesting finishes without error but in the log file clearly
>> > states that no metadata have been imported because of missing schemas:
>> >
>> > - - - - - - - -
>> >
>> > 2022-02-26T12:58:00,907+0000 INFO [ERDDAP] - Starting harvesting of
>> ERDDAP
>> > 2022-02-26T12:58:00,907+0000 DEBUG [ERDDAP] - AbstractHarvester login:
>> > ownerId = 116
>> > 2022-02-26T12:58:01,075+0000 INFO [ERDDAP] - Started harvesting from
>> > node : ERDDAP (WebDavHarvester)
>> > 2022-02-26T12:58:01,076+0000 INFO [ERDDAP] - WebDav doHarvest start
>> > 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Retrieving remote
>> > metadata information for : ERDDAP
>> > 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Scanning resource :
>> > https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/
>> > 2022-02-26T12:58:01,132+0000 DEBUG [ERDDAP] - Remote files found : 1
>> > 2022-02-26T12:58:01,132+0000 INFO [ERDDAP] - Start of alignment for :
>> > ERDDAP
>> > 2022-02-26T12:58:01,162+0000 DEBUG [ERDDAP] - Getting remote file :
>> >
>> >
>>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
>> > 2022-02-26T12:58:01,170+0000 DEBUG [ERDDAP] - Record got:
>> > <gmi:MI_Metadata xmlns:gmi="http://www.isotc211.org/2005/gmi&quot;
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
>> > xmlns:xlink="http://www.w3.org/1999/xlink&quot;
>> > xmlns:gco="http://www.isotc211.org/2005/gco&quot;
>> > xmlns:gmd="http://www.isotc211.org/2005/gmd&quot;
>> > xmlns:gmx="http://www.isotc211.org/2005/gmx&quot;
>> > xmlns:gml="http://www.opengis.net/gml/3.2&quot;
>> > xmlns:gss="http://www.isotc211.org/2005/gss&quot;
>> > xmlns:gts="http://www.isotc211.org/2005/gts&quot;
>> > xmlns:gsr="http://www.isotc211.org/2005/gsr&quot;
>> > xmlns:srv="http://www.isotc211.org/2005/srv&quot;
>> > xsi:schemaLocation="https://www.isotc211.org/2005/gmi
>> > https://data.noaa.gov/resources/iso19139/schema.xsd&quot;&gt;
>> > <gmd:fileIdentifier>
>> >
<gco:CharacterString>cnr_ismar_b37f_8e81_db5d</gco:CharacterString>
>> > </gmd:fileIdentifier>
>> >
>> > ### OMITTED FOR BREVITY ###
>> >
>> > </gmi:MI_Metadata>
>> > 2022-02-26T12:58:01,172+0000 WARN [ERDDAP] - Skipping metadata with
>> > unknown schema. Path is :
>> >
>> >
>>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
>> > 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - End of alignment for :
>> ERDDAP
>> > 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - WebDav doHarvest end
>> > 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - Ended harvesting from
>> > node : ERDDAP (WebDavHarvester)
>> >
>> > - - - - - - - -
>> >
>> > Here's the json repsonse to the query to the GeoNetwork API exposing
>> > the loaded schemas
>> > (
>> >
>>
https://geonetwork.ve.ismar.cnr.it/geonetwork/doc/api/index.html#/identifiers/getIdentifiers
>> > ):
>> >
>> > - - - - -
>> >
>> > [
>> > {
>> > "name": "iso19115-3.2018",
>> > "titles": {
>> > "en": "Geographic information -- Metadata",
>> > "fr": "Information géographique -- Métadonnées"
>> > },
>> > "descriptions": {
>> > "en": "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
>> > <
>> >
>>
http://cnig.gouv.fr/wp-content/uploads/2015/06/titellus_fx_prunayre_iso19115-3_inspire2015.pdf
>> >`_
>> > This standard is maintained on
>> > https://github.com/metadata101/iso19115-3.2018 and is available by
>> > default in GeoNetwork 3.8+. The TC211 is maintaining the XSD for this
>> > standard on https://github.com/ISO-TC211/XML. Example of catalogues
>> using
>> > this standard: - `Metawal - Catalogue pour l'information géographique
de
>> > Wallonie <http://metawal.wallonie.be/&gt;\`\_ 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.
>> > .. figure:: img/metawal-tramedesaxes.png - `Sextant - Checkpoints <
>> > https://sextant.ifremer.fr/&gt;\`\_ is using ISO19115-3 for data quality
>> > description of Specification / Products and upstream data. .. figure::
>> > img/sextant-checkpoint.png",
>> > "fr": "L’objectif de l’ISO 19115 est de fournir un modèle
>> > destiné à décrire des informations ou des ressources pouvant avoir des
>> > étendues géographiques. Cette partie de l’ISO 19115 est destinée à
>> > être utilisée, entre autres, par des analystes de systèmes
>> > d’informations, des planificateurs de programmes et des développeurs
>> > de systèmes d’informations, dans le but de définir des principes de
>> > base et des exigences permettant d’établir une description normalisée
>> > des ressources d’informations. Cette partie de l’ISO 19115 définit les
>> > éléments de métadonnées, leurs propriétés et les relations entre les
>> > éléments et établit un ensemble commun de terminologies, de
>> > définitions et de procédures d’extension concernant les métadonnées. 
>> > Bien que cette partie de l’ISO 19115 ait pour but principal de décrire
>> > les informations numériques qui ont une étendue géographique, elle
>> > peut être utilisée pour décrire tous les types de ressources, y
>> > compris les documents textuels, les initiatives, les logiciels, les
>> > informations non géographiques, les spécifications de produit et les
>> > entrepôts de données, c’est-à-dire qu’elle peut même être utilisée
>> > pour décrire des ressources d’informations n’ayant aucune étendue
>> > géographique. Certains domaines ont leurs propres normes de
>> > métadonnées, telles que celles du Dublin Core pour les bibliothèques.
>> > Si besoin, des profils de telles normes et de cette partie de l’ISO
>> > 19115 pourraient être développés pour créer un Schéma Communautaire.
>> > Ce schéma est également composé des normes : - ISO19110 pour les
>> > modèles de données - ISO19115-2 pour l'imagerie - ISO19157 pour la
>> > qualité des données"
>> > },
>> > "standardUrl":
>> > "
>> >
>>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32579
>> > ",
>> > "targetNamespace": "
http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
>> > "namespaces": {
>> > "dqm": "http://standards.iso.org/iso/19157/-2/dqm/1.0&quot;,
>> > "gml": "http://www.opengis.net/gml/3.2&quot;,
>> > "fcc": "http://standards.iso.org/iso/19110/fcc/1.0&quot;,
>> > "mmi": "http://standards.iso.org/iso/19115/-3/mmi/1.0&quot;,
>> > "mcc": "http://standards.iso.org/iso/19115/-3/mcc/1.0&quot;,
>> > "msr": "http://standards.iso.org/iso/19115/-3/msr/2.0&quot;,
>> > "mac": "http://standards.iso.org/iso/19115/-3/mac/2.0&quot;,
>> > "cit": "http://standards.iso.org/iso/19115/-3/cit/2.0&quot;,
>> > "gmw": "http://standards.iso.org/iso/19115/-3/gmw/1.0&quot;,
>> > "gco": "http://standards.iso.org/iso/19115/-3/gco/1.0&quot;,
>> > "reg": "http://standards.iso.org/iso/19135/-2/reg/1.0&quot;,
>> > "xml": "http://www.w3.org/XML/1998/namespace&quot;,
>> > "cat": "http://standards.iso.org/iso/19115/-3/cat/1.0&quot;,
>> > "mco": "http://standards.iso.org/iso/19115/-3/mco/1.0&quot;,
>> > "lan": "http://standards.iso.org/iso/19115/-3/lan/1.0&quot;,
>> > "gex": "http://standards.iso.org/iso/19115/-3/gex/1.0&quot;,
>> > "gcx": "http://standards.iso.org/iso/19115/-3/gcx/1.0&quot;,
>> > "mas": "http://standards.iso.org/iso/19115/-3/mas/1.0&quot;,
>> > "mrd": "http://standards.iso.org/iso/19115/-3/mrd/1.0&quot;,
>> > "mrc": "http://standards.iso.org/iso/19115/-3/mrc/2.0&quot;,
>> > "mpc": "http://standards.iso.org/iso/19115/-3/mpc/1.0&quot;,
>> > "mex": "http://standards.iso.org/iso/19115/-3/mex/1.0&quot;,
>> > "pre": "http://standards.iso.org/iso/19135/-2/pre/1.0&quot;,
>> > "mri": "http://standards.iso.org/iso/19115/-3/mri/1.0&quot;,
>> > "gfc": "http://standards.iso.org/iso/19110/gfc/1.1&quot;,
>> > "mrl": "http://standards.iso.org/iso/19115/-3/mrl/2.0&quot;,
>> > "mdb": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
>> > "mrs": "http://standards.iso.org/iso/19115/-3/mrs/1.0&quot;,
>> > "srv": "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;,
>> > "dqc": "http://standards.iso.org/iso/19157/-2/dqc/1.0&quot;,
>> > "mdq": "http://standards.iso.org/iso/19157/-2/mdq/1.0&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": [
>> > "schematron-rules-inspire.xsl",
>> > "schematron-rules-iso.xsl"
>> > ],
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.5.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "iso19139",
>> > "titles": {
>> > "en": "Geographic information -- Metadata (iso19139:2007)",
>> > "fr": "Information géographique -- Métadonnées (iso19139:2007)"
>> > },
>> > "descriptions": {
>> > "en": "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."
>> > },
>> > "standardUrl":
>> > "
>> >
>>
https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798\\n
>> >
>> > ",
>> > "targetNamespace": "http://www.isotc211.org/2005/gmd&quot;,
>> > "namespaces": {
>> > "gco": "http://www.isotc211.org/2005/gco&quot;,
>> > "gmx": "http://www.isotc211.org/2005/gmx&quot;,
>> > "xml": "http://www.w3.org/XML/1998/namespace&quot;,
>> > "gss": "http://www.isotc211.org/2005/gss&quot;,
>> > "srv": "http://www.isotc211.org/2005/srv&quot;,
>> > "gts": "http://www.isotc211.org/2005/gts&quot;,
>> > "gsr": "http://www.isotc211.org/2005/gsr&quot;,
>> > "gml": "http://www.opengis.net/gml/3.2&quot;,
>> > "gmd": "http://www.isotc211.org/2005/gmd&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": [
>> > "schematron-rules-url-check.xsl",
>> > "schematron-rules-inspire-sds.xsl",
>> > "schematron-rules-geonetwork.xsl",
>> > "schematron-rules-inspire.xsl",
>> > "schematron-rules-iso.xsl",
>> > "schematron-rules-inspire-strict.xsl"
>> > ],
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "dublin-core",
>> > "titles": {
>> > "en": "Dublin core"
>> > },
>> > "descriptions": {},
>> > "standardUrl": "http://dublincore.org/documents/dces/&quot;,
>> > "targetNamespace": null,
>> > "namespaces": {
>> > "": "http://purl.org/dc/dcmitype/&quot;,
>> > "dct": "http://purl.org/dc/terms/&quot;,
>> > "xml": "http://www.w3.org/XML/1998/namespace&quot;,
>> > "dc": "http://purl.org/dc/elements/1.1/&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": ,
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "csw-record",
>> > "titles": {
>> > "en": "Dublin core (for CSW only)"
>> > },
>> > "descriptions": {},
>> > "standardUrl": null,
>> > "targetNamespace": "http://www.opengis.net/cat/csw/2.0.2&quot;,
>> > "namespaces": {
>> > "dct": "http://purl.org/dc/terms/&quot;,
>> > "csw": "http://www.opengis.net/cat/csw/2.0.2&quot;,
>> > "ows": "http://www.opengis.net/ows&quot;,
>> > "dc": "http://purl.org/dc/elements/1.1/&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": ,
>> > "version": "2.0.2",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "iso19110",
>> > "titles": {
>> > "en": "Geographic information -- Methodology for feature
>> > cataloguing",
>> > "fr": "Information géographique -- Méthodologie de catalogage
>> > des entités"
>> > },
>> > "descriptions": {},
>> > "standardUrl": "\n
>> >
>> >
>>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965\\n
>> >
>> > ",
>> > "targetNamespace": "http://www.isotc211.org/2005/gfc&quot;,
>> > "namespaces": {
>> > "": "http://www.isotc211.org/2005/gss&quot;,
>> > "gco": "http://www.isotc211.org/2005/gco&quot;,
>> > "gmx": "http://www.isotc211.org/2005/gmx&quot;,
>> > "gfc": "http://www.isotc211.org/2005/gfc&quot;,
>> > "gml": "http://www.opengis.net/gml&quot;,
>> > "gts": "http://www.isotc211.org/2005/gts&quot;,
>> > "gsr": "http://www.isotc211.org/2005/gsr&quot;,
>> > "gmd": "http://www.isotc211.org/2005/gmd&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": ,
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": "iso19139"
>> > }
>> > ]
>> >
>> > - - - - - - -
>> >
>> > Do I have to load the missing schemas on GeoNetwork or do I have to
>> > perform some post processing on ERDDAP WAF endpoint in order to let
>> > GeoNetwork perform a smooth harvesting?
>> >
>> > With Best Regards,
>> > Pierpaolo Culurciello
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > GeoNetwork-users mailing list
>> > GeoNetwork-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> > GeoNetwork OpenSource is maintained at
>> > http://sourceforge.net/projects/geonetwork
>> >
>>
>>
>> --
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Vriendelijke groeten / Kind regards,Jose García
>> <http://www.geocat.net/&gt;Veenderweg 136721 WD BennekomThe NetherlandsT:
+31
>> (0)318 416664 <+31318416664>Please consider the environment before
printing
>> this email.*
>>
>> _______________________________________________
>> GeoNetwork-users mailing list
>> GeoNetwork-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> GeoNetwork OpenSource is maintained at
>> http://sourceforge.net/projects/geonetwork
>>

Hi Francois,

I can confirm that the manual import on my GeoNetwork instance works as well!

https://geonetwork.ve.ismar.cnr.it/geonetwork/srv/eng/catalog.search#/metadata/cnr_ismar_b37f_8e81_db5d

There are mainly aestethic differences with your instance maybe due to
the interface customization.
However, if I also check the "validate" box the import fails with the
errors below:

- - - - -

IllegalArgumentException

XSDValidationErrorEx : XSD Validation error(s): <xsderrors> <error>
<typeOfError>ERROR</typeOfError> <errorNumber>1</errorNumber>
<message>cvc-complex-type.2.4.a: Invalid content was found starting
with element 'srv:couplingType'. One of
'{"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:serviceTypeVersion,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:accessProperties,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:couplingType,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:coupledResource,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operatedDataset,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:profile,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:serviceStandard,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:containsOperations,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operatesOn,
"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:containsChain\}' is
expected. (Element: srv:couplingType with parent element:
srv:SV_ServiceIdentification)</message>
<xpath>mdb:identificationInfo[2]/srv:SV_ServiceIdentification/srv:couplingType</xpath> </error> <error> <typeOfError>ERROR</typeOfError> <errorNumber>2</errorNumber> <message>cvc-complex-type.2.4.a: Invalid content was found starting with element 'srv:operationName'. One of '{"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operationName\}' is expected. (Element: srv:operationName with parent element: srv:SV_OperationMetadata)</message> <xpath>mdb:identificationInfo[2]/srv:SV_ServiceIdentification/srv:containsOperations/srv:SV_OperationMetadata/srv:operationName</xpath> </error> <error> <typeOfError>ERROR</typeOfError> <errorNumber>3</errorNumber> <message>cvc-complex-type.2.4.a: Invalid content was found starting with element 'srv:couplingType'. One of '{"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:serviceTypeVersion, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:accessProperties, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:couplingType, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:coupledResource, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operatedDataset, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:profile, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:serviceStandard, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:containsOperations, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operatesOn, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:containsChain\}' is expected. (Element: srv:couplingType with parent element: srv:SV_ServiceIdentification)</message> <xpath>mdb:identificationInfo[3]/srv:SV_ServiceIdentification/srv:couplingType</xpath> </error> <error> <typeOfError>ERROR</typeOfError> <errorNumber>4</errorNumber> <message>cvc-complex-type.2.4.a: Invalid content was found starting with element 'srv:operationName'. One of '{"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operationName\}' is expected. (Element: srv:operationName with parent element: srv:SV_OperationMetadata)</message> <xpath>mdb:identificationInfo[3]/srv:SV_ServiceIdentification/srv:containsOperations/srv:SV_OperationMetadata/srv:operationName</xpath> </error> <error> <typeOfError>ERROR</typeOfError> <errorNumber>5</errorNumber> <message>cvc-complex-type.2.4.a: Invalid content was found starting with element 'srv:couplingType'. One of '{"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:serviceTypeVersion, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:accessProperties, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:couplingType, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:coupledResource, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operatedDataset, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:profile, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:serviceStandard, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:containsOperations, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operatesOn, "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:containsChain\}' is expected. (Element: srv:couplingType with parent element: srv:SV_ServiceIdentification)</message> <xpath>mdb:identificationInfo[4]/srv:SV_ServiceIdentification/srv:couplingType</xpath> </error> <error> <typeOfError>ERROR</typeOfError> <errorNumber>6</errorNumber> <message>cvc-complex-type.2.4.a: Invalid content was found starting with element 'srv:operationName'. One of '{"http://standards.iso.org/iso/19115/-3/srv/2.1&quot;:operationName\}' is expected. (Element: srv:operationName with parent element: srv:SV_OperationMetadata)</message> <xpath>mdb:identificationInfo[4]/srv:SV_ServiceIdentification/srv:containsOperations/srv:SV_OperationMetadata/srv:operationName</xpath> </error>
</xsderrors>

- - - - -

Can you suggest me a pipeline in order to automate the import on
GeoNetwork of the ERDDAP WAF endpoints?
I would like to be able to scrape a directory like this:

https://opendap.co-ops.nos.noaa.gov/erddap/metadata/iso19115/xml/

and to find the datasets in GeoNetwork.
Maybe I should upload the XML files in a path into GeoNetwork and then
use the manual import selecting the "import a set of files from a
folder on the server" or is there a clever solution?

Best regards,
Pierpaolo

Quoting Francois Prunayre <fx.prunayre@anonymised.com>:

Hi Pierpaolo

Open the import panel, select your XML and choose the conversion in the list
https://geonetwork-opensource.org/manuals/4.0.x/en/user-guide/describing-information/importing-metadata.html
so you can first test that you can import this type of record.

It looks to be ok eg.
https://apps.titellus.net/geonetwork/srv/eng/catalog.search#/metadata/cnr_ismar_b37f_8e81_db5d

Cheers.
Francois

Le mer. 2 mars 2022 à 18:49, Pierpaolo Culurciello <
pierpaolo.culurciello@anonymised.com> a écrit :

Hello Francois and Jose,

and thanks for your quick replies!
I was on holiday and so I beg your pardon for answering only a few days
later.
I am not very familiar with metadata schemas, I am trying to publish
scientific datasets originally on THREDDS and ERDDAP servers from a
central catalogue (GeoNetwork) and I am exploring the available
alternatives.
WAF harvesting seemed to me a good choice because ERDDAP automatically
builds the WAF endpoint URL for all the datasets (in my case it is
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/) and I
thought it worked "out of the box".
Anyway this can became a good opportunity to dig further into metadata
schemas and so if you could give me a couple of advices on how to
perform the ISO19139-to-ISO19115-3-2018 transformation I'd really
appreciate it.
I found on my GeoNetwork instance a mapping file:

/usr/local/tomcat/webapps/geonetwork/WEB-INF/data/config/schema_plugins/iso19115-3.2018/convert/ISO19139/fromISO19139.xsl

but I honestly don't know how to use it to perform the conversion and
I was neither able to find some guides on the web.

With Best Regards,
Pierpaolo Culurciello

Quoting Francois Prunayre <fx.prunayre@anonymised.com>:

> Hi, so those records are using ISO19115-2 for imagery dataset. This is
only
> supported using ISO19115-3 in GeoNetwork. So using a transformation
> "ISO19139-to-ISO19115-3-2018" could have worked but unfortunately is not
an
> option of the WAF harvester.
>
> You can first give a try importing manually one record with that
conversion
> to see if it works.
>
> Cheers.
> Francois
>
> Le lun. 28 févr. 2022 à 12:26, Jose Garcia via GeoNetwork-users <
> geonetwork-users@lists.sourceforge.net> a écrit :
>
>> Hi Pierpaolo
>>
>> The metadata starts with this element gmi:MI_Metadata, that doesn't
>> correspond to any metadata schema bundled in GeoNetwork.
>>
>> Regards,
>> Jose García
>>
>> On Sat, Feb 26, 2022 at 4:53 PM Pierpaolo Culurciello via
GeoNetwork-users
>> <
>> geonetwork-users@lists.sourceforge.net> wrote:
>>
>> >
>> > Dear all,
>> >
>> > I am trying to harvest the native WAF endpoint of an ERDDAP instance
>> > from GeoNetwork 3.10.6.
>> > The harvesting finishes without error but in the log file clearly
>> > states that no metadata have been imported because of missing schemas:
>> >
>> > - - - - - - - -
>> >
>> > 2022-02-26T12:58:00,907+0000 INFO [ERDDAP] - Starting harvesting of
>> ERDDAP
>> > 2022-02-26T12:58:00,907+0000 DEBUG [ERDDAP] - AbstractHarvester login:
>> > ownerId = 116
>> > 2022-02-26T12:58:01,075+0000 INFO [ERDDAP] - Started harvesting from
>> > node : ERDDAP (WebDavHarvester)
>> > 2022-02-26T12:58:01,076+0000 INFO [ERDDAP] - WebDav doHarvest start
>> > 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Retrieving remote
>> > metadata information for : ERDDAP
>> > 2022-02-26T12:58:01,091+0000 DEBUG [ERDDAP] - Scanning resource :
>> > https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/
>> > 2022-02-26T12:58:01,132+0000 DEBUG [ERDDAP] - Remote files found : 1
>> > 2022-02-26T12:58:01,132+0000 INFO [ERDDAP] - Start of alignment for :
>> > ERDDAP
>> > 2022-02-26T12:58:01,162+0000 DEBUG [ERDDAP] - Getting remote file :
>> >
>>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
>> > 2022-02-26T12:58:01,170+0000 DEBUG [ERDDAP] - Record got:
>> > <gmi:MI_Metadata xmlns:gmi="http://www.isotc211.org/2005/gmi&quot;
>> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
>> > xmlns:xlink="http://www.w3.org/1999/xlink&quot;
>> > xmlns:gco="http://www.isotc211.org/2005/gco&quot;
>> > xmlns:gmd="http://www.isotc211.org/2005/gmd&quot;
>> > xmlns:gmx="http://www.isotc211.org/2005/gmx&quot;
>> > xmlns:gml="http://www.opengis.net/gml/3.2&quot;
>> > xmlns:gss="http://www.isotc211.org/2005/gss&quot;
>> > xmlns:gts="http://www.isotc211.org/2005/gts&quot;
>> > xmlns:gsr="http://www.isotc211.org/2005/gsr&quot;
>> > xmlns:srv="http://www.isotc211.org/2005/srv&quot;
>> > xsi:schemaLocation="https://www.isotc211.org/2005/gmi
>> > https://data.noaa.gov/resources/iso19139/schema.xsd&quot;&gt;
>> > <gmd:fileIdentifier>
>> >
<gco:CharacterString>cnr_ismar_b37f_8e81_db5d</gco:CharacterString>
>> > </gmd:fileIdentifier>
>> >
>> > ### OMITTED FOR BREVITY ###
>> >
>> > </gmi:MI_Metadata>
>> > 2022-02-26T12:58:01,172+0000 WARN [ERDDAP] - Skipping metadata with
>> > unknown schema. Path is :
>> >
>>
https://erddap.ve.ismar.cnr.it/erddap/metadata/iso19115/xml/cnr_ismar_b37f_8e81_db5d_iso19115.xml
>> > 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - End of alignment for :
>> ERDDAP
>> > 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - WebDav doHarvest end
>> > 2022-02-26T12:58:01,172+0000 INFO [ERDDAP] - Ended harvesting from
>> > node : ERDDAP (WebDavHarvester)
>> >
>> > - - - - - - - -
>> >
>> > Here's the json repsonse to the query to the GeoNetwork API exposing
>> > the loaded schemas
>> > (
>> >
>>
https://geonetwork.ve.ismar.cnr.it/geonetwork/doc/api/index.html#/identifiers/getIdentifiers
>> > ):
>> >
>> > - - - - -
>> >
>> > [
>> > {
>> > "name": "iso19115-3.2018",
>> > "titles": {
>> > "en": "Geographic information -- Metadata",
>> > "fr": "Information géographique -- Métadonnées"
>> > },
>> > "descriptions": {
>> > "en": "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
>> > <
>> >
>>
http://cnig.gouv.fr/wp-content/uploads/2015/06/titellus_fx_prunayre_iso19115-3_inspire2015.pdf
>> >`_
>> > This standard is maintained on
>> > https://github.com/metadata101/iso19115-3.2018 and is available by
>> > default in GeoNetwork 3.8+. The TC211 is maintaining the XSD for this
>> > standard on https://github.com/ISO-TC211/XML. Example of catalogues
>> using
>> > this standard: - `Metawal - Catalogue pour l'information géographique
de
>> > Wallonie <http://metawal.wallonie.be/&gt;\`\_ 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.
>> > .. figure:: img/metawal-tramedesaxes.png - `Sextant - Checkpoints <
>> > https://sextant.ifremer.fr/&gt;\`\_ is using ISO19115-3 for data quality
>> > description of Specification / Products and upstream data. .. figure::
>> > img/sextant-checkpoint.png",
>> > "fr": "L’objectif de l’ISO 19115 est de fournir un modèle
>> > destiné à décrire des informations ou des ressources pouvant avoir des
>> > étendues géographiques. Cette partie de l’ISO 19115 est destinée à
>> > être utilisée, entre autres, par des analystes de systèmes
>> > d’informations, des planificateurs de programmes et des développeurs
>> > de systèmes d’informations, dans le but de définir des principes de
>> > base et des exigences permettant d’établir une description normalisée
>> > des ressources d’informations. Cette partie de l’ISO 19115 définit les
>> > éléments de métadonnées, leurs propriétés et les relations entre les
>> > éléments et établit un ensemble commun de terminologies, de
>> > définitions et de procédures d’extension concernant les métadonnées. 
>> > Bien que cette partie de l’ISO 19115 ait pour but principal de décrire
>> > les informations numériques qui ont une étendue géographique, elle
>> > peut être utilisée pour décrire tous les types de ressources, y
>> > compris les documents textuels, les initiatives, les logiciels, les
>> > informations non géographiques, les spécifications de produit et les
>> > entrepôts de données, c’est-à-dire qu’elle peut même être utilisée
>> > pour décrire des ressources d’informations n’ayant aucune étendue
>> > géographique. Certains domaines ont leurs propres normes de
>> > métadonnées, telles que celles du Dublin Core pour les bibliothèques.
>> > Si besoin, des profils de telles normes et de cette partie de l’ISO
>> > 19115 pourraient être développés pour créer un Schéma Communautaire.
>> > Ce schéma est également composé des normes : - ISO19110 pour les
>> > modèles de données - ISO19115-2 pour l'imagerie - ISO19157 pour la
>> > qualité des données"
>> > },
>> > "standardUrl":
>> > "
>> >
>>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32579
>> > ",
>> > "targetNamespace": "
http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
>> > "namespaces": {
>> > "dqm": "http://standards.iso.org/iso/19157/-2/dqm/1.0&quot;,
>> > "gml": "http://www.opengis.net/gml/3.2&quot;,
>> > "fcc": "http://standards.iso.org/iso/19110/fcc/1.0&quot;,
>> > "mmi": "http://standards.iso.org/iso/19115/-3/mmi/1.0&quot;,
>> > "mcc": "http://standards.iso.org/iso/19115/-3/mcc/1.0&quot;,
>> > "msr": "http://standards.iso.org/iso/19115/-3/msr/2.0&quot;,
>> > "mac": "http://standards.iso.org/iso/19115/-3/mac/2.0&quot;,
>> > "cit": "http://standards.iso.org/iso/19115/-3/cit/2.0&quot;,
>> > "gmw": "http://standards.iso.org/iso/19115/-3/gmw/1.0&quot;,
>> > "gco": "http://standards.iso.org/iso/19115/-3/gco/1.0&quot;,
>> > "reg": "http://standards.iso.org/iso/19135/-2/reg/1.0&quot;,
>> > "xml": "http://www.w3.org/XML/1998/namespace&quot;,
>> > "cat": "http://standards.iso.org/iso/19115/-3/cat/1.0&quot;,
>> > "mco": "http://standards.iso.org/iso/19115/-3/mco/1.0&quot;,
>> > "lan": "http://standards.iso.org/iso/19115/-3/lan/1.0&quot;,
>> > "gex": "http://standards.iso.org/iso/19115/-3/gex/1.0&quot;,
>> > "gcx": "http://standards.iso.org/iso/19115/-3/gcx/1.0&quot;,
>> > "mas": "http://standards.iso.org/iso/19115/-3/mas/1.0&quot;,
>> > "mrd": "http://standards.iso.org/iso/19115/-3/mrd/1.0&quot;,
>> > "mrc": "http://standards.iso.org/iso/19115/-3/mrc/2.0&quot;,
>> > "mpc": "http://standards.iso.org/iso/19115/-3/mpc/1.0&quot;,
>> > "mex": "http://standards.iso.org/iso/19115/-3/mex/1.0&quot;,
>> > "pre": "http://standards.iso.org/iso/19135/-2/pre/1.0&quot;,
>> > "mri": "http://standards.iso.org/iso/19115/-3/mri/1.0&quot;,
>> > "gfc": "http://standards.iso.org/iso/19110/gfc/1.1&quot;,
>> > "mrl": "http://standards.iso.org/iso/19115/-3/mrl/2.0&quot;,
>> > "mdb": "http://standards.iso.org/iso/19115/-3/mdb/2.0&quot;,
>> > "mrs": "http://standards.iso.org/iso/19115/-3/mrs/1.0&quot;,
>> > "srv": "http://standards.iso.org/iso/19115/-3/srv/2.1&quot;,
>> > "dqc": "http://standards.iso.org/iso/19157/-2/dqc/1.0&quot;,
>> > "mdq": "http://standards.iso.org/iso/19157/-2/mdq/1.0&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": [
>> > "schematron-rules-inspire.xsl",
>> > "schematron-rules-iso.xsl"
>> > ],
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.5.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "iso19139",
>> > "titles": {
>> > "en": "Geographic information -- Metadata (iso19139:2007)",
>> > "fr": "Information géographique -- Métadonnées (iso19139:2007)"
>> > },
>> > "descriptions": {
>> > "en": "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."
>> > },
>> > "standardUrl":
>> > "
>> >
>>
https://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798\\n
>> >
>> > ",
>> > "targetNamespace": "http://www.isotc211.org/2005/gmd&quot;,
>> > "namespaces": {
>> > "gco": "http://www.isotc211.org/2005/gco&quot;,
>> > "gmx": "http://www.isotc211.org/2005/gmx&quot;,
>> > "xml": "http://www.w3.org/XML/1998/namespace&quot;,
>> > "gss": "http://www.isotc211.org/2005/gss&quot;,
>> > "srv": "http://www.isotc211.org/2005/srv&quot;,
>> > "gts": "http://www.isotc211.org/2005/gts&quot;,
>> > "gsr": "http://www.isotc211.org/2005/gsr&quot;,
>> > "gml": "http://www.opengis.net/gml/3.2&quot;,
>> > "gmd": "http://www.isotc211.org/2005/gmd&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": [
>> > "schematron-rules-url-check.xsl",
>> > "schematron-rules-inspire-sds.xsl",
>> > "schematron-rules-geonetwork.xsl",
>> > "schematron-rules-inspire.xsl",
>> > "schematron-rules-iso.xsl",
>> > "schematron-rules-inspire-strict.xsl"
>> > ],
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "dublin-core",
>> > "titles": {
>> > "en": "Dublin core"
>> > },
>> > "descriptions": {},
>> > "standardUrl": "http://dublincore.org/documents/dces/&quot;,
>> > "targetNamespace": null,
>> > "namespaces": {
>> > "": "http://purl.org/dc/dcmitype/&quot;,
>> > "dct": "http://purl.org/dc/terms/&quot;,
>> > "xml": "http://www.w3.org/XML/1998/namespace&quot;,
>> > "dc": "http://purl.org/dc/elements/1.1/&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": ,
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "csw-record",
>> > "titles": {
>> > "en": "Dublin core (for CSW only)"
>> > },
>> > "descriptions": {},
>> > "standardUrl": null,
>> > "targetNamespace": "http://www.opengis.net/cat/csw/2.0.2&quot;,
>> > "namespaces": {
>> > "dct": "http://purl.org/dc/terms/&quot;,
>> > "csw": "http://www.opengis.net/cat/csw/2.0.2&quot;,
>> > "ows": "http://www.opengis.net/ows&quot;,
>> > "dc": "http://purl.org/dc/elements/1.1/&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": ,
>> > "version": "2.0.2",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": null
>> > },
>> > {
>> > "name": "iso19110",
>> > "titles": {
>> > "en": "Geographic information -- Methodology for feature
>> > cataloguing",
>> > "fr": "Information géographique -- Méthodologie de catalogage
>> > des entités"
>> > },
>> > "descriptions": {},
>> > "standardUrl": "\n
>> >
>>
http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965\\n
>> >
>> > ",
>> > "targetNamespace": "http://www.isotc211.org/2005/gfc&quot;,
>> > "namespaces": {
>> > "": "http://www.isotc211.org/2005/gss&quot;,
>> > "gco": "http://www.isotc211.org/2005/gco&quot;,
>> > "gmx": "http://www.isotc211.org/2005/gmx&quot;,
>> > "gfc": "http://www.isotc211.org/2005/gfc&quot;,
>> > "gml": "http://www.opengis.net/gml&quot;,
>> > "gts": "http://www.isotc211.org/2005/gts&quot;,
>> > "gsr": "http://www.isotc211.org/2005/gsr&quot;,
>> > "gmd": "http://www.isotc211.org/2005/gmd&quot;,
>> > "xlink": "http://www.w3.org/1999/xlink&quot;
>> > },
>> > "readwriteUUID": false,
>> > "schematronRules": ,
>> > "version": "1.0",
>> > "appMinorVersionSupported": "3.4.0",
>> > "appMajorVersionSupported": null,
>> > "dependsOn": "iso19139"
>> > }
>> > ]
>> >
>> > - - - - - - -
>> >
>> > Do I have to load the missing schemas on GeoNetwork or do I have to
>> > perform some post processing on ERDDAP WAF endpoint in order to let
>> > GeoNetwork perform a smooth harvesting?
>> >
>> > With Best Regards,
>> > Pierpaolo Culurciello
>> >
>> > _______________________________________________
>> > GeoNetwork-users mailing list
>> > GeoNetwork-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> > GeoNetwork OpenSource is maintained at
>> > http://sourceforge.net/projects/geonetwork
>> >
>>
>> --
>>
>> *Vriendelijke groeten / Kind regards,Jose García
>> <http://www.geocat.net/&gt;Veenderweg 136721 WD BennekomThe NetherlandsT:
+31
>> (0)318 416664 <+31318416664>Please consider the environment before
printing
>> this email.*
>>
>> _______________________________________________
>> GeoNetwork-users mailing list
>> GeoNetwork-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> GeoNetwork OpenSource is maintained at
>> http://sourceforge.net/projects/geonetwork
>>