Legacy EmbargoSetter places embargo policies on Bundles which later breaks visibility of Bitstream and Request-a-copy #2057
Open
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
To Reproduce
Steps to reproduce the behavior:
- Enable a dc.date.embargo field in submission and populate in dspace.cfg#embargo.field.lift
- Enable request-copy in configuration
- Submit item with dc.date.embargo set in future
- Bitstreams will not be visible in Item view
- 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
Type
Projects
Status
📋 To Do