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

[Bug 27155] New: Biblio and Item hooks should pass a deleted object on record deletion
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '21

26 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27155 Bug ID: 27155 Summary: Biblio and Item hooks should pass a deleted object on record deletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org The biblio and item hooks now look up a record which is deleted already. We could pass the deletedbiblio or deleteditem? Especially on item deletion I am interested in receiving the biblionumber. The code for items differs between 19.11 and master. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 28047] New: Standardize: Call number, callnumber, Call no. etc.
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28047 Bug ID: 28047 Summary: Standardize: Call number, callnumber, Call no. etc. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have various ways on how we use call number in the templates. It would help, also for translations, if we always used the same spelling/term. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 28084] New: Standardize: Cardnumber, Card number, Card
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28084 Bug ID: 28084 Summary: Standardize: Cardnumber, Card number, Card Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have different spellings in the templates that could/should be standardized to one spelling to ease translation and documentation. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 16446] New: Allow librarians to add borrowers to lists by borrowernumber or cardnumber
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16446 Bug ID: 16446 Summary: Allow librarians to add borrowers to lists by borrowernumber or cardnumber Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to be able to add borrowers to lists based on a supplied list of cardnumbers or borrowernumbers (that they could get from a report, for example). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 26875] New: Allow printing of just one barcode
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26875 Bug ID: 26875 Summary: Allow printing of just one barcode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The new barcode batch printing tool from bug 7468 requires that one enter barcodes a "to" barcode higher than one's "from" barcode. That means you have to print at least 2 barcodes. It's be nice if the check was, instead, "to" must be greater than or equal to "from." -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 23243] New: Show items expired before today in check expiration of serials page
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23243 Bug ID: 23243 Summary: Show items expired before today in check expiration of serials page Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: adrien.saurat(a)biblibre.com, charles.farmer(a)inlibro.com, colin.campbell(a)ptfs-europe.com, eric.begin(a)inLibro.com, katrin.fischer(a)bsz-bw.de, koha-bugs(a)lists.koha-community.org, koha.sekjal(a)gmail.com, martin.renvoize(a)ptfs-europe.com, maxime.beaulieu(a)inlibro.com, paola.rossi(a)cineca.it, paul.poulain(a)biblibre.com, pelletiermaxime(a)gmail.com, philippe.blouin(a)inlibro.com, simith.doliveira(a)inlibro.com Depends on: 6968 +++ This bug was initially created as a clone of Bug #6968 +++ The Check Expiration page in Serials is now hardcoded (bug 15171) to always show all subscriptions that expire/expired before the date specified. We should have optionally enabled filtering out the historic expirations that have happened before today rather than removing that feature entirely. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6968 [Bug 6968] Show items expired before today in check expiration of serials page -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. You are on the CC list for the bug.

1 33

[Bug 22614] New: Request migration from one backend to another should not create new request
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22614 Bug ID: 22614 Summary: Request migration from one backend to another should not create new request 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: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- Currently, when requests are migrated from one backend to another, a new request is created containing the attributes of the existing one but with the backend set to the migration destination backend and the metadata is derived from the migration destination backend. The existing request is then marked as reverted and a record is made of where the request was migrated to. The downside of this approach is that two requests now exist in the system, whereas in actual fact, it's still the same request. This can be problematic for statistics etc. This bug proposes that request migration should preserve the original request and, instead, change its backend and replace the metadata from the original backend to that of the migration destination backend. Also, we should log where the request has been migrated from and to. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 26544] New: Housebound module should show delivery preferences when scheduling
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26544 Bug ID: 26544 Summary: Housebound module should show delivery preferences when scheduling Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 In the housebound module, you set the day and frequency in the details section, but when you schedule a new delivery, you cannot see the day or frequency, so users have no way of seeing when a delivery should be scheduled. It would be helpful to see the day and frequency on the Delivery details section. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 28073] New: Patron modifications should auto-open panel for referring patron record
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28073 Bug ID: 28073 Summary: Patron modifications should auto-open panel for referring patron record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 27873 The "Pending patron modifications" link from the checkout or patron details page should pass the borrowernumber so that the patron update page can expand the correct panel. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27873 [Bug 27873] Make display of patron restrictions, charges, notes, etc. consistent for check out and patron details screens -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 25173] New: Create list of parameters to choose from via a query
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25173 Bug ID: 25173 Summary: Create list of parameters to choose from via a query Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently, you can use something like <<Library|branches>> to have a parameter prepopulate with choices from predetermined tables (in this case, from branches), or you can point to a authorised list. But, if you want to prepopulate from other tables, you are out of luck. I would love to be able to do something like <<List|(SELECT shelfname FROM virtualshelves)>> and have it prepopulate with the results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8