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

[Bug 20434] New: Unimarc - updating Unimarc existing frameworks with IFLA updates
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '20

03 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20434 Bug ID: 20434 Summary: Unimarc - updating Unimarc existing frameworks with IFLA updates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: fpichenot(a)ville-roubaix.fr QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 105

[Bug 15686] New: Rename "item level holds" circ rule column to "OPAC item level holds"
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '20

01 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15686 Bug ID: 15686 Summary: Rename "item level holds" circ rule column to "OPAC item level holds" Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 5786 moved the OPACItemHolds sys pref setting to the Circulation Rules table. However, the naming of the new circ rules column is quite confusing. It is called "Item level holds" which makes it sound like this setting controls the item level holds placing from anywhere in the system (staff and OPAC sides) Instead, the setting only affects item level hold placing from the OPAC side. Should this column then be renamed to "OPAC item level holds"?, so it's not so confusing? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 18355] New: Permanent location should show with cart location
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '20

31 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18355 Bug ID: 18355 Summary: Permanent location should show with cart location Change sponsored?: --- Product: Koha Version: 3.22 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 It would be helpful if the permanent location would show even when the cart location is in use. For example: Location CART (Adult Non-fiction) It is difficult to track an item if it has an unusual location, like a display location, and it is recently returned. This information should show anywhere the shelving location is displayed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 22426] New: Elasticsearch - Index location is missing in advanced search
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '20

31 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22426 Bug ID: 22426 Summary: Elasticsearch - Index location is missing in advanced search Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: marjorie.barry-vila(a)collecto.ca Target Milestone: --- Hi, A search made on Shelving location tab in advanced search gives 0 result. Test plan : - in advanced search, choose a location in shelving location tab and start search (opac-search.pl?idx=kw&op=and&idx=kw&op=and&idx=kw&do=Search&limit=mc-loc) - 0 result - check that location exist by doing a simple search and filtering on the location facet - have some results I think problem is index "loc" is used in advanced search or it could be index "location" like facet. Or is it a configuration problem? Regards Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 20243] New: ILS-DI CIDR notation
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '20

30 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20243 Bug ID: 20243 Summary: ILS-DI CIDR notation Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: bc(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org At present it is only possible to add single IP addresses to ILS-DI:AuthorizedIPs. This is difficult to manage if the source resource has a large pool of public addresses that can be used to connect. Adding CIDR notation ability to ILS-DI:AuthorizedIPs would help to manage this problem. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[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