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

Create metadata error when using subportals #8251

Open
josegar74 opened this issue Jul 10, 2024 · 1 comment
Open

Create metadata error when using subportals #8251

josegar74 opened this issue Jul 10, 2024 · 1 comment
Milestone

Comments

@josegar74
Copy link
Member

Describe the bug

When creating metadata from a subportals an error can be reported depending on the portal filter:

create-metadata-subportal

To Reproduce
Steps to reproduce the behavior:

  1. Create groups: groupA, groupB
  2. Create users: editorA (Editor in the groupA), editorB (Editor in the groupB)
  3. Create subportals: portalA with filter: groupPublishedId:100 (use the ID of the groupA), portalB with filter: groupPublishedId:101 (use the ID of the groupB)
  4. Load the iso19139 templates and assign them the view privilege to groupA and groupB
  5. With editorA, go to portalA and create a metadata --> OK
  6. With editorA, go to portalB and create a metadata --> An error is displayed. As userA is editor in groupA, the metadata is published to groupA, but the portalB is filtering metadata published to groupB only, causing the error.

Expected behavior

Subportals probably should be disabled for the Editor / Administration modules.

@josegar74 josegar74 added this to the 4.4.6 milestone Jul 10, 2024
@fxprunayre
Copy link
Member

There are some instructions at the end of https://docs.geonetwork-opensource.org/4.4/administrator-guide/configuring-the-catalog/portal-configuration/#creating-a-sub-portal-for-partners which explains a bit how to organize users/groups/portals/templates "one partner = one group = one sub-portal and users are only member of one group" if you want to be able to avoid that cases. Maybe we can be more precise on this.

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

No branches or pull requests

2 participants