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

[Bug 5843] New: semicolon preceded by space in 490 subfield a (Series statement) causes search to time out
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '12

19 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5843 Bug #: 5843 Summary: semicolon preceded by space in 490 subfield a (Series statement) causes search to time out Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All URL: http://catalogue.efdss.org OS/Version: All Status: NEW Severity: critical Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: eb(a)efdss.org QAContact: koha-bugs(a)lists.koha-community.org CC: dpk(a)randomnotes.org, ian.walls(a)bywatersolutions.com In 3.2.5, This seems to be a problem with newly edited records and records already in the system. If there is a series statement in subfield a, and a volume number in subfield v the correct punctuation for subfield a is to end with a space semicolon space http://openlib.org/home/krichel/courses/lis512/aacr2/6.html However, if subfield a is punctuated as above, it causes a fault in the search, in both the OPAC and the staff interface. The search times out. To test it out on our catalogue (in the URL field above) search for 'school songs' You'll get a slew of items that are in the Novello's school songs series. Clicking on the series in the list on the left side of the page works fine. But if you go to an item that has both the series and the number (Folksongs from Somerset, Set II for example) and click on the series link there (in the normal view), it doesn't work. Chrome eventually returns a message that the page is unresponsive. I have deleted the spaces around the semicolon in a few records (the series County folklore) and the series link in the normal view works 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 1

[Bug 5767] New: serials not auto calculating barcode
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '12

19 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5767 Summary: serials not auto calculating barcode Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 If you have the automatic barcoding function on for cataloging serials is ignoring it. So if I receive a serial and the item record appears I have to type in my own barcode. If auto barcoding is on then it should also be taken into consideration on the serial receive form. -- 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 1

[Bug 5508] New: Biblibre Serials work
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '12

19 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5508 Summary: Biblibre Serials work Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 This bug is to track the biblibre serials. -- 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 5109] New: Display of serials enumeration (volume info) at OPAC inconsistent
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '12

19 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5109 Summary: Display of serials enumeration (volume info) at OPAC inconsistent Change sponsored?: --- Product: Koha Version: rel_3_0 Platform: Other OS/Version: Linux Status: NEW Severity: minor Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: virtualthinking(a)hotmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Problem: (1) 3 serial records were created and items added. (2) 2 were created by me with items, The 3rd record was imported via Z39.50. (3) While viewing at OPAC, the 2 records (created manually) displayed the volume info, while the third record did not display volume info. -- 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 3

[Bug 6938] New: The "Subscription History" public and private note fields have gone missing
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '12

19 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6938 Bug #: 6938 Summary: The "Subscription History" public and private note fields have gone missing Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org The commit that removed them was this one: http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=01e4b668caa… It has no associated bug or RM signoff, provides no migration path away from using those fields, and was wrong in the description (they're not redundant: the removed fields are associated with the subscription history table, not the subscription one.) It's debatable whether we should have that many note fields, but for now we will, until something that removes them properly can be implemented. -- 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 12

[Bug 6496] New: authors appearing incorrectly in OPAC and Staff Client
by bugzilla-daemon＠bugs.koha-community.org 17 Feb '12

17 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6496 Bug #: 6496 Summary: authors appearing incorrectly in OPAC and Staff Client Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Created attachment 4447 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=4447 opac with dots In the staff client if the additional author (7xx) has multiple parts it's putting dots in between the parts if XSLT is on and hyphens if it's off. It's easier to read with the hyphens. In the OPAC there are dots and no spaces and it's all smooched up. See attached. It should probably be hyphens or spaces instead of dots. Also some strangeness is happening with the order of authors. In the staff client when you have XSLT on additional authors are clearly on another line (easy to read) but in the OPAC, things aren't coming through right. In the OPAC the 100s are first then the 700s and then the 110s and then the 710s ... it should be all 1xxs and then all 7xxs (preferrably with the relator code showing so you know if it's an editor or illustrator) - at the very least the order should be fixed in this way. My screenshots show this all for you on my very bad marc record :) -- 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 38

[Bug 5088] New: HTML tags in Amazon reviews
by bugzilla-daemon＠bugs.koha-community.org 17 Feb '12

17 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5088 Summary: HTML tags in Amazon reviews Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All URL: /cgi-bin/koha/opac-detail.pl OS/Version: All Status: NEW Severity: normal Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2453 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2453 screenshot: grammar in use Amazon reviews can contain visible HTML tags ( ) in the text. I tried different AmazonLocale settings: Grammar in use : reference and practice for intermediate students of English by Murphy, Raymond ISBN: 0521348439 AmazonLocale: American (screenshot, ), German Sofies Welt : Roman ueber die Geschichte der Philosophie by Gaarder, Jostein 3446173471 AmazonLocale: German Koha version: 3.01.00.145 -- 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 10

[Bug 6718] New: No manager_id saved for writeoff of fines
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '12

16 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6718 Bug #: 6718 Summary: No manager_id saved for writeoff of fines Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All URL: /cgi-bin/koha/members/boraccount.pl?borrowernumber=19 OS/Version: All Status: NEW Severity: major Priority: P5 Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com No manager_id saved in accountlines when you do a 'writeoff'. To reproduce: - create manual invoice. Example. Sundry, 0.25 - writeoff fine from pay fines page - check accountlines table for manager_id -- 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 5875] New: waitingreserves highlighting now depends on maxpickupdate
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '12

15 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5875 Bug #: 5875 Summary: waitingreserves highlighting now depends on maxpickupdate Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: chris(a)bigballofwax.co.nz QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Blocks: 5575 -- 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

[Bug 6850] New: two new fields in aqorders
by bugzilla-daemon＠bugs.koha-community.org 15 Feb '12

15 Feb '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6850 Bug #: 6850 Summary: two new fields in aqorders Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: tdavis(a)uttyler.edu QAContact: koha-bugs(a)lists.koha-community.org Created attachment 5325 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5325 Location of fields 1 I need two fields added the aqorders table. One for document id, and another for invoice date. The document id should be functionally the same as the booksellerinvoicenumber field. I would use it to enter document ids for the UT acquisitions system Points Plus (e.g., W6VP1995080) The invoice date should be similar to shipment date, but should not be overwritten by a timestamp when receiving items. I don’t know if this is automatic—but it would also be good if they appeared in the Guided Reports Wizard wherever the acorders table currently does. Both fields should appear in acquisitions on the receive shipment screen: -- 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