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

[Bug 5847] New: Manage Staged MARC Records stuck at 0% if isbn matching rule selected.
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5847 Bug #: 5847 Summary: Manage Staged MARC Records stuck at 0% if isbn matching rule selected. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: critical Priority: P1 Component: MARC Bibliographic record staging/import AssignedTo: gmcharlt(a)gmail.com ReportedBy: kmkale(a)anantcorp.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com If we try to use ISBN match rule while importing a staged batch, the Manage Staged MARC Records gets stuck at 0%. I can see a www-data owned background job running but the browser is stuck at 0% and no entries in the db. Tried leaving it overnight with no progress. Tried with firefox and chrome. Same MARC file is imported fine without using the ISBN match rule. The same marc records file imports fine with bulkmarcimport.pl utility even with the -isbn option. Sadly the bulkmarcimport.pl lacks the option to still add items even while ignoring a biblio if a isbn match is found. See attached screenshot for rules used during this import. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug.

1 4

[Bug 8878] New: koha-shell: a command to make using koha commands easier
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '14

09 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8878 Priority: P5 - low Change sponsored?: --- Bug ID: 8878 CC: robin(a)catalyst.net.nz Assignee: koha-bugs(a)lists.koha-community.org Summary: koha-shell: a command to make using koha commands easier Severity: enhancement Classification: Unclassified OS: All Reporter: robin(a)catalyst.net.nz Hardware: All Status: NEW Version: master Component: Packaging Product: Koha Need a command that drops you into a shell with your environment set up for interacting with koha, by setting PERL5LIB and KOHA_CONF appropriately, etc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 7667] New: add a koha-setenv or an improved koha-foreach
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '14

09 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7667 Priority: P5 - low Change sponsored?: Seeking cosponsors Bug ID: 7667 Assignee: robin(a)catalyst.net.nz Summary: add a koha-setenv or an improved koha-foreach QA Contact: koha.sekjal(a)gmail.com Severity: enhancement Classification: Unclassified OS: All Reporter: mjr(a)ttllp.co.uk Hardware: All Status: NEW Version: unspecified Component: Packaging Product: Koha there should be an easy way to set the environment variables for a site in /etc/koha/sites, or to run a command on only one site through koha-foreach, or an interactive subshell. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 8233] New: New search engine layer - introduce solr without breaking anything else
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '14

