Re: [Koha] call number sort problem
Hie, If you changed the default classification source, it will not affect the actual classification source in items, nor the items.cn_sort. You may use the script touch_items.pl to edit all items and so recompute the items.cn_sort. Best regards, Le 04/07/2014 18:25, Bruce A Metcalf a écrit : Fridolin SOMERS fridolin.som...@biblibre.com wrote: Look into database the values of items.cn_sort for thoses callnumbers. The call numbers are fine. It's the sorting sequence I wanted to change. As in my previous post, I effected this by changing to a different set of Classification Filing Rules. LCC did what I wanted, Generic did not. Regards, / Bruce / Bruce A. Metcalf Librarian The Augustan Society, Inc. Le 11/06/2014 05:29, Bruce A Metcalf a écrit : Fridolin SOMERS fridolin.som...@biblibre.com wrote: Le 21/03/2014 22:05, Margo Duncan a écrit : We're having some issues with call number sort in our reports and I'm wondering if anyone has any insights. It appears that cn_sort has two different methods of sorting call numbers. One way is that 0 is added so that a call number of HD30.19 is HD003019. The other way is with _ so HD30.19 is HD_0030_19. ... So can I adjust the sorting method, or is there something wrong with my data? items.cn_sort calculation depends on items.cn_source value, if no value, the default classification source is used (defined in syspref DefaultClassificationSource). I think I understand this, but I don't understand how to make a call number like H B34 sort before one like HM B34. It seems the default is to sort spaces after letters and numbers (which takes me all the way back to Hollerith sorts!). Can this be changed, and if so, how? Regards, / Bruce / Bruce A. Metcalf Library Director The Augustan Society, Inc. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.som...@biblibre.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] How to stop series title volume enter Authorities
Hi Paul, Thanks for your response. By following your suggestion, we need to predetermine whether each series title is a new heading. As well, the need to remove volume designator before the first save of bibliographic record concerned. Then paste such detail back before saving the same bib. record again. Definitely room for improvement, especially when Koha can simply ignore subfield $v, then this problem is all resolved! - Iming Chan Translib Information Service Melbourne, Australia http://opac.translib.com Phone: +61 3 9801 5097 Fax: +61 3 9801 4024 E-mail: im...@translib.com -- View this message in context: http://koha.1045719.n5.nabble.com/How-to-stop-series-title-volume-enter-Authorities-tp5803348p5803436.html Sent from the Koha-general mailing list archive at Nabble.com. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] koha with solar serch engine
Koha does not work with Solr. 2014-07-05 8:16 GMT+02:00 vinod kumar vinod.kumar@gmail.com: Hi all anyone know how to koha run with solar search engine. plz guide me ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] How to stop series title volume enter Authorities
At 03:04 AM 7/7/2014 -0700, Iming Chan wrote: Hi Paul, Thanks for your response. By following your suggestion, we need to predetermine whether each series title is a new heading. Our cataloguers (so I'm told), always check the 1**, 4**, 6** and 7** authority entries -- it's an intrinsic part of the biblio db integrity without which we lose the OPAC usefulness of being able to click on authority links. I've just had a quick look, and here's an example of how things can go wrong: Time-Life Books http://koha-admin/cgi-bin/koha/authorities/detail.pl?authid=6585Details http://koha-admin/cgi-bin/koha/catalogue/search.pl?type=intranetop=do_searchidx=an,phrq=65854 biblio(s) Time-Life Books. http://koha-admin/cgi-bin/koha/authorities/detail.pl?authid=12090Details http://koha-admin/cgi-bin/koha/catalogue/search.pl?type=intranetop=do_searchidx=an,phrq=1209074 biblio(s) Automation is wonderful, but the Mark 1 human eyeball is still superior :=) Best -- Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. http://NavalMarineArchive.com and http://UltraMarine.ca ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] patron categories [bulkmarcimport]
Eric, I've read the changes from 5.5 to 5.6, and don't seem to be a way to prevent the problems you found with any option switch. I don't think 3.14 would do it better. You should fill the bug, and remeber you can have a separate DB server until we solve it. Regards To+ On Sun, Jul 6, 2014 at 12:19 PM, Eric Lease Morgan eric_mor...@infomotions.com wrote: On Jul 5, 2014, at 12:07 PM, Eric Lease Morgan eric_mor...@infomotions.com wrote: I recommend that you downgrade to MySQL 5.5, or better install on top of Ubuntu LTS/Debian Wheeze. I recommend Ubuntu 12.04 Server. And follow the official instructions [2]. [1] http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html [2] http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages Alas, I can not afford to downgrade MySQL nor find an additional operating system. Instead, I have installed Koha version 3.16.01 on a machine with MySQL 5.1. Tomorrow I will dump the initialized database and import it into MySQL on a different machine where I plan to run Koha for “real. Wish me luck. I’m making progress. Four steps forward and three steps back. I installed Koha 3.16.01 on a different host. I dumped the database. I installed Koha 3.16.01 on yet a different host, sans database initialization. Then, my hand, I populated my koha database with the database dump from the first host. After doing this I was able to add patrons, namely, myself. There were no weird errors. All of this was four steps forward. Then I: 1. used the Z39.50 interface to add some bibliographic records. I searched the Library of Congress for books on origami. I got a list. I tried to add one to my catalog. After filling out a number of fields I said go, but it did not save. I forget what the error was. I tried other searches, and no matter what I searched for I got no results. It seemingly broke. One step backwards. 2. tried to stage some records. Import. See all 1,400 of them. I cleaned them. I try to import the staged records and get No data available in table”. A second step backwards. 3. su’ed to the koha user. I set my environment variables. I ran bulkimport.pl and I got the same errors as before. .DBD::mysql::st execute failed: Field 'marcxml' doesn't have a default value at /usr/local/koha/lib/C4/Biblio.pm line 3222, GEN15 line 1465. ERROR in _koha_add_biblioitem INSERT INTO biblioitems SET” Searches against my OPAC return Zebra error 109. I have no bibliographic data. A third step backward. I’m running out of options. I will: 1. try to repeat the above process but with version 3.14 2. break down and use my “different host” — Eric ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] call number sort problem
At 09:36 AM 7/7/2014 +0200, Fridolin SOMERS wrote: Hie, If you changed the default classification source, it will not affect the actual classification source in items, nor the items.cn_sort. You may use the script touch_items.pl to edit all items and so recompute the items.cn_sort. I can't find any documentation on 'touch_items.pl' except a few mentions on IRC chat https://www.google.com/search?q=site%3Akoha-community.orgq=touch_items.plsa=Searchgws_rd=ssl -- could you please point me in the right direction? Thanks -- Paul ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Upload recodrs via Z39.50 into target
Hello, YAZ support Z39.50 upload feature, but Koha has implemented just search and download. Did anybody solve same problem? We are looking solution for upload authority records directly form Koha. Any ideas? Thaks for assistance. Mike ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Crontab - is that one tabs used to open beer cans?
In the absence of a sane plan, I'm going with yours (just kidding -smile). This is a paraphrase from the TV series Red Dwarf and I love to use it whenever I can. Thank you so much for sharing. This will make it much easier for me to get things working in Koha. Although I'll have to do some substitution since Koha was loaded in /etc/koha this is going to help tremendously to recreate the crontab for Koha. Phillip Date: Mon, 7 Jul 2014 09:32:52 +0530 Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? From: vishal.pa...@osslabs.biz To: pponc...@live.com Hi Philip, I think you have to set crontab again for this new version. I am using below crontab:PATH=/usr/bin:/sbin:/bin:/usr/sbinHOME=/home/koha/koha-dev(config) PERL5LIB=/home/koha/kohaclone(src-code)KOHA_CONF=/home/koha/koha-dev(config)/etc/koha-conf.xmlKOHA_CRON_PATH = /home/koha/kohaclone(src-code)/misc/cronjobs*/1 * * * * $PERL5LIB/misc/migration_tools/rebuild_zebra.pl -b -z 5 2 * * * $KOHA_CRON_PATH/fines.pl*/15 * * * * $PERL5LIB/misc/cronjobs/process_message_queue.pl10 3 * * * $KOHA_CRON_PATH/advance_notices.pl -c 0 3 * * * $KOHA_CRON_PATH/overdue_notices.pl -t#5 2 * * * $KOHA_CRON_PATH/fines.pl50 * * * * $KOHA_CRON_PATH/holds/build_holds_queue.pl /dev/null 21 0 3 * * * $KOHA_CRON_PATH/holds/cancel_expired_holds.pl /dev/null 21 Hope this will help you. On Mon, Jul 7, 2014 at 9:19 AM, Phillip Ponchot pponc...@live.com wrote: My new version of koha 3.14 is up and working. I was just looking at the crontab jobs and I didn't find anything in there. I used sudo crontab -e to open crontab. From the old version of koha, there were several contrab jobs - exporting Perl, running fines.pl etc. Are these jobs automatically put into crontab or do I have to put the jobs into crontab myself. Does anyone have a good example of the koha crontab jobs that should be in the crontab? Thanks, Phillip ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Warm Regards,Vishal Patil Software Engineer - Nucsoft Ltd.phone: 022 32080161 www.osslabs.biz www.nucsoft.com vishal.pa...@osslabs.biz ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha API
Greetings, We could use some help understanding how we go about querying the data in Koha to produce things like book cover images, new item lists, etc. I might suggest reading on the wiki. http://wiki.koha-community.org/wiki/APIs_and_protocols_supported_by_Koha Though, I am not sure everything you is in there, but that doesn't stop you from submitting a patch. :) GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Crontab - is that one tabs used to open beer cans?
The old koha was installed as a tarball on the old server so I believe this makes it a source-based. The new koha was installed via a repository. apt-get install koha-common. I did find in /etc/cron.d a koha-common file. The contents of this file was: --- # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl - also there is a directory in /user/share/koha/bin/cronjobs - are these run by the koha program or do I have to schedule them in a crontab job? advance_notices.pl holds backup.sh import_webservice_batch.pl batch_anonymise.pl j2a.pl build_browser_and_cloud.pl longoverdue.pl cart_to_shelf.plMARC21_parse_test.pl check-url.pl overdue_notices.pl check-url-quick.pl printoverdues.sh cleanup_database.pl process_message_queue.pl cloud-kw.pl purge_suggestions.pl cloud-sample.conf rss CONFIGURE.gmail runreport.pl create_koc_db.plserialsUpdate.pl crontab.example services_throttle.pl delete_expired_opac_registrations.pl social_data delete_patrons.plstaticfines.pl delete_unverified_opac_registrations.pl thirdparty fines.pl update_totalissues.pl gather_print_notices.pl -- I just want to run automatically anything that needs to be done to keep koha up to date. Thanks Phillip From: mtomp...@hotmail.com To: pponc...@live.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? Date: Mon, 7 Jul 2014 14:00:19 -0400 Greetings, First, you still did not specify if you were doing a package installation or a source-based installation. Which are you doing? If a source-based installation, then your hacked up solution is passable, though not optimal. Second, let's reply to your points: There is a systems crontab which ubuntu warns not to change. You can create crontab jobs at the system level without modifying existing ones. Every file placed in the appropriate cron.* directory is its own crontab file. The crontab on the old server is sudo crotab -uroot -e where all the koha cronjobs are setup. This is a user crontab still. Was the old system a source-based installation or was it a packages based installation? If you are finding user crontabs, then it likely was a source-based installation. Why do you need to have the new system as a source-based install? A package-based installation sets up all the crontab jobs you need by default for you already. No crontab job tweaks required. Seriously, please consider a packages based installation: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages And thirdly and lastly, did you actually go looking for crontab jobs manually? Like the following done on a package installation of Koha that we are using in production. $ cd /etc/cron.d $ ls -la total 20 drwxr-xr-x 2 root root 4096 Feb 11 17:29 . drwxr-xr-x 98 root root 4096 Jul 7 17:39 .. -rw-r--r-- 1 root root 422 Nov 22 2013 koha-common -rw-r--r-- 1 root root 102 Jun 19 2012 .placeholder -rw-r--r-- 1 root root 396 Dec 16 2011 sysstat $ cat koha-common # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl $ cd ../cron.daily $ ls -la total 84 drwxr-xr-x 2 root root 4096 Jun 25 11:55 . drwxr-xr-x 98 root root 4096 Jul 7 17:39 .. -rwxr-xr-x 1 root root 633 Jul 12 2013 apache2 -rwxr-xr-x 1 root root
Re: [Koha] Koha API
Id suggest looking at the reports library on the wiki. All the data is available that way Chris On 8 July 2014 6:48:58 am NZST, Mark Tompsett mtomp...@hotmail.com wrote: Greetings, We could use some help understanding how we go about querying the data in Koha to produce things like book cover images, new item lists, etc. I might suggest reading on the wiki. http://wiki.koha-community.org/wiki/APIs_and_protocols_supported_by_Koha Though, I am not sure everything you is in there, but that doesn't stop you from submitting a patch. :) GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Crontab - is that one tabs used to open beer cans?
Don't touch anything. Seriously. If you have a packaged install, it's all been done. Look in cron.d, cron.daily etc all the jobs have been set up. Chris On 8 July 2014 7:17:29 am NZST, Phillip Ponchot pponc...@live.com wrote: The old koha was installed as a tarball on the old server so I believe this makes it a source-based. The new koha was installed via a repository. apt-get install koha-common. I did find in /etc/cron.d a koha-common file. The contents of this file was: --- # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl - also there is a directory in /user/share/koha/bin/cronjobs - are these run by the koha program or do I have to schedule them in a crontab job? advance_notices.pl holds backup.sh import_webservice_batch.pl batch_anonymise.pl j2a.pl build_browser_and_cloud.pl longoverdue.pl cart_to_shelf.plMARC21_parse_test.pl check-url.pl overdue_notices.pl check-url-quick.pl printoverdues.sh cleanup_database.pl process_message_queue.pl cloud-kw.pl purge_suggestions.pl cloud-sample.conf rss CONFIGURE.gmail runreport.pl create_koc_db.plserialsUpdate.pl crontab.example services_throttle.pl delete_expired_opac_registrations.pl social_data delete_patrons.plstaticfines.pl delete_unverified_opac_registrations.pl thirdparty fines.pl update_totalissues.pl gather_print_notices.pl -- I just want to run automatically anything that needs to be done to keep koha up to date. Thanks Phillip From: mtomp...@hotmail.com To: pponc...@live.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? Date: Mon, 7 Jul 2014 14:00:19 -0400 Greetings, First, you still did not specify if you were doing a package installation or a source-based installation. Which are you doing? If a source-based installation, then your hacked up solution is passable, though not optimal. Second, let's reply to your points: There is a systems crontab which ubuntu warns not to change. You can create crontab jobs at the system level without modifying existing ones. Every file placed in the appropriate cron.* directory is its own crontab file. The crontab on the old server is sudo crotab -uroot -e where all the koha cronjobs are setup. This is a user crontab still. Was the old system a source-based installation or was it a packages based installation? If you are finding user crontabs, then it likely was a source-based installation. Why do you need to have the new system as a source-based install? A package-based installation sets up all the crontab jobs you need by default for you already. No crontab job tweaks required. Seriously, please consider a packages based installation: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages And thirdly and lastly, did you actually go looking for crontab jobs manually? Like the following done on a package installation of Koha that we are using in production. $ cd /etc/cron.d $ ls -la total 20 drwxr-xr-x 2 root root 4096 Feb 11 17:29 . drwxr-xr-x 98 root root 4096 Jul 7 17:39 .. -rw-r--r-- 1 root root 422 Nov 22 2013 koha-common -rw-r--r-- 1 root root 102 Jun 19 2012 .placeholder -rw-r--r-- 1 root root 396 Dec 16 2011 sysstat $ cat koha-common # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email
Re: [Koha] Koha/Evergreen Comparison Site
Hi Steve, Diana will be responding in more detail but the home page of the site lists the versions being compared. We are a bit behind but we do try to keep it as current as possible. I'm not sure who you are responding to when you make your true believer comment but I'm quite agnostic as to Koha and Evergreen and just generally interested in helping people see that both are extremely fully featured. So, the site was created to fulfill that purpose more than to point them away from either Koha or Evergreen. And, if you would like to help us correct any mistakes or add information that you feel is lacking, we'd love to have your help. Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group (707) 763-6869 // lori.a...@galecia.com Availability: http://doodle.com/loriayre lori.a...@galecia.comSpecializing in software solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Fri, Jul 4, 2014 at 5:27 AM, Steve Sowder sow...@andrews.edu wrote: For someone trying to make up their mind choosing between Evergreen and Koha the website would send them to Evergreen. Just because you are a Koha true believer (this is the Koha listserv!) doesn't mean that everyone else will choose Koha. There is nothing in the comparison to indicate version nor how old it it. The comparison should be correct, accurate, and up to date. my $0.02 Steve sow...@andrews.edu On 7/3/2014 4:39 PM, Nicole Engard wrote: I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will. Nicole ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Crontab - is that one tabs used to open beer cans?
+1 El jul 7, 2014 4:57 PM, Chris Cormack chr...@catalyst.net.nz escribió: Don't touch anything. Seriously. If you have a packaged install, it's all been done. Look in cron.d, cron.daily etc all the jobs have been set up. Chris On 8 July 2014 7:17:29 am NZST, Phillip Ponchot pponc...@live.com wrote: The old koha was installed as a tarball on the old server so I believe this makes it a source-based. The new koha was installed via a repository. apt-get install koha-common. I did find in /etc/cron.d a koha-common file. The contents of this file was: --- # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl - also there is a directory in /user/share/koha/bin/cronjobs - are these run by the koha program or do I have to schedule them in a crontab job? advance_notices.pl holds backup.sh import_webservice_batch.pl batch_anonymise.pl j2a.pl build_browser_and_cloud.pl longoverdue.pl cart_to_shelf.plMARC21_parse_test.pl check-url.pl overdue_notices.pl check-url-quick.pl printoverdues.sh cleanup_database.pl process_message_queue.pl cloud-kw.pl purge_suggestions.pl cloud-sample.conf rss CONFIGURE.gmail runreport.pl create_koc_db.plserialsUpdate.pl crontab.example services_throttle.pl delete_expired_opac_registrations.pl social_data delete_patrons.plstaticfines.pl delete_unverified_opac_registrations.pl thirdparty fines.pl update_totalissues.pl gather_print_notices.pl -- I just want to run automatically anything that needs to be done to keep koha up to date. Thanks Phillip From: mtomp...@hotmail.com To: pponc...@live.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? Date: Mon, 7 Jul 2014 14:00:19 -0400 Greetings, First, you still did not specify if you were doing a package installation or a source-based installation. Which are you doing? If a source-based installation, then your hacked up solution is passable, though not optimal. Second, let's reply to your points: There is a systems crontab which ubuntu warns not to change. You can create crontab jobs at the system level without modifying existing ones. Every file placed in the appropriate cron.* directory is its own crontab file. The crontab on the old server is sudo crotab -uroot -e where all the koha cronjobs are setup. This is a user crontab still. Was the old system a source-based installation or was it a packages based installation? If you are finding user crontabs, then it likely was a source-based installation. Why do you need to have the new system as a source-based install? A package-based installation sets up all the crontab jobs you need by default for you already. No crontab job tweaks required. Seriously, please consider a packages based installation: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages And thirdly and lastly, did you actually go looking for crontab jobs manually? Like the following done on a package installation of Koha that we are using in production. $ cd /etc/cron.d $ ls -la total 20 drwxr-xr-x 2 root root 4096 Feb 11 17:29 . drwxr-xr-x 98 root root 4096 Jul 7 17:39 .. -rw-r--r-- 1 root root 422 Nov 22 2013 koha-common -rw-r--r-- 1 root root 102 Jun 19 2012 .placeholder -rw-r--r-- 1 root root 396 Dec 16 2011 sysstat $ cat koha-common # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra
Re: [Koha] Crontab - is that one tabs used to open beer cans?
I've got the big picture now. I see where the koha crontab jobs are setup. Thanks so much for your help. Phillip From: mtomp...@hotmail.com To: koha@lists.katipo.co.nz Date: Mon, 7 Jul 2014 17:14:57 -0400 Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? Greetings, Chris Cormack wrote: Don't touch anything. Seriously. If you have a packaged install, it's all been done. Look in cron.d, cron.daily etc all the jobs have been set up. Yet another wonderful reason to not even be tinkering with crontab jobs. +1 for package installations. +1 for not having to touch crontab jobs. +1 for confirmation of this awesomeness. +2 cents to round to the nearest nickel, because pennies are out of circulation in Canada now. ;) GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Crontab - is that one tabs used to open beer cans?
Ok, I see where the jobs are. I didn't understand that there was a difference between a source install and a package install. In some of the 3.14 documentation there is a chapter on cronjobs and how to set them up. Now i understand that these particular documents must be mean for the source installs. Personally, I'm a little relieved that I don't have to build the cronjob for Koha. Thanks to everyone for the help. Hang in there, Phillip Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? From: chr...@catalyst.net.nz Date: Tue, 8 Jul 2014 07:56:30 +1200 To: pponc...@live.com; mtomp...@hotmail.com CC: koha@lists.katipo.co.nz Don't touch anything. Seriously. If you have a packaged install, it's all been done. Look in cron.d, cron.daily etc all the jobs have been set up. Chris On 8 July 2014 7:17:29 am NZST, Phillip Ponchot pponc...@live.com wrote: The old koha was installed as a tarball on the old server so I believe this makes it a source-based. The new koha was installed via a repository. apt-get install koha-common. I did find in /etc/cron.d a koha-common file. The contents of this file was: # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl also there is a directory in /user/share/koha/bin/cronjobs - are these run by the koha program or do I have to schedule them in a crontab job? advance_notices.pl holds backup.sh import_webservice_batch.pl batch_anonymise.pl j2a.pl build_browser_and_cloud.pl longoverdue.pl cart_to_shelf.plMARC21_parse_test.pl check-url.pl overdue_notices.pl check-url-quick.pl printoverdues.sh cleanup_database.pl process_message_queue.pl cloud-kw.pl purge_suggestions.pl cloud-sample.conf rss CONFIGURE.gmail runreport.pl create_koc_db.plserialsUpdate.pl crontab.example services_throttle.pl delete_expired_opac_registrations.pl social_data delete_patrons.plstaticfines.pl delete_unverified_opac_registrations.pl thirdparty fines.pl update_totalissues.pl gather_print_notices.pl I just want to run automatically anything that needs to be done to keep koha up to date. Thanks Phillip From: mtomp...@hotmail.com To: pponc...@live.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? Date: Mon, 7 Jul 2014 14:00:19 -0400 Greetings, First, you still did not specify if you were doing a package installation or a source-based installation. Which are you doing? If a source-based installation, then your hacked up solution is passable, though not optimal. Second, let's reply to your points: There is a syste ms crontab which ubuntu warns not to change. You can create crontab jobs at the system level without modifying existing ones. Every file placed in the appropriate cron.* directory is its own crontab file. The crontab on the old server is sudo crotab -uroot -e where all the koha cronjobs are setup. This is a user crontab still. Was the old system a source-based installation or was it a packages based installation? If you are finding user crontabs, then it likely was a source-based installation. Why do you need to have the new system as a source-based install? A package-based installation sets up all the crontab jobs you need by default for you already. No crontab job tweaks required. Seriously, please consider a packages base d installation: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages And thirdly and lastly, did you actually go looking for crontab jobs manually? Like the following done on a package installation of Koha that we are using in production. $ cd /etc/cron.d $ ls -la total 20 drwxr-xr-x 2 root root 4096 Feb 11 17:29 . drwxr-xr-x 98 root root 4096 Jul 7 17:39 .. -rw-r--r-- 1 root root 422 Nov 22 2013 koha-common -rw-r--r-- 1 root root 102 Jun 19 2012 .placeholder -rw-r--r-- 1 root root 396 Dec 16 2011 sysstat $ cat koha-common # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled)
Re: [Koha] Koha/Evergreen Comparison Site
FYI, the Features site (http://ils.foss4lib.org) includes over 1000 ILS features, the vast majority of which are functional in both Koha and Evergreen. Updates are current through nearly all of the version 3.14 new features (this will soon be reflected more clearly). Can you clarify for me which features are listed as NO which are actually YES in Koha now? I will correct those ASAP. The features database was generated from RFP's and RFI's published by libraries in the recent past, and supplemented with new features development from the past 18 months of Koha and Evergreen versions. Of course, the Features site cannot list every bit of functionality in the Koha software, but we hope its value lies in meeting the stated needs of libraries seeking a new ILS with the current capabilities of open source systems. As the person responsible for updates over the past 18 months I welcome additional documentation of new functions. Currently, I study the notes in Bugzilla and comb the release notes and documentation for explanations of new functionality, but I could definitely use additional information. The Bywater videos offer excellent depth--thank you Nicole Engard!--and I would love to see more. Respectfully, Diana Spaulding The Galecia Group On Thu, Jul 3, 2014 at 6:42 PM, Lori Bowen Ayre lori.a...@galecia.com wrote: Hi All, I'm sorry that the features listing is out-of-date but we will be bringing it up to speed very soon. As Nicole and Hugo mentioned, it is more about letting people know that the Koha and Evergreen product DO have all the features that people expect from the proprietary ILSs. I'd love to add Alma and Symphony, WMS, and Sierra, etc, to the list but sadly, that is way more of an undertaking than my company or Lyrasis can handle. So, by putting this product out there, we are at least taking some pressure off the service providers (e.g. ByWater, Equinox, Catalyst, PTFS, Libime???) who might not have the marketing departments that Innovative and SirsiDynix and OCLC have. It would be great to get a little help from the Koha community on this as it ultimately benefits everyone by enticing more people to move to Koha (and Evergreen). I understand your reluctance but I hope you'll see this resource as something desired to support Open Source, not hinder. If you'd like to contribute, let me know. In the meantime, we do expect to get it updated in the next couple of weeks or so. But feedback about features we're misrepresented or which need to be added are ALWAYS welcome! Lori =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group (707) 763-6869 // lori.a...@galecia.com Availability: http://doodle.com/loriayre lori.a...@galecia.comSpecializing in software solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Thu, Jul 3, 2014 at 1:39 PM, Nicole Engard neng...@gmail.com wrote: I'm with Hugo and Chris - in that it's not really a useful tool, but I worry that people will see it and say oh Koha (or Evergreen) can't do XYZ and so isn't as good as Proprietary System ABC. Just thought you should all know it's out there so you can educate people accordingly - I know I will. Nicole ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Crontab - is that one tabs used to open beer cans?
Thanks for sticking with me. Sometimes I can be a little dense. I see the koha jobs in cron.daily and realize based on the info that you've given me that I don't have to setup the cron jobs. I'm a little relieved that I don't - smile. Thanks everyone for your help. Thank you especially Tomas. Phillip Date: Mon, 7 Jul 2014 17:45:32 -0300 Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? From: tomasco...@gmail.com To: chr...@catalyst.net.nz CC: koha@lists.katipo.co.nz; pponc...@live.com; mtomp...@hotmail.com +1 El jul 7, 2014 4:57 PM, Chris Cormack chr...@catalyst.net.nz escribió: Don't touch anything. Seriously. If you have a packaged install, it's all been done. Look in cron.d, cron.daily etc all the jobs have been set up. Chris On 8 July 2014 7:17:29 am NZST, Phillip Ponchot pponc...@live.com wrote: The old koha was installed as a tarball on the old server so I believe this makes it a source-based. The new koha was installed via a repository. apt-get install koha-common. I did find in /etc/cron.d a koha-common file. The contents of this file was: --- # /etc/cron.d/koha-common # # Call koha-rebuild-zebra for each enabled Koha instance, to make sure the # Zebra indexes are up to date. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin */5 * * * * root test -x /usr/sbin/koha-rebuild-zebra koha-rebuild-zebra -q $(koha-list --enabled) */15 * * * * root koha-foreach --enabled --email /usr/share/koha/bin/cronjobs/process_message_queue.pl - also there is a directory in /user/share/koha/bin/cronjobs - are these run by the koha program or do I have to schedule them in a crontab job? advance_notices.pl holds backup.sh import_webservice_batch.pl batch_anonymise.pl j2a.pl build_browser_and_cloud.pl longoverdue.pl cart_to_shelf.plMARC21_parse_test.pl check-url.pl overdue_notices.pl check-url-quick.pl printoverdues.sh cleanup_database.pl process_message_queue.pl cloud-kw.pl purge_suggestions.pl cloud-sample.conf rss CONFIGURE.gmail runreport.pl create_koc_db.plserialsUpdate.pl crontab.example services_throttle.pl delete_expired_opac_registrations.pl social_data delete_patrons.plstaticfines.pl delete_unverified_opac_registrations.pl thirdparty fines.pl update_totalissues.pl gather_print_notices.pl -- I just want to run automatically anything that needs to be done to keep koha up to date. Thanks Phillip From: mtomp...@hotmail.com To: pponc...@live.com CC: koha@lists.katipo.co.nz Subject: Re: [Koha] Crontab - is that one tabs used to open beer cans? Date: Mon, 7 Jul 2014 14:00:19 -0400 Greetings, First, you still did not specify if you were doing a package installation or a source-based installation. Which are you doing? If a source-based installation, then your hacked up solution is passable, though not optimal. Second, let's reply to your points: There is a systems crontab which ubuntu warns not to change. You can create crontab jobs at the system level without modifying existing ones. Every file placed in the appropriate cron.* directory is its own crontab file. The crontab on the old server is sudo crotab -uroot -e where all the koha cronjobs are setup. This is a user crontab still. Was the old system a source-based installation or was it a packages based installation? If you are finding user crontabs, then it likely was a source-based installation. Why do you need to have the new system as a source-based install? A package-based installation sets up all the crontab jobs you need by default for you already. No crontab job tweaks required. Seriously, please consider a packages based installation: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages And thirdly and lastly, did you actually go looking for crontab jobs manually? Like the following done on a package installation of Koha that we are using in production. $ cd /etc/cron.d $ ls -la total 20 drwxr-xr-x 2 root
[Koha] How to migrate hindi language data
Respected Member, I want to Know how to convert hindi language data from excel to marc format(MRC) and migrate in KOHA. Regards, == Ramakant Senior Library Information Assistant Technical Division In-charge Digitization Unit P.K.Kelkar Library Indian Institute of Technology Kanpur- 16 Ph. 0512-2597223(O) Mo. +91 8090049089 E-mail:- ramak...@iitk.ac.in, ramakant_g...@yahoo.com == If you Salute your Duty, you no need to Salute Anybody, But if you pollute your Duty, You have to Salute Everybody - Kalam ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
