Shapefile metadata persistent identifier (fileIdentifier) is overwriten when uploaded through API

[eblondel]

Expected Behavior

A shapefile + its ISO 19115/19139 XML metadata uploaded through the web API, with a persistent identifier when it is a specified at source in the metadata (fileIdentifier). GeoNode should not overwrite this information with a new identifier (UUID). In case this match an identifier already known from the system, we already get an error which is fine.

Actual Behavior

In previous version of development, the source metadata identifier was persistent and kept by GeoNode (UUID - or any other semantic identifier chosen actually -), which was right. A persistent identifier should not be altered. For data managers it is the way to identify his/her resources in time, and be able to operate update cycles.

Since recent deployment over https://development.demo.geonode.org and https://master.demo.geonode.org the metadata identifier is systematically altered and overwriten by GeoNode, even if the source metadata was already a valid UUID.

Steps to Reproduce the Problem

1. Get this shapefile (and associated ISO 19115 XML file): https://github.com/eblondel/geonode4R/tree/main/inst/extdata/samples
2. Try to upload it with the API

The integration test here (R language) reproduces the full test: https://github.com/eblondel/geonode4R/blob/main/tests/testthat/test_uploads.R

Specifications

https://development.demo.geonode.org
https://master.demo.geonode.org

cc @kikislater @juldebar

[giohappy]

@etj?

[giohappy]

@eblondel I suppose you're talking about the upload of a new resource, and not the upload of the metadata xml for an existing GeoNode resource, right?

[eblondel]

@giohappy thanks for your prompt reply. Yes i refer to a new dataset upload that comes together with its metadata XML (that contains a persistent identifier in it: semantic-based or an UUID already generated prior to its upload)

[eblondel]

@giohappy @etj @kikislater have you been able to look at this?