October 2020 - Koha-bugs - lists.koha-community.org

[Bug 23705] New: Add a syspref to enable record locking, so that when one record is opened to be edited, it's read only for other users
by bugzilla-daemon＠bugs.koha-community.org 10 May '24

10 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23705 Bug ID: 23705 Summary: Add a syspref to enable record locking, so that when one record is opened to be edited, it's read only for other users Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: chris(a)bigballofwax.co.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It should be possible to allow Koha cataloguing to operate in a way where only one person can be editing a record at a time. This feature will add a syspref to enable that behaviour -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 15786] New: specify a default framework on a per-login basis
by bugzilla-daemon＠bugs.koha-community.org 10 May '24

10 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15786 Bug ID: 15786 Summary: specify a default framework on a per-login basis Change sponsored?: Seeking cosponsors Product: Koha Version: master Hardware: All URL: http://devs.bywatersolutions.com/projects/default-fram eworks/ OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Goal of development: To be able to specify a default framework on a per-login basis Work to be done: 1) Add new field ‘frameworkcode’ to table ‘borrowers’ 2) Revail in the patron editor as “Preferred framework” 3) Make the selected framework the default for new records 4) If editing existing record that does not match preferred framework, pop up confirmation dialog asking/warning to switch to new framework Looking for sponsors here: http://devs.bywatersolutions.com/projects/default-frameworks/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 26369] New: Set use_zebra_facets to 0 in the templates
by bugzilla-daemon＠bugs.koha-community.org 10 May '24

10 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26369 Bug ID: 26369 Summary: Set use_zebra_facets to 0 in the templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com bug 13665 points out performance issues of zebra facets, let's not enable them by default -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 18016] New: C4::Auth_with_ldap:: ldap_entry_2_hash inserts 0000-00-00 for invalid dateofbirth
by bugzilla-daemon＠bugs.koha-community.org 09 May '24

09 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18016 Bug ID: 18016 Summary: C4::Auth_with_ldap::ldap_entry_2_hash inserts 0000-00-00 for invalid dateofbirth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: dpavlin(a)rot13.org QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 26206] New: Extended Patron Attributes don't have a stable id on OPAC
by bugzilla-daemon＠bugs.koha-community.org 08 May '24

08 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26206 Bug ID: 26206 Summary: Extended Patron Attributes don't have a stable id on OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org On the OPAC extended patron attributes don't have a stable id on the opac, but instead the id changes each time the page reloads. This makes it impossible to use JQ to effect them during the self-registration process. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16703] New: Home > Reports > Circulation statistics showing no circulation
by bugzilla-daemon＠bugs.koha-community.org 08 May '24

08 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16703 Bug ID: 16703 Summary: Home > Reports > Circulation statistics showing no circulation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org koha/reports/issues_stats.pl is giving incorrect results. Here are the parameters added: Period From: 01/01/2016 To : 06/07/2016 Type: Checkout group by: None Library: Takoma Park Maryland Library Home Library: Takoma Park Maryland Library Holding Library: Takoma Park Maryland Library The output is: Circulation statistics Filtered on: Period From 01/01/2016 Period To 06/07/2016 Library = TPML Home library = TPML Holding library = TPML Event issue / TOTAL TOTAL 0 Here are the actual circulation statistics: select count(*) from statistics where type = 'issue' and branch='TPML' and date(datetime) between '2016-01-01' and '2016-06-07'; +----------+ | count(*) | +----------+ | 33891 | +----------+ To re-create: 1/ Choose a koha instance that has circulation 2/ Go to Home > Reports > Circulation statistics 3/ Select the following: Period From: <Your start date> To : <Your end date> Type: Checkout group by: None Library: <BRANCH> Home Library: <BRANCH> Holding Library: <BRANCH> Cell Value: Count total items Output: To screen into the browser 4/ Click submit You will see Event issue / TOTAL TOTAL 0 5/ select count(*) from statistics where type = 'issue' and branch='BRANCH' and date(datetime) between '<Your start date>' and '<Your end date>' (Replace BRANCH and dates with values corresponding to the report above). Assuming that your date range contains checkouts, the output from issues_stats.pl is clearly incorrect. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 18439] New: Resend button for notices being hidden by CSS and never unhidden
by bugzilla-daemon＠bugs.koha-community.org 08 May '24

08 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18439 Bug ID: 18439 Summary: Resend button for notices being hidden by CSS and never unhidden Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Enable EnhancedMessagingPreferences Ensure you have some sent or failed notices View notices tab and don't see a 'resend' button Inspect the status column, note a hidden for containing the 'resend' button -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 25324] New: After editing an authority record with CatalogModuleRelink on, relinking appears to happen before the edited record is saved
by bugzilla-daemon＠bugs.koha-community.org 08 May '24

08 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25324 Bug ID: 25324 Summary: After editing an authority record with CatalogModuleRelink on, relinking appears to happen before the edited record is saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org The actual behavior these contrived steps imitate is using AutoCreateAuthorities and CatalogModuleRelink, using LinkerModule: First Match so that in case of duplicate authorities the linker will choose the first, oldest, lowest authid, and then buying one book by an author before he dies, cataloged with Name, Birthyear-, and then buying another after he dies, cataloged with Name, Birthyear-Deathyear. 1. Set AutoCreateAuthorities, BiblioAddsAuthorities, CatalogModuleRelink, and LinkerModule: First Match 2. Create a personal name authority record with 100 1# $aBrzezinski, Zbigniew,$d1928- (imitating one you imported before 2017) 3. In any existing bib record, add a 700 linked to that authority record, just so it has a linked bib 3. Cataloging, new from Z39.50, search for Brzezinski, Zbigniew as author, import and save any record with the 100 field having his $d as 1928-2017. 4. Since your report of newly created authority records shows Brzezinski, Zbigniew, 1928-2017 when you know you already owned something he wrote, go to Authorities and search for Brzezinski. You need to update your previously imported record (well, the fake of one you created), so Edit the one without a 2017, Replace record via Z39.50, find the 1928-2017 record and import and save it. 5. Search again for Brzezinski. Expected results: Because you created the one that was originally 1928- first, before the one autocreated as 1928-2017 from your imported bib record, and you set First Match as your LinkerModule, you should expect that when you edit the first record in a way that causes the two records to become duplicates, that relinking would link both bib records to the first match. Actual results: Both bib records are linked to the second match, the autocreated one, rather than to the original, looking very much like the bib record without -2017 was updated and both bib records were relinked before the authority record you turned into a match actually was a match. As a result, rather than just being able to delete a now-unused autocreated record, you have to merge it to your newly edited record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 17763] New: Exact ponctuation and words order is needed for matching results for author and title in adv. search
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17763 Bug ID: 17763 Summary: Exact ponctuation and words order is needed for matching results for author and title in adv. search Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org When we use in advanced search, the exact ponctuation ("," and "-") and words order (name, first name) is required to find the good author. Also, when we search by customer, we must put an "-" in the customer name to find the good one. Some people want a more flexible way to find the good author or the good customer in theirs orders. There is a patch or a fix of any kind to do this without ",", "-" and the specific word order ? I searched but find nothing related (maybe I miss something...) Thanks, -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 19763] New: Improve the close budget screen
by bugzilla-daemon＠bugs.koha-community.org 03 May '24

03 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19763 Bug ID: 19763 Summary: Improve the close budget screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When closing a budget the message once orders are resolved is: There are no unreceived orders for this budget. Back Perhaps a message that the budget is ready to be closed, or a link to make the budget inactive and locked would be helpful to the user. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2