change language for deaccession not valid reason#11985
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
|
Changes unknown |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
pdurbin
requested changes
Mar 31, 2026
pdurbin
reviewed
Mar 31, 2026
|
|
||
| Once the database is updated the Solr indexes need to be rebuilt using the following Admin API: | ||
|
|
||
| - `curl http://localhost:8080/api/admin/index/continue` |
Member
There was a problem hiding this comment.
"continue" only works if you clear the index timestamps first. See https://guides.dataverse.org/en/6.10.1/admin/solr-search-index.html
This is just a heads up. We can probably just suggest a full reindex in the final release notes.
Contributor
Author
There was a problem hiding this comment.
updated the doc
This comment has been minimized.
This comment has been minimized.
1 similar comment
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
pdurbin
reviewed
Apr 1, 2026
| @@ -0,0 +1,3 @@ | |||
| -- modify datasetversion.deaccessionnote entries with new Bundle string 'file.deaccessionDialog.reason.selectItem.notValid' | |||
| UPDATE dvobject SET indextime=null WHERE id in (SELECT dataset_id FROM datasetversion WHERE deaccessionnote='Not a valid dataset.'); | |||
| UPDATE datasetversion SET deaccessionnote='Not valid. This dataset does not comply with repository policies.' WHERE deaccessionnote='Not a valid dataset.'; | |||
Member
There was a problem hiding this comment.
I'm just putting this at the bottom but why does this PR have 66 commits for such a small change? Seems very strange.
Related:
Member
pdurbin
approved these changes
Apr 1, 2026
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
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 this PR does / why we need it:The current list of deaccessioning reasons may not fully capture all the legitimate grounds for dataset removal. One common and important case—when a deposit violates repository terms of use, submission policies, or legal/ethical guidelines—is not explicitly listed. Including this as a standardized reason improves clarity and accountability in the deaccessioning process.
Which issue(s) this PR closes:IQSS/dataverse.harvard.edu#360
Special notes for your reviewer:
Suggestions on how to test this: UI and API calls.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?: included
Additional documentation: