How to change dspace authorization policies? -


i'm in process of changing authorization policy large dspace repo filled closed collections. created new group facilitate new access rights , added appropriate users group. finally, edited collection items policy through "advanced policy manager". in exact, added collection x , group y 'default_bitstream_read'.

when browse items of collection see item files have corresponding policy (policy id:822518 - action:default_bitstream_read - eperson: ... - group: groupy)

this means members of groupy should able open bitstream/read file. problem while users in fact able to, can't. there better way edit user authorizations? how debug problem? there proposed tutorial on performing dspace administration tasks?

thank time.

adding new default_* policies collections not effect of existing items. default_* policy settings used create policies when new items added. in other words: items bitstream_read policies informed default_bitstream_read policies of collection at time of adding item.

it sounds system sets default_bitstream_read policy contains groupy. therefore items should have bitstream_read set container group. if true change groupy's members, adding additional users open access bitstreams in closed collection. if so, need make sure, there no unintended consequences. approach not have desired effect, if groupy used in collections should stay closed.


Comments

Popular posts from this blog

angular - Ionic slides - dynamically add slides before and after -

minify - Minimizing css files -

Add a dynamic header in angular 2 http provider -