July 2019 - Koha-bugs - lists.koha-community.org

[Bug 21747] New: Update C4::Overdues::UpdateFine to use Koha::Account->add_debit
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '20

30 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21747 Bug ID: 21747 Summary: Update C4::Overdues::UpdateFine to use Koha::Account->add_debit Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org All account handling should go via the Koha::Account class. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 15704] New: split up 264 index
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '20

28 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15704 Bug ID: 15704 Summary: split up 264 index 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: nengard(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 14198 Right now the 260 index look like this:  <index_subfields tag="260" subfields="a"> <target_index>pl:w</target_index> <target_index>pl:p</target_index> </index_subfields>  <index_subfields tag="260" subfields="b"> <target_index>Publisher:w</target_index> <target_index>Publisher:p</target_index> </index_subfields>  <index_subfields tag="260" subfields="c"> <target_index>copydate:w</target_index> <target_index>copydate:s</target_index> </index_subfields>  <index_data_field tag="260"> <target_index>pl:w</target_index> <target_index>Provider:w</target_index> </index_data_field> The 264 only indexes the entire thing.  <index_data_field tag="264"> <target_index>Provider:w</target_index> </index_data_field> We should break the 264 up for better/more accurate searching. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14198 [Bug 14198] RDA: Indexing 264 field (Zebra) -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 21608] New: Arranging holds priority with dropdowns is faulty when there are waiting/intransit holds
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '20

27 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21608 Bug ID: 21608 Summary: Arranging holds priority with dropdowns is faulty when there are waiting/intransit holds Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Find a record with multiple items 2 - Place 4 holds (or more) 3 - Capture one ohld as waiting, one as in transit 4 - View the holds on the record - switch the last to priority one 5 - Waiting and transit statuses get confused -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 59

[Bug 22046] New: Simplify C4::Matcher->get_matches
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '20

27 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22046 Bug ID: 22046 Summary: Simplify C4::Matcher->get_matches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently we process things separately for ES and Zebra For ES we get the results: get the biblionumber field using GetMarcFromKohaField extract the biblionumber from the record, save as id store the record in a hash like: $matches->{$id}->{record} = $matched For zebra: we use the xml record from zebra $matched as the id store it in a hash like $matches->{$id}->{record} = $matched $id and $matched are both the full xml of the record For both: We then convert the record into a Marc::Record Call C4::Biblio::TransformMarcToKoha - this gets all the koha fields Use only the biblionumber to return results It would be simpler to follow the ES pattern for both and avoid the TranformMarcToKoha call -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 22721] New: Normalize GetMarcFromKohaField calls
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '20

27 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22721 Bug ID: 22721 Summary: Normalize GetMarcFromKohaField calls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 23115] New: Totals are unclear when a credit is involved on the 'Pay fines' screen
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '20

24 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23115 Bug ID: 23115 Summary: Totals are unclear when a credit is involved on the 'Pay fines' screen Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, r.delahunty(a)arts.ac.uk, testopia(a)bugs.koha-community.org Depends on: 23106 Blocks: 14825 Target Milestone: --- We currently display the unapplied credit lines above the 'Total due' line on the opac 'Fines and charges' page and then we include the un-applied credit amounts in the total due. This is confusing to the end user, especially if they then select all to pay as an online payment, as the 'Amount to pay' will be more than the 'Total due' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14825 [Bug 14825] Accounts Rewrite Omnibus https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23106 [Bug 23106] Totals are unclear when a credit is involved on the 'Pay fines' screen -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 23157] New: 19.05 appears to only being tested on D9
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '20

24 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23157 Bug ID: 23157 Summary: 19.05 appears to only being tested on D9 Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Continuous Integration Assignee: tomascohen(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com Target Milestone: --- D8 and U18 are missing? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 21280] New: Unify MARC tab HTML generation
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '20

23 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21280 Bug ID: 21280 Summary: Unify MARC tab HTML generation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 11885 improved the MARC detail tab view, so it it easier to style with CSS, but the authority MARC tabs are still in a sorry state. We can unify the code into a single include file, and reuse that from both. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 21346] New: Remove return2 div from returns.tt now that modal interface exists
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '20

23 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21346 Bug ID: 21346 Summary: Remove return2 div from returns.tt now that modal interface exists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Someone added a new modal for holds/transfers in return.tt (yay!). They left the old dialog in the background, and if you ignore the modal, it remains. To replicate: 1) Place a hold on an item from Branch A to be delivered to Branch B. 2) Checkin in the item at Branch A and confirm the hold to transfer. 3) Be human and make a mistake. Login as Branch C and check the item in. 4) Note the great modal to redirect the hold. Note that the old dialog is behind it! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 104

[Bug 21049] New: Rancor 007 field does not retain value
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '20

22 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21049 Bug ID: 21049 Summary: Rancor 007 field does not retain value Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using Rancor, 007 field editor, you select the material type, and as soon as the record is saved, it reverts to the first material type in the list. The information is saved correctly, but every time the record gets edited the correct material type has to be selected again or else it is saved as the material type listed first in the dropdown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23