allow to alter metadata extracted from wms-capabilities

[pvgenuchten]

a typical geonetwork usecase is a harvest of metadata from wms-capabilities. The user then wants to complete the metadata using geonetwork. A next time a harvester runs, it should not replace the manual alterations, but it would be nice if it would update the dynamic fields such as data-bounds etc

[pvgenuchten]

the current "allow to modify metadata" in the harvester config may give the impression to users that this feature is already available. But (as I understood) metadata changes are currently overwritten by the next harvest.

[fxprunayre]

the current "allow to modify metadata" in the harvester config may give the impression to users that this feature is already available. But (as I understood) metadata changes are currently overwritten by the next harvest.

So maybe we could start by adding a clear help message below the settings "Allow editing on harvested records" to warn user.

Then for the harvesting process, maybe we could have a similar approach to the Talend Spatial crawler (https://github.com/talend-spatial/workspace-metadata-crawler):

• first run : create complete metadata record for each resources
• second run : if in UPDATE mode, only update existing resources.

The UPDATE mode is based on a list of XPATH to update and use CSW Transaction for the crawler. For OGC/WxS harvester, we could use the XPATH API and config could be something like:

• XPATH of the value to extract in the Capabilities,
• XPATH of the insertion point in ISO19139 records

What do you think ?

[landryb]

My understanding was that the resulting MD wasn't editable, and that all the values you wanted to be in the MD should be in the GetCapabilities content, or eventually tweaked via a custom xsl process ?