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

Website / ID Meeting Notes
by Joshua Ferraro 18 Aug '05

18 Aug '05

Website / Interface Design Meeting Notes Full log at koha.org/irc present: indradg owen kados russ shaun thd Shaun demoed his page design: http://dev.shaunevans.co.uk/koha/kohaconcept.png discussed use of case study box Sourceforge Homepage will become Koha Sourceforge Homepage COMMUNITY LINKS will become QUICK LINKS Call for Content Writers content editing will be done by irma (spelling convention will be British English) thd will take FAQ and Features kados will take 'Koha Team', History, Support, Awards, Pay for Support russ will take shaun will take support/contributing Goal for submitting content and HTML coding is August 1st. The Programming Templates are coming along. Owen is committing to HEAD for now, we will see if programmers want to use them for rel_2_2 also after they are finished. Cheers, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

4 3

playing with the zebra on cvs head
by Paul POULAIN 13 Aug '05

13 Aug '05

(cc to zebra-koha ml, to show indexdata guys where things are) Hi koha fans, i'll leave tomorrow morning for 2 weeks, but before leaving, i have a gift for you : zebra is working in CVS head. I'll try to explain what I did & what does not work. In all this document, I consider that you have a working version of koha (cvs head) in directory KOHADIR 1- zebra SETTINGS =================== * download & compile zebra, following indexdata docs. * zebraidx must be in /usr/local/bin/zebraidx (hardcoded value in C4/Biblio.pm, modify it if you need) * /usr/local/share/idzebra/tab/ must contain default parameters for zebra (or change line 6 of zebra.cfg) * cd KOHADIR If you have an UNIMARC Koha : ln -s misc/zebra/unimarc zebra If you have a MARC21 Koha, you will have to : * either wait for joshua commits with a working marc21 config or * create your own (&commit it to CVS pls) the most important part is to enable ID indexing on biblionumber : in zebra.cfg : recordId: (bib1,Local-number) storeKeys:1 in .abs file : elm 090 Local-number - elm 090/? Local-number - elm 090/?/9 Local-number !:w (090$9 being the field mapped to biblio.biblionumber in Koha) what you MUST have at the end of this step is : * a directory KOHADIR/zebra, that is a symbolic link to your true zebra config file. * a directory KOHADIR/zebra/biblios, that will recieve biblios from koha * an empty zebra database. PLEASE don't create a true zebra directory & don't commit your symbolic link, you could delete my own unimarc setup ! Note that biblios directory must be writeable by apache user (don't panic about security issue, it will be useless once Perl/zoom is available) 2- Koha SETTINGS ================ * export KOHA_CONF & PERL5LIB as usual * cd KOHADIR * updater/updatedatabase => warning, may be long. Will do some changes in Koha DB (moving fields & rebuilding things) * marc_subfield_table, marc_word, marc_biblio and marc_blob tables are now useless but not removed for instance. You can rename them to be sure they won't be used (& see an error message if they are used somewhere) * misc/migration_tools/rebuild_zebra.pl => will create an entry in KOHADIR/zebra/biblios * cd KOHADIR/zebra * zebraidx update biblios => will add all biblios into zebra. * rm -f biblios/* => will delete all biblios once they are in zebra. * zebrasrv @:2100 (port 2100 is hardcoded in SearchMarc.pm for instance) must always be running, otherwise you won't be able to search anything ! 3- Play with your wonderful koha-zebra copy =========================================== * search an existing biblio. The search will work on title/author/isbn. Any other search will be done as keyword (anywhere) * modify this existing biblio. It should be modified in zebra as well (search it again, with the modified title, for example, should work) (Biblio.pm creates an iso2709 file in KOHADIR/zebra/biblios, launch zebraidx with a system(), and unlink the iso2709 file once it's done). * add a new biblio. It should appear in zebra. * add/modify items, they will be available in zebra as well (check through yaz-client to be sure) 4- what's next : ================ [PP] means i'll take care of it, but if someone else want, he can, of course ;-) 1- [PP] first, it's 2 weeks off for me. will be back on aug,29. (no web access where I go) 2- [PP] add support for deletion 3- (PP] re-introduce itemtype, that is no more in search result list (bug) 4- re-introduce "search ordered by" 5- [PP] improving -a lot- zebra unimarc settings, that are really basic 6- [PP] replace system() and Net::z3950 by the great Perl/zoom that indexdata will provide us soon 7- [PP and katipo] modify Biblio.pm to handle MARC=OFF as well as MARC=ON 8- fix some subs that are no more working atm, like FindDuplicate, getMARCnotes, getMARCsubjects... 9- fix other bugs that i haven't seen. 10- continue normalizing API, by using biblionumber & biblioitemnumber everywhere & moving some subs that should be in another place (i already removed some in SearchMarc.pm / Search.pm and Biblio.pm) 11- deeply modify the search API (SearchMarc.pm/cataloguesearch) 12- extend search to external z3950 servers (& improve admin/z3950 to be able to define z3950 servers for quick cataloguing and/or search) 13- modify z3950 client to get rid of Net::z3950 package, that can be replaced by . 14- introduce ranking search 5- questions : ============== for instance, item status are not stored in the marc record (being issued...) It means that when the user issues a catalogue query, if there is 20 resulting biblios, with 35 items, Koha has to check status of those 35 items. We can : * do nothing, the cpu needed is not so big. * embeed the item status. It means everytime the status is modified -issue/return/transfert-, the record has to be updated (cpu consumming too ?) * add a checkbox "show item status" on search screen (with orderby). disabled by default, would means "don't check status". -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

New document (for developers) on kohadocs
by Stephen Hedges 13 Aug '05

13 Aug '05

A new document for developers is available on http://www.kohadocs.org -- "Koha Coding Standards and Guidelines for Contributors." Look in section 5.1. -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

1 0

Re: [Koha-devel] Newer Versions of KOHA -- backing up
by Chris Cormack 12 Aug '05

12 Aug '05

Bruffey, Mark wrote: > Ah! It's Zebra, there's a post about it following my post here. Does > Zebra replace MySQL? Thanks, Mark > Ahh nope, Zebra complements mysql. Lots of stuff will be stored in mysql still. All the borrowers data, issues records, accounts data, etc. The bibliographical data will be stored in mysql and then files that zebra can index will be generated from that. So if the mysql database is backed up, you can recreate the zebra index from that backup if needed. At least thats my understanding, ill cc the devel list in to make sure I havent got the wrong end of the stick. Chris -- Chris Cormack Katipo Communications Programmer www.katipo.co.nz 027 4500 789

1 0

Returns and transfers
by Owen Leonard 12 Aug '05

12 Aug '05

Hi everyone, I'm interested in improving the management of items between branches, and there are a couple of things on my list for how to do this: 1. Display more information in returns about an item's homebranch/holdingbranch 2. Allow for easy updates of an item's homebranch via the Transfers process At NPL books move between branches very frequently, but almost always need to get back to their home branch after they're checked in. It would be useful to us if the returns process displayed an item's homebranch so that librarians can easily see if an item needs to be put in a cargo bag for transport. Along those lines, it would be good for there to be a simple process for changing an item's homebranch, just as there is now for changing an item's holdingbranch (via branchtransfers.pl). Perhaps branchtransfers.pl could be altered to allow for either holdingbranch updates /or/ homebranch updates. Or it could be a whole new page. Either one would work fine for us. I've been looking through the returns and branchtransfers script in the last couple days, and I see there's some kind of allowance for 'permanent' branches. I'm assuming this is a Katipo-specific thing? Maybe Chris could chime in and explain how that's supposed to work so that if the scripts get changed we won't break something. To my untrained eye it looks like returns are designed to work with a specific branch category 'PE,' which designates branches as permanent? I'd love to hear comments about all this. I'm curious how this sounds with regard to your own library procedures. thanks, -- Owen

1 0

Website Redev - Content Writers
by Russel Garlick 11 Aug '05

11 Aug '05

Hi All, Following up from the meeting yesterday. Content has been assigned as follows THD Features http://www.russandsarah.gen.nz/kohawebredev/content/features.html http://www.russandsarah.gen.nz/kohawebredev/content/opac.html http://www.russandsarah.gen.nz/kohawebredev/content/intranet.html http://www.russandsarah.gen.nz/kohawebredev/content/under-dev.html Faqs http://www.russandsarah.gen.nz/kohawebredev/content/faq.html KADOS About Koha http://www.russandsarah.gen.nz/kohawebredev/content/about-koha.html Koha Team http://www.russandsarah.gen.nz/kohawebredev/content/koha-team.html History http://www.russandsarah.gen.nz/kohawebredev/content/koha-history.html Support http://www.russandsarah.gen.nz/kohawebredev/content/support.html Pay for Support http://www.russandsarah.gen.nz/kohawebredev/content/pay-support.html Awards http://www.russandsarah.gen.nz/kohawebredev/content/awards.html SHAUN Homepage http://www.russandsarah.gen.nz/kohawebredev/content/index.html Contributing http://www.russandsarah.gen.nz/kohawebredev/content/contribute.html RUSSEL Showcase Case Studies Testimonials - I will be asking around for content to be used in this section. If anyone has a quote, testimonial or case study they would like to appear here, please let me know. For the testimonials/quotes - please supply a quote, the name, title (posistion) of the person, and the name and location of their library/organisation. Community SUBMITTING CONTENT We are striving for a go live of the site in the first week of September. In order to make this, please submit all content by 21 August. Please email the content to me. I am happy to accept text, html or open office documents from the content writers. Alternatively you can upload it somewhere and send me a link so I can download it. Once I have recieved the content I will use it to populate that pages on my site and then pass onto to Irma to edit. Once Irma has edited the content, Rachel will proof and approve. We can then set about plugging it into the CMS (once again I will be calling for volunteers for this) Cheers -- Russel Garlick Operations Manager Katipo Communications Ph: +64 4 934 1285 Fax: +64 4 934 1286 Mob: +64 27 537 1377 Skype: russelgarlick Web http://www.katipo.co.nz

1 0

new script in misc/migration_tools
by Paul POULAIN 11 Aug '05

11 Aug '05

I've added a rebuild_zebra script in misc/migration_tools directory. This script can be use to rebuild the zebra DB. It stores all koha MARC records in iso2709, in the bilbios directory. After that, you just have to "zebraidx update biblios" I tried on a 9900 DB, here are the results : [paul@bureau migration_tools]$ ./rebuild_zebra.pl -c 9900 9903 MARC record done in 37.9104120731354 seconds [paul@bureau zebra]$ zebraidx update biblios <snip> 18:31:24-11/08 zebraidx(20348) [log] Iterations . . . 144575 18:31:24-11/08 zebraidx(20348) [log] Distinct words . 39891 18:31:24-11/08 zebraidx(20348) [log] Updates. . . . . 46 18:31:24-11/08 zebraidx(20348) [log] Deletions. . . . 2 18:31:24-11/08 zebraidx(20348) [log] Insertions . . . 39843 18:31:24-11/08 zebraidx(20348) [log] zebra_register_close p=0x8104cf8 18:31:25-11/08 zebraidx(20348) [log] Records: 9887 i/u/d 9881/6/0 18:31:25-11/08 zebraidx(20348) [log] user/system: 531/145 18:31:25-11/08 zebraidx(20348) [log] zebra_stop 18:31:25-11/08 zebraidx(20348) [log] zebraidx times: 11.33 5.31 1.45 This script will be needed when migrating from 2.2 to 3.0. Now, let's go to add query tools in SearchMarc.pm. But that will be for tomorrow morning, as it's almost 7PM in France ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

[not so] long is the road to 3.0
by Paul POULAIN 11 Aug '05

11 Aug '05

My work on head advances faster than I expected... With todays commits, we can : * ADD and MODIFY BIBLIOS and ITEMS when MARC=ON only. * that updates the zebra database as well if you configured it correctly. See below how to configure the zebra for Koha. It's a 1st step, we will need more user-friendly tools later ! * if you query the zebrasrv with yaz-client or another z3950 client, you should get nice results. But still nothing if you search in Koha. * don't try to delete a biblio or an item, you would get a nice system crash ! HOW TO MAKE THE ZEBRA RUN : =========================== * go to koha cvs home directory * in misc/zebra there is a unimarc directory. I suggest that a marc21 libraries create a marc21 directory (& commit it to cvs to share ;-) ) * put your zebra.cfg files here & create your database. * from koha cvs home directory, ln -s misc/zebra/marc21 zebra (I mean create a symbolic link to YOUR zebra directory) * now, everytime you add/modify a biblio/item your zebra DB is updated correctly. NOTE : * this uses a system call in perl. CPU consumming, but we are waiting for indexdata Perl/zoom * deletion still not work * UNIMARC zebra config files are provided in misc/zebra/unimarc directory. The most important line being : in zebra.cfg : recordId: (bib1,Local-number) storeKeys:1 in .abs file : elm 090 Local-number - elm 090/? Local-number - elm 090/?/9 Local-number !:w (090$9 being the field mapped to biblio.biblionumber in Koha) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 1

stupid sourceforge rejecting commits as spam...
by Paul POULAIN 11 Aug '05

11 Aug '05

Hi, sf just rejected a mail generated by cvs after one of my commit. don't be surprised if you look at koha-cvs & your updated head if you find differences... the rejected mail was, of course, an important one for the move to 3.0 (of course, the commit worked, it's just the mail automatically made after by SF that has been rejected by SF. stupid SF...) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Newer Versions of KOHA -- backing up
by Bruffey, Mark 10 Aug '05

10 Aug '05

For the latest versions of KOHA, will I need capability to back up live SQL files, etc., for tape backups? Thanks, Mark L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264 mbruffey(a)centralseminary.edu <mailto:mbruffey@centralseminary.edu> Central Seminary www.centralseminary.edu <http://www.centralseminary.edu> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts <http://www.centralseminary.edu/wcts> *************************************** Have you experienced the good news? "Every one who calls on the name of the Lord will be saved!" [Romans 10:13] ***************************************

1 0