FLVC / flvc

FLVC-specific Islandora Hooks
0 stars 2 forks source link

FLIIRT: Desired XACML behavior: Allow a XACML restriction on object viewing to apply to the collection but NOT be applied to future children #66

Closed wrandtkeflvc closed 6 months ago

wrandtkeflvc commented 7 years ago

Here's desired XACML behavior for the FLIIRT project:

Currently, when someone puts a XACML policy on a collection in Islandora, they have the following options for how to handle children of the collection:

Choosing any of the available options results in a XACML policy being applied to future children of the collection.

That's causing confusion with some desired workflows for FLIIRT. For example, suppose faculty objects are to be open to the public but stored in a collection which is not open to the public. Someone can set that up initially by applying XACML to "New children of this object." But, then when they go to add a new faculty member, the new faculty member has a XACML policy, that's not readily apparent to the librarian, and the librarian will ask why the faculty member isn't showing up publicly. This happens alot and repeat from the same people and is not intuitive.

The desired behavior is to have an option for XACML on a collection to where: It's a restriction on object viewing. It applies to the collection only, but not to current children, and not to future children.