Skip to content

Legacy EmbargoSetter places embargo policies on Bundles which later breaks visibility of Bitstream and Request-a-copy #2057

Open
@mdiggory

Description

Describe the bug
The following line in the DefaultEmbargoSetter sets the embargo start date on the Bundle READ policy, which breaks Request-a-Copy

https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/embargo/DefaultEmbargoSetter.java#L97

To Reproduce
Steps to reproduce the behavior:

  1. Enable a dc.date.embargo field in submission and populate in dspace.cfg#embargo.field.lift
  2. Enable request-copy in configuration
  3. Submit item with dc.date.embargo set in future
  4. Bitstreams will not be visible in Item view
  5. Request-copy- cannot be activated

Expected behavior
Bitstream should show with lock next to it. Clicking link should open request a copy form

Recommendation
Remove line to not set embargo start date on Bundle policy

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions