January 2014 - Koha-bugs - lists.koha-community.org

[Bug 5552] New: circ dates in the past
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5552 Summary: circ dates in the past Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/circ/circulation.pl OS/Version: All Status: NEW Severity: major Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Created attachment 2918 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2918 error box with due date When you choose a due date in the past a box appears asking you to confirm the date. This box should have a calendar icon and a date format tip like all other date boxes in Koha to prevent big mistakes. -- 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 7635] New: ignoring hold still marks it in transit
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '14

10 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7635 Bug #: 7635 Summary: ignoring hold still marks it in transit Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 - low Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com Steps reproduce: 1. checkin item 2. ignore hold prompt to transfer 3. item says in transit on holds tab 4. item not listed in transfers to receive 5. item not listed in transit on the holdings table on the detail screen So the item isn't really in transit, but the holds tab seems to think it is and it's confusing to librarians looking at the holds tab. -- 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 7

[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 11453] New: Update EN default UNIMARC bibliographic framework
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '14

09 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11453 Bug ID: 11453 Summary: Update EN default UNIMARC bibliographic framework 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: bgkriegel(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org English default UNIMARC bibliographic framework need to be updated. UNIMARC manual (2008) http://archive.ifla.org/VI/8/unimarc-concise-bibliographic-format-2008.pdf Updates (2012) http://www.ifla.org/node/7974 -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 11650] New: multiplicated authorities after link_bibs_to_authorities.pl
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '14

07 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11650 Bug ID: 11650 Summary: multiplicated authorities after link_bibs_to_authorities.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: gmcharlt(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Under certain circumstances misc/link_bibs_to_authorities.pl creates multiple authority with identical heading. Test scenario: 1. Have some (2-3) biblio records with some repeated headings Have BiblioAddsAuthorities = allow, AutoCreateAuthorities = generate Have no authority records 2. Run misc/link_bibs_to_authorities.pl script 3. You will get multiple authority records -- one for each occurence of a heading in biblio record. -- You are receiving this mail because: You are watching all bug changes.

1 8

[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 11638] New: Untranslatable "Tag editor" in addbiblio.pl
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '14

03 Jul '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11638 Bug ID: 11638 Summary: Untranslatable "Tag editor" in addbiblio.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr addbiblio.pl has a hard-coded (and therefore untranslatable) "Tag editor" text. It appears in two places in the code. Also: print "Content-Type: text/html\n\n<html><body><h1>ERROR when DELETING BIBLIO $biblionumber : $error</h1></body></html>"; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14