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

[Bug 24857] New: Add ability to create "Volumes" for records, and assign items to volumes
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24857 Bug ID: 24857 Summary: Add ability to create "Volumes" for records, and assign items to volumes 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We have a partner that needs Volume Level Holds. This is a feature that some ILSs have that allows the creation of volumes at the bibliographic level, with items being optionally assigned to a given volume. This facilitates the ability to place holds at a volume level, rather than on a specific item or any available item on a record. This but is to add just the volume management itself, which no functionality tied to volumes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 697

[Bug 31339] New: Use Template::Toolkit WRAPPER for Koha Plugins
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31339 Bug ID: 31339 Summary: Use Template::Toolkit WRAPPER for Koha Plugins 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Rather than requiring Koha plugins to create entire templates, let's provide Template::Toolkit WRAPPER files to allow them to more easily integrate. This should also make it easier for plugins to fit into different versions of Koha. -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 18891] New: Download Reports Directly
by bugzilla-daemon＠bugs.koha-community.org 09 Oct '25

09 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18891 Bug ID: 18891 Summary: Download Reports Directly 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: cslone(a)camdencountylibrary.org QA Contact: testopia(a)bugs.koha-community.org There should be an option to download a report directly, rather than having to run the report and then choose to download it (effectively running it twice). This would be especially helpful when dealing with reports that take a while to load, though it would also be convenient for reports that are run regularly for distribution and therefore really don't need to be previewed on the screen before downloading. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 18147] New: Records images in public lists
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18147 Bug ID: 18147 Summary: Records images in public lists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Hi, We have a request to put the image of the records (which is normally present in the left column in the results board of a catalog search) in the results board of the public list (where they don’t appear anywhere). The image will not appears even if the record had one and can be seen when you clic on detailed infos page of the record from this page. 1)Got ot list module 2)Go to public list 3)Find a record that had an image (you have to select the detailed page one by one for each to find one) 4)After you found one, do « previous page » 5)Observe if no image are present there (there will be nothing) Some librairians making public lists for students and they would like to have the images because it's more easy to do lists with that. Thanks, Alexandre from CCSR -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 26479] New: Self checkout: option for returning items is missing with SCOAllowCheckin
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26479 Bug ID: 26479 Summary: Self checkout: option for returning items is missing with SCOAllowCheckin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When returning items from the self checkout screens is allowed, there is no link to do so in GUI. It looks like the table of checkouts should have a return item link in the manual, but there is only a renew link visible https://koha-community.org/manual/20.05/en/html/circulation.html#self-check… To test: - Activate WebBasedSelfCheck and SCOAllowCheckin - Go to the self checkout in OPAC - Check an item out - Verify there is only a renew link and no visible option to return it -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 23875] New: Elasticsearch - ES - When sorting by score we should provide a tiebreaker
by bugzilla-daemon＠bugs.koha-community.org 08 Oct '25

08 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23875 Bug ID: 23875 Summary: Elasticsearch - ES - When sorting by score we should provide a tiebreaker Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com In ES if we sort by 'relevance' we actually don't pass anything to ES and results are ordered by score. When doing a search limiting only by collection or type, the scores are all the same. This is fine, except that editing any record will then cause a reordering of the results, even though it won't affect the score. We should provide a tie-breaker in the case of equal sort scores -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 54

[Bug 30719] New: ILL should provide the ability to create batch requests
by bugzilla-daemon＠bugs.koha-community.org 07 Oct '25

07 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30719 Bug ID: 30719 Summary: ILL should provide the ability to create batch requests 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 Some interlibrary loan providers, for example Reprints Desk, allow for ILL requests to be submitted in batches. In the Reprints Desk case, a batch is created with the supplier, then requests are then submitted including the batch ID. Obviously, this workflow may differ according to supplier and these differences should be abstracted away into the supplier backend. For core Koha, we should provide the ability for it to recognise if a given backend can process batch requests. If so, we should provide an interface for creating and manipulating batches within Koha, then submitting a batch to the supplier. It should also be possible to view all batches and the contents of a given batch. The funding institution has defined the following workflow for creating and populating batches: - A encapsulating "batch" is created with a name and a requesting borrower - Requests are added to a batch via two methods: - In bulk: - A form which allows the user to paste in a collection of identifiers, such as DOI / PMID etc. - For each of these identifiers: - The request metadata should be populated via API queries to metadata suppliers, for example, PubMed API or LibKey/Browzine. This behaviour is governed by the presence of appropriate plugins. - (Optional) Once the metadata is populated for an item, we check for item availability via any installed ILL availability plugins - Individually: - A regular ILL request form, requests are added to the batch -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 194

[Bug 22815] New: Save item's homebranch in patron's fines list
by bugzilla-daemon＠bugs.koha-community.org 06 Oct '25

06 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22815 Bug ID: 22815 Summary: Save item's homebranch in patron's fines list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- bug 15136 added a column to the fines screen (boraccount.pl) that shows the item's home branch. If the item is deleted the branch information goes away. It would be helpful if that column was filled and the data saved so if the item is deleted the information is not lost. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31547] New: Lost item and check-in date
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '25

03 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31547 Bug ID: 31547 Summary: Lost item and check-in date Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aspencatteam(a)clicweb.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 140386 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=140386&action=e… word document for confusing check-in and return date Items that have gone lost from long overdue, and also lost items that have been paid have confusing date checked-in information. Perhaps more information could be added to the checkin date/time - for example in red system could say "long overdue to lost". On the circulation history, when an item has been paid for, instead of having just a return date, it could say in red "Date lost and paid" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 29074] New: DefaultHoldExpirationdatePeriod blank value interpreted as zero
by bugzilla-daemon＠bugs.koha-community.org 03 Oct '25

03 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29074 Bug ID: 29074 Summary: DefaultHoldExpirationdatePeriod blank value interpreted as zero 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 26498 If DefaultHoldExpirationdate is on and DefaultHoldExpirationdatePeriod is blank, the blank is treated as a zero and all holds are created with an expiration date of today. I'm not sure what the best answer is. We could: - add some text to the syspref to make clear that a blank is treated as zero - make it always save and display a zero when you try to save a blank or - make it treat a blank as disabled (and then add some text to the syspref to tell people that) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26498 [Bug 26498] Add option to set a default expire date for holds at reservation time -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37