-
Notifications
You must be signed in to change notification settings - Fork 131
⚙️ disable batch upload feature main #7202
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
base: main
Are you sure you want to change the base?
Conversation
Test Results 13 files ±0 13 suites ±0 2h 49m 25s ⏱️ - 4m 43s Results for commit 9f83c59. ± Comparison against base commit 23613bb. This pull request removes 360 and adds 360 tests. Note that renamed tests count towards both.This pull request skips 2 tests.♻️ This comment has been updated with latest results. |
16c0505 to
2318b0a
Compare
This commit prevents admin users from enabling batch_upload in settings. This addresses the issue that batch uploads and Valkyrized works are incompatible. The current Batch Add uses a fake Active Fedora form with fixed terms that ignore the selected work type, causing Valkyrie validations to fail (especially on 6.2). It was determined that fixing this issue is low-priority compared to general Bulkrax improvements. To ensure users are not enabling broken features, batch_upload is disabled until further decisions are made. Ref: - notch8/palni_palci_knapsack#479
The longer explanation about the disabled feature and accompanying URL causes a long line error in Rubocop. Ignoring the offense. Ref: - notch8/palni_palci_knapsack#479
Batch uploads have been disabled since batch uploads and Valkyrized works are incompatible. The current Batch Add uses a fake Active Fedora form with fixed terms that ignore the selected work type, causing Valkyrie validations to fail (especially on 6.2). It was determined that fixing this issue is low-priority compared to general Bulkrax improvements. This commit skips the batch_upload tests until further decisions are made. Ref: - #7185 - notch8/palni_palci_knapsack#479
2318b0a to
9f83c59
Compare
randalldfloyd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This solution is solid and it tests out for me locally; but we're going to defer to product owners long enough to come to a consensus on if it should be disabled in Hyrax. So I'll wait to merge to see how that goes.
|
@randalldfloyd Thanks! Sounds good to me. I wanted to document the change since we added it to 5.0-flexible. |
Fixes
This commit prevents admin users from enabling batch_upload in settings.
This addresses the issue that batch uploads and Valkyrized works are
incompatible. The current Batch Add uses a fake Active Fedora form with
fixed terms that ignore the selected work type, causing Valkyrie
validations to fail (especially on 6.2).
It was determined that fixing this issue is low-priority compared to
general Bulkrax improvements. To ensure users are not enabling broken
features, batch_upload is disabled until further decisions are made.
Ref:
Type of change (for release notes)
Add an appropriate
notes-*label to the PR (or indicate here) that classifies this change.Choose from:
notes-majorMajor Changes (Potentially breaking changes)notes-minorNew Features that are backward compatiblenotes-deprecationDeprecationsnotes-bugfixBug Fixesnotes-valkyrieValkyrie Progressnotes-docsDocumentationnotes-containerContainerization related (Docker, Helm, etc)@samvera/hyrax-code-reviewers