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

[Bug 5341] New: Serial issues improvements
by bugzilla-daemon＠bugs.koha-community.org 25 May '12

25 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5341 Summary: Serial issues improvements Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Serial_issue_seria ls_RFC OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The "save" button will be moved to the top of the serial receiving We will add a feature to bulk modify issues (equivalent to bulkmodify of items & biblios) -- 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 7

[Bug 5346] New: Linking suggestions & orders
by bugzilla-daemon＠bugs.koha-community.org 25 May '12

25 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5346 Summary: Linking suggestions & orders Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Linking_sugg_order _acq_RFC OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 in Koha 3.2, the suggestions is not completly linked to the related order. The link is only done through the biblionumber. We will add a field to have a fully qualified link. We will be able to add links to jump from suggestion to orders & from orders to suggestion -- 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 21

[Bug 5459] New: merging records loses holds from one
by bugzilla-daemon＠bugs.koha-community.org 24 May '12

24 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5459 Summary: merging records loses holds from one Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 When you use the merge records tool, if both bibs have holds on them, when the merge is complete only the holds from the main record are kept and all others are lost. -- 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 42

[Bug 5596] New: add author to holds to pull report
by bugzilla-daemon＠bugs.koha-community.org 24 May '12

24 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5596 Summary: add author to holds to pull report Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 It would be nice if the holds to pull report had author listed. -- 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 17

[Bug 5373] New: fields listed on patron import do not match the csv file
by bugzilla-daemon＠bugs.koha-community.org 24 May '12

24 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5373 Summary: fields listed on patron import do not match the csv file Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: ASSIGNED Severity: normal Priority: P5 Component: Tools AssignedTo: nengard(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 the fields listed in plain text on the patron import tool do not match those in the csv - the csv is correct, the text is wrong. -- 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 19

[Bug 5266] New: Patron Search Produces Incorrectly Sorted and Missing Results
by bugzilla-daemon＠bugs.koha-community.org 23 May '12

23 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5266 Summary: Patron Search Produces Incorrectly Sorted and Missing Results Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: HP OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: glawson(a)rhcl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Koha version: 3.01.00.145 Zebra version: Zebra 2.0.44 MySQL version: mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu Staff user reports that she types "johnston" (for example) into the patron search field on the staff interface. This produces 10 pages of results, but not the desired patron named Jessica. That name did not show up - it jumped from Jesse to Joan. However, if the user went in and typed "johnston, jessica", it came up. Also, later she had a different patron's record up and tried the search again with "johnston". That brought up the 10 pages of Johnstons again, but each page was alphabetical for the names displayed on that page - so each page started over with an "A" name and so on, but the names on each page were different and apparently non-repeating. -- 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 5

[Bug 5674] New: Staff client - placing holds - patron name sort not ignoring letter case
by bugzilla-daemon＠bugs.koha-community.org 23 May '12

23 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5674 Summary: Staff client - placing holds - patron name sort not ignoring letter case Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: bchurch(a)ptfs.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 When you are placing holds for patrons in the staff client, patron names do not sort correctly if patron names are entered in upper case. To recreate this issue, do the following: 1. Add two test patron records, one with the name "Smith, Joseph" and the other "SMITH, THOMAS". 2. Search for a title in the staff client and click Holds to open the request.pl window. 3. Do patron search for the name "Smith" and you will see that SMITH, THOMAS sorts before "Smith, Joseph". -- 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 9

[Bug 5473] New: 952 fields should be filled in by Acquisitions
by bugzilla-daemon＠bugs.koha-community.org 23 May '12

23 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5473 Summary: 952 fields should be filled in by Acquisitions Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 >From an email: "In Koha 2.2.9 when you used the Acquisitions module and acquired an item, in the item record it would put in 952$e the number Koha assigned to that vendor when it is created in the Acquisitions module. - I really liked this feature in v2.2.9 and find it is strange why it was taken out of v3." It makes perfect sense that if you're adding an item from acquisitions that it should fill in not only the 952e but also all other acquisitions related fields: 952d, 952g, 952v, and 952w. -- 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 30

[Bug 5605] New: Add Support for SIP Fee Paid Message
by bugzilla-daemon＠bugs.koha-community.org 23 May '12

23 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5605 Summary: Add Support for SIP Fee Paid Message Change sponsored?: Sponsored Product: Koha Version: HEAD Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: P5 Component: SIP2 AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: colin.campbell(a)ptfs-europe.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In order to support the payment feature in 3M self-issue units. The FeePaid Message needs to be supported in the Koha SIP software. Initial implementation currently in testing -- 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 11

[Bug 5543] New: Date ISO format wrong separator
by bugzilla-daemon＠bugs.koha-community.org 23 May '12

23 May '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5543 Summary: Date ISO format wrong separator Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: I18N/L10N AssignedTo: frederic(a)tamil.fr ReportedBy: fridolyn.somers(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Hie, In code Dates.pm, iso date format is defined as : iso => 'yyyy-mm-dd' But in system preference, iso is displayed as : 'yyyy/mm/dd'. Same in "date-format.inc". Regards, -- 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 15