August 2015 - Koha-bugs - lists.koha-community.org

[Bug 12702] New: Suggestions still accessible in OPAC when deactivated
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12702 Bug ID: 12702 Summary: Suggestions still accessible in OPAC when deactivated Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/opac-suggestions.pl OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org To reproduce: - Turn off suggestion and AnonSuggestions. - Verify there are no longer links visible in navigation and patron account to visit the OPAC suggestion page. - Try to access the page directly: .../cgi-bin/koha/opac-suggestions.pl - Verify that the page is still shown. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 13564] New: Items search: rename Stock number to Inventory number
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13564 Bug ID: 13564 Summary: Items search: rename Stock number to Inventory number Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In the English UNIMARC and MARC21 frameworks the subfield for items.stocknumber has the description "Inventory number". It would be good to use the same term on the items search form and results table. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 13683] New: Display library name on holds queue page
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13683 Bug ID: 13683 Summary: Display library name on holds queue page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On the holds queue report page if holds are found for a library, it displays: x items found for MPL above the table. Instead of showing 'MPL' it should show the library's name using the TT plugin. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 9351] New: item type not recorded correctly in statistics for returns and some local use
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9351 Bug ID: 9351 Summary: item type not recorded correctly in statistics for returns and some local use Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When returning a loan, or when returning an item for local use when the RecordLocalUseOnReturn syspref is on, the corresponding entry in the statistics table takes the item type from the bib level. This is incorrect when item-level item types is enabled, and among other consequences can lead to problematic local use reports from the circ statistics wizard. In particular, if the library is also doing checkouts to a stats-only borrower to record local use, a circ statistics report on local uses that includes the item type as a row or column can have nonsensical totals because of the NULL statistics.itemtype value. The converse problem affects sites that use biblio-level item types, since local uses recorded from stats-only patrons use the item-level item type regardless of the setting of item-level_itypes. The desired behavior is that when recording a local use, the recorded item type should respect the item-level_itypes system preference. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 83

