Bug 27298 - Adjusting a Numbering Pattern will not show in receiving next issue
Summary: Adjusting a Numbering Pattern will not show in receiving next issue
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Serials (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-22 20:31 UTC by Kelly McElligott
Modified: 2024-02-01 21:14 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly McElligott 2020-12-22 20:31:34 UTC
Publishers will sometimes change how their serials are numbered mid-year or a library may have their prediction pattern originally set up correctly, for whatever the reason, if a library edits an existing serial's prediction numbering pattern-the first expected issue after this change does not show the revised prediction.

Steps:
1. Have a serial in which there is a numbering pattern and an issue has been received. For example, monthly magazine Vol. 25, No 3
2. Edit this existing subscription and alter the numbering pattern- to Vol 31 No.1.  
3. Test this subscription and see Koha is accurately predicting the new numbering pattern of Vol 31 No. 1, Vol 31 No 2 etc.
4. Save subscription.
5. Attempt to receive that new issue, Vol 31, No.1 - see that Koha believes it is still receiving Vol 25, No 3. 
6. Receive this issue, alter the enumeration for this issue.
7. Receive the next issue, and see Koha is successfully predicting the next issue Vol 31 No 2.
Comment 1 Katrin Fischer 2021-01-15 14:11:59 UTC
I just tested this yesterday in 20.05 and it does show in the next generated issue, but Koha won't ever change an already expected existing issue.

I am not sure if the current behaviour is not the correct one? There could be multiple expected issues at the same time, can we safely determine which one to change and how to change it? Libraries could have made changes to the issue already.
Comment 2 Katrin Fischer 2023-07-01 15:20:44 UTC
I believe that any changes only applying to the next generated issue is currently the expected behavior. 

I am trying to think up a way to change this, but it's not easy. There could be multiple predicted issues, having links to items or not, a need to update the history, etc.

Could we close this WONTFIX?