Setting to configure whether editor users who are metadata owners can edit their metadata when they do not have editing privileges for the metadata.

[josegar74]

This change adds a new setting to configure whether editor users who are metadata owners can edit their metadata when they do not have editing privileges for the metadata.

By default, the setting is enabled to preserve the original behavior in GeoNetwork: editor users can edit a metadata if they are the owner of the metadata or have editing privileges in any of the groups where they have the editor profile. For most users it is not necessary to change this setting.

When the setting is disabled a user with editor profile can only edit a metadata if has edit privileges in any of the groups where has the Editor role.

The setting doesn't affect Administrator users, that can always edit the metadata.

---

The pull request contains Sonarlint code improvements.

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

• Funded by IFremer

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud