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

Updated Koha Manual
by Nicole Engard 08 May '09

08 May '09

Hi all, As you saw there is a new Koha site and I wanted to let you all know that the current Google Site version of the manual is not up to date. I will set up a redirect as soon as things are finalized, but for now - check out the new manual: http://new.koha.org/documentation My favorite feature is that I was able to break the FAQ out from 1 doc into several searchable FAQs. Please let me know of any feedback you have regarding the manual!! I also can't wait to get some help from some of you in editing the manual - and adding tutorials and such :) I'm not sure how it's all going to work, but I'd love to get it to work - I'll all for collaboration and bettering the manual and documentation in general. --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce(a)liblime.com AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/

1 0

SIP2 configuration in koha
by chirag purohit 08 May '09

08 May '09

Hello All, I am trying to configure SIP2 in koha and I followed the link: https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/A… I also able to start the sip2 server using the command given. I also verified this using grep command. I have created user kohaadmin with password smartant and given him all privileges,but when I tried to log as kohaadmin I got the following error. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri May 8 12:05:42 2009 from pyther-699f23ee.local chirag@debian:~$ cd $PERL5LIB/C4/SIP chirag@debian:~/koha/lib/C4/SIP$ perl -I./ ./SIPServer.pm ./SIPServer.xml >~/sip_log.out 2>~/sip_log.err & [1] 7983 chirag@debian:~/koha/lib/C4/SIP$ telnet localhost 8023 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. login: kohaadmin password: smartant Connection closed by foreign host. [1]+ Done perl -I./ ./SIPServer.pm ./SIPServer.xml >~/sip_log.out 2>~/sip_log.err Thanking you in advance. -- Purohit Chirag

2 1

RFC: relicense wiki.koha.org
by Galen Charlton 07 May '09

07 May '09

