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

[Bug 27316] New: In mappings use yes/no for sortable
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27316 Bug ID: 27316 Summary: In mappings use yes/no for sortable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com In search engine configuration (Elasticsearch), there is a colum 'sortable'. It contains 'Undef', 0 or 1. 0 and 1 are not really friendly values for a boolean. And also the translation seems to replace 0 by empty string (seen in fr-FR translation). I propose to replace by Yes/No like other boolean. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 20589] New: Add field boosting and use elastic query fields parameter instead of depricated _all
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20589 Bug ID: 20589 Summary: Add field boosting and use elastic query fields parameter instead of depricated _all Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com Generate a list of fields for the query_string query fields parameter, with possible boosts, instead of using "_all"-field. Also add "search" flag in search_marc_to_field table so that certain mappings can be excluded from searches. Add option to include/exclude fields in query_string "fields" parameter depending on searching in OPAC or staff client. Refactor code to remove all other dependencies on "_all"-field. (the atomicupdate sql-file is a bit obfuscated since had to be able to run in multiple time without error because of our local deploy-script, when moving this all procedure related code can be removed, only the "ALTER TABLE.."-lines are relevant.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 102

[Bug 25325] New: ElasticSearch mapping export lacks staff_client/opac fields
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25325 Bug ID: 25325 Summary: ElasticSearch mapping export lacks staff_client/opac fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: frederic(a)tamil.fr export_elasticsearch_mappings.pl doesn't export staff_client and opac fields. Its means that when reimporting (Reset mapping in Search engine configuration) indexing rules, the searchability (staff/opac) of fields will be lost. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 26398] New: Credit type on creating a manual credit is not translatable
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26398 Bug ID: 26398 Summary: Credit type on creating a manual credit is not translatable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr, martin.renvoize(a)ptfs-europe.com The "Credit type" pull down on the "Manual credit" page contains untranslatable values. To test: - Make sure another language than English is installed (tested with de-DE) - Go to any patron account - Accounting tab - Create manual credit tab - Verify the credit type pull down is there - Switch language to non-English - Verify the values remain in English -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 25412] New: [OMNIBUS] Enhance POD in Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25412 Bug ID: 25412 Summary: [OMNIBUS] Enhance POD in Koha namespace Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 19236] New: UNIF_TITLE authority ignores 2nd indicator value for all new headings saved
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19236 Bug ID: 19236 Summary: UNIF_TITLE authority ignores 2nd indicator value for all new headings saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: imingchan(a)yahoo.com.au QA Contact: testopia(a)bugs.koha-community.org When saving new headings to UNIF_TITLE authority, second indicator value is not saved. So when you selected such authority heading (as part the cataloguing), you have to manually re-enter the indicator value concerned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19237] New: PERSO_NAME authority file ignores first indicator value of new headings saved
by bugzilla-daemon＠bugs.koha-community.org 03 May '21

03 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19237 Bug ID: 19237 Summary: PERSO_NAME authority file ignores first indicator value of new headings saved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: imingchan(a)yahoo.com.au QA Contact: testopia(a)bugs.koha-community.org When saving new headings to PERSO_NAME authority, first indicator value is not saved. So when you selected such authority heading (as part the cataloguing), you have to manually re-enter the indicator value concerned. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 25969] New: Checking in a found hold at a different branch then confirming the hold causes internal server error
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '21

30 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25969 Bug ID: 25969 Summary: Checking in a found hold at a different branch then confirming the hold causes internal server error 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If a record level hold is filled and waiting at Library A, and the item is checked in at Library B, AddReturn() calls RevertWaitingStatus(), which unsets found, and itemnumber ( if the hold was record level ). AddReturn() then retuns the message 'ResFound', which triggers the hold fulfillment dialog, which passes the reserve_id back to circulation.pl. Then, circulation.pl attempts to get the biblio via the itemnumber, which the hold doesn't have, causing an ISE. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 17202] New: Deleting a rotating collection with items should either be prohibited or items should be removed
by bugzilla-daemon＠bugs.koha-community.org 30 Apr '21

30 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17202 Bug ID: 17202 Summary: Deleting a rotating collection with items should either be prohibited or items should be removed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Create a rotating collection Add an item Delete the rotating collection View the db (SELECT * FROM collections_tracking;) The item is still in the collection -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 16787] New: 'Too many holds' message appears inappropriately and is missing data
by bugzilla-daemon＠bugs.koha-community.org 29 Apr '21

29 Apr '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16787 Bug ID: 16787 Summary: 'Too many holds' message appears inappropriately and is missing data Change sponsored?: --- Product: Koha Version: master 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 bug 11250 changed the holds message to be and if,elsif loop, falling through to catch the first appropriate message bug 13116 changed the reporting from CanItemBeReserved causing tooManyHolds to trigger when no holds are allowed A side effect is that 'maxreserves' is only passed to the template when there are too many reserves, but the too many reserves message is called when no holds are available To recreate: Set maxreserves to 50 Set some item type to allow 0 holds Attempt to place a hold on a record with that itemtype Message will be "Too many holds: [Firstname Surname] can only place a maximum of total holds." Message should be "[Firstname Surname] cannot place any holds on these items." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 100