Skip to content

DIS-2941: Editing Volume Numbers in a Series Does Not Save - #86

Merged
mdnoble73 merged 1 commit into
26.10.00from
work/26.10.00/DIS-2941
Oct 7, 2026
Merged

mdnoble73 merged 1 commit into
26.10.00from
work/26.10.00/DIS-2941

Conversation

@K-Alette

@K-Alette K-Alette commented Oct 7, 2026 •

Copy link
Copy Markdown
Collaborator

Added new variable "userDefinedVolume" to track whether or not volume information should be overwritten during indexing. Gets set to true if user edits the volume field on an entry Gets set back to false if the user defined value is equal to the value found during indexing

Update GroupedWorkIndexer.java:

  • When checking if we should add series member with volume, check if we are looking at an existing series member with a user defined volume in addition to checking if the volume exists

The following needs to be true to add a new series member with volume (to avoid duplicates from user-defined members):

  • The volume does not exist in the current series members
  • The series member grouped work permanent ID equals the grouped work permanent id being indexed and does not have a user defined volume OR the grouped work permanent IDs don't match

If we go to updating an existing member instead of adding a new one, we will change the userDefinedVolume variable to false if the existing volumes contains the current volume being indexed

For deletion, we will no longer remove series members that have a user-defined volume value

Update release notes
Tested on my local instance of Aspen on individual grouped works and series Will need larger testing batches (nightly index before and after view) to ensure desired series indexing functionality remains

Added new variable "userDefinedVolume" to track whether or not volume information should be overwritten during indexing.
Gets set to true if user edits the volume field on an entry
Gets set back to false if the user defined value is equal to the value found during indexing

Update GroupedWorkIndexer.java:
- When checking if we should add series member with volume, check if we are looking at an existing series member with a user defined volume in addition to checking if the volume exists
The following needs to be true to add a new series member with volume (to avoid duplicates from user-defined members):
- The volume does not exist in the current series members
- The series member grouped work permanent ID equals the grouped work permanent id being indexed and does not have a user defined volume
OR the grouped work permanent IDs don't match

If we go to updating an existing member instead of adding a new one, we will change the userDefinedVolume variable to false if the existing volumes contains the current volume being indexed

For deletion, we will no longer remove series members that have a user-defined volume value

Update release notes
Tested on my local instance of Aspen on individual grouped works and series
Will need larger testing batches (nightly index before and after view) to ensure desired series indexing functionality remains
@mdnoble73
mdnoble73 merged commit 919d143 into 26.10.00 Oct 7, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants