Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIx importer when md is already validated #312

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

f-necas
Copy link
Collaborator

@f-necas f-necas commented Jan 7, 2025

In 4.2.8 (georchestra 24) we couldn't update with importer a matadata which has already been validated.

Steps to reproduce :
import a metadata and validate it.
Download xml and change title
Re-import with override
Title hasn't changed.

geOrchestra/geonetwork checklist

  • PR only involves cherry-picked commits from upstream.
  • PR contains custom code which will soon be available in an upstream release and can be overriden => 4.4.4
  • PR contains custom geOrchestra code, which need to be verified during future migrations.

@f-necas f-necas requested review from pmauduit and landryb January 7, 2025 12:00
@pmauduit
Copy link
Member

pmauduit commented Jan 7, 2025

upstream fix: geonetwork/core-geonetwork@3444440

@pmauduit
Copy link
Member

pmauduit commented Jan 7, 2025

Not a JPA expert, but looks good ; as already applied to upstream, I guess we can go with it.

@pmauduit pmauduit merged commit 3b68e90 into georchestra-gn4.2.x-24.0 Jan 7, 2025
1 check failed
@pmauduit pmauduit deleted the fix-importer-when-validated branch January 7, 2025 12:36
@MaelREBOUX
Copy link
Member

I can confirm that it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants