- Koha-devel - lists.koha-community.org

Re: [Koha-devel] The best option for index after a batch change
by Stefano Bargioni 04 Dec '13

04 Dec '13

Ciao Zeno, if you are not interested to short the batch change as much as possible, you can add a delay in your loop, to ensure that your zebra queue is filled at a regular pace, and that rebuild-zebra will manage only few records each time it runs. This solution, if suitable for your installation, doesn't require to modify the background indexing, neither to stop cataloguing. And if you are using the solr-browse we developed together, don't forget its reindexing process... Bye. Stefano > Hi to all, > > I will do a batch chage on bibliographic data with a perl script. > Around 2.000 record on 150.000 biblios. > Before to launch the script, I close the background indexing (I use > Tamil daemon). > After the change I will have 2.000 entry in zebraque table. > > In your opinion what is the best oprion to do after ? > a)I restart background indexing with Tamil's daemon > or > b)I reindex on command line with -z option ? > > Cheers > Zeno Tajoli

1 0

Re: [Koha-devel] RSS method for checking and warning about current installed version
by Paul A 03 Dec '13

03 Dec '13

At 07:48 AM 12/4/2013 +1300, Chris Cormack wrote: >On 4/12/2013 6:38 am, "Tomas Cohen Arazi" ><<mailto:tomascohen@gmail.com>tomascohen(a)gmail.com> wrote: > > > > What would you think of adding some way for the > <http://about.pl>about.pl page to load information on newer versions > available, or even if the currently used branch has reached EOL? > > >I like this idea, assuming it is an opt in option. (and easily switched >off again too) >Chris TomÃ¡s, please tell me that this does NOT involve instances of Koha attempting, unsupervised, to contact an external website. Thanks and best regards, Paul

2 1

RSS method for checking and warning about current installed version
by Tomas Cohen Arazi 03 Dec '13

03 Dec '13

What would you think of adding some way for the about.pl page to load information on newer versions available, or even if the currently used branch has reached EOL? Regards To+ -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 4333190 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

4 4

The best option for index after a batch change
by Zeno Tajoli 03 Dec '13

03 Dec '13

Hi to all, I will do a batch chage on bibliographic data with a perl script. Around 2.000 record on 150.000 biblios. Before to launch the script, I close the background indexing (I use Tamil daemon). After the change I will have 2.000 entry in zebraque table. In your opinion what is the best oprion to do after ? a)I restart background indexing with Tamil's daemon or b)I reindex on command line with -z option ? Cheers Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

2 1

Display of due dates and times
by Galen Charlton 30 Nov '13

30 Nov '13

Hi, Following up on some discussion I started in bug 11148 [1], I would like to pose a general question: if a library uses hourly loans, how would you like due dates and times to display. Various options I can think of are: [1] Only display the date. E.g., 2013-12-01 whether or not the loan is due at the end of the day or earlier. [2] Always display the date and time. E.g., "2013-12-01 23:59", "2013-12-05 13:30", "5/12/2013 15:45", "12/5/2013 4:30 p.m.", etc. [3] Display the time only if it's something other than 23:59. E.g., "2013-12-01 13:45" for an hourly loan, "2013-12-01" for a daily loan. While I started this thread to get some visibility for the question, it may be better to comment in the bug. Regards, Galen [1] http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11148 -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

2 1

3 patchs to sign off
by Mathieu Saby 30 Nov '13

30 Nov '13

Hello I've made some patches which are waiting for sign off (20, according to bugzilla http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=Needs%20Sig… ). Of course I would like to see all of them pushed into master one day - otherwise I would not have written them - ;-) But, among them, some are more important because I wanted to build other patches on top of them. And, to avoid complex dependency issues, I would prefer them to be QAed before writing the patches which will depend on them. It's -bug 11230Refactor C4::Stats::UpdateStats and add UT Once it is validated, I want to add some columns to statistics table (bug 7021) - bug 10869 can't delete order line if title deleted Once it is validated, I will finish bug 10758 *Show bibliographic information of deleted records in acquisitions* - bug 9807 There should be a way to show the content of a basketgroup without reopening it It was QAed, but I added a followup for reindenting code, because without that, working on basketgroup.tt is a torture ;-) Once it is validated, I will work on a patch creating a closing date for basketgroups, and using this date instead of closing date of basket in some parts of Koha (especially claims). It could be syspref dependant, but the current behavior is not good at all (if a basket is closed today, put in a basketgroup in 2 months, printed in pdf, and send to the vendor, Koha uses the today date for claims) Could some people take a look at these? Regards, Mathieu -- Mathieu Saby Service d'Informatique Documentaire Service Commun de Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

1 1

vm koha for 3.14
by Samuel Desseaux 29 Nov '13

29 Nov '13

Hi, I've just uploaded my first vm for koha3.14. You will find the archive at this address http://download.koha-community.org/vm/vmkoha314_beta.zip. It's more a beta version: there's zebra to fix (i've a problem to run it automatically as a service) and enbale shutdown on the desktop. If someone could have a look and eventually help me to this point, i'd be happy. So, it's my first contribution (ouf). Your opinion, ideas in order to ameliorate these vm would be helpful for me. Best regards, Samuel PS: i will upload asap a vm for koha 3.12 (i wanted to do it today but my vm has crashed :-[ )

2 3

Koha development server on Debian Wheezy
by Holger Meissner 29 Nov '13

29 Nov '13

Dear community, I'd like to set up Koha and Git for development. I use Oracle VM Virtual Box and Debian 7.2 Wheezy. First thing I tried, was to follow those instructions: http://wiki.koha-community.org/wiki/Install_and_Setup_Koha_to_use_Git_on_a_… After pointing the files to the kohaclone I get a 403 Forbidden, when trying to navigate localhost:8080. How do I upgrade the database? I also tried to use Koha-gitify, but there was the same problem. https://github.com/mkfifo/koha-gitify Then I tried to install without packages: http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.debian Yet the VirtualHost configuration seems to be incorrect and I'm unable to figure out why. [warn] NameVirtualHost *:80 has no VirtualHosts [warn] NameVirtualHost *:8080 has no VirtualHosts Any suggestions how to fix these errors? Thanks! Holger

2 1

QA: Patches with database changes (DBix::Class)
by Marcel de Rooy 29 Nov '13

29 Nov '13

Hi all, How do we deal with database changes now DBIx::Class is in place? We have the db structure now in at least two places: installer/data/mysql/kohastructure.sql and the separate files in Koha/Schema/Result (per table). Can we get rid of that redundancy in short time? DBIx::Class should now build a new database instead of kohastructure.. (How exactly btw?) About the result sets, do we really need to keep track of the same things in two places there (pod line and in add_columns again)? If a patch presents a dbrev the old way (with updatedatabase and kohastructure), should we reject it now? How does the new-style dbrev actually look like in updatedatabase (upgrade part) ? Which call should we make there to DBIx::Class or Koha::Database ? Probably calling e.g. add_column in updatedatabase and adding the column in the result class file? Or is there a nicer way to say to DBIx "update my items table" or "sync the whole db structure" (if that does not take too much time) ? Should a new style patch currently also update the old style files too? Most probably, yes. Even more reason to eliminate that redundancy. We should also update the wiki and inform developers what we do expect now. Marcel

2 1

Koha 3.12.x and VIAF
by Partha Mukhopadhyay 29 Nov '13

29 Nov '13

2 1