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

[Bug 14385] Extend OpacHiddenItems to allow specifying exempt borrower categories
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14385 M. Tompsett <mtompset(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #66103|0 |1 is obsolete| | Attachment #66104|0 |1 is obsolete| | Attachment #66105|0 |1 is obsolete| | Attachment #66106|0 |1 is obsolete| | Attachment #66107|0 |1 is obsolete| | Attachment #66108|0 |1 is obsolete| | Attachment #66109|0 |1 is obsolete| | Attachment #66110|0 |1 is obsolete| | Attachment #66111|0 |1 is obsolete| | Attachment #66112|0 |1 is obsolete| | Attachment #66113|0 |1 is obsolete| | Attachment #66114|0 |1 is obsolete| | Attachment #66115|0 |1 is obsolete| | Attachment #66128|0 |1 is obsolete| | Attachment #66131|0 |1 is obsolete| | Attachment #66132|0 |1 is obsolete| | --- Comment #84 from M. Tompsett <mtompset(a)hotmail.com> --- Created attachment 66192 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66192&action=ed… Bug 14385: Extend OpacHiddenItems to allow specifying exempt borrower categories Edit: Fixing merge conflicts in - t/db_dependent/Items.t - t/db_dependent/Search.t - C4/Search.pm Changes the API for calling GetHiddenItems and all the places in the code that call it. This is to allow borrower categories to be passed in. Adds an OpacHiddenItemsExceptions syspref to allow certain borrower categories to be able to see items, even if they are marked hidden by OpacHiddenItems To test: 1) Make two borrowers, one in a category that should see everything (ie Adult), and another in a category that should only see certain things (ie Adult - exceptions) 2) Add the borrower that can see everything (the Adult) to OpacHiddenItemsExceptions 3) To the OpacHiddenItems syspref, add an item type (ensure that you have some records that fall under this type in your library). 4) Log in as the borrower that should only see certain things (Adult - exception) 5) Do a search, filtered to show records which are the item type that you specified in the OpacHiddenItems syspref. No records should show for this borrower as this item type is hidden to them. 6) Log in as the borrower that should see everything (Adult) 7) Do the same search. There should be results from this search, as this borrower category has been specified as an exception to the hidden items Signed-off-by: Claire Gravely <c.gravely(a)arts.ac.uk> Signed-off-by: Mark Tompsett <mtompset(a)hotmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 19152] New: Search always defaults to keyword rather than stay on the search option selected
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19152 Bug ID: 19152 Summary: Search always defaults to keyword rather than stay on the search option selected Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: karen(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org One of our library partners was searching for a list of titles and wanted to use the Title option for each of her searches. She noticed that after every search she did using Title search option, the system always defaulted back to Keyword. The expected behavior is that the search option would stay on Title and not default back to Keyword each time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19151] New: ijifjdifjdifjd
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19151 Bug ID: 19151 Summary: ijifjdifjdifjd Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: kikisyorgawi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Created attachment 66185 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=66185&action=ed… ucokregar burung -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 5534] Koha does not ignore punctuation when searching
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534 --- Comment #16 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I think I'd put Elasticsearch related issues on a separate bug - most of the discussion here applies to Zebra and both have different configuration files. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 5534] Koha does not ignore punctuation when searching
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534 --- Comment #15 from J Schmidt <jschmidt(a)switchinc.org> --- Is this bug specifically tied to Zebra indexing or with this also be the case with ElasticSearch as Koha users move towards that? Thanks. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 18455] New: Holiday range has incorrect starting date when crossing a weekly holiday
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18455 Bug ID: 18455 Summary: Holiday range has incorrect starting date when crossing a weekly holiday Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Holidays Assignee: koha-bugs(a)lists.koha-community.org Reporter: marka(a)pobox.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 62359 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=62359&action=ed… Screen shot of calendar after creation of two holidays mentioned in description. When a holiday of type "Holidays on a range" is created with a date range that overlaps a holiday of type "Holiday repeated every same day of the week", the starting date of the range is changed to a month or two earlier, creating a large number of incorrect holidays. To reproduce: Start with an empty calendar. Create a holiday on a Wednesday and give it type "Holiday repeated every same day of the week". Create a holiday on a Tuesday (e.g., May 2 2017) with an ending date of a Thursday (e.g., May 4 2017) and a type of "Holidays on a range". This will create a set of single holidays starting on a day much earlier than the user-specified start date. On my system (16.11.06.000) it created holidays starting on March 30 2017. See attached screenshot for the result. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 18456] New: Update Italian installer sample files for 17.05
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18456 Bug ID: 18456 Summary: Update Italian installer sample files for 17.05 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: z.tajoli(a)cineca.it QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Update and translate sample SQL file of the Italinan installer; version for 17.05 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 5534] Koha does not ignore punctuation when searching
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534 --- Comment #14 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Sorry, I see now that this here all started with the discussion about apostrophes - just a lot of information and other problems have been added since. Maybe splitting this into several bugs would still be good - we can link them all to this one. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 5534] Koha does not ignore punctuation when searching
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534 --- Comment #13 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hi, I suggest filing a separate bug with your example - Zebra is able to do things like that, but there are known issues with quotes and similar. Sometimes it also depends on configuration (ICU vs. grs-1, installation choices, etc...). Please include information about how you installed Koha and if you changed defaults etc. on installation if possible. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 5534] Koha does not ignore punctuation when searching
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '17

18 Aug '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5534 dguidry(a)lcg.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dguidry(a)lcg.org --- Comment #12 from dguidry(a)lcg.org --- Is there any update in regards to this particular issue? I'm running Koha 17.05 and are experiencing the same problem. One example is we have an entry for "Expositor's Dictionary". The only way it will return a result is by searching for "expositor" or "expositor's", but the average person seems to type "expositors" and it returns no results. A typical search engine in 2017 is generally able to handle this, so this is the prevailing user expectation these days. Are there any plans to resolve this sort of usability issue? We've had multiple people report this problem over the last year when searching for various items in our catalog that contain an apostrophe. If there's no fix in the works, is there a decent workaround that can be implemented in the meantime to smooth this over for our users? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0