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

[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

[Bug 29515] New: Don't require title for HTML customizations
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29515 Bug ID: 29515 Summary: Don't require title for HTML customizations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 24387 The title field is mandatory for HTML customizations, but the field isn't used for display and doesn't make sense here. I think we should at least make it not mandatory, but possibly could remove it altogether. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24387 [Bug 24387] Rename News tool -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 18086] New: overduerules table is lacking foreign key constraints
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18086 Bug ID: 18086 Summary: overduerules table is lacking foreign key constraints Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com The overduerules table has no foreign key constraints to any for the related tables. The columns for branchcode, categorycode, letter1, letter2, and letter3 should all be foreign keys. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 101

[Bug 16698] New: UpdateItemLocationOnCheckin preference needs a gui editor
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16698 Bug ID: 16698 Summary: UpdateItemLocationOnCheckin preference needs a gui editor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 14576 adds a new syspref that accepts YAML for determining how the rules are applied. While there are other prefs accepting values in the same way, we should not expect users to understand YAML text formatting and should offer an easier option for entering the data We should decide on a best practice here for adding these guis. One option is to add pages on admin, however, I think this could get overwhelming the more sysprefs that use this method. I would propose adding a popup editor that will allow for easy entry, this editor will populate the syspref value so that advanced users can still access directly. Welcome to hear other thoughts, will proceed as proposed until then. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 18533] New: MARC::Record->encoding does not handle UNIMARC records
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '24

07 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18533 Bug ID: 18533 Summary: MARC::Record->encoding does not handle UNIMARC records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 18152 Regarding bug 18152 MARC::Record->encoding should not be called directly from our codebase. C4::Charset::SetMarcUnicodeFlag should call MARC::Record->encoding for MARC21 and NORMARC but does the UNIMARC trick for UNIMARC records. It seems that MARC::Record->encoding calls should be replaced with C4::Charset::SetMarcUnicodeFlag everywhere. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18152 [Bug 18152] UNIMARC bib records imported with invalid 'a' char in label pos.9 -- You are receiving this mail because: You are watching all bug changes.

1 3