Bug 37796 - Generated issue has incorrect number in pattern when receiving
Summary: Generated issue has incorrect number in pattern when receiving
Status: Failed QA
Alias: None
Product: Koha
Classification: Unclassified
Component: Serials (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Nick Clemens (kidclamp)
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-30 20:32 UTC by Esther Melander
Modified: 2025-05-01 19:28 UTC (History)
5 users (show)

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


Attachments
Incorrect number on generated issue (54.07 KB, image/png)
2024-08-30 20:32 UTC, Esther Melander
Details
Bug 37796: Pass correct publication date when generating the next serial form the serial collection page (2.14 KB, patch)
2024-09-13 20:09 UTC, Nick Clemens (kidclamp)
Details | Diff | Splinter Review
Bug 37796: Adjust unit tests (1.70 KB, patch)
2024-09-13 20:09 UTC, Nick Clemens (kidclamp)
Details | Diff | Splinter Review
Bug 37796: Adjust GetNextSeq unit test file (22.93 KB, patch)
2024-09-13 20:09 UTC, Nick Clemens (kidclamp)
Details | Diff | Splinter Review
Serial numbering pattern when receiving (37.54 KB, image/jpeg)
2025-02-07 18:04 UTC, Esther Melander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Esther Melander 2024-08-30 20:32:40 UTC
Created attachment 170927 [details]
Incorrect number on generated issue

Discovered while testing Bug 35646

To Replicate

1. Follow Bug 35646 and create a numbering pattern for {MonthName} {Year}.
2. Test the pattern for a 1/month frequency, subscription start date on the first day of the month.

See that the numbering pattern increments correctly for the month names and year.

3. Find a serial in the catalog and add a new subscription.
4. On the second page of the subscription configuration, select the numbering pattern for MonthName Year.
5. Test the prediction pattern and see everything increments correctly.
6. Save the subscription.
7. Receive.

See the the first issue displays correctly for the month name and year.

8. Mark the issue as arrived and generate the next issue.

See the next issue does not have the correct month name and year. (image attached).

9. Mark the next issue Arrived and generate the third issue.

The date published and number continue to increment incorrectly.

Possibly connected to bug 20653, though this example is not irregular.
Comment 1 Nick Clemens (kidclamp) 2024-09-13 20:09:23 UTC
Created attachment 171498 [details] [review]
Bug 37796: Pass correct publication date when generating the next serial form the serial collection page

This patch changes the call to GetNextSeq from serial-collection.pl to ensure the new issue publication date is used to
generate the numbers

To test:
1 - On the serial used in previous patch go to 'Serial collection'
2 - Generate next issue
3 - Confirm the numbering is correctly generated after this patch
Comment 2 Nick Clemens (kidclamp) 2024-09-13 20:09:25 UTC
Created attachment 171499 [details] [review]
Bug 37796: Adjust unit tests
Comment 3 Nick Clemens (kidclamp) 2024-09-13 20:09:27 UTC
Created attachment 171500 [details] [review]
Bug 37796: Adjust GetNextSeq unit test file

The crux of the change here was adding an extra param to the call, but when it died
I had no idea where it did. Taking the liberty to tidy, move to subtests, and add diag
Comment 4 Esther Melander 2025-02-07 18:04:46 UTC
Created attachment 177654 [details]
Serial numbering pattern when receiving

I tested this and the numbering pattern still seems to be off. When the prediction pattern is tested in the subscription it appears to be correct, but when receiving it is still one month off. I also tested this with a daily subscriptions and the generated issues were one day off. Attached screen shot of the generated issues for the month/year subscription.
Comment 5 Megan McShane 2025-03-11 16:56:19 UTC
We would appreciate any updates on this as well.
Comment 6 Lisette Scheer 2025-05-01 19:28:22 UTC
I had the same issue as Esther.