El Mon Feb 02 2015 at 15:06:00, Cindy Murdock Ames (cmurd...@ccfls.org)
escribió:
Hi Michał,
The opac isn't publicly accessible yet but here's a screenshot:
http://i.imgur.com/0hdHrbm.png
The area where the facets usually are is completely blank, even the Refine
your search header is
Hi everybody,
To answer a bunch of questions:
Yes, setting use_zebra_facets to 0 (and restarting memcached in my case)
does bring the facets back. As far as I know doing that reverts facets to
the old system that uses grs1. I would prefer to be able to use dom as
grs1 is being deprecated, from
Good afternoon,
I am working on moving our current koha 3.08 setup over to Debian 7.8
and koha 3.18. (I am also new to koha, so learning as I go).
The problem I am running into is once the data has been moved over to
the new machine, and koha is up and running, everything appears to be
Thanks Tomas and Kyle for the clarification, sorry for the
misinterpretation.
Here's the output from zebra when I start it manually and do a search in
the catalog:
11:00:43-03/02 zebrasrv(3) [session] Session - OK 3
unix:/home/kohaclone/koha-dev/var/run/zebradb/bibliosocket PID=23191
Setting use_zebra_facets0/use_zebra_facets is not making Koha use
GRS-1. You're safe switching it.
It only falls back to the old calculation method that wouldn't calculate
the facets out of the result set, but from a small number of records from
the results. It is less precise.
The way to debug
On Tue, Feb 3, 2015 at 10:12 AM, Cindy Murdock Ames cmurd...@ccfls.org
wrote:
Hi everybody,
To answer a bunch of questions:
Yes, setting use_zebra_facets to 0 (and restarting memcached in my case)
does bring the facets back. As far as I know doing that reverts facets to
the old system
Okay, here's the yaz-client output:
kohaclone@koha:~$ yaz-client
unix:/home/kohaclone/koha-dev/var/run/zebradb/bibliosocket
Connecting...OK.
Sent initrequest.
Connection accepted by v3 target.
ID : 81
Name : Zebra Information Server/GFS/YAZ
Version: 2.0.59/5.9.0
Hi Cindy,
it doesn't help much, but it's not only your installation - I can
reproduce the error message you see on my installation as well:
Diagnostic message(s) from database:
[25] Specified element set name not valid for specified database -- v2
Also using the same version of Zebra.
Can u confirm that *NOT* using IndexData's repositories to grab Zebra,
things work as expected?
On Tue, Feb 3, 2015 at 2:21 PM, Katrin Fischer katrin.fischer...@web.de
wrote:
Hi Cindy,
it doesn't help much, but it's not only your installation - I can
reproduce the error message you see on my
Yep, with use_zebra_facets=0 I can see author facets:
http://imgur.com/lj7v0Uw
And thanks Katrin, I'm sorry you're having the same problem but it makes me
feel a bit better knowing that it's not just me!
---
Cindy Murdock Ames
IT Services
If you perform the same search, making sure use_zebra_facets=0, do u see
author facets?
On Tue, Feb 3, 2015 at 1:12 PM, Cindy Murdock Ames cmurd...@ccfls.org
wrote:
Okay, here's the yaz-client output:
kohaclone@koha:~$ yaz-client
unix:/home/kohaclone/koha-dev/var/run/zebradb/bibliosocket
Hi Cindy,
we figured out the problem now - it's related to the Zebra version.
I removed Indexdata's repos now and reinstalled everything. Using
2.0.44-3.1 now and facets are working!
Katrin
Am 03.02.2015 um 19:25 schrieb Cindy Murdock Ames:
Yep, with use_zebra_facets=0 I can see author
At 01:25 PM 2/3/2015 -0500, Cindy Murdock Ames wrote:
Yep, with use_zebra_facets=0 I can see author facets:
http://imgur.com/lj7v0Uw
And thanks Katrin, I'm sorry you're having the same problem but it makes me
feel a bit better knowing that it's not just me!
For what it's worth, here's my
Robin Sheat schreef op wo 04-02-2015 om 11:36 [+1300]:
* Make sure you've reindexed everything: sudo koha-rebuild-zebra -f
-v
And by that, I actually mean:
sudo koha-rebuild-zebra -f -v instancename
--
Robin Sheat
Catalyst IT Ltd.
✆ +64 4 803 2204
GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5
Howard Fleming schreef op di 03-02-2015 om 17:24 [-0500]:
In mysql, created a database with the same name as the current
production system (kohadb).
If that's what you actually did, the name was wrong. Assuming you're
using 'kohadb' as your instance name (which is a tautological name for
it,
Hello,
Regarding this matter, we are counting on in-house staff for this process. We
are with some mapping doubts. ILS Aleph has the acquisition module very
different from koha. At Aleph the main point is the order number and in koha
that figure does not exist and the main point is the
Just an update.
I solved this one. It turned out that the mysql dump wasn't restoring to
the database name that I thought it would.
Prior to update the koha database was called kohadata. I decided to change
the name to avoid confusion with a possible future database. I thought that
mysql -uroot
17 matches
Mail list logo
