November 2024 - Koha-bugs - lists.koha-community.org

[Bug 29575] New: Add a JS render function equivalent of the patron-title.inc TT include
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29575 Bug ID: 29575 Summary: Add a JS render function equivalent of the patron-title.inc TT include Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Blocks: 28854, 28874, 29275 We need a re-usable function that will use the json patron object as returned from the API and render an equivalent to the TT patron-title.inc output. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28854 [Bug 28854] [ALTERNATIVE] Add ability to create bundles of items https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28874 [Bug 28874] We need javascript equivalents to many of our TT plugins https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29275 [Bug 29275] Use the API to render checkout history for a biblio -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 29519] New: One should be able to resolve a return claim at checkin
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29519 Bug ID: 29519 Summary: One should be able to resolve a return claim at checkin 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, upon checking in an item that has a return claim associated with it, we highlight this to the librarian but we don't give any option to resolve the claim there and then (but we do mark the item as found in the background). We should give the librarian the option to resolve the claim. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 31633] New: Allow selection of branch to be applied in quick spine label CSS class
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31633 Bug ID: 31633 Summary: Allow selection of branch to be applied in quick spine label CSS class 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 28512 Bug 28512 makes the quick spine label include a css class of the logged-in library to facilitate branch-specific customization of labels. Some libraries may prefer that the spine label formatting key off of the item's homebranch or holdingbranch, rather than the user's logged-in branch. Maybe a system preference to select which branch to apply? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28512 [Bug 28512] Quick spine label creator: Add CSS class with logged in library's branchcode -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 30007] New: Make ->anonymize methods throw an exception if AnonymousPatron is not set
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30007 Bug ID: 30007 Summary: Make ->anonymize methods throw an exception if AnonymousPatron is not set Change sponsored?: --- Product: Koha Version: unspecified 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If the system preference AnonymousPatron is not set, the following methods should throw an exception: - Koha::Old::Hold(s)->anonymize - Koha::Old::Checkout(s)->anonymize -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 32030] New: Electronic resource management (ERM)
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 Bug ID: 32030 Summary: Electronic resource management (ERM) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: new feature Priority: P5 - low Component: Staff Client Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We are building an Electronic Resource Management (eRM) module for Koha. See the related resources for earlier communication: [Koha] Electronic Resource Management for Koha https://lists.katipo.co.nz/pipermail/koha/2022-February/057447.html “Electronic resource management (ERM) is the practices and techniques used by librarians and library staff to track the selection, acquisition, licensing, access, maintenance, usage, evaluation, retention, and de-selection of a library’s electronic information resources. These resources include, but are not limited to, electronic journals, electronic books, streaming media, databases, datasets, CD-ROMs, and computer software.” https://en.wikipedia.org/wiki/Electronic_resource_management Before the emergence of eRM's, libraries would typically store details of electronic subscriptions in a manual way, for example, Excel spreadsheets, or in cupboards or filing cupboards as paper documents. An eRM allows libraries to store and organise these documents electronically. It also services as an index to electronic subscriptions. An eRM can track the whole lifecycle of an electronic resource, from acquisition, to negotiating an agreement with a publisher, storing the license information, activating title and package resources online to identifying usage patterns with resources. Libraries will vary in size from small, specialist library (with maybe a few topic specific resources) like a music library to large universities who will subscribe to tens of thousands of titles. It maybe that a library wants to record a few dozens resources each with their own subscription with a publisher, or track thousands of titles from aggregators like EBSCO. The code is available at https://gitlab.com/joubu/Koha/-/commits/erm The entry point is at https://tree.taiga.io/project/joubu-koha-erm/wiki/home And the current work activities can be seen at https://tree.taiga.io/project/joubu-koha-erm/kanban -- You are receiving this mail because: You are watching all bug changes.

1 90

[Bug 31963] New: Only show reserve fee message on OPAC if they will actually be charged
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31963 Bug ID: 31963 Summary: Only show reserve fee message on OPAC if they will actually be charged Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hold fees can be set at the patron-category level, and if a patron who could be charged a reserve fee logs into the OPAC and tries the place a hold, a message about being charged a hold fee will show. This message does not take HoldFeeMode into consideration. When HoldFeeMode is set to "any time a reserve is collected" the message will be "You will be charged a hold fee of $X when you collect this item", but if HoldFeeMode is set to anything else, the message will be what we are seeing "You will be charged a hold fee of $X for placing this hold". This message can be a bit unexpected, especially if HoldFeeMode is set so hold fees should only be charged if all items are checked out and the record has at least one hold already. We don't expect we should see the message if there are items available and no holds on the record, when HoldFeeMode is set this way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 31236] New: Add ability to send custom item fields via SIP using Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31236 Bug ID: 31236 Summary: Add ability to send custom item fields via SIP using Template Toolkit 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha has been able to send arbitrary item fields via the "item_field" parameter in the config. We have partners that need the ability to created custom item fields from templates, as the item_fields feature cannot accomplish what they need. We need to add a templated custom field feature for items, similar to what we have for patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 26368] New: Add support for OCLC Encoding level values
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26368 Bug ID: 26368 Summary: Add support for OCLC Encoding level values 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl https://www.oclc.org/bibformats/en/fixedfield/elvl.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 31692] New: Let librarians change item level holds to record level holds when possible
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31692 Bug ID: 31692 Summary: Let librarians change item level holds to record level holds when possible Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha has item level holds (only a specific item was requested) and record level holds (any next available item). There can be a case when a librarian wishes to change an item level hold to a record level hold. This is currently not (easily) possible, as they would have to cancel the hold and then set another type of hold and place it to the previous point in hold queue. This Bug aims to add an easy way to change hold types. Only one type of hold is allowed simultaneously for a record and a patron. The two types cannot be mixed. In other words a patron can't have both item level and record level holds on a specific record at the same time. This must be kept in mind when designing such functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 82

[Bug 31033] New: SIP2 does not correctly handle multiple simultaneous connections
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31033 Bug ID: 31033 Summary: SIP2 does not correctly handle multiple simultaneous connections Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: marka(a)pobox.com QA Contact: testopia(a)bugs.koha-community.org If two connections are made to the SIP2 server simultaneously, the second connection does not receive any replies until the first connection is closed. Here is how I reproduced the problem: In terminal #1, use 'telnet koha.ourlibrary.com 6001' to connect to the SIP2 server. Send a 9300CN message to log into SIP2. The SIP2 server sends back the expected 941 response. In terminal #2, use telnet in the same way to connect to the SIP2 server. Then try sending the 9300CN message to log in. The SIP2 does not send any response. In terminal #1, close the telnet connection. Now terminal #2 receives its expected 941 message. This problem was discovered by Lyrasis, a content provider that we are trying to integrate with our library's Koha installation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33