Unable to set a time frame for bitstream's access conditions

[marsaoua]

Describe the bug

A User with proper right to edit a bitstream is not able to select the date until which the related access condition is applied.
Testathon 10.0

To Reproduce

Steps to reproduce the behavior:

1. Login with proper right to edit a bitstream
2. Edit bitstream
3. Select an access condition type
4. Try to set a time frame

Bildschirmaufzeichnung.vom.2026-04-11.15-20-41.webm

Expected behavior

Users should be able to select the date until which the related access condition is applied

[lgeggleston]

Hi @marsaoua, thank you for writing this! I believe this may be expected behavior though, in that the access conditions have different settings for start and end dates. For example, the default for embargo is to only have a start date, and for lease is to only have an end date. Those defaults can be found and configured via access-conditions.xml: https://wiki.lyrasis.org/display/DSDOC9x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams

Let me know if I'm misunderstanding though, or if you are thinking of a use case that can't be covered by the current settings.

[marsaoua]

@lgeggleston thank you for the reply! I was not thinking of the default value settings in the sandbox while testing. Seeing the input fields for a start date and end date, I assumed that it should be possible to set a time frame for at least one of the access conditions. If this should be the expected behavior based on the settings, we certainly could improve UX.

[tdonohue]

@marsaoua : @lgeggleston 's note is correct. The expected behavior is that those two fields are enabled/disabled based on the "Access condition type" that you select (in the dropdown)

• If you select "openaccess" -> This means the file is immediately open access, so it's not possible to change the "Grant access from" or "Grant access to" fields.
• If you select "administer" -> This means the file is immediately restricted to Admins, so it's not possible to change the "Grant access from" or "Grant access to" fields.
• If you select "embargo" -> This means the file is temporarily restricted to Admins and will be open access later. So, only the "Grant access from" field is enabled to let you define the end of the embargo.
• If you select "lease" -> This means the file is temporarily open access and will be later restricted to Admins. So, only the "Grant access until" field is enabled to let you define when the lease ends.

Overall, these fields appear to be acting as expected. That said, I agree that perhaps we could document these options better.

If usability improvements are being suggested, then I think we need to better understand the recommended changes. For instance, it wouldn't make sense for an "embargo" to support a "Grant access until" date, because then by definition it is no longer an embargo. The "Grant access until" date will always remove all current access permissions after that date... so, defining that on an embargo would make the embargo permanent (i.e. it'd be the same as the "administer" option, which is permanent access restrictions)