Hi,
I am migrating several million records from an existing vtls system to
koha. We are using mariadb, koha 17.05 (have pulled from master
yesterday ), elastic search 5.4 and plack on debian systems. As I
wanted to preserve all the authority to biblio record links I wrote my
own migration
Hi,
We would like to see this feature working. Do we just report what is
not working in Bugzilla and submit patches for the items or is their
some kind of coordination with other people that we need to take into
account ?
Is there a plan or roadmap for elastic search work or do we just do
Hi ,
Thanks for your answer Chris. Is there some kind of plan / road map to
get it working or should I just go ahead and try to fix it in a side
branch of my own ?
Is anyone coordinating the work for this ?
Best Regards,
Dave
On 08/03/2017 10:42 PM, Chris Cormack wrote:
* David
Hi Micheal,
I originally tried the script link_bibs_to_authorities.pl but there were
two issues with it:
1. After running for days it would use up all available memory and stop
working
2. It does not preserve the links we have today between auths and
biblios but does its best to connect
ronment? i.e. type of Koha install (assuming dev
instal)
MARC21/UNIMARC, OS, Catmandu/ES dependency versions?
-Nick
On Tue, May 16, 2017 at 8:54 AM David Holoshka
<david.holos...@ub.lu.se <mailto:david.holos...@ub.lu.se>>
wrote:
> Nau Mai,
>
>
Nau Mai,
I am working with migrating an vtls ILS to koha for a uni library.
Mostly I have been recoding and optimizing some old bywater scripts and
some koha import utilities to import our 3.2 M+ holdings into koha.
We are trying to run koha master with elastic search due to performance
Hi,
Starting from version 17.11-02 we have made extensive changes to koha to
get elastic search working in koha. We don't run the zebra server but
we see an error in the about box saying that it is not running.
Everything seems to work but we are wondering what functions need zebra
even
Hi,
The code that 'prints' the html code to the browser seems to be missing
from the new sub in Repository.pm or where it is created in oai.pl.
There was an update in the HTTP::OAI classes on cpanm that cause koha
runtime errors when harvesters try to access oai. The required info is
8 matches
Mail list logo