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

[Bug 26067] New: Email validation of member based on MX record
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '21

19 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26067 Bug ID: 26067 Summary: Email validation of member based on MX record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Currently we are checking Email validation of member (both Staff and OPAC interface)based on the Email::Valid->address but we are not checking the MX record of the domain name, We have encountered the issue with one of our client while doing the email validation through PatronSelfRegistration. I am planning to add below code. Email::Valid->address( -address => 'amitddng135(a)gmail.com', -mxcheck => 1 ); instead of Email::Valid->address('amitddng135(a)gmail.com'); Can you provide us your feedback. Should we do fix code through system preference for ex: "EmailValidationMXrecord" or without system preference. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 26522] New: Elasticsearch - don't attempt to index record if it cannot be retrieved
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '21

19 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26522 Bug ID: 26522 Summary: Elasticsearch - don't attempt to index record if it cannot be retrieved Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com In ModZebra we call GetMarcBiblio - this can fail on malformed records. If it does, we should not attempt to index, otherwsie we get an error: [Wed Sep 23 14:49:59.978945 2020] [cgi:error] [pid 131451] [client 172.18.0.1:46768] AH01215: [Wed Sep 23 14:49:59 2020] manage-marc-import.pl: {UNKNOWN}: Can't call method "leader" on an undefined value at /kohadevbox/koha/Koha/SearchEngine/Elasticsearch.pm line 566. at /kohadevbox/koha/tools/manage-marc-import.pl line 252: /kohadevbox/koha/tools/manage-marc-import.pl, referer: http://localhost:8081/cgi-bin/koha/tools/manage-marc-import.pl?import_batch… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 25445] New: Avoid use of "item" when not talking about items (holdings)
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '21

19 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25445 Bug ID: 25445 Summary: Avoid use of "item" when not talking about items (holdings) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement 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 In translation we don't have a lot of context to work from. At the most, we see the file a string comes from, but that is not always helpful. There are certain words that can be used in English in different contexts, but would require different translations in other languages. Item is such an example. It would be nice if we could avoid using items when we are not talking about holdings. These two strings listed below refer to when selecting no 'item' for adding to a list/cart from the result list: koha-tmpl/intranet-tmpl/prog/en/includes/js_includes.inc: var MSG_NO_RECORD_SELECTED = _("No item was selected"); koha-tmpl/opac-tmpl/bootstrap/en/includes/opac-bottom.inc: var MSG_NO_RECORD_SELECTED = _("No item was selected"); Maybe we could use - no record - no title - no search result entry ? instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22109] New: Koha to Marc Mapping Chart is not in english in the English version
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '21

19 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22109 Bug ID: 22109 Summary: Koha to Marc Mapping Chart is not in english in the English version Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Hi, On this page in the 18.05 manual linking to the Koha to marc Mapping, the column "Lib" is actually written in French. https://koha-community.org/manual/18.05/en/html/administration.html#koha-to… Kelly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 26930] New: Add css class to collaborators in OPAC results
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '21

19 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26930 Bug ID: 26930 Summary: Add css class to collaborators in OPAC results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When a record has a lot of collaborators/added authors (70X to 75X in MARC21), the record in the results list can get quite big, and all that information is not necessary for a first look. The proposition is to add a CSS class to added authors/collaborators in order to be able to hide them if needed. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 27024] New: Multiple subfields are removed after linking authority
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '21

19 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27024 Bug ID: 27024 Summary: Multiple subfields are removed after linking authority Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org In this example: 650 _ 0 ‡aCooking‡zMexico‡zOaxaca (State) It is possible to have multiple subfield z. After linking the authority with the linker (ctrl-shift L), the marc tag looks like: 650 _ 0 ‡aCooking‡zMexicoOaxaca (State)‡9318501 Where the second subfield Z is removed. I then have to manually add the second subfield Z label back in. The authority linker should respect multiple subfields. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25668] New: ElasticSearch 6 deprecation: the default number of shards will change in version 7
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '21

18 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25668 Bug ID: 25668 Summary: ElasticSearch 6 deprecation: the default number of shards will change in version 7 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: victor(a)tuxayo.net This happens in koha-testing-docker with ES 6.8.8 When indexing: ./misc/search_tools/rebuild_elasticsearch.pl -v -d Here are both deprecation messages that are outputted and related: [DEPRECATION] the default number of shards will change from [5] to [1] in 7.0.0; if you wish to continue using the default of [5] shards, you must manage this on the create index request or with an index template - In request: {body => {settings => {index => {analysis => {analyzer => {analyzer_phrase => {char_filter => ["punctuation"],filter => ["icu_folding"],tokenizer => "keyword"},analyzer_standard => {filter => ["icu_folding"],tokenizer => "icu_tokenizer"},analyzer_stdno => {char_filter => ["punctuation"],filter => ["icu_folding"],tokenizer => "whitespace"}},char_filter => {punctuation => {pattern => "([\\x00-\\x1F,\\x21-\\x2F,\\x3A-\\x40,\\x5B-\\x60,\\x7B-\\x89,\\x8B,\\x8D,\\x8F,\\x90-\\x99,\\x9B,\\x9D,\\xA0-\\xBF,\\xD7,\\xF7])",replacement => "",type => "pattern_replace"}},normalizer => {icu_folding_normalizer => {filter => ["icu_folding"],type => "custom"},nfkc_cf_normalizer => {char_filter => "icu_normalizer",type => "custom"}}}},"index.mapping.total_fields.limit" => 10000}},ignore => [],method => "PUT",mime_type => "application/json",path => "/koha_kohadev_biblios",qs => {},serialize => "std"} [DEPRECATION] the default number of shards will change from [5] to [1] in 7.0.0; if you wish to continue using the default of [5] shards, you must manage this on the create index request or with an index template - In request: {body => {settings => {index => {analysis => {analyzer => {analyzer_phrase => {char_filter => ["punctuation"],filter => ["icu_folding"],tokenizer => "keyword"},analyzer_standard => {filter => ["icu_folding"],tokenizer => "icu_tokenizer"},analyzer_stdno => {char_filter => ["punctuation"],filter => ["icu_folding"],tokenizer => "whitespace"}},char_filter => {punctuation => {pattern => "([\\x00-\\x1F,\\x21-\\x2F,\\x3A-\\x40,\\x5B-\\x60,\\x7B-\\x89,\\x8B,\\x8D,\\x8F,\\x90-\\x99,\\x9B,\\x9D,\\xA0-\\xBF,\\xD7,\\xF7])",replacement => "",type => "pattern_replace"}},normalizer => {icu_folding_normalizer => {filter => ["icu_folding"],type => "custom"},nfkc_cf_normalizer => {char_filter => "icu_normalizer",type => "custom"}}}},"index.mapping.total_fields.limit" => 10000}},ignore => [],method => "PUT",mime_type => "application/json",path => "/koha_kohadev_authorities",qs => {},serialize => "std"} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 25213] New: It would be beneficial to be able to notify the patron of a resolution
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '21

18 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25213 Bug ID: 25213 Summary: It would be beneficial to be able to notify the patron of a resolution Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org With bug 4461 we introduce a mechanism for patrons to report issues with the OPAC and manage the status of such issues. I would be beneficial to be able to notify the patron when such issues are resolved. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 21626] New: Add 'current maintenance team' to the 'Koha team' page
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '21

18 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21626 Bug ID: 21626 Summary: Add 'current maintenance team' to the 'Koha team' page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently, we display the 'release team' for the duration of a releases maintenance period. I propose that we add an additional column next to this to display the current 'maintenance' team and thus give more exposure to their hard work. A release team doesn't just look to the next release but also contributes to the maintenance of existing branches by continuing to find and fix bugs... lets showcase that side of their work too :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 140

[Bug 25301] New: Category code is blank when renewing or editing expired/expiring patron
by bugzilla-daemon＠bugs.koha-community.org 18 Jan '21

18 Jan '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25301 Bug ID: 25301 Summary: Category code is blank when renewing or editing expired/expiring patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When renewing or editing the details of an expired patron via the "Renew" or "Edit details" links, there is a blank argument to "categorycode=". At a glance, it doesn't seem to cause problems, so we should either fix the argument, or remove the parameter. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22