07 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8233 Priority: P5 - low Change sponsored?: --- Bug ID: 8233 Assignee: gmcharlt(a)gmail.com Summary: New search engine layer - introduce solr without breaking anything else Severity: enhancement Classification: Unclassified OS: All Reporter: claire.hernandez(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Searching Product: Koha Introduce the Koha::SearchEngine work (hackfest12 kohacon12) and a first poc with Solr. The goal is to break nothing and provide a first work wich will be enhance. Please use the wiki or koha-devel for discussion: http://wiki.koha-community.org/wiki/SearchEngine_Layer_RFC -- You are receiving this mail because: You are watching all bug changes.

1 62

[Bug 8567] New: Set output directory for fines.pl in cron config created by the packages
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '14

04 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8567 Priority: P5 - low Change sponsored?: --- Bug ID: 8567 CC: robin(a)catalyst.net.nz Assignee: koha-bugs(a)lists.koha-community.org Summary: Set output directory for fines.pl in cron config created by the packages Severity: enhancement Classification: Unclassified OS: All Reporter: magnus(a)enger.priv.no Hardware: All Status: NEW Version: master Component: Packaging Product: Koha When the Debian packages are installed, they create a /etc/cron.daily/koha-common config based on the template in debian/koha-common.cron.daily. This results in the following command for fines.pl: koha-foreach --enabled /usr/share/koha/bin/cronjobs/fines.pl and this results in this script writing daily log files to /tmp, which is less than ideal. Now, fines.pl has an option --out to specify where the logs are saved, so we could change the cron config to something like this: koha-foreach --enabled /usr/share/koha/bin/cronjobs/fines.pl --out /var/log/koha/__instancename__ Caveat: This depends on Bug 8566 being implemented first! (Because without it there is no way for koha-foreach to use directories named after the instances.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 7441] New: search results showing wrong branch?
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '14

03 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7441 Bug #: 7441 Summary: search results showing wrong branch? Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 - low Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com When you search in the OPAC it shows you the HOME branch on the location in XSLT (see here: http://screencast.com/t/m870Mr8Wm) but if you click through to the detail page it shows you the CURRENT BRANCH in the holdings table which is very confusing to patrons. I don't know what's the right solution - home or holding branch, but they should be the same in both places for the patron's sake. If you do the same search in the staff client you see the right branch info on the search results and on the detail page. Nicole -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 83

[Bug 8466] New: Holds on MARC records with no item causes silent error in koha-error_log
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '14

03 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8466 Priority: P5 - low Change sponsored?: --- Bug ID: 8466 CC: m.de.rooy(a)rijksmuseum.nl Assignee: gmcharlt(a)gmail.com Summary: Holds on MARC records with no item causes silent error in koha-error_log Severity: minor Classification: Unclassified OS: All Reporter: kolpen(a)o2.pl Hardware: All Status: NEW Version: rel_3_6 Component: Cataloging Product: Koha Created attachment 10931 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=10931&action=edit proposed (two) patches While cataloging, viewing MARC details of record that hasn't items yet, a silent error occurs in koha-error_log when a librarian clicks on the "Holds" tab. The error messages are like that: request.pl: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 3 at /usr/share/koha/lib/C4/Koha.pm line 811., request.pl: DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/C4/Koha.pm line 814., The reason is an empty items value in dynamically build query in procedures: - Module: Items.pm, procedure: GetItemInfosOf - Module: Biblio.pm, procedure: GetBiblioItemInfosOf Proposed patch refers to the version 3.6.4 The bug occurs also in later Koha versions (ie. 3.6.6, 3.8) and the same patches should be implemented there (it is only one line add), respectively: Module: Items.pm - line 1064 in version 3.6.6; line 1069 in version 3.8 Module: Biblio.pm - line 1014 in version 3.6.6; line 1026 in version 3.8 -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 10068] New: Move from the utf8:: pragma methods to Encode::
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '14

02 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10068 Bug ID: 10068 Summary: Move from the utf8:: pragma methods to Encode:: Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com As stated by Larry Wall [1] we should not be using the loose (UTF-8 implementation) utf8::encode utf8::decode methods, and using Encode::encode and Encode::decode (respectively) instead, which are stricter. At first sight this might have important consequences (breakage for people having bad data). I belive it won't: we currently have reports on the lists of people having trouble with wide characters and bad encodings on the lists. (I think) several libs, we rely on, use UTF-8 instead of utf8. And we are not catching encoding problems properly because of the mixture. To+ [1] http://perldoc.perl.org/Encode.html#UTF-8-vs.-utf8-vs.-UTF8 -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 8566] New: Enable koha-foreach to insert the instancename into commands
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '14

02 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8566 Priority: P5 - low Change sponsored?: --- Bug ID: 8566 CC: robin(a)catalyst.net.nz Assignee: koha-bugs(a)lists.koha-community.org Summary: Enable koha-foreach to insert the instancename into commands Severity: enhancement Classification: Unclassified OS: All Reporter: magnus(a)enger.priv.no Hardware: All Status: NEW Version: master Component: Packaging Product: Koha The synopsis for koha-foreach looks like this: koha-foreach [--enabled] [--email|--noemail] [command] It is used e.g. in cron configs, like this: koha-foreach --enabled /usr/share/koha/bin/cronjobs/fines.pl It would be very useful if we could provide a placeholder in the command, which could then be replaced with the name of the current instance. Then we could do e.g.: koha-foreach --enabled /usr/share/koha/bin/cronjobs/fines.pl --out /var/log/koha/__instancename__ and have fines.pl use the right directory for each instance. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 7518] New: searches with quotation marks don't work
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '14

02 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7518 Bug #: 7518 Summary: searches with quotation marks don't work Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: melia(a)bywatersolutions.com QAContact: koha.sekjal(a)gmail.com A search term without quotation marks returns the expected results. The same search term with quotation marks returns no results. I expected Koha to ignore the quotation marks and return results anyway... -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 56