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
Right now, curation requests are created regardless of the whether the uploader is a reviewer or a "regular" user.
Since reviewers can accept and publish their own requests, this effectively just means an unnecessary extra few clicks in their workflow.
To fix that, we could either...
(a) require another reviewer's OK for that, or
(b) allow reviewers to simply publish without review, or
(c) have the system automatically set the review to "accepted" upon creation
The first variant may be desirable for larger teams, but of course breaks if you only have a single reviewer available.
The second and third options are very similar, and probably the simpler (and potentially even more desirable way) to go.
For the needs of TU Wien, I think the third option would be the most convenient.
Then we can configure the test deployment to automatically accept requests in general, without changing the underlying workflow.
The text was updated successfully, but these errors were encountered:
Right now, curation requests are created regardless of the whether the uploader is a reviewer or a "regular" user.
Since reviewers can accept and publish their own requests, this effectively just means an unnecessary extra few clicks in their workflow.
To fix that, we could either...
(a) require another reviewer's OK for that, or
(b) allow reviewers to simply publish without review, or
(c) have the system automatically set the review to "accepted" upon creation
The first variant may be desirable for larger teams, but of course breaks if you only have a single reviewer available.
The second and third options are very similar, and probably the simpler (and potentially even more desirable way) to go.
For the needs of TU Wien, I think the third option would be the most convenient.
Then we can configure the test deployment to automatically accept requests in general, without changing the underlying workflow.
The text was updated successfully, but these errors were encountered: