Bug 41876 - Restrict the numbering patterns available for a subscription based on its frequency
Summary: Restrict the numbering patterns available for a subscription based on its fre...
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: 2026-02-18 13:05 UTC by Mathieu Saby
Modified: 2026-02-19 14:11 UTC (History)
0 users

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
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 Mathieu Saby 2026-02-18 13:05:19 UTC
It would be useful to restrict the numbering patterns available for a subscription based on its frequency, in order to facilitate subscription management (saving time and limiting errors).
E.g, if monthly frequency, display only monthly numbering patterns
Comment 1 Katrin Fischer 2026-02-18 15:40:16 UTC
I am sorry, but I don't think this can work as suggested.

Numbering patterns have no indicator to tell you if they are monthly or not. And we can't look for "12" as we don't know:

- which variable it might appear in
- frequency might be monthly, but only 10 issues (counter is 10) and some irregularities recorded
- frequency might be monthly, but there are 2 6 issue cycles a year and the numbering goes 1-6, 1-6 for each

The current system is very flexible, but it makes it really hard to limit the pull down like you suggest.
Comment 2 Mathieu Saby 2026-02-19 14:11:22 UTC
Thanks for your feedback!

The KohaLa association is considering funding a development, but we have not yet requested a cost estimate.

Here are the specifications we have been working on. Does this seem realistic to you?

- add an optional "frequency" field to the numbering pattern: each pattern can now be linked to a frequency (to be selected from a drop-down list). If the field remains empty, no usage restrictions will be applied to the pattern (maintaining current behavior).

- When modifying or creating a subscription, only display numbering pattern that correspond to the subscription's periodicity and pattern for which no usage restrictions have been set.

- When a subscription is modified the consistency of the data between the frequency and numbering pattern fields must be checked before validation, and an alert must be displayed in the event of inconsistency. E.g.: if a monthly subscription (with a numbering model that can only be used for monthly subscriptions) becomes quarterly, the librarian will have to modify the numbering model.