Hi, Content on the Koha wiki (http://wiki.koha.org/) is currently available under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported license (http://creativecommons.org/licenses/by-nc-sa/3.0/) MJ Ray has pointed out on #koha that this is a problem. I agree with him for the following reasons: * The non-commercial use clause prevents any commercial entity from reusing content from the wiki (with proper attribution) in training materials. * The Koha manual is licensed under the GPL, and a CC-BY-NC-SA license is not compatible, making it questionable whether content from the wiki can be incorporated into the manual. * Many edits on the wiki were made by people acting as an employee of a Koha support vendor or a paid consultant. * It is not clear that there was a conscious decision by the Koha project to use CC-BY-NC-SA - it may well be the case that this license was chosen by default or by accident when the wiki was migrated to DokuWiki. Consequently, I propose that we relicense the wiki under the Creative Commons Attribution-Share Alike 3.0 Unported license (http://creativecommons.org/licenses/by-sa/3.0/) As with the current license, this means that wiki content can be reused, but only with proper attribution and the requirement that derivative works be available under a compatible license. Relicensing would require the consent of those who have made significant edits to the wiki. I propose that we follow a process similar to Wikipedia's proposed relicensing (http://meta.wikimedia.org/wiki/Licensing_update) [1] The electorate will be the set of people meeting all of the following criteria: * have a registered account on wiki.koha.org * have created at least one page or made at least 5 edits by the end of the day on 5 May 2009 according to the wiki server's clock. * have a valid email address I will put together a list of people meeting those criteria by the end of the week and send them each of them an email to the address registered on the wiki. Anybody whose email bounces will not be considered part of the electorate unless they contact me. [2] The election will run next week during the 72 hours spanning 13 May to 15 May in the US Eastern time zone. The ballot will have three options: * Yes, I am in favor of this change * No, I am opposed to this change * I do not have an opinion on this change If more than 50% of the people who cast a vote either accept or reject the change, the vote will carry. If no majority is obtained, or if the majority of voters express no opinion, we'll go back to the drawing board and discuss this. I will use one of the DokuWiki voting plugins to run the vote. Comments on the substance of the proposal or the proposed voting procedure are welcome. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

3 3

Re: [Koha-devel] How to run two zebra servers at once in one computer for multiple databases?
by Michael Hafen 07 May '09

07 May '09

Sorry for the delay in reply. I'll check on differences between my two installations to see if I can find any more changes that need to be made. in the etc/koha-httpd.conf the SetEnv KOHA_CONF line needs to be changed on each VirtualHost. These tell the scripts where to look for the koha config file. the ErrorLog and TransferLog, might as well change those also. in etc/zebradb/zebra-authorities.cfg and zebra-biblios.cfg lockDir, register, shadow, setTmpDir, and keyTmpDir should be changed in etc/zebradb/zebra-authorities-dom.cfg the same lines as in zebra-authorities.cfg should be changed IF you have seperate directories for the two sites C4 modules then you will want to change lib/C4/Context.pm. There's one line there, INSTALLED_CONFIG_FNAME, that points to the koha_conf.xml if the environment doesn't have KOHA_CONF. Those changes to the zebra config's will mean you also have to change book-conf.xml. You will have to make 'book' specific copies of those files and point book-conf.xml at them. in the '<server ...' section there's a '<config>...' statement. Those lines will need to be changed too. See if that helps. Good luck. On Sat, 2009-05-02 at 16:35 +0000, ashik rajbhandari wrote: > Dear Sir, > > I tried to follow your procedures, but it is still indexing records > from firstly created database i.e. "Koha", not from second database > "book". Can you please help me out to run two zebra servers > simultaeneously for two different databases by providing me step by > step procedures in detail to change the directories for biblioserver > and authorityserver zebra and also to change the lines for > koha-zebra-ctl.sh / book-zebra-ctl.sh, koha-conf.xml / book-conf.xml > with detailed examples. Looking forward for your kind cooperation. > > Thanking you, > > Ashik Rajbhandari > Nepal > > > Subject: RE: [Koha-devel] How to run two zebra servers at once in > one computer for multiple databases? > > From: mdhafen(a)tech.washk12.org > > To: theashik(a)hotmail.com > > CC: koha-devel(a)lists.koha.org > > Date: Wed, 29 Apr 2009 11:27:40 -0600 > > > > Here's what I see in my koha-conf.xml. Also, Joe's reply on list is > > necessary to follow. > > > > The two '<listen ' statements need to have different directories for > the > > sockets. These are how zebra communicates with other applications > > ( like Koha ). > > > > Next I see is the definition of the 'biblioserver': > > <server id="biblioserver" listenref="biblioserver"> > > <directory> > > > > The directory will be where zebra puts most of it's files, that > database > > ones. This will need to be different for the different servers. > > > > Same goes for the "authorityserver" definition and it's directory. > > > > In addition to Joe's advice on the koha-zebra-ctl.sh file, you will > want > > to change the RUNDIR and LOCKDIR values. > > > > Good luck. > > > > On Wed, 2009-04-29 at 17:10 +0000, ashik rajbhandari wrote: > > > Dear Sir, > > > > > > Thanks for the reply. May I know in detail how i can point zebra > at a > > > different directory to store it's files. Looking forward for your > kind > > > cooperation. > > > > > > with regards, > > > Ashik Rajbhandari > > > > > > > Subject: Re: [Koha-devel] How to run two zebra servers at once > in > > > one computer for multiple databases? > > > > From: mdhafen(a)tech.washk12.org > > > > To: theashik(a)hotmail.com > > > > CC: koha-devel(a)lists.koha.org > > > > Date: Wed, 29 Apr 2009 10:55:26 -0600 > > > > > > > > It is possible to run two zebra servers on the same computer. I > have > > > > this sort of setup. It will probably mean changing some values > in > > > > book-conf.xml to point zebra at a different directory to store > it's > > > > files. > > > > > > > > On Wed, 2009-04-29 at 16:12 +0000, ashik rajbhandari wrote: > > > > > Dear Sir/Madam, > > > > > > > > > > I have created two databases namely koha and book in mysql for > two > > > > > different libraries with two different ip addresses for each. > > > Also, i > > > > > have created xml and conf files namely koha-httpd.conf, > > > koha-conf.xml > > > > > and book-httpd.conf, book-conf.xml files for each databases. > Zebra > > > > > server is also running well and i can index records from both > > > database > > > > > as well. But the problem is: when i try to index the records > of > > > > > database book only, it shows the indexed records from database > > > koha > > > > > also. Finally, I have studied the problem and i found that > when i > > > run > > > > > zebra server, it exports records from both databases, so why > even > > > i > > > > > try to index a record from one database it indexes from the > other > > > one > > > > > as well. The zebra server keeps the records of both the > databases > > > > > combinely in the database called biblios of zebra. What i want > is > > > > > just to index the records of one database from its library > only. > > > Is it > > > > > possible to give different port number to different database > > > biblios > > > > > of zebra such that every database i create will have different > > > port > > > > > number for biblios database of zebra server with different ip > > > address. > > > > > Also, is there any possibility to run two zebra servers at the > > > same > > > > > time for two different databases with different port addresses > in > > > the > > > > > same computer. > > > > > > > > > > Please help me!! > > > > > > > > > > Thank you, > > > > > > > > > > with regards, > > > > > > > > > > Ashik Rajbhandari > > > > > Kathmandu > > > > > > > > > > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > check out the rest of the Windows Live™. More than mail– > Windows > > > Live™ > > > > > goes way beyond your inbox. More than messages > > > > > _______________________________________________ > > > > > Koha-devel mailing list > > > > > Koha-devel(a)lists.koha.org > > > > > http://lists.koha.org/mailman/listinfo/koha-devel > > > > -- > > > > Michael Hafen > > > > Systems Analyst and Programmer > > > > Washington County School District > > > > Utah, USA > > > > > > > > for Koha checkout > > > > http://development.washk12.org/gitweb/ > > > > or > > > > git://development.washk12.org/koha > > > > > > > > > > > > > > ______________________________________________________________________ > > > See all the ways you can stay connected to friends and family > > -- > > Michael Hafen > > Systems Analyst and Programmer > > Washington County School District > > Utah, USA > > > > for Koha checkout > > http://development.washk12.org/gitweb/ > > or > > git://development.washk12.org/koha > > > > > ______________________________________________________________________ > See all the ways you can stay connected to friends and family -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha

1 0

testing stable version
by LAURENT Henri-Damien 07 May '09

07 May '09

Hi I am glad to announce that work for stable version 3.0.2 is well advanced. You can test it on koha-maintenance project see http://git.koha.org/cgi-bin/gitweb.cgi?p=koha-maintenance.git;a=summary for the code. How can I test it ? if you have a dev version : git remote add maintenance git://git.koha.org/pub/scm/koha-maintenance.git git fetch maintenance git branch --track testing_3.0.2 remotes/maintenance/master git checkout testing_3.0.2 for those who are using HEAD already, either your version is 3.01.00.30 and you have nothing to do OR your version is before, and you may have to fix your kohaversion in your database to set it to 3.00.01.00 so that updatedatabase can update your database. You may have some duplicate warnings for all the transformations which has already been made. then login to intranet and updatedatabase will occur. And test and file any bug to me personnaly. What IS NOT in that version branchtransfer limits, holding queues and all the enhanced contents Librarything and babelTheque. I know it is a pity. And I am sorry about that. But I had told that there would be no new features, bug fix only for this one. And there are bug fixes. Plenty of them. (around 280 patches) Nevertheless, galen and I will be working on a reconciliation version that will provide you with all the best of stable and HEAD version as soon as this version is released. And we should be able to get it out for the end of June. About translations, a quick update on french version showed 86 untranslated strings, 286 fuzzy. So hopefully, it should not be too much of a hassle. I leave it up to Chris to update translations on pootle for that and send a go to translators. -- Henri-Damien LAURENT Release Maintainer 3.0.x

2 1

Re: [Koha-devel] [Koha] Query re set up of Koha catalogue
by gsl 07 May '09

07 May '09

Check out DSpace - http://www.dspace.org/ I am getting ready to evaluate it for a digital archive, and if you look at some web sites of the many users listed you'll see lots of examples like what you are asking about. Greg Lawson Network Administrator Rolling Hills Consolidated Library 1912 N. Belt Highway St. Joseph, MO 64506 ---------------- ----- Original Message ----- From: "Sue Brockway" <library(a)achsensw.org.au> To: koha(a)lists.katipo.co.nz Sent: Wednesday, May 6, 2009 11:05:15 PM GMT -06:00 US/Canada Central Subject: [Koha] Query re set up of Koha catalogue Hi there I am looking at moving to Koha LMS from Athena but I have a query. My catalogue is mainly indexed journal articles and web reports with only a few books. The Koha demonstrations site seems to have only book catalogues. Does anyone know of a catalogue similar to mine or has anyone set up a similar catalogue? I would welcome any suggestions. Regards Sue Brockway Librarian ACHSE NSW Health Planning and Management Library PO Box 341 NORTH RYDE NSW 1670 Ph: (02) 9805 0125 Fx: (02) 9889 3099 Email: library(a)achsensw.org.au sbrockwa(a)nsccahs.health.nsw.gov.au _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Next #koha general meeting - 3 June 2009
by Galen Charlton 07 May '09

07 May '09

Hi, Thanks to everybody who participated in the IRC meeting yesterday. The log of the meeting can be found at http://tinyurl.com/cysrwr, which points to a search of the of #koha log at http://koha.org/cgi-bin/logs.pl. I would like to hold the next general IRC meeting on 3 June 2009 at 10:00 UTC+0. The agenda currently has the following items: 1. Update on 3.2 2. Update on 3.0.x 3. Follow-up on actions from the 6 May 2009 IRC meeting. To propose additional items for the agenda, please editing the wiki page for this meeting (http://wiki.koha.org/doku.php?id=meetingnotes09jun3) or respond by email. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

For #koha meeting - smaller bugs database changes
by Galen Charlton 06 May '09

06 May '09

Hi, A couple other ideas that came from KohaCon: * creating a new product for bugs/requests related to koha.org websites and moving existing website components out of the product for Koha itself. PRO: shortens the component dropdowns CON: adds another page and click when entering a new bug * archiving or merging bugs for versions of Koha before 2.2.9 (or perhaps 2.2.x) PRO: shortens the version dropdown CON: truncates history Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

For #koha meeting - bugs database policies - enhancements and cosponsorship
by Galen Charlton 06 May '09

06 May '09

Hi, Apologies for the delay sending this out. One of the items discussed at KohaCon was a desire by interested parties to have a global list of proposed and active Koha development projects. The purpose of this list would be not only to let people know what new features may be coming down the pike, but to give interested users and funding agencies a way to coordinate the funding of such work. The general outcome of the KohaCon session was a suggestion that the Koha bugs database (bugs.koha.org) be used for this purpose. Specific changes that might support that include: * turning on bug voting * encouraging all active developers and vendors to create bugs for all prospective enhancement projects, supplementing the RFCs distributed via email and the wiki * adding a custom field, status, or tagging convention to Bugzilla to let interested parties identify projects that are seeking sponsorship. * adding some canned reports to the bugzilla home page to identify sponsored projects. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Reminder: Koha project IRC meeting
by MJ Ray 06 May '09

06 May '09

This is a reminder of a general meeting on the #koha IRC channel on Wednesday, 6 May 2009 at 19:00 UTC with a nominal finish time of 21:00. To convert to your timezone, try date -d @1241636400 Will include Koha 3.2/tip status and timeline, Koha 3.0.x status, Koha bugs database, KohaCon 2009 report. The full agenda is at http://wiki.koha.org/doku.php?id=meetingnotes09apr07 Connection details are shown at http://wiki.koha.org/doku.php?id=start#irc but are basically irc://irc.katipo.co.nz:6667/#koha Hope to see you there, -- MJ Ray (slef). LMS developer and supporter for a small, friendly worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237

1 0