You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Embargoed items are not behaving correctly. The file list for embargoed items ie empty, which is not what we want. We believe this is due to a policy issue on items that are under embargo.
Acceptance criteria
All files are visible to all users, whether they are under embargo or not
If off campus, embargoed items show a lock icon next to them, and are not loadable
If on campus, embargoed items no longer show a lock icon and are loadable (on campus embargo policies were working in DSpace 6)
From Catherine:
ETDs with embargoed bitstreams are displaying as metadata only records for any user who is not logged in to Dspace. This includes users who are on campus within the designated IP-range. The record does not appear that it has any file/bitstream associated with it. We expect that any user (whether logged in or not) can see the file name. Those users who are not on VPN or logged in or on campus should also see the file name with a "locked" icon next to it, and be unable to open the file. Attached find three images to illustrate-- one showing the user display, one with a missing set of UO Only permissions and a third with both sets of permissions, which is as we expect. One impact, in addition to incorrect display of current items, is that we cannot ingest any ETD files that carry embargoes, as they would all need to be updated individually.
Screenshots
The text was updated successfully, but these errors were encountered:
Embargoed items are not behaving correctly. The file list for embargoed items ie empty, which is not what we want. We believe this is due to a policy issue on items that are under embargo.
Acceptance criteria
From Catherine:
Screenshots
The text was updated successfully, but these errors were encountered: