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

[Bug 28133] New: Show subscription information on multiple bibliographic records
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28133 Bug ID: 28133 Summary: Show subscription information on multiple bibliographic records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I am not sure yet on how this would be implemented best, so I am starting with a description of the use case: Serials are odd things. They can change their names quite frequently, they can divide, merge, and so on. This is usually reflected in using 780/785 linking records for the different "versions" of the serial. A subscription can currently only be linked to one record at a time. So in case of a name change of the serial, what can we do? - We can close the current subscription and start a new one on the record. This way the serial issues will show on the record with the title matching. The holdings will now be divided up on different records. But this might cause issues with your acq orders and will make it really hard to keep history as things are split up over multiple records. - We can change the bibliographic record the subscription is linked to and move all the information to the "latest" version of the serial. This keeps all the issues and subscription information in one spot, but in the OPAC there are no longer any issues showing at the older record. So what could we do? Ideas: - Make it possible to keep track of the biblionumber an issue was created for (there is already an "unused" field in the database). We could use this to control display and show issues on different records, not only the current one. - Make it possible to link the subscription to a current and additional biblionumbers where you want to show your holdings. ... ? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 16820] New: add possibility to edit fines
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16820 Bug ID: 16820 Summary: add possibility to edit fines Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, It would be great to have to edit fines if a mistake is made in the amount or in the notes. Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 21379] New: OMNIBUS: Circulation history UI improvements - Add column "Where Checked-in"
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21379 Bug ID: 21379 Summary: OMNIBUS: Circulation history UI improvements - Add column "Where Checked-in" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com New column "Where Checked-in" Very useful if looking for soem mised items. Its info about where item was last time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25815] New: SIP Checkout: add more information on why the patron is blocked.
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25815 Bug ID: 25815 Summary: SIP Checkout: add more information on why the patron is blocked. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Currently, on SIP checkout, Koha only returns "Patron Blocked" when there is a problem with the patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 21847] New: OAI-PMH server should enforce correct syntax for identifiers (including OAI-PMH:archiveID)
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21847 Bug ID: 21847 Summary: OAI-PMH server should enforce correct syntax for identifiers (including OAI-PMH:archiveID) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org According to http://www.openarchives.org/OAI/2.0/guidelines-oai-identifier.htm, OAI-PMH identifier must follow this format: oai-identifier = scheme ":" namespace-identifier ":" local-identifier scheme = "oai" namespace-identifier = domainname-word "." domainname domainname = domainname-word [ "." domainname ] domainname-word = alpha *( alphanum | "-" ) local-identifier = 1*uric At the moment in Koha you can put whatever you like in OAI-PMH:archiveID and make all sorts of invalid identifiers. We should change this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 26596] New: koha-upgrade-schema should check version before calling updatedatabase.pl
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '23

13 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26596 Bug ID: 26596 Summary: koha-upgrade-schema should check version before calling updatedatabase.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, koha-upgrade-schema indiscriminately runs updatedatabase.pl, regardless of whether or not the Koha instance actually requires a database upgrade. I've noted that running koha-upgrade-schema against a large number of instances (e.g. 50 instances) takes a couple of minutes. Jonathan has noted doing an upgrade will take 1.5 seconds, so 1.5 x 50 = would be 1.25 minutes. Jonathan and I agreed via email that koha-upgrade-schema should do a check similar to C4::Auth::_version_check but without using the ORM via C4::Context->preference() to avoid the overhead of loading the DBIC schema. In theory, koha-upgrade-schema should be able to spin through 50 instances in a fraction of a second, if none of them need database upgrades. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 18117] New: Convert browser alerts to modals
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '23

12 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18117 Bug ID: 18117 Summary: Convert browser alerts to modals Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org With modals becoming more active in Koha, I think we need to move away from alert messages and stick with modals. Alert messages look different from browser to browser, and you have less/no control over the look and feel of the alert. Modals would allow for more enhancement, such as color and sound, if someone chose that. The big concern is consistency. We lack consistency between alerts and modals, and with alerts between browsers. I would proposed a stop on use of alert messages, and convert existing uses of alerts to modal. That's my opinion. Would like to hear others. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 30575] New: Returning an ILL item shouldn't just change the request status
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '23

12 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30575 Bug ID: 30575 Summary: Returning an ILL item shouldn't just change the request status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com In the context of more complex ILL backends, in which returning an item could imply, for example, notifying an external source it is just not enough to call $req->status('RET')->store We should be calling something like ->backend_return instead, as we do with other actions, and let the plugin handle it however they need to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27849] New: Koha::Token may access undefined C4::Context->userenv
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '23

12 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27849 Bug ID: 27849 Summary: Koha::Token may access undefined C4::Context->userenv Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: mjr(a)software.coop QA Contact: testopia(a)bugs.koha-community.org The _add_default_csrf_params internal function accesses C4::Context->userenv without checking that it has been defined. I think not all of the potential callers of it declare that they require a defined userenv, so we should test and provide defaults for required values if it is not defined, to avoid some "Can't use an undefined value as a HASH reference" HTTP 500 Internal Server Errors. Step to Reproduce: write some code that results in that function being used before a set_userenv call Actual Result: error logged, code exits Expected Result: code runs to completion Additional Information: I am not sure whether this is currently triggered by any released core koha code, or only a few plugins and mods. It looks to me like a bug waiting to happen, based on the documentation, which can be avoided simply. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 16514] New: Force scalar cotext where param assumes a list incorrectly in admin/edi scripts
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '23

11 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16514 Bug ID: 16514 Summary: Force scalar cotext where param assumes a list incorrectly in admin/edi scripts 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: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CGI's param method assumes a list context when lvalue not explicitly scalar. Force the correct context to avoid errors being logged -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13