May 2019 - Koha-bugs - lists.koha-community.org

[Bug 22689] New: Add ability for staff to cancel a SERIAL_ALERT
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '23

01 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22689 Bug ID: 22689 Summary: Add ability for staff to cancel a SERIAL_ALERT Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- The SERIAL_ALERT notice (RLIST notice prior to 18.05: See Bug 19794) is used to send an email to patrons who have subscribed to the alert service via their account. They are notified when a new issue for a subscription arrives. We have users who have left, and whose emails are no longer valid but who have not cancelled their alerts. These are generating quite a number of undeliverable emails, which bounce back. We know no way of cancelling the redundant SERIAL_ALERT via the Koha intranet other than by an SQL delete which we do not want to risk. Ideally there would be a way for staff to kill off these redundant alerts. Perhaps the alert cancellation could be tied to the borrowers.dateexpiry? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 16665] New: Add a staffadmin bar to the opac interface in order to edit the previewing record (MARC)
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16665 Bug ID: 16665 Summary: Add a staffadmin bar to the opac interface in order to edit the previewing record (MARC) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: dimantonak(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently when a librarian previewing a record in the opac interface and wants to edit that record, has to go to the staff interface, search again for that record and edit it. It would be useful to add a staffadmin bar (IF a librarian is logged in) linking to the staff interface (cgi-bin/koha/catalogue/detail.pl?biblionumber=#) in order to edit the MARC record directly. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 19166] New: Add the ability to add adjustments to an invoice
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19166 Bug ID: 19166 Summary: Add the ability to add adjustments to an invoice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The goal of this enhancement is to allow libraries to make adjustments to invoices based on feedback form a vendor (credit for returned books, damaged books, or fees for extra charges etc.) -- You are receiving this mail because: You are watching all bug changes.

1 158

[Bug 20824] New: Display of cancelled Orders show up in Acquisitions
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20824 Bug ID: 20824 Summary: Display of cancelled Orders show up in Acquisitions Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, any orders that have been cancelled will show up in Acquisitions (basket.pl). It would be nice from a display side, to have this view (cancelled orders ) be collapsed so if needed, they are still viewable, but generally they do not appear on this screen. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17723] New: Using MySQL on external server - lack of documentation giving example
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17723 Bug ID: 17723 Summary: Using MySQL on external server - lack of documentation giving example Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: fooquency(a)gmail.com I am trying to create a Koha instance using MySQL on a remote server. https://wiki.koha-community.org/wiki/Debian#Create_a_Koha_instance states: "create a new file in its place containing the connection information for the server, in the form of a my.cnf file." but no example is given. I would assume this somehow allows specification of all of hostname, username and password, but it is entirely unclear currently how to do this. Could someone kindly add an example or give more details of what format exactly "the connection information" should be in? http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html has no mention of a password configuration for instance. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 17311] New: koha-common service should be restarted on upgrade
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '23

27 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17311 Bug ID: 17311 Summary: koha-common service should be restarted on upgrade Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The upgrade process should restart the koha-common service. This is needed so Plack processes are restarted too and Koha version is reloaded (otherwise end users keep getting upgrade messages on the UI. Any other patched file will be reloaded (apache, zebra, etc). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 22214] New: New authority RDA indexes
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '23

27 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22214 Bug ID: 22214 Summary: New authority RDA indexes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: viliam.polonec(a)snk.sk Target Milestone: --- Is it possible to add new authority indexes: birth_date / death_date / birth_place / death_place / country / related_place / field_of_activity / occupation / gender / language that are RDA compiliant? Also the KOHA OPAC ability to search by theese new indexeses. thank you -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 17892] New: Move _extract_biblionumbers to a module
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17892 Bug ID: 17892 Summary: Move _extract_biblionumbers to a module 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org See bug 17273 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17848] New: Count not updated in digest-only notices
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17848 Bug ID: 17848 Summary: Count not updated in digest-only notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: rbit(a)rbit.cz QA Contact: testopia(a)bugs.koha-community.org When using <count>> in CHECKIN/CHECKOUT/RENEWAL notices, its value is not correctly updated. A letter is prepared during the first round and then its updated with iterated data items as they come. This means that placeholders like <<count>> are not updated anymore so we can see letters saying eg. "you returned 3 items", but in the fact there is much more of them listed in: ---- <<biblio.title>> ---- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 17730] New: Uniform mapping for biblio.biblionumber (Unimarc)
by bugzilla-daemon＠bugs.koha-community.org 25 Jun '23

