From ca419376e9c545afefbd8bedeebe4d5dac686603 Mon Sep 17 00:00:00 2001 From: Matus Kasak Date: Fri, 7 Aug 2026 11:51:20 +0200 Subject: [PATCH] JCU/fix(access-status): report a file's embargo to privileged users too access.status.for-user.bitstream = current computes a bitstream's access status for the current user, so anyone who can read the file - administrators, editors, anyone the policy lets in early - is told the file is open.access. The Item View then shows them no embargo label at all, which is backwards: the people curating the repository are the ones who need to know an embargo exists and when it ends. Switch it to anonymous, which is what access.status.for-user.item already uses and what XOAI always uses. The label becomes a statement about the file rather than about the viewer's own permissions; access itself is unchanged, this only affects the reported status. Pairs with dspace-angular#1439, which turns the label on. Co-Authored-By: Claude Opus 5 (1M context) --- dspace/config/dspace.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dspace/config/dspace.cfg b/dspace/config/dspace.cfg index 259772a2451..8a1d5b4d9e3 100644 --- a/dspace/config/dspace.cfg +++ b/dspace/config/dspace.cfg @@ -915,7 +915,7 @@ access.status.embargo.forever.day = 1 # This configuration doesn't impact the calculation for OAI-PMH. The XOAI plugin will always # calculate the status with the "anonymous" type. access.status.for-user.item = anonymous -access.status.for-user.bitstream = current +access.status.for-user.bitstream = anonymous # implementation of access status helper plugin - replace with local implementation if applicable # This default access status helper provides an item status based on the policies of the primary