Open livingstonel opened 4 years ago
Created this issue about the validation in GeoNetwork opensource project as is not only related to HNAP: https://github.com/geonetwork/core-geonetwork/issues/5008
Seem fixed by https://github.com/geonetwork/core-geonetwork/pull/4996
Seem also fixed by https://github.com/geonetwork/core-geonetwork/pull/4996
The working copy is not really related to the metadata status. An alternative is to add a Filter for the metadata with working copy, like, would that solve the issue @livingstonel ?
For brand new record scenario with just a submitted draft the publish (approved by default feature) is worked. It was a admin setting option that needed to be enabled within the workflow config section. ie. "Allow publication of non-approved metadata"
Once fist published and a new work copy is created, validate and then re submitted for review the CR is unable to to access the working copy through any link or any means in the publishing record view. The CR only see the publish record. the Working copy has the following icon (?) unknown copy - "valid status -"
However when going to an account with Admin privileges. The account is able to access the working copy of the submitted record.
@jodygarnett and @josegar74 The issue is not necessarily the filtering option, but simply not be able to access the submit working copy record for review by a CR account for that group.....
@livingstonel I've done this test, using the latest version of the schema and GeoNetwork 3.10.5
Users: editor
and reviewer
editor
creates a metadata, validates it and submits for approval
reviewer
approve and publishes it
editor
edits the metadata, creating a draft copy and validates it:
editor
submits for approval.
reviewer
gets the following in the editor dashboard, with the correct status:
Please check if the steps are the same as yours or there's any difference.
Publication of new drafts: Need re-confirmation – if an editor submits metadata for review, the CR can approve the metadata OR publish (which approves the metadata by default) correct? Or, if the metadata is submitted, the CR must approve THEN publish - separate actions?
Review submission/publish of working copies: problem. As an editor;
As Content Reviewer;
2020-09-05: in testing this afternoon, I've submitted a metadata record "Publication in GeoCat Live - Test 7" (48fcb49e-993f-4eef-bb55-f4c65a50c191) as an editor successfully but the metadata fails to appear for approval/publish in the CR account. Can't account for why this would happen. Workspaces are a match.