August 2018 - 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 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 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 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 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

[Bug 16421] New: Move hold edit actions into dropdown menu
by bugzilla-daemon＠bugs.koha-community.org 22 Jan '20

22 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16421 Bug ID: 16421 Summary: Move hold edit actions into dropdown menu Change sponsored?: --- Product: Koha Version: master Hardware: All URL: /cgi-bin/koha/reserve/request.pl OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 51111 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51111&action=ed… Screenshot showing proposed interface change I propose that we re-work the way existing holds are displayed in the staff client so that many of the actions associated with a hold are moved into a dropdown menu. I would also add some additional information about the status of a hold into the "details" column. This change would accomplish a few things: - Make the display more compact - Make clearer some information which may not be clear. For instance, that a hold is suspended until a particular date, or that a hold is set to lowest priority. - Make clearer the meaning of the hold priority icons. Using text labels with icons, the meaning of each is explicit. Unfortunately Font Awesome doesn't have the equivalent of the "move to top" or "move to bottom" icon, so I've tried to fake it with a border. It's not perfect buy may be passable. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 21206] New: C4::Items - Remove GetItem
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '20

21 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21206 Bug ID: 21206 Summary: C4::Items - Remove GetItem Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Let's use Koha::Items! -- You are receiving this mail because: You are watching all bug changes.

1 67

[Bug 19417] New: Improve display of errors from background job during stage for import
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '20

21 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19417 Bug ID: 19417 Summary: Improve display of errors from background job during stage for import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When importing records, if there is an error in the staging we display: Failed to submit form: error This is not helpful, we should instead display the error textReponse field -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27