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 have updated the title to accurately reflect the bug description
Description
The 'update relation field' feature is not available in the author dashboard, even if the author has permission to edit metadata. This feature is unavailable for both preprints in the production stage and preprints that have already been posted.
In the screenshots it is possible to compare the author's point of view (first screenshot) with the moderator point of view (second screenshot)
Steps to Reproduce
Login with an author
Navigate to a pre-print submission
Click on any metadata menu item (i.e: Tile & Abstract)
The 'Relation Status' won't be available to the author visualize or change
Expected Result
When navigating to the pre-print metadata, authors should be able to see and edit their submission 'Relation' field.
Actual Result
OPS is not currently allowing authors to visualise or update the "Relation" field.
Environment Details
No response
Application Version
OPS 3.5
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Valid Title
Description
The 'update relation field' feature is not available in the author dashboard, even if the author has permission to edit metadata. This feature is unavailable for both preprints in the production stage and preprints that have already been posted.
In the screenshots it is possible to compare the author's point of view (first screenshot) with the moderator point of view (second screenshot)
Steps to Reproduce
Expected Result
When navigating to the pre-print metadata, authors should be able to see and edit their submission 'Relation' field.
Actual Result
OPS is not currently allowing authors to visualise or update the "Relation" field.
Environment Details
No response
Application Version
OPS 3.5
Logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: