Hi Claudia

Thank you for the detailed instructions.  *Unfortunately* I have tried 
everything you said BUT its not changing.  Here is what I did.

1. I cleared the collection's policies just to make sure that I do not miss 
anything and that I have only the policies I needed.  After doing so I 
checked the collection's page and it had this message:
 

*This collection is restricted. You do not have the credentials to access 
the restricted collection [Collection Name here].*2. I changed the 
DEFAULT_BITSTREAM_READ and DEFAULT_ITEM_READ to Anonymous 
 

* Log in as admin -> Edit collection -> Collection's Authorizations-> Add a 
new policy-> DEFAULT_BITSTREAM_READ and DEFAULT_ITEM_READ to Anonymous *3. 
I checked under Edit collection -> Assign Roles Tab under the Default Read 
access. It had this message:
   *Default read for incoming items and bitstreams is currently set to 
Anonymous.  E-People and Groups that can read new items submitted to this 
collection. Changes to this role are not retroactive. Existing items in   
the system will still be viewable by those who had read access at the time 
of their addition. *The collection's home page still indicated that the 
collection was restricted.

4. Still logged in as admin:
Administer -> AccessControl Authorization-> Advanced/ItemWildcard Policy 
Admin Tool 

And I did the following as per instruction: 
Select Collection
ChooseContent Type - Item 
Choose Group - Anonymous 
Choose Action - READ 
Repeat this step with Content Type - Bitstream 

*Still no change.  The collection is still restricted.*

5. I added READ access to Anonymous 
 
* Log in as admin -> Edit collection -> Collection's Authorizations-> Add a 
new policy-> READ  to Anonymous *The collection is no longer resticted BUT 



*nothing comes out. THE CHANGES ARE STILL NOT BEING APPLIED TO THE EXISTING 
ITEMS*I have tried this with two different collections but the results are 
the same.  Maybe I am missing a step or there could a step which is not 
stated explicitly, or perhaps a setting?  I am now at my wits end.  Perhaps 
it would be easier if I were to do it directly in SQL. Has anyone changed 
authorisation's using the database directly?  Any help would be appreciated.





On Monday, March 12, 2018 at 3:44:23 PM UTC+2, Claudia Jürgen wrote:
>
> Hi Justice, 
>
> just tested this on the demo and worked ok. 
> If you have unchecked "New items should be publicly readable" while 
> creating a collection, both item and bitstreams will be restricted. 
> In order to have the item page and the bitstreams for already ingested 
> and future items visible you got to do 2 things 
>
> 1. Change the default settings for the collection, for newly submitted 
> items 
> Log in as admin -> 
> Edit collection -> 
> Collection's Authorizations 
> There change the DEFAULT_BITSTREAM_READ and DEFAULT_ITEM_READ to Anonymous 
>
> 2. Change the item and bitstream policies for existing items in a 
> collection 
> log in as admin -> 
> Administer -> 
> AccessControl Authorization-> 
> Advanced/ItemWildcard Policy Admin Tool 
>
> Now 
> Select Collection 
> ChooseContent Type - Item 
> Choose Group - Anonymous 
> Choose Action - READ 
> Repeat this step with Content Type - Bitstream 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
> Am 12.03.2018 um 14:17 schrieb Justice Kasiroori: 
> > Hi All 
> > 
> > I have the same problem here. I want to set READ policy to a collection 
> to 
> > in retrospective.  I want to provide access to everyone ( READ 
> privileges 
> > to Anonymous).  I tried using the Advanced Policy Manager but still the 
> > collection is restricted.  I am using DSpace 6.2 and Postgresql.  I 
> tried 
> > it using the XMLUI and the JSPUI but the changes are not being applied 
> to 
> > the collection.  I have tried following the steps provided by the DSpace 
> > wiki 
> > <
> https://wiki.duraspace.org/display/DSpaceDirectKB/Getting+Started+How-To> 
> > but still the changes are not being applied.  I m willing to use SQL to 
> > change the authorisation. If someone has a working SQL script for DSpace 
> > 6.x please help. 
> > 
> > On Friday, February 16, 2018 at 12:50:24 PM UTC+2, Claudia Jürgen wrote: 
> >> Hello Lewatle, 
> >> 
> >> the settings DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ only apply to 
> >> newly ingested items. 
> >> You can use the advanced policy manager. 
> >> Login as admin -> Administer -> Access Control -> Authorization 
> >> 
> >> Hope this helps 
> >> 
> >> Claudia Jürgen 
> >> 
> >> 
> >> Am 16.02.2018 um 09:46 schrieb Lewatle Johannes Phaladi: 
> >>> Dear All, 
> >>> 
> >>> I have edited collection authorization policy it is not applying to 
> the 
> >>> items submitted previously in the collection, I am using DSpace 6.2, 
> >>> collection has close to 500 items I would like to have previously 
> >> submitted 
> >>> items to be accessible to the public/anonymous without them logging 
> in, 
> >>   I 
> >>> have added DEFAULT_ITEM_READ to anonymous. Please share with me on 
> what 
> >>> steps to do even if it is SQL command to database, I am using postgres 
> >> db, 
> >>> all ITEMS should be accessible to everyone 
> >>> 
> >>> Regards, 
> >>> Lewatle 
> >>> 
> >> -- 
> >> Claudia Juergen 
> >> Eldorado 
> >> 
> >> Technische Universität Dortmund 
> >> Universitätsbibliothek 
> >> Vogelpothsweg 76 
> >> 44227 Dortmund 
> >> 
> >> Tel.: +49 231-755 40 43 
> >> Fax: +49 231-755 40 32 
> >> claudia...@tu-dortmund.de <javascript:> 
> >> www.ub.tu-dortmund.de 
> >> 
> >> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. 
> Sie 
> >> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der 
> für 
> >> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den 
> Absender 
> >> und vernichten Sie diese Mail. Vielen Dank. 
> >> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
> >> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher 
> >> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung 
> eines 
> >> solchen Schriftstücks per Telefax erfolgen. 
> >> 
> >> Important note: The information included in this e-mail is 
> confidential. 
> >> It is solely intended for the recipient. If you are not the intended 
> >> recipient of this e-mail please contact the sender and delete this 
> message. 
> >> Thank you. Without prejudice of e-mail correspondence, our statements 
> are 
> >> only legally binding when they are made in the conventional written 
> form 
> >> (with personal signature) or when such documents are sent by fax. 
> >> 
>
> -- 
> Claudia Juergen 
> Eldorado 
>
> Technische Universität Dortmund 
> Universitätsbibliothek 
> Vogelpothsweg 76 
> 44227 Dortmund 
>
> Tel.: +49 231-755 40 43 
> Fax: +49 231-755 40 32 
> claudia...@tu-dortmund.de <javascript:> 
> www.ub.tu-dortmund.de 
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie 
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für 
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender 
> und vernichten Sie diese Mail. Vielen Dank. 
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher 
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines 
> solchen Schriftstücks per Telefax erfolgen. 
>
> Important note: The information included in this e-mail is confidential. 
> It is solely intended for the recipient. If you are not the intended 
> recipient of this e-mail please contact the sender and delete this message. 
> Thank you. Without prejudice of e-mail correspondence, our statements are 
> only legally binding when they are made in the conventional written form 
> (with personal signature) or when such documents are sent by fax. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to