User with Editor role can't see private collection

[VivianChu]

Descriptive summary

For Hyrax 2.0.0.beta1, User with Editor role can't see a private collection created by other Users.
For Hyrax 2.0.0.alpha, Editor user can see private collection fine.

Hyrax 2.0.0.beta1

For Hyrax 2.0.0.alpha

Rationale

To have same editor function as previous hyrax version.

Expected behavior

Editor User can see private collection created by Admin or other Users.

Actual behavior

Editor User can't see private collection.

Steps to reproduce the behavior

1. Log in as admin
2. Create a new collection, select private visibility
3. Log out
4. Log in as editor
5. Go to Dashboard: Collections: All collections
6. Click on a new collection created by admin user
7. Should see message "You are not authorized to access this page"

[mjgiarlo]

Fixed by #1760

[mjgiarlo]

This only fixed the behavior for administrative users. Reopening.

[mjgiarlo]

Refs samvera-labs/nurax-pre2023#96

[elrayle]

Hyrax 1.0 - 2.0.0.rc1

In Hyrax 2.0, you cannot see collections you did not create through Dashboard -> Collections -> Your Collections. I am fairly certain that has been the case for all releases (alpha - beta - rc) of Hyrax. In Sufia, you could see collections shared with you on the 'Shared with me' tab.

In your steps to reproduce, you reference the All Collections tab. That tab is only shown to admin users. Perhaps your expectation that this used to work in alpha was because the test was done with an editor who was also an admin user.

Hyrax collections-sprint branch

In collections-sprint branch, we have added an additional Managed Collections tab to Dashboard -> Collections. On that tab, you see collections for which you were granted :manage, :deposit, or :view access. Users will be able to view the admin show page for a collection if they have any of these access levels granted.

[elrayle]

FYI... works have the same issue where there is no way to see works shared with you through Dashboard -> Works

FYI... There were previous discussions about incorporating Managed Collections and Managed Works into Hyrax 2.0 branch, but the consensus at the time was not to include it as it was too much new work and we were very close to a 2.0 release. This will be fixed in 2.1 when collections-sprint branch is merged into master.