Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bulk Access Management processes are executable without selecting any options in step 2 #3893

Open
maxsullivan opened this issue Jan 23, 2025 · 1 comment
Labels
bug component: administrative tools Related to the admin menu or tools help wanted Needs a volunteer to claim to move forward usability

Comments

@maxsullivan
Copy link

Describe the bug

Dspace version 7.6.2

A user can execute a bulk access management process when they have selected any item in step 1 without having selected an operation in step 2.

To Reproduce

Steps to reproduce the behavior:

  1. Go to the bulk access management page and select an item or collection in step 1.
  2. Skip step 2 and execute the process.
  3. The process will start and then fail.

2025-01-24 11:01:38.076 INFO bulk-access-control - 36 @ The script has started
2025-01-24 11:01:38.102 ERROR bulk-access-control - 36 @ item or bitstream node must be provided
2025-01-24 11:01:38.103 ERROR bulk-access-control - 36 @ null
2025-01-24 11:01:38.109 ERROR bulk-access-control - 36 @ org.dspace.app.bulkaccesscontrol.exception.BulkAccessControlException: item or bitstream node must be provided
	at org.dspace.app.bulkaccesscontrol.BulkAccessControl.validate(BulkAccessControl.java:209)
	at org.dspace.app.bulkaccesscontrol.BulkAccessControl.internalRun(BulkAccessControl.java:183)
	at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

Expected behavior

The Execute button should not be active until the user has selected an operation in step 2.

@maxsullivan maxsullivan added bug needs triage New issue needs triage and/or scheduling labels Jan 23, 2025
@tdonohue
Copy link
Member

This sounds like a front-end bug (as the button is not disabled when it should be). So, moving this ticket to the frontend & to our maintenance board for 7.x & 8.x

@tdonohue tdonohue transferred this issue from DSpace/DSpace Jan 24, 2025
@tdonohue tdonohue removed the needs triage New issue needs triage and/or scheduling label Jan 24, 2025
@github-project-automation github-project-automation bot moved this to 🆕 Triage in DSpace Backlog Jan 24, 2025
@tdonohue tdonohue added component: administrative tools Related to the admin menu or tools help wanted Needs a volunteer to claim to move forward labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug component: administrative tools Related to the admin menu or tools help wanted Needs a volunteer to claim to move forward usability
Projects
Status: 🆕 Triage
Development

No branches or pull requests

2 participants