Link to fulltext not visible to anonymous group

[gustav chinovava]

Dear DSpace Techies

I am migrating from 6.x to 7.6.2.

In my 6.x, I have items where the bitstreams is accessible to a closed group with anonymous having READ access to item metadata.

In 6.x, the anonymous group gets to see link to fulltext. When they click on the fulltext link, they get challenged for username/password.

For items I have moved from 6.x to 7.6.2 while preserving the same permissions i.e. anonymous with READ to item and specific groups with READ to bitstreams, the fulltext link is not visible alongside item metadata.

So a user who has not logged in will not be able to reach fulltext until they make a conscious decision to log in first.

Is there a way I can make link to fulltext visible to anonymous group so upon clicking such they get challenged to log in?

[DSpace Technical Support]

Hi,

This definitely isn't the default behavior in DSpace 7.6.x.   Restricted Bitstreams should still appear, but will have a lock icon next to them.

It may be possible that the issue is your "Bundle" objects are also access restricted. If the Bundle is restricted, then it may *hide* the Bitstreams.   Ideally, if you have a publicly READable Item, then all its Bundles should also be publicly READable.   But, I recall there being an issue of this type in the past here: https://github.com/DSpace/DSpace/issues/8902 and it was improved here: https://github.com/DSpace/DSpace/pull/8901

If that's the problem, you should be able to modify the Bundle permissions in the Item's Authorizations (on the "Edit Item" -> "Status" tab) to allow for Anonymous READ access.

Tim

[euler]

Hi Tim,

I have a similar issue. In our repository running DSpace version 6.x, I have a collection where the Item's READ policy is set to the Anonymous group, while the bitstreams READ policy is set to a special group named AQD. As an anonymous user, you can view the link to the full-text, and the subsequent page will display a request a copy form. Please see the Authorization --> Policy List of a simple item from this collection:

Below is the same item from my fresh DSpace 8.1 installation:

In version 6.x, the link to the full-text is visible but with a lock icon. In DSpace 8.1, there is no link to the full-text.

However, if I changed the READ policy of the ORIGINAL bundle only to the Anonymous group, but still retaining the READ policy to the AQD group for the bitstream:

The link to the full-text is now displayed in the in the simple item page with a lock icon.

So my question now is, how can I batch modify the policy for the Bundle ORIGINAL to Anonymous without changing the READ policy of its bitstream? I am asking because I have a bunch of collections wherein the items have a READ policy for a special group in both its ORIGINAL bundle and bitstream. Doing this per item is very tedious so I'm asking if this could be done by batch. I've tried using "Bulk Access Management" feature but it is only changing the bitstream policy and NOT the ORIGINAL bundle policy. In other words, even if the bitstream's policy is set to Anonymous READ, but the ORIGINAL bundle's READ is not Anonymous, the link to the full-text will not appear. See the screenshot below after I used Bulk Access Management and replaced the bitstream policy to Anonymous:

Any advise would be greatly appreciated! Thanks in advance,

euler

[DSpace Technical Support]

Hi euler,

I'm not aware of a way to batch change the permissions of every Bundle in DSpace.  As you noted, the Bulk Access Management tool currently only works for Items or Bitstreams. I don't believe it will modify the Bundle permissions -- but you could play around with the "replace access condition" mode to see if running that at the Item or Bitstream level will also update the Bundle.

You could also potentially achieve this either via the REST API directly, or at the database level.  I don't know exactly how to do that, but it should be possible.

For the REST API approach, you could look at the REST API request(s) sent by the User Interface when you update a **single Bundle** to have the correct permissions: https://wiki.lyrasis.org/display/DSDOC8x/REST+API#RESTAPI-FindingwhichRESTAPIEndpointtouse   But, then you'd have to find a way to run this same command for every Bundle.

Essentially, I don't know of an easy solution here.  It could be that this is a feature request to add the ability to modify *Bundle* Permissions to the existing "Bulk Access Management" tool.  But, that could take time to implement because it'd require finding a volunteer to work on it.

Maybe someone else on this list has encountered this before and has a suggestion on how to work around it.

Tim

[Andrew Thompson]

Also there is Python which can be quite easy to hack together a bulk modify script.

For example: https://github.com/the-library-code/dspace-rest-python

Bear in mind that this library isn’t made by DSpace.

-Andrew

On 1 Mar 2025, at 3:05 am, DSpace Technical Support <dspac...@googlegroups.com> wrote:

Hi euler,

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/e1f776b1-b60c-4302-9161-5baf6656aef6n%40googlegroups.com.