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

[Bug 10994] Allow use of branch/kohaAdmin e-mail address for sending claim notices
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10994 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amitddng135(a)gmail.com |koha-bugs(a)lists.koha-commun | |ity.org Status|ASSIGNED |NEW -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 17707] New: Check out and due date are same
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17707 Bug ID: 17707 Summary: Check out and due date are same Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 57860 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57860&action=ed… Circulation module screenshot My Koha version 16.05.5 Check out and due dates are same. Please see the attached screenshot. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 17745] New: Notices does not generate
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17745 Bug ID: 17745 Summary: Notices does not generate Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimal0212(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 58049 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58049&action=ed… Notices screenshot Dear Friends, My friends and me got problem regarding notices. Our Koha version is 16.05.5 Checked out 3 books. Notice (Digest) sent by Koha. It includes 3 books details. When the books check in two notices generated and sent, third book notice notice not generate by Koha. See the screen shot. https://s23.postimg.org/5klk9em63/Sent_notices_for_Vimal_Kumar_2.png -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 17907] New: Sessions Table disappearing continuously while google authentication is on
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17907 Bug ID: 17907 Summary: Sessions Table disappearing continuously while google authentication is on Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: mahsandu(a)gmail.com Created attachment 58984 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58984&action=ed… Messages when the problem occurs. >From recent days after upgrading to Koha-16.11 Sessions table dissappearing like it is not there. We need to re-enter the table to login to staff area. Steps to reproduce: I am unable to give any steps. But when the problem occurs. Staff login is impossible. Possible Solution: If you restore the sessions table or drop and recreate. It works again perfectly. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 18088] New: Software error additem.pl Can' t call method subfield error. Can't add items.
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18088 Bug ID: 18088 Summary: Software error additem.pl Can't call method subfield error. Can't add items. Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: hard359(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl While adding items it sais: Can't call method "subfield" on an undefined value at /usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 91. Line 88 to 103 sub _increment_barcode { my ($record, $frameworkcode) = @_; my ($tagfield,$tagsubfield) = &GetMarcFromKohaField("items.barcode",$frameworkcode); unless ($record->field($tagfield)->subfield($tagsubfield)) { my $sth_barcode = $dbh->prepare("select max(abs(barcode)) from items"); $sth_barcode->execute; my ($newbarcode) = $sth_barcode->fetchrow; $newbarcode++; # OK, we have the new barcode, now create the entry in MARC record my $fieldItem = $record->field($tagfield); $record->delete_field($fieldItem); $fieldItem->add_subfields($tagsubfield => $newbarcode); $record->insert_fields_ordered($fieldItem); } return $record; } -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 18199] New: Proxy support for UsageStats
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18199 Bug ID: 18199 Summary: Proxy support for UsageStats Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: tkalix(a)bredex.de QA Contact: testopia(a)bugs.koha-community.org Hello, I have had problems uploading the usage stats. The monthly script failed with some error message. The solution was to edit the file UsageStats.pm and insert my http proxy after line 347. And now it is working fine. It would be good if the utility uses the proxy support I configured in Koha, so one does not need to use the workaround I did. Thanks, Torsten. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 19923] New: conceptual searching in koha
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19923 Bug ID: 19923 Summary: conceptual searching in koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: reza0770(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Dear Friends, Why can’t we used the references systems (conceptual searching) based on our authority files in the OPAC of KOHA. What is the matter exactly and what should we do for using its benefits. Mainly, we have some authority files including subjective authority data, name authority data, etc., But our end users can’t do conceptual searches in the OPAC. For instance, where a user searches a non-preferred term of a name or a subject, the KOHA searching system (in the OPAC environment) cannot recognizes the relationship between the searched terms to the related preferred term in an authority file. While KOHA supports such kind of search in the authority data module. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19948] New: Rest API documentation is out of date in Koha manual
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19948 Bug ID: 19948 Summary: Rest API documentation is out of date in Koha manual Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The 'REST services' documentation does not fit the current implementation of the koha rest API. For instance, the documentation shows a 'user' endpoint: GET user/byid/:borrowernumber/holds GET user/:user_name/holds GET user/byid/:borrowernumber/issues GET user/:user_name/issues GET user/:user_name/issues_history GET user/byid/:borrowernumber/issues_history GET user/today GET user/all POST user But the endpoint implemented in api/v1 is "patrons", e.g. https://intranet.bywatersolutions.com/api/v1/patrons/221 The best current documentation that I'm aware of is https://wiki.koha-community.org/wiki/REST_api_RFCs It would be nice to build this documentation via api/v1/spec see also bug 17694 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 2786] Allow waiting holds to be diverted to different branch
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2786 --- Comment #7 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Lisette Scheer from comment #6) > (In reply to Katrin Fischer from comment #5) > > Would this work with the new feature to revert the waiting status? > > Yes, that does work! Once the hold is reverted we can change the pickup > branch and check the item in to send it on. > Lisette Great, thx for checking! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2786] Allow waiting holds to be diverted to different branch
by bugzilla-daemon＠bugs.koha-community.org 05 May '19

05 May '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2786 Lisette Scheer <lisetteslatah(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Lisette Scheer <lisetteslatah(a)gmail.com> --- (In reply to Katrin Fischer from comment #5) > Would this work with the new feature to revert the waiting status? Yes, that does work! Once the hold is reverted we can change the pickup branch and check the item in to send it on. Lisette -- You are receiving this mail because: You are watching all bug changes.

1 0