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

[Bug 2370] MARC21 non-public note is mapped to items.paidfor
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2370 Bug 2370 depends on bug 4222, which changed state. Bug 4222 Summary: Nonpublic note not appearing in the staff client http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4222 What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |RESOLVED Resolution|--- |MOVED -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 4222] Nonpublic note not appearing in the staff client
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

1 0

[Bug 4222] Nonpublic note not appearing in the staff client
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4222 --- Comment #49 from Kyle M Hall <kyle(a)bywatersolutions.com> --- I completely agree. I think the best course of action is to have notes in the release that they will need to map the non-public note in each framework, then run misc/maintenance/touch_all_items.pl to pull the note into the db column. (In reply to David Cook from comment #48) > What do folks think about trying to resolve this issue in stages? > > 1) Add new non-public item note column to items and deleteditems > > 2) Add template stuff for the new column (even if the column is empty, which > would be the default, this wouldn't change any default system behaviour) > > That's it. The responsibility of updating frameworks and migrating data can > be left up to Koha administrators. It's not ideal, but it would be progress. > > Perhaps we could update the frameworks for a fresh install to show that's > how things should go in the future, but I don't see an automatic way of > fixing this for everyone and I don't think it makes sense to stop working on > this because it can't be perfect. > > > > > P.S. If I understand koha2marclinks.pl correctly, it is a frightening > script. On a test instance, it will say that "paidfor" is mapped to 952$x, > but it's not really...or rather...it's mapped to 952$x for the FA framework > but none of the others. That's incredibly misleading... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12541] New: Marc modification template - empty field
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12541 Bug ID: 12541 Summary: Marc modification template - empty field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Paola found the following bug on testing bug 11395 comment 33: ERROR on batch_record_modification.pl [I've checked only "Preview MARC"]: case of repeteable subfield [x] in repeteable fields [650]: My biblio record had 3 fields 650, each one had 3 $x: 650 0 ...... _x1-650 x 1 Digital techniques 1 _xfirst 650, second $x _x1-650 x 3 Digital techniques 3 650 0 ........ _x2-650 x 1 Digital techniques 1 _xsecond 650, second $x _x2-650 x 3 Digital techniques 3 650 0 ...... _x3-650 x 1 Digital techniques 1 _xthird 650, second $x _x3-650 x 3 Digital techniques 3 I wanted to delete only the second occurrence of $x, only in the second occurrence of 650 field. So my action was: (A) Delete field 650$x if 650$x matches RegEx m/ ^second 650 / On preview MARC the result is not what I wanted, but: 650 0 ... _x1-650 x 1 Digital techniques 1 _xfirst 650, second $x _x1-650 x 3 Digital techniques 3 650 0 .... 650 0 .... _x3-650 x 1 Digital techniques 1 _xthird 650, second $x _x3-650 x 3 Digital techniques 3 Then I've tried another action, selecting the "first" option: B) Delete 1st field 650$x if 650$x matches RegEx m/ ^second 650 / but the result remained the same as for "All" (A). Neither the 2 negative forms gave me what I wanted: C) Delete field 650$x unless 650$x does not match RegEx m/ ^second 650 / D) Delete 1st field 650$x unless 650$x does not match RegEx m/ ^second 650 / Similar behaviours occurred in Copy, Update and Move cases. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 12876] New: Reserve in waiting/transfer status may be cancelled by user
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12876 Bug ID: 12876 Summary: Reserve in waiting/transfer status may be cancelled by user Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: rkopaczka(a)afm.edu.pl Reporter: rkopaczka(a)afm.edu.pl QA Contact: testopia(a)bugs.koha-community.org Depends on: 12837 User may cancel his own reservation at waiting or in transit status through calling opac-modrequest.pl. Cancel button is disabled in interface but possibility to cancel should be checked also in opac-moderequest.pl, before calling CancelReserve(). -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 12873] New: Reserve can be cancelled by any logged in user
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12873 Bug ID: 12873 Summary: Reserve can be cancelled by any logged in user Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P3 Component: OPAC Assignee: rkopaczka(a)afm.edu.pl Reporter: rkopaczka(a)afm.edu.pl QA Contact: testopia(a)bugs.koha-community.org It is possible to cancel reservations through simply running opac-modreserve.pl with existing reserve_id number. This may provide remove even all reservations from system. The only limitation is that user have to be logged in. Simplest solution is to check whether reserve belongs to user or not. A patch will follow. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 1973] Acquisitions : receive items that haven't been ordered
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '14

02 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1973 Zeno Tajoli <z.tajoli(a)cineca.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |z.tajoli(a)cineca.it Resolution|--- |INVALID --- Comment #2 from Zeno Tajoli <z.tajoli(a)cineca.it> --- The user needed only a suggestion to do the operation with thea actual interface -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 1807] search () give odd results
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '14

01 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1807 Jesse Maseto <jesse(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jesse(a)bywatersolutions.com --- Comment #8 from Jesse Maseto <jesse(a)bywatersolutions.com> --- //Fix subject search by striping parenthesis from url links $('#catalogue_detail_biblio a[href*="su:"]').attr('href', function(_,v){ return v.replace(/($|$)/g,'') }); This works for both the staff search and OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6858] New: Adds staticfines.pl for static fines processing
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '14

01 Oct '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6858 Bug #: 6858 Summary: Adds staticfines.pl for static fines processing Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: matthias.meusburger(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Add a tool to calculate static fine. For example, 7 days left = 1€ fixed fine -- 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 39