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

[Bug 13501] New: Allow autocompletion on drop-down lists
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13501 Bug ID: 13501 Summary: Allow autocompletion on drop-down lists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some users have very long lists of authorised values. It could be painful to pick a value in such lists with a simple drop-down list. Following patches will allow to type some text in order to filter these values and pick the good one easily. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 11280] New: Change Withdrawn toggle to drop down selection of authorized values
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11280 Bug ID: 11280 Summary: Change Withdrawn toggle to drop down selection of authorized values Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: mcoalwell(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Item view moredetail.pl, one is given the choice of selecting authorized values for Lost and Damaged statuses through a drop down. However, Withdrawn is a toggle, even though Withdrawn can be assigned various values in the same way as Lost and Damaged. I am proposing that the Withdrawn status have the same selection menu and "set status" formulation as Lost and Damaged. Statuses ( Lost ) Current location: Checkout status: Current renewals: Lost status: Damaged status: Withdrawn?:No -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[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 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 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

[Bug 10943] New: impossible to check and make fines when borrowers flag is desactivate
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10943 Bug ID: 10943 Summary: impossible to check and make fines when borrowers flag is desactivate Change sponsored?: --- Product: Koha Version: 3.12 Hardware: PC OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When a borrower has those flags: -circulate -catalog -reserveforothers -borrow -updatecharges He can not make and check fines on a other borrower. He can make check in and check out but he has not a access to the fines tab. See video. http://communaute.koha.ccsr.qc.ca/wp-content/uploads/2013/09/flags.swf Thanks Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 10887] New: Batch item deletion -- doesn't need Use default values section
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10887 Bug ID: 10887 Summary: Batch item deletion -- doesn't need Use default values section Change sponsored?: --- Product: Koha Version: 3.12 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org The batch item deletion tool doesn't need to have the option for "use default values section" to "Populate fields with default values from default framework." The option is applicable to the batch item modification tool, but not to batch item deletion -- because all the user is doing with the batch deletion is deleting items. Should this option be removed, as a result? -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 10241] New: Easy analyticals creates two 773 fields. Search/link from host to children is broken
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '16

19 Jan '16

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10241 Bug ID: 10241 Summary: Easy analyticals creates two 773 fields. Search/link from host to children is broken Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: normal Priority: P4 Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: eb(a)efdss.org UseControlNumber preference is set to "Don't use" and the EasyAnalyticalRecords preference is set to 'Display.' I created a record, and then selected New child record and created an analytic. Then, following the instructions in the manual Chapter 5 http://es.koha-community.org/manual/3.10/en/cataloging.html#cataloganalytics I linked the analytic to the host item. This resulted in two 773 fields. The first (created when adding a new child record contains: w Host Record control number 005037189 d Place, publisher, and date of publication Milwaukee : Hal Leonard, [2002?] z International Standard Book Number 0634038788 t Title Selections from O brother, where art thou? : The second 773, created when I linked the child to the parent contains the above, plus 0 Host Biblionumber 19017 9 Host Itemnumber 20551 The search for analytics is driven by the host item number, which is not included in the 773 that is created with a new child record. So you must link the child to the parent. But why create an additional 773? It looks messy. Second part possibly not related at all to the above: When I go to the host item in the staff interface and click on Analytics it says Used in 4 analytics ('4 analytics' is a link: http://kohaadmin-test.efdss.org/cgi-bin/koha/catalogue/search.pl?idx=hi&q=2… If I click on the link: No results found. No results match your search for 'hi,wrdl: 20551' in VWML Test Catalog. But if I put the host item number 20551 into the search field, it returns the children and the parent record. Something about the search from analytics is not functioning correctly. -- You are receiving this mail because: You are watching all bug changes.

1 27