25 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17730 Bug ID: 17730 Summary: Uniform mapping for biblio.biblionumber (Unimarc) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: dubyk(a)library.lviv.ua QA Contact: testopia(a)bugs.koha-community.org Created attachment 57999 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57999&action=ed… Screenshot I try to deal with empty links to record details in the search. I found that this occurs when used mapping 090$9<>biblio.biblionumber (in uk-UA Unimarc tables) and typical use UNIMARCslim2intranetResults.xsl. In Koha mapping of biblio.biblionumber and MARC-fields mentioned in many files: etc / zebradb / marc_defs / unimarc / biblios / record.abs 25 melm 001 Local-number,Local-number:n 26 # Local-number (biblionumber can be either in 090$9 or, on some setup, on 001) 28 melm 090$9 Local-number,Local-number:n etc / zebradb / marc_defs / unimarc / biblios / biblio-koha-indexdefs.xml 9 <index_control_field tag="001"> 10 <target_index>Local-number:n</target_index> 11 </index_control_field> 20 <index_subfields tag="090" subfields="9"> 21 <target_index>Local-number:w</target_index> 22 <target_index>Local-number:n</target_index> 23 </index_subfields> etc / zebradb / marc_defs / unimarc / biblios / biblio-zebra-indexdefs.xsl 47 <xslo:template match="marc:controlfield[@tag='001']"> 48 <z:index name="Local-number:w"> 49 <xslo:value-of select="."/> 50 </z:index> 51 <z:index name="Local-number:n"> 52 <xslo:value-of select="."/> 53 </z:index> 54 </xslo:template> 63 <xslo:template mode="index_subfields" match="marc:datafield[@tag='090']"> 64 <xslo:for-each select="marc:subfield"> 65 <xslo:if test="contains('9', @code)"> 66 <z:index name="Local-number:w Local-number:n"> 67 <xslo:value-of select="."/> 68 </z:index> 69 </xslo:if> 70 </xslo:for-each> 71 </xslo:template> koha-tmpl / opac-tmpl / bootstrap / en / xslt / UNIMARCslim2OPACDetail.xsl 21 <xsl:variable name="biblionumber" select="marc:datafield[@tag=090]/marc:subfield[@code='a']"/> koha-tmpl / intranet-tmpl / prog / en / xslt / UNIMARCslim2intranetDetail.xsl 22 <xsl:variable name="biblionumber" select="marc:datafield[@tag=090]/marc:subfield[@code='a']"/> koha-tmpl / opac-tmpl / bootstrap / en / xslt / UNIMARCslim2OPACResults.xsl 25 <xsl:variable name="biblionumber" 26 select="marc:datafield[@tag=090]/marc:subfield[@code='a']"/> koha-tmpl / intranet-tmpl / prog / en / xslt / UNIMARCslim2intranetResults.xsl 25 <xsl:variable name="biblionumber" select="marc:controlfield[@tag=001]"/> t / db_dependent / Biblio.t 84 'biblio.biblionumber' => { tagfield => '999', tagsubfield => 'c' }, biblio.biblionumber in UNIMARC-tables: ru-RU 090^9 es-ES 001^@ en 001^@ fr-FR 001^@ pl-PL 999^9 it-IT 001^@ uk-UA 090^9 That is, in the context of biblio.biblionumber mentioned next subfields: 090^9 001^@ 999^9 090^a 999^c Probably for greater uniformity is better to use one subfield for biblio.biblionumber. Maybe 001^@? -- You are receiving this mail because: You are watching all bug changes.

1 3