Skip to content

Conversation

josegar74
Copy link
Member

Using the metadata uuid for the resource identifier uuid is not recommended. With this change a random UUID is generated in the metadata editor suggestion to generate a resource identifier

Updated the ISO19115-3.2018 suggestion to use the metadata/resourceIdentifierPrefix setting in both processes to generate similar identifiers in both schemas.

Checklist

  • I have read the contribution guidelines
  • Pull request provided for main branch, backports managed with label
  • Good housekeeping of code, cleaning up comments, tests, and documentation
  • Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
  • Clean commit messages, longer verbose messages are encouraged
  • API Changes are identified in commit messages
  • Testing provided for features or enhancements using automatic tests
  • User documentation provided for new features or enhancements in manual
  • Build documentation provided for development instructions in README.md files
  • Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

… use a random UUID instead of use the metadata identifier value.

Use also metadata/resourceIdentifierPrefix setting in both processes to generate similar identifiers in both schemas.
@josegar74 josegar74 added this to the 4.4.9 milestone Sep 8, 2025
@josegar74 josegar74 requested a review from fxprunayre September 8, 2025 13:56
@CLAassistant
Copy link

CLAassistant commented Sep 8, 2025

CLA assistant check
All committers have signed the CLA.

<xsl:variable name="prefix" select="if ($resource-id-url-prefix != '') then $resource-id-url-prefix else $urlWithoutLang"/>
<xsl:variable name="code" select="concat($prefix, /*/mdb:metadataIdentifier/mcc:MD_Identifier/mcc:code/gco:CharacterString)"/>
<!-- Create a random resource identifier -->
<xsl:variable name="resource-id-url-prefix-tmp"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you want to have an option to keep current mechanism and the new one, you can also add a process parameter eg. https://github.com/geonetwork/core-geonetwork/blob/main/schemas/iso19115-3.2018/src/main/plugin/iso19115-3.2018/process/add-info-from-wms.xsl#L143

Image

@jahow
Copy link
Member

jahow commented Oct 2, 2025

@josegar74 I will refrain from including this in 4.4.9 as it may be better to offer a parameter to keep the previous behavior (even though it would be disabled by default). Unless you think this is not necessary and can be merged right away? Thanks

@josegar74 josegar74 modified the milestones: 4.4.9, 4.4.10 Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants