Bug 27499 - serialsUpdate doesn't create all late issues
Summary: serialsUpdate doesn't create all late issues
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Command-line Utilities (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-20 16:42 UTC by Caroline Cyr La Rose
Modified: 2021-09-03 16:54 UTC (History)
1 user (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
New subscription form 2/2 (41.01 KB, image/png)
2021-01-20 16:42 UTC, Caroline Cyr La Rose
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Caroline Cyr La Rose 2021-01-20 16:42:23 UTC
Created attachment 115449 [details]
New subscription form 2/2

I'm not sure if this is intended behaviour or not. I was trying to get a subscription with lots of late issues to test something. But every time I run serialsUpdate, it only create 1-3 issues instead of all the late issues up to today.

To test:
1) Go to Serials
2) Create a subscription for a weekly serial starting 2020-01-01 (I attached a screenshot of my new subscription form 2/2)
3) Go to serial collection
-- There should be the first issue of the subscription, 2020-01-01
4) Go to the terminal and run
./misc/cronjobs/serialsUpdate.pl -c -v
5) Go back to the serial collection
-- Only the next issue has been created (2020-01-08)

I would have expected this to create all missing issues from 2020-01-01 to 2021-01-13.

Right now, it only replaces the "Generate next" button.
Comment 1 Caroline Cyr La Rose 2021-01-20 16:43:38 UTC
I understand if this is the intended behaviour, as it is supposed to be run every day; eventually it should catch up. And my use is a but outside the norm.
Comment 2 Katrin Fischer 2021-02-06 19:11:18 UTC
I believe it might be the intended behaviour right now - we run this daily. But I see merit in the other behavior - maybe it could be an option?