You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've chosen webarchive.org.uk/act/targets/86223 as an example of a watched target, owned by the NLS Curator
With an Archivist role, I can deselect the target and add a revision log
As you can see, it no longer appears in the list of Watched Targets for the user (would have been first on list)
Changing the target again so that it's now selected and Watched. However, as I am not the owner of the target I am unable to include extra metadata (which is correct).
Could this a potential issue as a Watched Target could be deselected then selected again without the Target owner's knowledge and missing the required information:
As opposed to the original metadata:
Creating and changing a Watched Target for a Target I own looks as though it's working as expected:
@crarugal actually current issue is related to allow users with archivist role to take over the control of target if the target owner cannot do it (due to some personal reasons, not technical), i.e. in this particular case to (de)select Watched Status of any target. I think your observations could be discussed later and its related to curator permission management logic, so new ticket should be created if agreed. And this issue was tested and should be closed.
@crarugal it's fine that only the Archivist can take control of /reassign a WT. The workflow envisages that we communicate outside of ACT with Target owners about the WT status. Ownership and editorial control of WTs should be a lot more "locked down" than Targets, under the supervisions of the business owners (e.g. Official Publications) and the Archivists.
We've found a Target that appears to be Watched but should not be. Even the Archivist role cannot remedy this, as currently:
This should be reviewed, and the Archivist role should be able to override this.
The text was updated successfully, but these errors were encountered: