May 2022 - Koha-bugs - lists.koha-community.org

[Bug 30214] New: Add option to send ACCDETAILS notice for new patrons added via self registration
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30214 Bug ID: 30214 Summary: Add option to send ACCDETAILS notice for new patrons added via self registration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, bwsdonna(a)gmail.com, gmcharlt(a)gmail.com, katrin.fischer(a)bsz-bw.de, kris.sinnaeve(a)etf.edu, kyle.m.hall(a)gmail.com, kyle(a)bywatersolutions.com, mirjam.vantieghem(a)etf.edu, oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org Depends on: 17648 Blocks: 9097 It would be helpful to add automatic email to users on patron self-registration. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9097 [Bug 9097] 'Welcome mail' for new library users https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17648 [Bug 17648] ACCTDETAILS notice doesn't show in the notices tab in staff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 27252] New: ES5 no longer supported (since 20.11.00)
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27252 Bug ID: 27252 Summary: ES5 no longer supported (since 20.11.00) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nick(a)bywatersolutions.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Since 20.11.00 and bug 27070 we dropped the support for ES5. We should add a warning on the about page. -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 15913] New: It should be possible to restrict a problem patron from editing their record or adding comments / tags to records
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15913 Bug ID: 15913 Summary: It should be possible to restrict a problem patron from editing their record or adding comments / tags to records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org A library reported a patron adding harassing comments to the system via editing their account and commenting on records. There is currently no way to restrict this activity for a single patron. Comments and changes are moderated, so only the staff member checking these is harassed, but a goal of 0 people harassed isn't a bad goal. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 23965] New: DVD covers
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23965 Bug ID: 23965 Summary: DVD covers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Wondering if the same resources that Plex uses could be used for Koha in DVD covers. TV shows use TVDB mainly and Freebase or Movieposters.DB for Movies -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 28529] New: Max holds per item type ineffective when using AllowHoldItemTypeSelection on bib-level holds
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28529 Bug ID: 28529 Summary: Max holds per item type ineffective when using AllowHoldItemTypeSelection on bib-level holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 15533 introduced a way to constraint biblio-level holds to a specific item type. This is controlled by the AllowHoldItemTypeSelection syspref. On the circulation rules, you are able to set max_holds for an item type. This max_holds setting, seems to be honoured for item-level holds only, and it is not quite correct. To reproduce: 1. Have a patron of category 'Staff' (S) 2. Have 3 records with items with the 'BK' item type, and maybe others 3. Enable AllowHoldItemTypeSelection 4. Set a limit of 2 max holds for that category+item type 5. In the OPAC. Place bibio-level holds, with item type contraint to 'BK' on those 3 records => FAIL: You can place the 3 holds -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 30035] New: Wrong month name in numbering pattern
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '22

25 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30035 Bug ID: 30035 Summary: Wrong month name in numbering pattern Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Serials Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In some languages (at least Catalan) the display for "month name" in the numbering pattern is wrong. For January for instance we use "de gener" when it should be "gener". -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 29504] New: Confirm Item Parts requires Force Checkout permission
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '22

24 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29504 Bug ID: 29504 Summary: Confirm Item Parts requires Force Checkout permission Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With bug 25261, CircConfirmItemParts system preference was added, which is highly popular with libraries. However, it requires staff to have the permission "Force checkout if a limitation exists (force_checkout)". This is a permission that many staff do not have. When a staff member without the Force permission attempts to checkout an item with a 952$3, they get a yellow box stating: Please confirm checkout Please confirm that the accompanying materials are present: check for 12 CDs The only option given is the Continue button (with a red X) and when clicked, the item does not get checked out. To replicate: 1. Set a staff member with circ permissions, but not FORCE_CHECKOUT 2. Turn on CircConfirmItemParts 3. Log in as staff member in step 1 4. Attempt to checkout an item with a 952$3 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 29829] New: Standardize multi-value system preferences to use | as separator
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '22

23 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29829 Bug ID: 29829 Summary: Standardize multi-value system preferences to use | as separator Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org A lot of our system preferences use | to separate multiple values, but some don't, which makes handling them a little bit harder than it needs to be. Examples: ILS-DI:AuthorizedIPs NotesToHide z3950AuthorAuthFields DefaultLongOverdueSkipLostStatuses -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26340] New: Printing labels without zero(s) in the start of labels
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '22

22 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26340 Bug ID: 26340 Summary: Printing labels without zero(s) in the start of labels Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: ivan.dziuba(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org TO TEST: 1. Go Tools > Label creator 2. Click +New -> Barcode range 3. Print barcode range with zero(s) in the start (Ex. from 00011881 to 00012000 ) 4. Select a template to be applied:: Code à barre 48467 Select a layout to be applied: Code à barres 5. Export 6. Open PDF The prefix is not displayed. We should see 00011881 on the labels, but we see 11881, 11882, ... without zeros in the start of labels. This patch fix it. -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 27665] New: Clarify usage of matching dropdown on addorderiso2709.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '22

22 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27665 Bug ID: 27665 Summary: Clarify usage of matching dropdown on addorderiso2709.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1 - have a marc record you know will match something in your system using ISBN 2 - In acquisitons, create a basket, click Add to basket, select From a new file 3 - stage your marc record, select the ISBN matching rule (this is on stage-marc-import.pl) 4 - confirm that your staging results include "1 records with at least one match in catalog per matching rule "ISBN"" 5 - click Add staged files to basket 6 - this takes you to addorderiso2709.pl 7 - check the box next to your title. Confirm you see a message like "Matches biblio 440 (score = 1000): So you want to be a lizard /" 8 - change the Matching dropdown to "Do not look for matching records" 9 - click Save 10 - confirm order is tied to the matched bib rather than a new bib If we pick a matching rule on the staging screen, then the acquisitions interface doesn't actually allow us to forget that match or change and re-check our matching rule. On the other hand: 1 - have a marc record you know will match something in your system using ISBN 2 - In acquisitons, create a basket, click Add to basket, select From a new file 3 - stage your marc record, select Do not look for matching records 4 - confirm that your staging results include "Did not check for matches with existing records in catalog" 5 - click Add staged files to basket 6 - this takes you to addorderiso2709.pl 7 - check the box next to your title. Confirm you don't see any message about matches 8 - confirm Matching dropdown defaults to Title and Author. Do not change it 9 - give your order a price and fund, click Save, get message "No record have been imported because they all match an existing record in your catalog." 10 - confirm you have no ability from this screen to tie your order to the existing bib 11 - change the Matching dropdown to "Do not look for matching records", click Save, confirm your order is created with a new bib If we picked a matching rule when staging our file, then we should completely hide the Matching dropdown on addorderiso2709.pl as a match when staging renders the Matching dropdown useless. If we did not pick a matching rule when staging, then the Matching dropdown on addorderiso2709.pl serves a purpose, but we really should have an option to select and use the existing bib if our Matching choice finds something. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3