January 2017 - Koha-bugs - lists.koha-community.org

[Bug 17885] New: Koha::SearchEngine::Elasticsearch-> reset_elasticsearch_mappings throws DBD::mysql Duplicate entry exceptions
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17885 Bug ID: 17885 Summary: Koha::SearchEngine::Elasticsearch->reset_elasticsearch _mappings throws DBD::mysql Duplicate entry exceptions 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 16972] New: ./misc/ sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section.
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16972 Bug ID: 16972 Summary: ./misc/sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz As far as I can tell, the following options are mandatory: -a (address) -p (port) -su (sip user) -sp (sip password) -l (sip location/institution) The sip terminator (-t) is not mandatory, but getting it wrong hangs the script without warning. The usage would look like this, more or less: Usage: $0 -a <address> -p <port> -su <sip user> -sp <sip port> -l <location> [--patron <patron barcode>] [--password <patron password>] [-i <item barcode>] [-fa] [-m <message>] [-h] -- You are receiving this mail because: You are watching all bug changes.

1 2

[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 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 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 17207] New: Cannot access the website from China
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '20

14 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17207 Bug ID: 17207 Summary: Cannot access the website from China Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: thadickal.mapleleaf(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Recently, many schools in China, specifically in Shanghai and surrounding area have not been able to access the Koha website. Can you please advise us how we can restore our connection to your service. Thanks -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 17093] New: JavaScript error on patron entry page if toolbar is not displayed
by bugzilla-daemon＠bugs.koha-community.org 14 Jan '20

14 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17093 Bug ID: 17093 Summary: JavaScript error on patron entry page if toolbar is not displayed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Under some circumstances the patron entry form and toolbar are not displayed by memberentrygen.tt. For instance, if there are no libraries or patron categories defined. If this happens a JavaScript error is triggered because a check for #toolbar's position returns null. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 17984] New: Warn catalogers if item type doesn't match 942c
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17984 Bug ID: 17984 Summary: Warn catalogers if item type doesn't match 942c Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Because circ rules can be thrown off if the item type in the items record doesn't match the 942c when it comes to bib level hold requests, it would be helpful to have a warning next to field "y - Koha item type" if it does not match the 942c. Maybe something like: "WARNING: item type does not match 942c. May have unexpected results on hold requests." -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 16766] New: Merging two records with title level holds for the same patron creates two holds on one record
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16766 Bug ID: 16766 Summary: Merging two records with title level holds for the same patron creates two holds on one record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 - Place a title level hold for a patron on a record 2 - Do it again on another record 3 - Merge these recrods 4 - See they now have two holds on one record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 16413] New: Prototype for GetLatestAutoRenewDate and GetSoonestRenewDate should be changed
by bugzilla-daemon＠bugs.koha-community.org 13 Jan '20

13 Jan '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16413 Bug ID: 16413 Summary: Prototype for GetLatestAutoRenewDate and GetSoonestRenewDate should be changed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16344 Currently the 2 GetLatestAutoRenewDate and GetSoonestRenewDate subroutines takes $borrowernumber and $itemnumber in parameter. They refetch the patron, item and issue information but they already are available from where they are called. It would make sense to change the prototype of these 2 subroutines to accept the patron, item and issue information directly to avoid unnecessary refetches. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16344 [Bug 16344] Add a circ rule to limit the auto renewals given a specific date -- You are receiving this mail because: You are watching all bug changes.

1 23