On Fri, May 9, 2014 at 9:59 AM, superthin <[email protected]> wrote: > I want to remove all polices of all communites, collections, items, > bitstreams (I think the way to do fit to me is run a chains of SQL with my > PostgreSQL), and reset it like:
Yes, you can use SQL to do that. Look at the "resourcepolicy" table. "resource_type_id" is one of the following constants: https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace-api/src/main/java/org/dspace/core/Constants.java#L20 "resource_id" is the relevant bitstream_id, item_id or collection_id. "action_id" is one of the following constants: https://github.com/DSpace/DSpace/blob/dspace-4_x/dspace-api/src/main/java/org/dspace/core/Constants.java#L75 Use either "eperson_id" or "epersongroup_id" - not both in the same resourcepolicy. Ignore "start_date" and "end_date", they are used to specify embargo. Don't forget to backup your database before you change anything. Ideally, clone the DSpace instance to your PC and do the experiments there. Then when you're satisfied with the result, you can just copy the database over to your production server. > - Have no *anonymous* access to communities, collections or items. If we > cannot remove anonymous, I want anonymous could browse/search and read only, > they cannot download everything. Remember that you cannot make communities and collections inaccessible to anonymous users by removing the anonymous READ permission. That works only for items and bitstreams. If you remove a permission from a collection, it will change the default set of permissions that new items submitted to that collection will get. For explanation, see [1]. > - 2 groups of users: *Students, Lecturers* have *read* access, some > communities/ collections will be browse/download by Lecturers only. > > - 1 group: *Summiters* has *add* right. > > Every items, bitstreams will have no permission individual, it will have > default permission or inherit permission from higher level of > communities/collections. There is currently no permission inheritance in DSpace. Again, see [1]. [1] https://wiki.duraspace.org/display/DSPACE/TechnicalFaq#TechnicalFaq-Ichangedaccessrestrictionsonacollection,butrestrictionsdidn'tchangeonitsitems Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
