April 2021 - Koha-bugs - lists.koha-community.org

[Bug 28001] New: delete_patrons.pl requires category but does not mention this in POD
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28001 Bug ID: 28001 Summary: delete_patrons.pl requires category but does not mention this in POD Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz You cannot run the script without category, the SQL fails - we should either fix this or note that category is mandatory in the script root@kohadevbox:koha(master)$ perl misc/cronjobs/delete_patrons.pl --expired_before =1910-01-01 C4::Members::GetBorrowersToExpunge(): DBI Exception: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') GROUP BY borrowers.borrowernumber ) xxx WHERE currentissue IS NULL' at line 12 [for Statement " SELECT * FROM ( SELECT borrowers.borrowernumber, MAX(old_issues.timestamp) AS latestissue, MAX(issues.timestamp) AS currentissue FROM borrowers JOIN categories USING (categorycode) LEFT JOIN ( SELECT guarantor_id FROM borrower_relationships WHERE guarantor_id IS NOT NULL AND guarantor_id <> 0 ) as tmp ON borrowers.borrowernumber=tmp.guarantor_id LEFT JOIN old_issues USING (borrowernumber) LEFT JOIN issues USING (borrowernumber) WHERE category_type <> 'S' AND ( borrowers.flags IS NULL OR borrowers.flags = 0 ) AND tmp.guarantor_id IS NULL AND dateexpiry < ? AND categorycode IN () GROUP BY borrowers.borrowernumber -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 12362] Branch transfer records orphaned on cancelled holds
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12362 --- Comment #24 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- Sorry, I wasn't clear there. The reason it's an improvement to set up the transfer request immediately is that with the subsequent check-in you can display a clear message as to why it's being transferred back.. without that you are not greeted with a clear reason.. instead the 'return to home/holding' is triggered which could be confusing as you've only just received the item from a transfer. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12362] Branch transfer records orphaned on cancelled holds
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12362 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Passed QA --- Comment #23 from Martin Renvoize <martin.renvoize(a)ptfs-europe.com> --- I've restored the test in bug 27281, it passes before and after patches are applied. This bug doesn't actually update the items holdingbranch at all. What it does is check the transfer queue for pending transfers and then adds a reverse transfer if no other transfers exist and the transfer was in transit at the time of cancellation. I discussed this with Peter, Joonas and Tomas I believe but I'm struggling to find the thread. We basically decided that now you can queue transfers having the 'request' happen immediately made sense rather than waiting for a subsequent checkin. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13985] Cash Management - Koha as 'Point of Sale'
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |28192 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28192 [Bug 28192] Archived credit/debit types should be filtered by default -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13985] Cash Management - Koha as 'Point of Sale'
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |28181 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28181 [Bug 28181] Archived debit type still shows as available in Point of Sale -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26535] New: Remove issues old_issues redundant indexes
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26535 Bug ID: 26535 Summary: Remove issues old_issues redundant indexes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Database Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org issues and old_issues have redundant indexes. Removing them seems to reduce dead locks occurrences. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26457 This patch doesn't try to remove existing indexes it only change DB structure for new instances. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 22248] New: Error when incrementing Mana comment
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22248 Bug ID: 22248 Summary: Error when incrementing Mana comment Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 17047 Target Milestone: --- When I select an existing Mana comment on a subscription the process completes successfully but in the console this error is returned: Can't return outside a subroutine at /home/vagrant/kohaclone/svc/mana/increment line 48. It looks like that script should return JSON. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17047 [Bug 17047] Mana Knowledge Base : share data -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 12362] Branch transfer records orphaned on cancelled holds
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

1 0

[Bug 14239] Bibframe support in Koha
by bugzilla-daemon＠bugs.koha-community.org 22 Apr '21

22 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14239 --- Comment #4 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Magnus Enger from comment #3) > Almost 6 years has gone by. What do we think about BIBFRAME today? The only time I ever hear about BIBFRAME is in the context of Ex Libris Alma and it looks like they just map their internal format into BIBFRAME for export/display: https://developers.exlibrisgroup.com/alma/integrations/linked_data/bibframe/ I haven't heard anything about it in years really. Its name gets mentioned here or there in some professional librarian circles but nothing significant that I've noticed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 19974] New: Marking an item as 'lost' will not actually modify the current item (cataloguing/additem.pl)
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '21

21 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19974 Bug ID: 19974 Summary: Marking an item as 'lost' will not actually modify the current item (cataloguing/additem.pl) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: charles.farmer(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When modifying an item through the intranet at the page /cgi-bin/koha/cataloguing/additem.pl?op=edititem, instead of changing the active item's information, the markaslost parameter will be applied to the first Item in the database that has no itemnumber. I'll submit a patch soon with a clear test plan. This should fortunately not take too long to test. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 82