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

GeoNetwork harvester - avoid double counting of updated metadata. #8389

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

josegar74
Copy link
Member

The counter for updated metadata is updated in updateMetadata method:

But with existing metadata managed by another harvester if the uuid collision policy is set to override, it was updated again in

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

This happens with existing metadata managed by another harvester if the uuid collision policy is set to override
Copy link

sonarcloud bot commented Sep 26, 2024

@josegar74 josegar74 merged commit cfcd829 into main Sep 26, 2024
10 checks passed
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.

2 participants