[Koha-bugs] [Bug 32903] New: callnumber.pl plugin - leading 0s are not added when using a prefix
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Feb 7 19:11:50 CET 2023
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32903
Bug ID: 32903
Summary: callnumber.pl plugin - leading 0s are not added when
using a prefix
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Cataloging
Assignee: koha-bugs at lists.koha-community.org
Reporter: david at davidnind.com
QA Contact: testopia at bugs.koha-community.org
CC: m.de.rooy at rijksmuseum.nl
The description in the script for the cataloguing/value_builder/callnumber.pl
says that if a prefix is used, then leading zeros are added when needed.
Example: If this call number exists for an item "PREFIX 0009678570", then
adding PREFIX to another item should generate "PREFIX 0009678571". However, it
generates it as "PREFIX 9678571".
To replicate (using KTD):
1. In a MARC21 instance, add the callnumber.pl plugin to 952$o for the BKS
framework.
2. Edit an item for a record and add "PREFIX 0009678570" as the call number and
save.
3. Edit another item for another record.
4. For the call number, enter "PREFIX" and then click on the three dots.
5. Note that it generates the call number as "PREFIX 9678571" instead of
"PREFIX 0009678571" with the leading 0s.
[1] Full description from the script:
Is used for callnumber computation.
If the user send an empty string, we return a simple incremented callnumber.
If a prefix is submited, we look for the highest callnumber with this prefix,
and return it incremented.
In this case, a callnumber has this form : "PREFIX 0009678570".
- PREFIX is an upercase word
- a space separator
- 10 digits, with leading 0s if needed
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list