[Bug 12770] New: Notice template tool enhancement
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12770 Bug ID: 12770 Summary: Notice template tool enhancement Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Sponsored by Halland County Library RFC (with mockup) : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement#Notice_templ… Description : The invoice will be set up as a notice in the « Notices & slips » tool. Three new tags will display the amounts charged to the patron for a specific item : <itemaccountlines> <noticefee> <total> <itemaccountlines> will display the note and the outstanding amount for a specific item. The values will come from the accountlines table (the values available in the « fines » tab from the patron account page). Before being inserted in the invoice, the information will be sorted by date. Only the daily fees will be displayed. The old fees will be put aside. <itemaccountlines> will be used along with the <item> tag. <itemaccountlines> is different from <fines> because it works with <item> tag. Set up together, they will build a table which will display for each item: the bibliographic information, the note from the accountlines table and the outstanding amount. See mock-up below. Example : <item>biblio.title, biblio.author, items.barcode <itemaccountlines> </item> <noticefee> will add the notice fee to the invoice. To avoid having multiple « notice fee » lines if several invoices are sent the same day, the system will take the first found in the accountlines table. <total> will calcute the total amount. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 13530] New: Typo in bulkmarcimport
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13530 Bug ID: 13530 Summary: Typo in bulkmarcimport Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A typo seems to have crept in bulkmarcimport causing GetMarcFrameworkCode to fail. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 13562] New: Item search: Not possible to add other search fields from 952?
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13562 Bug ID: 13562 Summary: Item search: Not possible to add other search fields from 952? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I have added some additional fields to the search using administration > Items search fields: 952$1, LOST auth value (tried all settings for lost in the form at the bottom) 952$z, Opac note, free text Both searches don't appear to work. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 13585] New: HEA - Report usage statistics to Koha community
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13585 Bug ID: 13585 Summary: HEA - Report usage statistics to Koha community Change sponsored?: --- Product: Koha Version: master Hardware: All URL: http://hea.koha-community.org OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Websites, Mailing Lists, etc Assignee: wizzyrea(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: claire.hernandez(a)biblibre.com, fridolyn.somers(a)biblibre.com, indradg(a)gmail.com, jonathan.druart(a)biblibre.com, julian.maurice(a)biblibre.com, katrin.fischer(a)bsz-bw.de, magnus(a)enger.priv.no, mtj(a)kohaaloha.com, tomascohen(a)gmail.com Depends on: 11926 Blocks: 13149 Bug #11926 added the ability for koha to collect usage statistics. Problem is, to set them up you have to both change the system preferences and jump on the server to add the cron script to your crontab. I think the server-side bit should be done at install time thus allwoing simple on/off switching via the staff client configurable sysprefs. To do this, we need to add the a line to: for packages: /kohaclone/debian/koha-common.cron.monthly and perhaps add something to get the file installed as it's new (our first monthly cronjob for packages :) ) for other installs, there's a cron template in /kohaclone/misc/cronjobs/crontab.example -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 10177] New: Koha Accepts Seven "Space" Characters as a Valid Password
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10177 Bug ID: 10177 Summary: Koha Accepts Seven "Space" Characters as a Valid Password Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: glawson(a)rhcl.org CC: dpavlin(a)rot13.org Koha 3.10.03 and presumably earlier versions accept seven "space" characters as a valid password. Concerns: 1. Some third party software using SIP to check the Koha database to authenticate users may interpret all blank characters, or even a single terminal blank character, as an invalid password. 2. gmcharlt suggests that patches submitted in the future may strip trailing whitespace characters in form input, causing pernicious perturbations. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 12911] New: batch_id for new label batches can be assigned to several batches
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12911 Bug ID: 12911 Summary: batch_id for new label batches can be assigned to several batches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nick(a)quecheelibrary.org QA Contact: testopia(a)bugs.koha-community.org When adding a new label batch the MAX batch_id is retrieved from creator_batches and incremented, however, the updated value is not saved until new items are added to the batch. This means that if one library opens a new batch but does not add items before another library opens the batch they will both be assigned the same batch number To recreate: 1 -In one browser window, go to tools->label creator and click the new batch button 2 - Before adding items, open a new browser, and go tools->label creator and click the new batch button 3 - Note that both batches have the same number listed 4 - Add an item to the first batch - you should now see one item in the batch 5 - Add an item to the second batch, you should see two items in the batch I can also verify this happens pretty often in our shared system. C4:Creators 44 sub new { 45 my ($invocant) = shift; 46 my $type = ref($invocant) || $invocant; 47 my $self = { 48 batch_id => 0, 49 items => [], 50 branch_code => 'NB', 51 batch_stat => 0, # False if any data has changed and the db has not been updated 52 @_, 53 }; 54 my $sth = C4::Context->dbh->prepare("SELECT MAX(batch_id) FROM creator_batches;"); 55 $sth->execute(); 56 my $batch_id = $sth->fetchrow_array; 57 $self->{'batch_id'} = ++$batch_id unless $self->{'batch_id'} != 0; # this allows batch_id to be passed in for individual label printing 58 bless ($self, $type); 59 return $self; 60 } 61 62 sub add_item { 63 my $self = shift; 64 my $number = shift; 65 ref($self) =~ m/C4::(.+)::.+$/; 66 my $number_type = ($1 eq 'Patroncards' ? 'borrower_number' : 'item_number'); 67 my $query = "INSERT INTO creator_batches (batch_id, $number_type, branch_code, creator) VALUES (?,?,?,?);"; 68 my $sth = C4::Context->dbh->prepare($query); 69 # $sth->{'TraceLevel'} = 3; 70 $sth->execute($self->{'batch_id'}, $number, $self->{'branch_code'}, $1); 71 if ($sth->err) { 72 warn sprintf('Database returned the following error on attempted INSERT: %s', $sth->errstr); 73 return -1; 74 } 75 $query = "SELECT max(label_id) FROM creator_batches WHERE batch_id=? AND $number_type=? AND branch_code=?;"; 76 my $sth1 = C4::Context->dbh->prepare($query); 77 $sth1->execute($self->{'batch_id'}, $number, $self->{'branch_code'}); 78 my $label_id = $sth1->fetchrow_array; 79 push (@{$self->{'items'}}, {$number_type => $number, label_id => $label_id}); 80 $self->{'batch_stat'} = 1; 81 return 0; 82 } -- You are receiving this mail because: You are watching all bug changes.

1 22