Skip to content

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

Open
josegar74 wants to merge 1 commit intomainfrom
44-owner-edit-privilege
Open

Setting to configure whether editor users who are metadata owners can edit their metadata when they do not have editing privileges for the metadata.#8631
josegar74 wants to merge 1 commit intomainfrom
44-owner-edit-privilege

Conversation

@josegar74
Copy link
Member

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.

edit-owner-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

@josegar74 josegar74 added this to the 4.4.7 milestone Jan 30, 2025
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

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

See analysis details on SonarQube Cloud

juanluisrp added a commit to eea/geonetwork-eea that referenced this pull request Feb 13, 2025
@josegar74 josegar74 modified the milestones: 4.4.7, 4.4.8 Apr 10, 2025
@josegar74 josegar74 modified the milestones: 4.4.8, 4.4.9 May 28, 2025
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

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

See analysis details on SonarQube Cloud

@jahow jahow modified the milestones: 4.4.9, 4.4.10 Oct 7, 2025
… edit their metadata when they do not have editing privileges for the metadata.
@juanluisrp juanluisrp force-pushed the 44-owner-edit-privilege branch from 5a6e21d to 032b888 Compare March 9, 2026 19:09
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 9, 2026

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

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.

2 participants