ZCU-PUB/Enable per-bitstream embargo badge (item.bitstream.showAccessStatuses) - #1403
Merged
milanmajchrak merged 2 commits intoJul 23, 2026
Merged
Conversation
…Statuses) The embargo-date badge (dspace-customers#823, FE #1378/#1390) is gated behind item.bitstream.showAccessStatuses, which defaults to false in default-app-config.ts. Set it to true in config.yml so the badge renders on redeploy. Safe now that the backend accessStatus endpoint is deployed for zcu-pub (DSpace#1377); the frontend fails closed without it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Enables the per-bitstream embargo-date badge in the Item View by setting
item.bitstream.showAccessStatuses: trueinconfig/config.yml.Why
The badge (dspace-customers#823, FE #1378 + #1390) is gated behind this flag, which defaults to
falseindefault-app-config.ts. On the dev instance the flag is off, so the badge never renders even though the frontend build and the backendaccessStatusendpoint (#1377) are already deployed. Verified live:GET /server/api/core/bitstreams/{uuid}/accessStatusreturns{status, embargoDate}, while/assets/config.jsonshows the flagfalse.Notes
config.ymlis the base config (merged beforeconfig.prod.yml), so this takes effect on redeploy unless the deployment's mountedconfig.prod.ymlor aDSPACE_ITEM_BITSTREAM_SHOWACCESSSTATUSESenv var overrides it. Verify after deploy at/assets/config.json.item.showAccessStatuses(item-level badge) is intentionally left at its default.🤖 Generated with Claude Code