Hyrax is a Ruby on Rails Engine built by the Samvera community. Hyrax provides a foundation for creating many different digital repository applications.
For Hyrax use case testing steps RA_1.9 in the worksheet, when the Features > Transfer works option is set to Off, an Admin user can see the option to Transfer works but is redirected to a Not Authorized error.
Steps to reproduce the behavior in User Interface (UI)
Login as an Admin user
Navigate to Settings > Features and ensure Transfer works is set to off
Go to Dashboard > Works and select a work you have deposited as an admin user
In the actions menu, select Transfer Ownership of Work
Observe that you are redirected to the homepage with a banner indicating "You are not authorized to access this page."
Actual behavior (include screenshots if available)
Include what version of Hyrax relates to this issue (3.x, 4.x, main branch, etc.) if appropriate, and any relevant error messages/tracebacks if you're reporting a bug.
Sirenia docker image - Hyrax 5 rc2.
Acceptance Criteria/Expected Behavior
[ ] An admin level user should either not see the option to Transfer works, or should see a new screen prompting the selection of a registered user to transfer the work to
[ ] An admin level user should not receive a not authorized error when initially starting this action
Rationale (for feature request only)
Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.
Admin users should be able to transfer works regardless of the Feature setting. This is the behavior noted in the test worksheet and confirmed in dev.nurax.
Related work
Link to related issues or prior related work here.
Descriptive summary
For Hyrax use case testing steps RA_1.9 in the worksheet, when the Features > Transfer works option is set to Off, an Admin user can see the option to Transfer works but is redirected to a Not Authorized error.
Steps to reproduce the behavior in User Interface (UI)
Actual behavior (include screenshots if available)
Include what version of Hyrax relates to this issue (3.x, 4.x, main branch, etc.) if appropriate, and any relevant error messages/tracebacks if you're reporting a bug.
Sirenia docker image - Hyrax 5 rc2.
Acceptance Criteria/Expected Behavior
Rationale (for feature request only)
Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.
Admin users should be able to transfer works regardless of the Feature setting. This is the behavior noted in the test worksheet and confirmed in dev.nurax.
Related work
Link to related issues or prior related work here.