December 2016 - Koha-bugs - lists.koha-community.org

[Bug 15503] Grab Item Information from Order Files
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15503 --- Comment #47 from Benjamin Daeuber <bdaeuber(a)cityoffargo.com> --- Created attachment 58165 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58165&action=ed… Item information after import 1 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15503] Grab Item Information from Order Files
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15503 --- Comment #46 from Benjamin Daeuber <bdaeuber(a)cityoffargo.com> --- Created attachment 58164 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58164&action=ed… Import screen I've attached a screenshot of the import screen, where I've highlighted in red the collection. That collection is the top alphabetical, even though the based on the collection in the order file, the first should be a book and the next a book club in a bag. It appears at this point that the collection code is correct. I've highlighted in green. The next two are ccode_1 and ccode_2, which are the item edit screens for both of these items. They both have the top collection code alphabetically, rather than the collection code we saw at import. Again, called in in green. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 17760] New: patron search not working in firefox
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17760 Bug ID: 17760 Summary: patron search not working in firefox Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com After upgrading my test version from 3.22.2 to 16.5.5.1 I observed problems when searching patrons. These problems were not visible when using MS-IE11. However normally I am using Firefox(50.0.2) and the following problems are observed: Giving the patrons full cardnumber (barcode) : ok, everything is fine. Giving a substring of username or cardnumber : no success (even the small pop-up "loading" doesn't show. Choosing the start letter of the username: no success. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 14224] patron notes about item shown at check in
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14224 Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #27 from Jonathan Druart <jonathan.druart(a)bugs.koha-community.org> --- Aleisha, Have a look at your patches, there are some weird stuffs to fix: 1/ kohastructure: you re-add the entire item table 2/ update db: you should specify the "after" sql clause to keep the same order as the kohastructure (not necessary useful but good practice to have) 3/ There is no need to use strict and warnings alongside Modern::Perl; 4/ The svc script has a BibLibre copyright 5/ I don't understand the need of the new subroutine in the svc script (ajax_auth_cgi). You should not need it, have a look at how the other svc scripts deal with authentication 6/ QA script fails with: FAIL installer/data/mysql/sysprefs.sql FAIL sysprefs_order Not blocker: Sysprefs AllowIssueNotes is bad placed (see bug 10610) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15503] Grab Item Information from Order Files
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15503 --- Comment #45 from Matthias Meusburger <matthias.meusburger(a)biblibre.com> --- Benjamin, I can successfully map ccodes and item types. Can you explain this sentence : "Even on initial import (i.e the order edit screen when adding to a basket), it simply shows the our top collection alphabetically."? Notforloans are working for me (items are shown not available when needed) but I tested it with my last patch. Could you have another look at it? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7187] Prioritize cover image sources such as Amazon, Google and add fail over i.e. if first source fails, go to next
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7187 --- Comment #42 from Chris Cormack <chris(a)bigballofwax.co.nz> --- Yes, bug 9850 meets all the requirements of this. We have it in production for our sites. So we will not be doing any more work on this. Our recommendation is to use coce for book covers -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7187] Prioritize cover image sources such as Amazon, Google and add fail over i.e. if first source fails, go to next
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7187 --- Comment #41 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- We are really interested in this as well - centralizing the code would make it easier to add new content providers. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14570] Make it possible to add multiple guarantors to a record
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14570 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jweaver(a)bywatersolutions.co |kyle(a)bywatersolutions.com |m | Status|Needs Signoff |Failed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14570] Make it possible to add multiple guarantors to a record
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14570 --- Comment #14 from Owen Leonard <oleonard(a)myacpl.org> --- Created attachment 58159 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58159&action=ed… Proposal for initial state of add guarantor form It seems that now the search for patrons to select as a guarantor includes patrons with a 'Child' type patron category. Is that intentional? Shouldn't they be excluded? I notice also that when you select a patron to be a guarantor, the patron number is no longer a link to the patron record. I think it would make more sense to not show the borrowernumber at all, but make the guarantor name a link: <a href="moredetail.pl?borrowernumber=0000">Surname, Firstname (cardnumber)</a> I think it's confusing that there are two buttons, 'Add guarantor', 'Set to patron.' They could potentially mean the same thing. I think we might have the initial state of this form have only two links: 'Search to add guarantor' and 'Add guarantor manually' (see attached image). Clicking the 'Add manually' link would display the form along with a submit button, and the "Clear" link would be shown. The manual add form should prevent the user from submitting empty data. Sorry, I know that's a lot, and I'm willing to help with follow-ups if folks think these are good ideas. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7187] Prioritize cover image sources such as Amazon, Google and add fail over i.e. if first source fails, go to next
by bugzilla-daemon＠bugs.koha-community.org 13 Dec '16

13 Dec '16

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7187 --- Comment #40 from Magnus Enger <magnus(a)libriotech.no> --- (In reply to Chris Cormack from comment #37) > We are actually evaluating 9580 at the moment to see if it will meet all the > requirements of this bug. Will let you know shortly Any results from the evaluation yet? ;-) -- You are receiving this mail because: You are watching all bug changes.

1 0