Items Inherit Unit- and Collection-level Staff and Special Access Roles

[joncameron]

Inherit Staff Roles and Special Access from unit/collection at the item level (instead of storing them all at the item level); includes display of default value for Special Access from collection and allows adding more at the item level.

• "Assign special access" reparented to not be under "Set Default Access for New Items"
• special access at the collection level automatically applies to items in the collection
• inheritance is additive but not allowed to be subtractive (no removing users from an item who have access set at the parent level)
• Change display of "special access" form for media object edit pages

[joncameron]

There are use cases that need to be attended to for certain items being disallowed, or for items having different access levels than for each other that should be considered.

[elynema]

There were a couple of use cases identified as the MCO working group meeting on 12/16 around restricting some items within a collection. https://docs.google.com/document/d/1SiLrhPGRw9fNpBDpp7kEXSnz6nQ_yQKmKTvscYZCoYE/edit?tab=t.0#heading=h.hovomqs9sk4k

use case:

• some items within a collection may need to be specially restricted so that future users given special access to the collection do not gain access to those items (ex: extremely graphic violence). Currently, this could potentially be accomplished by removing a user at the item level or unpublishing the item. There might be other better solutions for this.
• Within some collections, there are valid reasons for items to have different item access levels. For example, the collection may default to IU Only, as an MDPI collection, but perhaps some items have been through copyright evaluation and can be made accessible to the public. In this case, we could not apply a single generic access level from the collection down to all items.