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

[Bug 12478] Elasticsearch support for Koha
by bugzilla-daemon＠bugs.koha-community.org 17 Feb '17

17 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 --- Comment #257 from Nick Clemens <nick(a)bywatersolutions.com> --- Hi Jorge, You will need to manual add a block like the below into the config section of your koha-conf.xml: <elasticsearch> <server>es-server:9200</server> <index_name>koha_instance</index_name> </elasticsearch> The best way to reach the community is probably via Probably using the listservs: https://koha-community.org/support/koha-mailing-lists/ Or IRC: https://koha-community.org/get-involved/irc/ Good luck! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12478] Elasticsearch support for Koha
by bugzilla-daemon＠bugs.koha-community.org 17 Feb '17

17 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 Jason Palmer <jpalmer(a)switchinc.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpalmer(a)switchinc.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12461] Add patron clubs feature
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12461 --- Comment #49 from Kyle M Hall <kyle(a)bywatersolutions.com> --- (In reply to Josef Moravec from comment #48) > Kyle, could you please provide followup due to bug 16239? > > See https://wiki.koha-community.org/wiki/Interface_patterns Josef, can you please be more specific? Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14405] Add datatable to fines table in OPAC patron account
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14405 Johnny Rotten <georgew(a)latahlibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|georgew(a)latahlibrary.org, | |gwilliams(a)nekls.org | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14405] Add datatable to fines table in OPAC patron account
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14405 Johnny Rotten <georgew(a)latahlibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |george(a)nekls.org, | |georgew(a)latahlibrary.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12478] Elasticsearch support for Koha
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 Jorge de Cardenas <jdeca(a)smfpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdeca(a)smfpl.org --- Comment #256 from Jorge de Cardenas <jdeca(a)smfpl.org> --- I am trying to test Elasticsearch in Koha and I keep getting an error: No 'elasticsearch' block is defined in koha-conf.xml. I am running a fresh install of Koha 16.11.03.000 and Debian 8 and imported our data from 3.16.04.000 I have enabled Memcached and Plack. Installed openjdk-8 and elastic search. I first got the error while trying run rebuild_elastic_search.pl I not sure why but changing <memcached_server> to the static IP allowed the index to run but when I try to do a search on the staff side I get the error again. If this is not the place to ask please let me know. Jorge de Cardenas -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15427] Allow db connections using TLS
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15427 --- Comment #13 from Mirko Tietgen <mirko(a)abunchofthings.net> --- In the non-TLS file I see a lot of MySQL commands. Like SELECTs. In the TLS file I don't (actually I see one, not sure why), but mostly "garbage". -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8548] Add callnumber sort option to overdue report
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8548 Baptiste <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |baptiste.wojtkowski@biblibr | |e.com Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14784] Missing checkin message for debarred patrons when issuing rules ' fine days = 0'
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14784 Baptiste <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |baptiste.wojtkowski@biblibr | |e.com --- Comment #15 from Baptiste <baptiste.wojtkowski(a)biblibre.com> --- Hi, The scenario 2 leads me to a message, even without patching -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 12460] Search history: Combine to start a new search
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '17

16 Feb '17

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12460 Claes <claes.eriksson(a)vti.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claes.eriksson(a)vti.se --- Comment #19 from Claes <claes.eriksson(a)vti.se> --- Since this feature would appeal to more experienced user I think that it would be better to align with common search interfaces. The option "Start a new search" is not intuitive at all. What we want to do is: "Combine sets/queries" "Match any" and "match all" is not really common language and it is not intuitive. It seems that I must select either match any/ match all even if I just want to select line 4 NOT line 2. The results indicate that the search works as it should but it is certainly not clear for a user. I have 2 suggestions: the first beeing a bit simpler and probably easier to apply. The second would be the most up to date solution. My first suggestion for a design remake would be: 1) At the search history page add 2 new columns 2) One column with the heading "Delete Sets". In this column, each line/search set should have a tick box. Two buttons in the same heading with "select all" and the second button "X delete" 3) The second column with the heading "Combine sets or Combine queries". In this heading two tick boxes: "AND" & "OR". And this column should also have a tick box for each line. 4) remove the big red button "Remove selected searches" 5) remove the first column with tick boxes So how about the option "NOT"? My experience as information specialist is that this operator is not well understood and often misused by normal users. A second suggestion would complicate it for the developer :-) but here it comes: 1) The search history page should have a number for each search set/search querie. And the numbers should be in this format: #1, #2, #3 2) An extra column at the end of the line with tick boxes for each line and with the heading "Delete searches". As in 2) above. 3) A search line above the search history with the text Combine queries and a brief example (#1 OR #3) AND #6. As the example show there are no box ticking here but you send a querie using old search sets. 4) remove the big red button "Remove selected searches" 5) remove the first column with tick boxes -- You are receiving this mail because: You are watching all bug changes.

1 0