setting item bitstreams as private but item open DSpace 6

[Lewatle Johannes Phaladi]

Dear Colleagues,

I would like to set all items bitstreams as private in one collection of 1000 items and allow users to see items metadata like title, author etc but denying access only to PDF files, please share ways to do this.

Regards,

Lewatle

[Lewatle Johannes Phaladi]

How to set request copy to all bitstrams in a collection 

[Lewatle Johannes Phaladi]

Dear Dspace Colleagues,

I have resolved the issue by using administer authorization policies tool via JSPUI interface see attached, I have set item bitstream restricted on entire community.

Regards,

Lewatle 

[Hutchinson, Alvin]

Hello, Lewatle.

 

I hope I am wrong, but my understanding of using the policies authorization tool is that the policies chosen will apply only to subsequent items added to the collection—not to existing items in the collection.

 

In other words, if you change policies to a collection, they will be in effect only for new items and existing items policies will remain unchanged.

 

Am I wrong?

 

-Alvin

Alvin Hutchinson

Smithsonian Institution

Washington, DC

--
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 dspace-communi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/9138be52-e6f8-4824-be83-f6b2d2186802%40googlegroups.com.

[Tim Donohue]

Hi Alvin,

Using the Policy Authorization Tool allows you to change policies immediately in a bulk manner.  So, this affects existing items immediately.

What you are referring to is that if you only change a Collection's "Default Read Access" setting (from the Collection's Edit screen), this change will only affect subsequent items deposited to that Collection.

So, long story short, Lewatle's solution (of using the Policy Authorization Tool) applies to all existing items (but not future ones).  Whereas changing the Collection's "Default Read Access" setting only applies to *future* items (but not existing ones).  Therefore, depending on your local needs, you may need to use one or both of these approaches.

Tim

---

From: 'Hutchinson, Alvin' via DSpace Community <dspace-c...@googlegroups.com>
Sent: Friday, July 12, 2019 10:04 AM
To: Lewatle Johannes Phaladi; DSpace Community
Subject: RE: [dspace-community] Re: setting item bitstreams as private but item open DSpace 6

 

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/BN6PR12MB168470EFCD0D419CC5C4BF59CCF20%40BN6PR12MB1684.namprd12.prod.outlook.com.

[Hutchinson, Alvin]

Well, that clears that up.

 

I guess my response was more of a question.

 

Thanks, Tim

 

Learn something every day.

 

-Alvin