Re: [Koha-devel] [Koha] Koha 17.11 release dates
Hi all, Il 25/09/2017 19:58, Jonathan Druart ha scritto: On Mon, 25 Sep 2017 at 14:27 Mike D. <blac...@gmail.com <mailto:blac...@gmail.com>> wrote: Hi Jonathan, REST API will be implemented in 17.11? Fully or partially? the full list of bugs about 'REST API' that needs us is here: https://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=__open__=REST%20api_id=213773 Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] ES6 usage in the staff client
Hi to all, Il 08/08/2017 12:30, Tomas Cohen Arazi ha scritto: When people say IE, what specific version of the product are you all talking about? in fact rearding https://www.netmarketshare.com/ IE=16% [worldwide on desktop] The version are: Microsoft Internet Explorer 11.0 = 13.71% Microsoft Internet Explorer 10 = 0.90 % Microsoft Internet Explorer 9 = 1,14 % Microsoft Internet Explorer 8 = 1,65 % See: https://www.netmarketshare.com/browser-market-share.aspx?qprid=2=0 In fact the problem is the high numbers of IE 11 that doesn't support ES6 Bye -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Dedicated Zebra Server
Hi, Il 18/07/2017 13:28, Mansur Ali ha scritto: Hello, I am using KOHA ILS. Can i able to use dedicated Zebra Server which is installed in another server? Could you please advice if possible? with present standard installation, the answer is no, it is not possible. In theory if: 1)You setup to use PazPar instead of Zebra [an old option not tested from years] AND 2)You rewrite the updating scripts and deamon you can try to do it. I suggest you to do a try only if you are very skilled on Zebra and others Indexdata's tools. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Koha 17.05 Dates
Hi to all, >May 12 - Feature Freeze, String Freeze, 1st Draft of Release Notes I don't find the 1st Draft of Release Note for 17.05. Where can I find it ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Update of SQL files transaltion for 17.05 and bug 18039
Hi Katrin, In fact I'm working only about this point: 2) Bug 18039 is about the translated installers. Afaikt what it does aim to do is to have the translated installer directories structure matching the English installer directory structure, so files and directories are named the same - this should not require any new translations or a change of the workflow. So I am not sure why this would be a problem? Wonder what I am missing. I have done now a patch to update italian SQL setup: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18456 If anyone push into master bug 18039 BEFORE my bug 18456, I need to rewrite the patch, as I know. In fact now 18456 is a blocker on 18039. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Update of SQL files transaltion for 17.05 and bug 18039
Hi to all, Now 17.05 is near, we need to think how to transalte SQL files. In fact we have a huge change with bug 18039: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18039 So, what do we do ? Do you want 18039 inside 17.05 or not ? IMHO we don't have the resources to insert it into 17.05 Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Help requested - new Koha installer and onboarding tool
Hi to all, Il 16/02/2017 14:45, Jonathan Druart ha scritto: But we need bug 18039 (move the installer files for translated languages) first. It is not easy to test everything for just one guy, so we would need one person for each language: de-DE, es-ES, fr-FR, fr-CA, , it-IT, nb-NO, pl-PL, ru-RU and uk-UA I tested and sign-off it-IT. I added a follow up for it-IT because for Italy the files notices.sql, notices.txt and system_preferences.sql are better suited for dir 'default'. The sign-off create a quite big file (2 Mb). There is any setup of git to avoid this result ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Task schedulers and message queues for Koha
Hi David and all, Il 21/02/2017 23:29, David Cook ha scritto: . Two, they wanted to execute OAI-PMH requests every 2-3 seconds and cron has 1 minute as its finest granularity. Three, even if you setup a cronjob to run every minute, long running tasks could get duplicated (although you could mitigate that with locks which would be a pain). Plus, you want to run tasks in parallel, so you're going to want to use multiple processes, which cron isn't really set up to achieve. Ok, if you need those features cron isn't enough. But why do you drop the option Celery + RabbitMQ + AnyEvent::RabbitMQ They have official debiano packages: https://packages.debian.org/jessie/python-celery https://packages.debian.org/jessie/rabbitmq-server https://packages.debian.org/jessie/libanyevent-rabbitmq-perl We still use one of their dpendencies for similar tasks (libanyevent-perl "event loop framework with multiple implementations"). Python is already present in our Debian/Ubuntu system, it is a prereq of the distributions. Redone a so complex stack in perl i think is very complex. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Task schedulers and message queues for Koha
Hi David, Il 20/02/2017 02:01, David Cook ha scritto: In 2016, I worked on a Koha task scheduler for downloading and importing records via OAI-PMH. I have code which works, but it’s lacking test coverage and I’m unsure that it will make it through QA and be accepted. for me is not 100% clear why do you use a Task scheduler. Why do you no manage queues only with cron ? At least we need a web interface to setup cron. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] About defaults of indicators for auth merges
Hi Marcel, Il 17/01/2017 15:25, Marcel de Rooy ha scritto: But in this specific case (when we change authority type in a merge) we need as a fallback the default indicators of the biblio record. ( As you explained on bug 14769, we cannot trust the indicators from the authority record. Since the indicators on a 100 authority cannot be used on a 600 biblio field etc. -- Who invented those rules, should be rewarded ;) in fact we partialy trust the indicators from the authority record tag 110 'A' + tag 111 'B' = tag 100 'CC' an tag 100 'CC' is connect with biblios 100s, 700s, 600s, etc. I hope that before to definitily save I can fix indicators in auth. I think is mandatory to have 'change-by-hand' in merge. After I save; now modifications start on biblios records and tags. What we want ? Knowing that auth tag = 100, I know that I can copy 1° auth indicator into 1° bib tag indicator. And for the second bib tag indicator ? Two option: -1) default of bib tag framewok [your solution] -2) mantain what is still present [I prefer this option]. I think that the selection between the two option could by done by a system preference. Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] proper sorting order and search for Swedish characters and ISBN search
Hi Gaetan and all, Il 04/11/2016 17:20, Gaetan Boisson ha scritto: The issue is: in Swedish ä, ö and å are separate letters. Not variants of a and o. This means that searching for å shouldn't bring up a. When sorting, they belong to the very end of the alphabet, after z, not along a and o. ICU has some kind of setting that allows to standardize isbns for searching, so you can search for any hyphenated variant, and still find the isbn that actually appears in your data. I *think* this works by removing all the hyphens in the index, but i am not quite sure. Anyway, in order to get the Swedish letters right, we had to do some specific chr configuration. Doing this forces us not to use ICU, which means giving up on standardized isbn search. I think you speaking about general index. zebradb/lang_defs/en/sort-string-utf.chr 7 lowercase {0-9}{a-y}üzæäøöå 8 uppercase {0-9}{A-Y}ÜZÆÄØÖÅ [..] 16 # equivalent æä(ae) 17 # equivalent øö(oe) 18 # equivalent å(aa) 19 # equivalent uü zebradb/etc/words-icu.xml 2 3 4 5 zebradb/etc/phrases-icu.xml 2 3 4 5 Is it not enough to change only those configurations to fix your problem ? Which configuration do force you to CHR conf instead of ICU ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Coding patterns discussion
Hi, Il 13/09/2016 12:19, Kyle Hall ha scritto: TryCatch requires Moose while Try::Tiny is lightweight, but I guess we’re going down the Moose rabbit hole anyways these days? Doesn’t TryCatch just do try/catch/catch instead of if/elsif/elsif? I had thought TryCatch's use of Moose would be a deal-breaker ( at least until Koha is officially plack-only ), but after inspecting the code, I don't believe it actually uses Moose. It does use packages in the Moose namespace, but it doesn't appear to use Moose itself, though it's possible I didn't go far enough down the rabbit hole. reading the code of TryCatch I see that it use: Moose::Util::TypeConstraints that it use: Moose::Exporter; Moose::Deprecated that they use: Moose::Util::MetaRole Moose::Util Try::Tiny So in fact: -- Installing TryCatch we install also Try::Tiny -- We need to create an ad hoc debian package, the debian standard package uses Moose. -- Try::Tiny is in this package: https://packages.debian.org/jessie/libtry-tiny-perl, version 0.22 it is enough ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] SPAM in bugzilla: what do we do ?
Hi to all, Watching new bug in bugzilla I see around one SPAM 'bug' every 2 day. What do we want to do with those 'bugs' ? Bye Zeno Tajoli -- Zeno Tajoli /SVILUPPO PRODOTTI CINECA/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Frameworks / DB constraints
Hi to all, Il 19/04/2016 16:34, Tomas Cohen Arazi ha scritto: Hi fellows, I noticed (in a production server) that a cataloguing framework was deleted by a user. This raised a problem with records that used that framework: trying to look at the record's detail page ended up in a fatal error. [...] Jesse proposed on IRC creating the foreign key with ON DELETE SET NULL. I'm agree on solution proposed by Jesse: creating the foreign key with ON DELETE SET NULL. Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Country-specific forks?
Hi Magnus and all, Il 11/02/2016 10:38, Magnus Enger ha scritto: So do we want one Koha to rule them all, including country-specific features, or do we want one fork per country? Personally, I prefer the former. In the case of the Norwegian patron DB, that is one of the 2-3 "must have" features that all Norwegian public libraries will be looking for when they are choosing between Koha or some proprietary system. Should we be telling them "Nope, you can't use the real Koha, but you can use this fork over here"? That will not increase their confidence in choosing Koha, I suspect. I subscribe the option "one Koha to rule them all". In fact in Italy is possible that "one login DB for all libraries" and "one Italian id for Authority[like Idref from France]" will became very important. Clearly those principles are important: > That said, I do think some principles should be applied: > > - Strive to make even the country specific features as general as > possible, so that others can use them as starting points for similar > features. > > - Strive to make the features as unobtrusive as possible. and I hope that "in time, the plugin system can be made powerful enough that it can handle some or all of the country-specific features?" Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Zebra: the 'elements zebra::snippet' doesn't work
Hi all, I trying to check my indexes in Zebra. My setup: OS: Debian jessie Koha: 3.20.7 [manual install] Zebra: 2.0.61 [install from IndexData repo] Format: UNIMARC Probably the fact that I use unimarc is relevant but I don't understand where. I do the debug described here: http://wiki.koha-community.org/wiki/Troubleshooting_Zebra#Why_does_a_search_return_that_result The result of a working search is: Diagnostic message(s) from database: [25] Specified element set name not valid for specified database -- v2 addinfo 'zebra::snippet' but my ../etc/zebradb/retrieval-info-bib-dom.xml is correct: http://indexdata.com/yaz;> Do I need to check in other places for the setup of ' zebra::snippet' ? Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Zebra: the 'elements zebra::snippet' doesn't work
Hi Tomas, Il 26/01/2016 17:21, Tomas Cohen Arazi ha scritto: You need to check if you are actually using the etc/zebradb/retrieval-info-bib-dom.xml file. Maybe is using a different one, without the line. I read koha-conf.xml and I find: xmlns:xi="http://www.w3.org/2001/XInclude"/> this is the path to the correct retrieval-info-bib-dom.xml file. This file has the line "" Could I check samething else ^ Bye Zeno Tajoli -- Zeno Tajoli / SVILUPPO PRODOTTI/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Which version of Zebra in Debian Jessie?
Hi David and all, Il 21/01/2016 01:57, David Cook ha scritto: Yeah, I think it's OK to use Debian's Zebra packages if you use CHR indexing, if you use ICU indexing, I think you have to use Indexdata's Zebra (and related) packages, or it won't work well. in fact for myself ICU indexing is mandatory, so I need to use Indexdata's Zebra. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Which version of Zebra in Debian Jessie?
Hi David and all 2)Wait unitl IndexData update its version of libnet-z3950-zoom-perl news from IndexData: Adam Dickmeiss has update libnet-z3950-zoom-perl with http://ftp.indexdata.com/pub/debian/pool/dists/jessie/main/amd64/libnet-z3950-zoom-perl_1.30-2.indexdata_amd64.deb so now, if you install libnet-z3950-zoom-perl with IndexData repository you retrive: sudo apt show libnet-z3950-zoom-perl ... Version: 1.30-2.indexdata Depends: perl (>= 5.20.2-3+deb8u1), perlapi-5.20.2, libc6 (>= 2.2.5), libxml2 (>= 2.6.27), libxslt1.1 (>= 1.1.25), libyaz5 (>= 5.13.0), libmarc-record-perl So now my answer to the question "Which version of Zebra in Debian Jessie?" is: "The version that you retrive from IndexData repository." For me now, if you use Debian Jessie, it is a good idea to add also IndexData repository in /etc/apt/sources.list.d/ Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Which version of Zebra in Debian Jessie?
Hi all Il 20/01/2016 11:26, Wolfram Schneider ha scritto: how about installing libnet-z3950-zoom-perl from the Indexdata repository? http://ftp.indexdata.com/pub/debian/pool/dists/jessie/main/amd64/libnet-z3950-zoom-perl_1.30-1.indexdata_amd64.deb the problem is that in a normal installation yaz and zebra are installed BEFORE libnet-z3950-zoom-perl. I don't know if apt-get try to use libnet-z3950-zoom-perl from Indexdata repo or from general Jessie repo. The version of Indexdata is the same on general Jessie repo. See also my other answer to David Cook. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Which version of Zebra in Debian Jessie?
Hi David and all Il 19/01/2016 23:26, David Cook ha scritto: What do you mean by "goes wrong"? Can you paste the results into an email? On openSUSE, I'm using Zebra 2.0.60, YAZ 5.1.2, and Net::Z3950::ZOOM 1.30, and everything works fine. I think is a problem on integration Jessie general repo and Indexdata repo. Recreate the problem is quite long, you need to start from a basic Jessie with only ssh server. The steps are: 1)A new debian jessie with only ssh server 2)Login as 'root' 3)vi /etc/apt/sources.list.d/koha.list deb http://debian.koha-community.org/koha oldstable main 4)vi /etc/apt/sources.list.d/indexdata.list deb http://ftp.indexdata.dk/debian jessie main deb-src http://ftp.indexdata.dk/debian jessie main 5)wget -O- http://debian.koha-community.org/koha/gpg.asc | apt-key add - 6)wget -O- http://ftp.indexdata.dk/debian/indexdata.asc | apt-key add - 7)apt-get update 8)apt-get upgrade 9)apt-get install koha-deps Now you have installed yaz (5.15.2-1.indexdata) and idzebra-2.0 (2.0.61-1.indexdata) 10)install koha-perldeps Now the error: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-perldeps : Depends: libnet-z3950-zoom-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. If I use koha-common instead of koha-deps and koha-perldeps I receive the same error. I write also to indexdato to ask them to create a new version of libnet-z3950-zoom-perl for Jessie. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Fwd: Call for testers: next release of Net::OAI::Harvester Perl module may break legacy custom handlers
Messaggio Inoltrato Oggetto: Call for testers: next release of Net::OAI::Harvester Perl module may break legacy custom handlers Data: Fri, 15 Jan 2016 12:38:17 +0100 Mittente: Thomas BergerRispondi-a: t...@gymel.com Organizzazione: Gymel.com A: Perl for libraries , Using XML in libraries -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [Apologies for cross-posting] The Perl module Net::OAI::Harvester implements a client framework for the OAI Protocol for Metadata Harvesting (OAI-PMH) and was authored and originally maintained by Ed Summers. It has been available on CPAN ever since 2003 and its last stable version 1.15 has been released almost four years ago: < http://search.cpan.org/~thb/OAI-Harvester-1.15/ >. Since one of the repositories used for testing vanished from the web some time ago and this is breaking the test suite a new version has to be released fairly soon. Over time I had been tackling various minor issues and published developer releases on CPAN, cf. the list at the end of this mail or the Changes document linked at the CPAN page for the current release 1.16_12: < http://search.cpan.org/~thb/OAI-Harvester-1.16_12/ > However the sum of these changes is not negligible and specifically their impact on "custom metadata handlers" (which are to be used when processing other metadata formats than oai_dc) may affect applications using the module: Up to version 1.15 the metadataHandler was inconsistently fed with input : - GetRecord exposed the almost complete XML response to the Handler (including start_document/end_document events) - ListRecords exposed the (OAI)record element (header, metadata and optional about containers) but did not propagate start_document or end_document events. In both cases the events for the header tags itself and for the optional setSpec subelements had not been forwarded Version 1.20 introduces a modified behavior for metadataHandler and an additional recordHandler: - a metadataHandler will see only the (single) subelement of the OAI metadata element (so for an deleted record it might never be invoced at all) - a recordHandler will see the OAI record element and its subelements Therefore a metadataHandler will now be confined to the metadata fragment(s) of the response, and the new recordHandler approximates the old behavior of ListRecords, however OAI-PMH:identifier and OAI-PMH:datestamp will now be properly encapsulated within their OAI-PMH:header element. Additionally, two new methods responseDate() and request() allow access to the corresponding top-level OAI-PMH elements in all response types. A SAX filter of class Net::OAI::Record::DocumentHelper may be used to inject start_document and end_document events into the chain if they are needed. As a temporary measure, you may set $Net::OAI::Harvester::OLDmetadataHandler =1 to change the behavior of handlers passed as "metadataHandler" into that of a recordHandler. << Obviously the change of semantics for a metadataHandler to deal with the "metadata" elements of the response instead of the "record" elements is a design decision and may be questioned by users of the module. The current version also contains several changes which solve deficiencies of Net::OAI::Harvester 1.15 but possibly break existing workarounds for these deficiencies. For example officially (per documentation) you never could acccess the responseDate of the OAI-PMH result, but due to a sloppy implementation of processing for the identify verb it was possible to extract it in this case by an undocumented method. The current version supplies a dedicated responseDate() accessor for all verbs but at the same time fixes the behavior in the identify case. I may be overly optimistic but my impression is that the changes between the current 1.15 and the coming version (most probably numbered 1.20) do actually fix many issues but the fear is realistic (I experienced that myself with an old application of mine using the module) that these fixes may conflict with workarounds introduced by users to make things work before. *** So please, if you are currently using Net::OAI::Harvester *and* had been forced to introduce workarounds or tweak internals of the module, perform thorough testing before upgrading to the coming stable version, preferably already now with the developer version 1.16_12. And, please, please: provide feedback if you should run into trouble, either via the CPAN request tracker for the module at < https://rt.cpan.org/Public/Dist/Display.html?Name=OAI-Harvester > or by direct mail. Sorry for the inconvenience viele Gruesse Thomas Berger Changes to Net::OAI::Harvester since version 1.15 1.16_12 Tue, Jan 12 00:20:05 CET 2016 - - dealing with CPANTS Kwalitee issues, esp. version number mess - - new filter class Net::OAI::Record::DocumentHelper for tweaking 1.16_11 Tue, Jan 12 00:20:05 CET 2016 - -
Re: [Koha-devel] IMPORTANT: Global Bug Squashing Week
Hi to all, Il 04/11/2015 09:54, Andreas Hedström Mace ha scritto: Or maybe make the Trello board public? now Trello is public, but to work on it you need to be inscript into the board. At 05/11/2015 I will try to sign-off bug 14969, Remove C4::Dates from serials/*.pl files Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Bug 7736 and t/db_dependent/TestBuilder.t
Hi to all, working on bug 7736, after insert code and update db, I find problem with this test: prove t/db_dependent/TestBuilder This is the error that I receviee: t/db_dependent/TestBuilder.t .. 3/41 DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails (`koha`.`edifact_messages`, CONSTRAINT `emfk_basketno` FOREIGN KEY (`basketno`) REFERENCES `aqbasket` (`basketno`)) [for Statement "DELETE FROM `aqbasket` WHERE ( `basketno` = ? )" with ParamValues: 0='37'] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1593. DBIx::Class::ResultSet::delete_all(): Cannot delete or update a parent row: a foreign key constraint fails (`koha`.`edifact_messages`, CONSTRAINT `emfk_basketno` FOREIGN KEY (`basketno`) REFERENCES `aqbasket` (`basketno`)) at /production/develops/t/lib/TestBuilder.pm line 94 DBIx::Class::Carp::__ANON__(): A DBIx::Class::Storage::TxnScopeGuard went out of scope without explicit commit or error. Rolling back. at /usr/share/perl5/DBIx/Class/Storage/TxnScopeGuard.pm line 132 # Looks like you planned 41 tests but ran 35. # Looks like your test exited with 255 just after 35. t/db_dependent/TestBuilder.t .. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 6/41 subtests Test Summary Report --- t/db_dependent/TestBuilder.t (Wstat: 65280 Tests: 35 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 41 tests but ran 35. Files=1, Tests=35, 9 wallclock secs ( 0.04 usr 0.01 sys + 7.54 cusr 0.24 csys = 7.83 CPU) Result: FAIL The bug 7736 add 3 table to Koha: edifact_ean table vendor_edi_accounts table edifact_messages vendor_edi_accounts with does constraints CREATE TABLE IF NOT EXISTS vendor_edi_accounts ( ... CONSTRAINT vfk_vendor_id FOREIGN KEY ( vendor_id ) REFERENCES aqbooksellers ( id ), CONSTRAINT vfk_shipment_budget FOREIGN KEY ( shipment_budget ) REFERENCES aqbudgets ( budget_id ) ... ) CREATE TABLE IF NOT EXISTS edifact_messages ( ... CONSTRAINT emfk_vendor FOREIGN KEY ( vendor_id ) REFERENCES aqbooksellers ( id ), CONSTRAINT emfk_edi_acct FOREIGN KEY ( edi_acct ) REFERENCES vendor_edi_accounts ( id ), CONSTRAINT emfk_basketno FOREIGN KEY ( basketno ) REFERENCES aqbasket ( basketno ) ... ) ALTER TABLE aqinvoices ADD COLUMN message_id INT(11) REFERENCES edifact_messages( id ); ALTER TABLE aqinvoices ADD CONSTRAINT edifact_msg_fk FOREIGN KEY ( message_id ) REFERENCES edifact_messages ( id ) ON DELETE SET NULL; CREATE TABLE IF NOT EXISTS edifact_ean ( ... CONSTRAINT efk_branchcode FOREIGN KEY ( branchcode ) REFERENCES branches ( branchcode ) ... ) The full update done by bug 7736 is here: https://github.com/colinsc/koha/blob/edifact_snapshot_150911/installer/data/mysql/atomicupdate/edifact.sql As I see there is a problem on about this costraint of table edifact_messages: CONSTRAINT emfk_basketno FOREIGN KEY ( basketno ) REFERENCES aqbasket ( basketno ) Reading the code of t/db_dependent/TestBuilder.t I don't understand if there is problem on how the constraint is done or I need to change TestBuilder.t. Do you have any idea ? Where can i find more info about TestBuilder.t ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Feature slush about bug 7736 -EDI enhancement
Hi to all, Il 26/10/2015 17:07, Tajoli Zeno ha scritto: So, can I use also tomorrow (27/10, CST time) to insert this enhancement in 3.22 ? I stop the request to insert bug 7736 into 3.22 There are still problem on the code. so no EDI in 3.22 I update the bug with extre info http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7736 Bye -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Bug 7736 and t/db_dependent/TestBuilder.t
Hi, Il 27/10/2015 13:26, Jonathan Druart ha scritto: I can have a look but the patch does not apply anymore and I have got an error on updating the DB: DBD::mysql::db do failed: Can't create table `koha`.`edifact_ean` in fact the definition of edifact_ean in atomicupdate is wrong. I'm rebasing the patch Bye -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Feature slush about bug 7736 -EDI enhancement
Hi to all, I'm working on sign-off bug 7736, to insert EDI support in Koha Acquisition. The bug add many files abut change in light way templates of Acqi. About C4 and cgi: C4/Acquisition.pm |6 +- C4/Installer/PerlDependencies.pm | 10 + acqui/basket.pl| 77 ++ acqui/basketgroup.pl | 18 +- acqui/invoices.pl |4 +- So it doesn't interfer much with other develops. So, can I use also tomorrow (27/10, CST time) to insert this enhancement in 3.22 ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Install master on debian jessie
Hi to all, i'm try to install git master version on debian jessie. I installed modules using repo deb http://debian.koha-community.org/koha stable main [unstable doesn't work now] using the commands: sudo apt-get install koha-deps sudo apt-get install koha-perldeps sudo apt-get install liblog-log4perl-perl sudo apt-get install libplack-middleware-reverseproxy-perl sudo apt-get install memcached then I do git clone, checked and installed perl dependecies. For apache I installed sudo a2enmod rewrite deflate sudo a2enmod cgi sudo a2dissite 000-default sudo a2ensite koha Now there problem on apache. The intranet log says: [Tue Sep 15 17:25:04.573995 2015] [authz_core:error] [pid 7132] [client 10.0.2.2:54862] AH01630: client denied by server configuration It seems connect with this change from 2.2 to 2.4: http://httpd.apache.org/docs/2.4/upgrading.html -> Authorization I try to do the change from 2.2 configuration: Order deny,allow Deny from all to 2.4 configuration: Require all denied But it does't work. Do you have any more idea on the topic ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] About the dependency Test::CGI::Multipart
Hi to all, I write to advice about the module Test::CGI::Multipart It is an optional module, connect with test. Attention that it is availabe only in whezzy as .deb, it is not presente in jessied (or in sid or in testing). It was added with bug 6874, this commit: http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=209faec18305eb570bda377c1db03425cd53f087 Probalby we need to create the package in koha repo. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Question about Schema
Hi all, Il 09/09/2015 01:45, David Cook ha scritto: While "retarded" was common in colloquial English, especially American English, in the '90s, it's not really acceptable anymore. Feel free research ableism for explanations why. we need to rember that we at leat 5 different 'English' inside us: 1)American English 2)UK English 3)India English 4)AUS/NZ English 5)English as second languge in the rest of the world. With a mix of Western/No Western coltures. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Test Planck
Hi to all, one important thing to do is to test in master the new code for plack. But, after install planck, how could I test error connect with plack ? Do you have any suggesstion about this topic ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Bug 13906: the start of Auth/Web test rewritting of Olli-Antti Kivilahti
Hi to all, I'm starting to see what to do for sign-off the work done by Olli-Antti Kivilahti about rewritting of Authentication and Test web interface of Koha. I see that first bug to test is bug 13906 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13906 The bug is 'In discussion'. I'm not sure od situation. What do you think about the proposal of Olli-Antti ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Proposal on how to skip articles on sorting titles (only MARC21)
Hi to all, here: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14332 there is a proposal on how to skip articles on sorting titles using indicator n. 2 of field 245. Clearly it works only on MARC21 I'm not sure to have used a good way to do the result, but I find very difficult to use the three files of Zebra xslt setup (marc21/biblios/biblio-koha-indexdefs.xml, marc21/biblios/biblio-zebra-indexdefs.xsl and zebradb/xsl/koha-indexdefs-to-zebra.xsl). Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.taj...@cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI) ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Sort by title. Based only on Title or also on Title-cover ?
Hi, reading from etc/zebradb/marc_defs/marc21/biblios/biblio-koha-indexdefs.xml I see that from 245 $a are crerated two indexes: Title and Title-cover: index_subfields tag=245 subfields=a target_indexTitle-cover:w/target_index target_indexTitle-cover:p/target_index target_indexTitle-cover:s/target_index target_indexTitle:w/target_index target_indexTitle:p/target_index target_indexTitle:s/target_index /index_subfields Sort by title (A-Z) and (Z-A) in opac are based only on 'Title' Zebra index or also on Title-cover ? It is not clear for me. Bye Zeno Tajoli ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Plugin marc21_linking_section.pl
Hi, Il 14/05/2015 16:04, Marcel de Rooy ha scritto: Is anyone of you using this plugin? I use this plugin in Koha 3.12.06 and it works. I can launch it, search for a record. But if I click the Choose button, nothing happens. (I would expect to get back something into the field that launched the plugin.) It insert (into he field that launched the plugin.) $w - 001 of searched record $t - field 245$a of searched records If you use it, please let me know what I am doing wrong :) See also bug 13437 which makes some changes to various marc21 plugins including this one. I think there is same bug in the code. Do you test it on 3.18.x or on 3.20-beta ? Bye Zeno Tajoli -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Language overlays or: On the way to finally resolve important translation issues in Koha
Hi to all, Il 30/04/2015 12:07, Marc Véron ha scritto: A couple of days ago I filed Bug 14063 - Implement language overlay for authorised values It is a small, minimal invasive patch (19 lines) that uses additional entries in the table authorised_values. To use it, one can simply create an additional entry with a trailing language code, e.g. BSELL-de-DE or BSELL-fr-FR It can be used As is without any changes to the database or to the user interface. for me the patch done by Marc is a good start. We can start with this in 3.20. Bye -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Metasearch on Opac (bug 10486)
Hi to all, I report the developing of a metasearch in Koha Opac. a)The path that I try on Marsiglia meeting, to reuse the z39.50 interface of intranet, was a dead end. It is too slow, It download the records, insert them ino resevoir then display. b)Now I try to use pazpar2 with less modificaton on Koha as possible. c)So I create a new opac template and opac cgi d)I create a syspref to display a link to metasearch in opac header e)I doing also pazpar setup on command line. In fact it in not very difficult using this example: https://github.com/ssp/pazpar2-all f)You nee to insert a specific config in koha-httpd.conf Now I'm working on opac template and I have same problems with js (pazpar2 is called by ajax). I plan to release code with a big wiki page on installation for Koha 3.22 Bye Zeno Tajoli -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Install and use memcached
Hi to all, I'm starting to use memcached. I see that there isn't many info in Koha wiki. I installed it with sudo apt-get install memcached on Debian Wheezy Setup the variables in koha-httpd.conf It works !! So the questions: Is the package libmemcached useful to install ? For apt-get it is only 'suggest' How much RAM ? The default in /etc/memcached.conf is 64 MB, I don't what could be a 'good' value. Bye Zeno Tajoli -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] Massime import slow (around 800 record in 1 minute).
Hi to all, Il 16/02/2015 13:57, MJ Ray ha scritto: Tajoli Zeno wrote: I'm finding a quite slow import into a Koha DB with bulkmarcimport.pl. It imports only 800 record in 1 minute. With top: 90-95 % bulkmarcimport.pl 5 % mysql apache, zebra, indexing are down. Down the list rather than down=not-running, I hope! no MJ Ray, down=not-running. I imported 300.000 biblio records in a empty Koha. At the end the speed is 1200 record in 1 minute as average. Records without items are much more fast. I'm trying to understand better the situation. Bye Zeno Tajoli -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Fix on DOM inedxing. We still work on biblio-koha-indexdefs.xml or directly on biblio-zebra-indexdefs.xsl
Hi to all, I find a bug on MARC21/Normarc DOM indexing. Bug 12948: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12948 Now that grs1 is deprecated, do we still use biblio-koha-indexdefs.xml and generate biblio-zebra-indexdefs.xsl ? Or now do we prefer edit biblio-zebra-indexdefs.xsl directly Bye Zeno Tajoli -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
[Koha-devel] Massime import slow (around 800 record in 1 minute).
Hi to all, I'm finding a quite slow import into a Koha DB with bulkmarcimport.pl. It imports only 800 record in 1 minute. With top: 90-95 % bulkmarcimport.pl 5 % mysql apache, zebra, indexing are down. I have 2 CPU so total CPU load is around 50% Full of RAM, 8 Gb, used 4 Gb. Option used: -b -commit 1000 -file /patth of file Do you have suggestions on how to speed the import ? Bye Zeno Tajoli -- Dr. Zeno Tajoli Servizi Innovativi -- Automazione Biblioteche z.taj...@cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/