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

[Bug 15500] Add FRBRized View to OPAC Results
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15500 Jessie Zairo <jzairo(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzairo(a)bywatersolutions.com Status|CLOSED |REOPENED Resolution|WONTFIX |--- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 15326] Add CMS feature
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15326 Paul Derscheid <paul.derscheid(a)lmscloud.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul.derscheid(a)lmscloud.de -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8838] Digest option for HOLD notice
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8838 George Williams (NEKLS) <george(a)nekls.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |george(a)nekls.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12141] On Display Module
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12141 Sam Passey <passey(a)uintah.utah.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |passey(a)uintah.utah.gov --- Comment #18 from Sam Passey <passey(a)uintah.utah.gov> --- This would be very helpful! Our library would help be a fiscal sponsor for such a development if needed. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2244] RFID Cataloguing - Programming RFID tags from Koha
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2244 --- Comment #9 from Sam Passey <passey(a)uintah.utah.gov> --- this would be a fantastic addition to Koha. Right now many public libraries pay for third party software to read and write RFID tags. RFID pads should work similar to barcode readers and koha should have built in abilities to read/write RFID. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 2244] RFID Cataloguing - Programming RFID tags from Koha
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2244 Sam Passey <passey(a)uintah.utah.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |passey(a)uintah.utah.gov --- Comment #8 from Sam Passey <passey(a)uintah.utah.gov> --- The ability to read/write RFID tags natively from Koha (similar to how bar code readers are supported) would be amazingly beneficial! If a fiscal sponsor is needed it is likely that Basin Libraries Consortium in Utah, United States could commit some funding. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 31600] New: Holds to pull displaying the patron for the last lowest priority hold instead of the first highest priority hold
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31600 Bug ID: 31600 Summary: Holds to pull displaying the patron for the last lowest priority hold instead of the first highest priority hold 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If there are holds on a record for patrons A, B and C with priorities 1, 2 and 3, the holds to pull report will display patron C even though patron A is most likely the patron the item will trap for. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30497] New: Constraint old_reserves_ibfk_4 should be SET NULL instead of CASCADE
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30497 Bug ID: 30497 Summary: Constraint old_reserves_ibfk_4 should be SET NULL instead of CASCADE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org kohastructure defines it as SET NULL but this upgrade 'decided' differently: $DBversion = "3.23.00.055"; ALTER TABLE old_reserves ADD CONSTRAINT `old_reserves_ibfk_4` FOREIGN KEY (`itemtype`) REFERENCES `itemtypes` (`itemtype`) ON DELETE CASCADE ON UPDATE CASCADE; I think we should go for SET NULL here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 30490] New: Should deleting a parent itemtype be CASCADING?
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30490 Bug ID: 30490 Summary: Should deleting a parent itemtype be CASCADING? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This is a sync issue between schema and upgrades. MASTER structure: CONSTRAINT `itemtypes_ibfk_1` FOREIGN KEY (`parent_type`) REFERENCES `itemtypes` (`itemtype`) ON DELETE CASCADE ON UPDATE CASCADE $DBversion = '20.06.00.022'; ALTER TABLE itemtypes ADD CONSTRAINT itemtypes_ibfk_1 FOREIGN KEY (parent_type) REFERENCES itemtypes (itemtype) NOTE: When you do not add CASCADE, you fallback to RESTRICT ! Main question is now: Which is right? Should the delete be cascading or not? I would opt for RESTRICT here. A pragmatical choice too; deleting item types will normally not be done so much :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 7021] Add patron category to the statistics table
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7021 --- Comment #59 from Tomás Cohen Arazi <tomascohen(a)gmail.com> --- Pushed to master for 22.11. Nice work everyone, thanks! -- You are receiving this mail because: You are watching all bug changes.

1 0