Skip to content

Request a Copy does not work for old versions of versioned items #6180

Description

@engsterhold

Describe the bug

(I am not sure if this is a DSpace or DSpace-angular issue)
When you activate the "Request a copy" feature for a bitstream by restricting the READ access of the bitstream to administrator or WITHDRAWN_READ for anonymous it leads to a login page instead of the "Request a copy" site if you use it on an old version of a versioned item. The main version works as expected.

The Access policies are equivalent:
Main version:
Image

Old version:
Image

The urls for the main item and the versioned item differs (local example, link probably not accessible)
Main version:
https://vhrz2249.hrz.uni-marburg.de/items/844af867-15b7-44dd-814a-978fb33cea60/request-a-copy?bitstream=1235b2f3-6f8d-418d-a1a3-42a11ce359f8

Old version:
https://vhrz2249.hrz.uni-marburg.de/bitstreams/b9567c49-6bc8-4d4b-b50f-00d4d4edbaf1/download

I am using DSpace 10, browser Safari / Chrome / Firefox
A short video demo (it shows a custom ui, but with the default ui the same happens, I have tested it local with the default ui)
First I try to download the old version (1), after that I switch to the new version (2)

dspace10-request-a-copy-bug.mov

To Reproduce

Steps to reproduce the behavior:

  1. create an item
  2. Restrict the access to a bitstream either by changing READ to administrator or set the anonymous access to "WITHDRAWN_READ"
  3. Test if you get the "Request a copy" Proxy site when you want to download the bitstream.
  4. Create a new Version for this item
  5. The new / main version has default access settings
  6. The old version has restricted access but leads to the login page instead of the "Request a copy" page
  7. Changing the access settings for the latest / main item links to the "Request a copy" proxy site

Expected behavior

I would expect, that the old version also lead to the "Request a copy" proxy page.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugneeds triageNew issue needs triage and/or scheduling

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions