March 2017 - Koha-bugs - lists.koha-community.org

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #10 from Olli-Antti Kivilahti <olli-antti.kivilahti(a)jns.fi> --- Created attachment 60937 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=60937&action=ed… Bug 15399 - MARCXML records larger than 1 MB (1048576 bytes) are not searchable. fka. KD-1512 - Remove items from the search index for serial mothers Make stuff searchable again. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12478] Elasticsearch support for Koha
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 alfre69 <alfre(a)ibdinternet.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alfre(a)ibdinternet.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 --- Comment #9 from alfre69 <alfre(a)ibdinternet.com> --- If you increase $max_record_size too much it breaks the Z39.50 server. A yaz-client search report this: Target has closed the association. Reason: protocolError, message: Incoming package too large -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15399] MARCXML records larger than 1 MB (1048576 bytes) are not searchable.
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15399 alfre69 <alfre(a)ibdinternet.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alfre(a)ibdinternet.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7614] Branch transfer limit and holds
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7614 --- Comment #13 from Koha Team AMU <koha.aixmarseille(a)gmail.com> --- I tried to test in sandbox but failed : The sandbox you've requested is not ready. Some problems occurred applying patches from bug 7614: <h1>Something went wrong !</h1>Applying: Bug 7614: Add a new method Koha::Libraries->pickup_locations Applying: Bug 7614: Check transfer limit in CanBookBeReserved and CanItemBeReserved Applying: Bug 7614: Check branch transfer limits in opac-reserve.pl Applying: Bug 7614: Consider transfer limits in Koha::Template::Plugin::Branches fatal: sha1 information is lacking or useless (Koha/Template/Plugin/Branches.pm). Repository lacks necessary blobs to fall back on 3-way merge. Cannot fall back to three-way merge. Patch failed at 0001 Bug 7614: Consider transfer limits in Koha::Template::Plugin::Branches When you have resolved this problem run git bz apply --continue. If you would prefer to skip this patch, instead run git bz apply --skip. To restore the original branch and stop patching run git bz apply --abort. Bug 7614 - Branch transfer limit and holds 60141 - Bug 7614: Add a new method Koha::Libraries->pickup_locations 60142 - Bug 7614: Check transfer limit in CanBookBeReserved and CanItemBeReserved 60785 - Bug 7614: Check branch transfer limits in opac-reserve.pl 60786 - Bug 7614: Consider transfer limits in Koha::Template::Plugin::Branches 60787 - Bug 7614: Build a list of pickup locations in OPAC considering transfer limits Apply? [(y)es, (n)o, (i)nteractive] Patch left in /tmp/Bug-7614-Consider-transfer-limits-in-KohaTemplateP-J1NHLc.patch . -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7534] New OPACAllowUserToChooseBranch setting for only showing libraries allowing holds
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7534 Koha Team AMU <koha.aixmarseille(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #35 from Koha Team AMU <koha.aixmarseille(a)gmail.com> --- (In reply to Jonathan Druart from comment #34) > (In reply to Koha Team AMU from comment #33) > > I don't change status to signed off because I can't test on sandbox 2 > > elements : > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7534#c18 > > This is done automatically on a sandbox. > > > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7534#c19 > > This is for the QA step. > > Go ahead :) Thank you very much for the explanations ! :-) So, it works as expected and I change status to signed off ! :-) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9988] Leave larger authority merges to merge_authorities cronjob ( pref AuthorityMergeLimit)
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '17

09 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9988 Jacek Ablewicz <abl(a)biblos.pk.edu.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abl(a)biblos.pk.edu.pl -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '17

08 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 Bouzid <bouzid.fergani(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff CC| |bouzid.fergani(a)inlibro.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12446] Enable an adult to have a guarantor
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '17

08 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 Bouzid <bouzid.fergani(a)inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #60930|0 |1 is obsolete| | --- Comment #45 from Bouzid <bouzid.fergani(a)inlibro.com> --- Created attachment 60934 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=60934&action=ed… Bug 12446 - Enable an adult to have a guarantor Concflicts has been fixed. Also attributes in system preference : AdditionalGuarantorField are now displayed correctly in all scenerios. I have rebased every patch. This includes all the features from the previous patches. Removed the dollar signs and stopped using C4::Category On the patron category page, there is a new field to specify whether patrons can be guarantee or not. The atomic update SQL script adds this new field and sets it to true for categories of type "C" and "P". 1) Apply the patch 2) Run updatedatabase.pl to add AdditionalGuarantorField to preferences and canbeguarantee to categories. 3) Go to patron category administration, edit a category and change the value of Can Be Guarantee to yes (for Child and Professional mostly to set it by default) 4) See below to test various scenarios - Enable an adult to have a guarantor: 0.0) Create or edit a patron category of type 'A'. 0.1) Set the "Can be guarantee" field to "Yes" and save. 1) Select an adult patron -> details tab; 2) Click edit button; 3) validate "guarantor information" fieldset; - Shows guarantees' fines in the guarantor's page: 4) Click Set to patron button and select a guarantor; 5) Generate a fine; 6) Select guarantor patron -> details tab; 7) Validate guarantee's fine information. - Transfer some guarantor's information to the guarantee while adding a guarantiee: 0) Select an adult patron; 1) Insert all information; 2) Click Add guarantiee bouton; 3) Validade Garantor information/Main address/Contact fieldsets filled; - Transfer some guarantor's information to the guarantee while creating a new patron 0) Select an adult patron; 1) Insert all information; 2) Add a new adult patron; 3) Click "Set to patron" button; 4) Select the adult patron from 0); 5) Validade Garantor information/Main address/Contact fieldsets filled; - Transfer some guarantor's information to the guarantee while adding a guarantiee: 0) Select an adult patron; 1) Insert all information; 2) Click Add guarantiee bouton; 3) Validade Garantor information/Main address/Contact fieldsets filled; - Transfer guarantor's alternate address/contact to the guarantee while creating a new patron: 0) Search AdditionalGuarantorField preference; 1) Insert some additional database columns from alternate address/contact to be transferred from guarantor; 2) Select an adult patron; 3) Insert all information; 4) Add a new adult patron; 5) Click "Set to patron" button; 6) Select the adult patron from 0); 7) Validade Garantor information/Main address/Contact fieldsets filled; 8) Validade Garantor additional alternate address/contact filled; - Transfer guarantor's alternate address/contact to the guarantee while adding a guarantiee: 0) Search AdditionalGuarantorField preference; 1) Insert some additional database columns from alternate address/contact to be transferred from guarantor; 3) Select an adult patron; 4) Insert all information; 5) Click Add guarantiee bouton; 6) Validade Garantor information/Main address/Contact fieldsets filled; 7) Validade Garantor additional alternate address/contact filled; -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13153] Waiting hold checked in at different library doesn' t re-route item to correct library
by bugzilla-daemon＠bugs.koha-community.org 08 Mar '17

08 Mar '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13153 Christopher Brannon <cbrannon(a)cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |In Discussion --- Comment #15 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- There seems to be an intermittent problem with routing/information. I tried my previous scenario again, and it worked fine this time, but then I got the same failure through a different scenario. 1) Checked in item with no checkouts or holds belonging to Library B at Library A for transfer. Item is now in transit to Library B. 2) Placed a hold on item to be picked up at Library C. 3) Triggered hold at Library A and was routed to Library C. Item is in transit to Library C. 4) Signed in as Library D, checked in item and it routed Library C fine. 5) Signed in as Library C and triggered the hold. Item is now waiting. 6) Signed in as Library D, checked in item. The modal doesn't come up, and the transfer message is on the screen to got to transfer the item to Library C, but patron barcode and name are missing. 7) If I cancel the transfer and check it in again, the modal comes up and patron information shows properly. I think there is a conflict with an initial transfer that doesn't get cleared out in the whole process. On master, if I follow the same steps, this is what I see: 1) Checked in item with no checkouts or holds belonging to Library B at Library A for transfer. Item is now in transit to Library B. 2) Placed a hold on item to be picked up at Library C. 3) Triggered hold at Library A and was routed to Library C. Item is in transit to Library C. 4) Signed in as Library D, checked in item and it wants to go home to Library B. WRONG 5) Signed in as Library C and triggered the hold. Item is now waiting. 6) Signed in as Library D, checked in item. The modal doesn't come up, and the transfer message is on the screen to got to transfer the item HOME to Library B, AND to confirm hold for patron. The library the patron is picking up at is NOT showing, but patron name and barcode ARE showing. The extra bullet is showing and is a pre-existing issue. 7) If I cancel the transfer and check it in again, there are no messages and a local use is recorded. WRONG -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0