Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Easy Xacml": Preset policies that can be applied from a select list #3

Open
rosiel opened this issue Aug 18, 2015 · 2 comments
Open

Comments

@rosiel
Copy link
Contributor

rosiel commented Aug 18, 2015

The XACML editor is complicated. Many sites have use cases with a limited number of "states" that objects can be in, e.g.:

  • object is invisible to everyone except admin and the object's owner
  • object is invisible to everyone except logged in users
  • metadata is visible to everyone, but OBJ locked down to logged in users or a specific user
  • object and all datastreams are visible to the world.

Why not let a technical site admin configure these policies, then have them accessible to apply to each object from a drop-down list?

This would be similar in concept to the Embargo module, which applies a template XACML datastream, only with more configuration available.

@rosiel
Copy link
Contributor Author

rosiel commented Aug 25, 2015

@whikloj pointed out the islandora_restricted module, which does a similar thing, though using a RELS-EXT relationship instead of XACML and for a hard-coded set of states.
https://github.com/discoverygarden/islandora_restricted

@whikloj
Copy link

whikloj commented Aug 28, 2015

@rosiel we at the U Manitoba use this for a specific collection where you can find the images but can't see them or their metadata without appropriate privileges. It does the job but (as you mention) is not super flexible. (I've made some slight modifications here). If you are interested in it, I can see about getting it released to the community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants