Dear Rohit, For items that are already in the repository, you can embargo them through the authorizations screen (reached through "edit this item"). If you want users to only see the metadata, but not the bitstreams, you can set the Item Policies to READ for anonymous (this will let everyone see the metadata). Policies for bundles and bitstreams can also be set to READ, but with a start date (equal to the date on which the embargo ends). You can set this for every group of users If you want to embargo all items in a collection, you can also use the Advanced Policy Manager.
ADD, REMOVE and ADMIN are permissions on communities and collections (meaning you can add an item, remove an item or both). Regards, Marina Op vrijdag 29 september 2017 20:01:04 UTC+2 schreef Rohit Patil: > > Thanks for your reply Marina. > > I would also like to know what are the steps to embargo items already in > repository. How can we restrict the access for everyone not just anonymous > group? > > I was trying to find descriptions of different Policy action items but > could not find it in documentation. Does anyone know what does WRITE, ADD, > REMOVE, ADMIN and WITHDRAWN_READ action mean? > > -Rohit > > On Friday, September 29, 2017 at 8:51:16 AM UTC-7, Marina Muilwijk wrote: >> >> Dear Rohit, >> >> we embargo only the item bitstreams. >> Since the metadata will be publicly visible, we warn authors that they >> shouldn't put anything sensitive in the fields of the submissions form. >> >> >> Regards, >> Marina >> >> >> Op woensdag 27 september 2017 19:00:08 UTC+2 schreef Rohit Patil: >>> >>> We are running DSpace 5.6 and we would like to know what are the best >>> methods to embargo >>> 1. item bitstreams until specific date >>> 2. entire item (metadata and item bitstreams) until specific date >>> >>> The bitstreams/items we embargo are critical (patents being applied or >>> soon submitted to journal) and i wanted to make sure the method is safe and >>> will not make anything public until embargo date. I guess the last option >>> would be to not upload them but i wanted to check what method is followed >>> by other users for hiding critical data. >>> >>> Please suggest. >>> >>> >>> >>> >>> -- 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.
