Hi Hendrik, I'm not able to reproduce this behavior on our Demo Site ( http://demo.dspace.org/jspui/), running v6.3. So, I wonder if you've changed something locally that could be affecting this?
A quick note: * First, it seems testing this is only possible in the JSPUI. I don't see a way to even *set* "DEFAULT_BITSTREAM_READ" policies on a Collection in the XMLUI (But maybe I overlooked it) Here's what I tried: 1) I created a Collection and added "DEFAULT_BITSTREAM_READ=SubGroup" and "DEFAULT_ITEM_READ=Main Group" to that Collection. Here it is: http://demo.dspace.org/jspui/handle/10673/128 2) I submitted a new Item (with a single "test_pdf.pdf" bitstream) into this Collection. It's policies (after submitting) are: * Item READ policy = "Main Group" * Bundle (Original) READ policy = "SubGroup" * Bitstream (test_pdf.pdf) READ policy = "SubGroup" Here's that test Item that I created: http://demo.dspace.org/xmlui/handle/10673/131 So, I'm seeing the permissions applied properly in 6.3. You are welcome to also try this out yourself on the demo site, in case I overlooked something. If you have more information or notice something that we've missed, let us know on this mailing list. Tim On Tue, Sep 18, 2018 at 7:44 AM Hendrik Geßner <[email protected]> wrote: > Hello everyone, > > I currently try to restrict the default access to bitstreams in DSpace 6.3 > without restricting access to the item (and its metadata). So if there is a > "main group" and a "special group" that is part of "main group", an item > should be readable by all members of "main group", but the bitstreams > should only be accessible by members of "special group". > > My collection has the following authorization policy: > > ADD foobar_WORKFLOW_STEP_2 > WORKFLOW_STEP_2 foobar_WORKFLOW_STEP_2 > ADD special group > DEFAULT_BITSTREAM_READ special group > READ main group > DEFAULT_ITEM_READ main group > > When submitting an item, it gets the following authorization policies: > > Item Policies > READ main group > Policies for Bundle ORIGINAL > READ special group > Bitstream Article.pdf > READ special group > READ main group > > The last line, READ "main group" for the article, should not be there, but > if I change the DEFAULT_ITEM_READ to "special group" then the item policy > lacks a READ "main_group" from the first line. What am I missing here? > > Kind regards, > Hendrik Geßner > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-community. > For more options, visit https://groups.google.com/d/optout. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-community. For more options, visit https://groups.google.com/d/optout.
