Skip to content

Instantly share code, notes, and snippets.

@mjgiarlo
Created March 14, 2017 23:01
Show Gist options
  • Save mjgiarlo/1945fa8a6f50eef2f9268af34f34dd47 to your computer and use it in GitHub Desktop.
Save mjgiarlo/1945fa8a6f50eef2f9268af34f34dd47 to your computer and use it in GitHub Desktop.
Comments on Understanding Admin Sets Participants

Here are the divergences I found with https://github.com/projecthydra/sufia/wiki/Understanding-Admin-Sets-Participants

Admin Set Managers

  1. Admin Set managers can not currently edit Admin Set metadata until they are elevated to repository administrators. This is because only repository administrators can access the Admin Set edit UI, which is under /admin/. When an Admin Set manager deposits to an Admin Set, they have edit access.
  2. Admin Set managers can not edit works simply by virtue of being Admin Set managers; this is controlled by the work's ACLs still.

These two are yet-to-be-implemented features.

Admin Set Depositors

  1. Admin Set depositors can only edit works in an Admin Set if they have deposited the works themselves.

I think this is as we want it to be.

Admin Set Viewers

  1. Admin Set viewers can not view works simply by virtue of being Admin Set viewers.

This is a yet-to-be-implemented feature.

@mjgiarlo
Copy link
Author

In reply to your former comment...

  1. Building on the other comments, the plan in Hyrax is to leverage the combined user/admin dashboard and grant Admin Set Managers access to manage admin sets in this UI. Inclination is to work on this in Hyrax since I don't think this feature is in scope for 7.3.0 (now that we're in the release candidate phase).
  2. My take here is that an Admin Set Manager should have the ability to edit all works in an Admin Set, and I'm ambivalent regarding whether we implemented that in persisted ACLs or Ability logic. Inclination is to work on this in Hyrax since I don't think this feature is in scope for 7.3.0 (now that we're in the release candidate phase).
  3. Yes, this is the case now.
  4. It sounds like we're on the same page here. Inclination is to work on this in Hyrax since I don't think this feature is in scope for 7.3.0 (now that we're in the release candidate phase).

@mjgiarlo
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment