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

Koha and mod_perl
by Joshua Ferraro 20 Aug '05

20 Aug '05

Hi all, I've seen a few messages on the list in the past about running Koha on mod_perl. Would anyone who's actually doing it be willing to describe the process of setting it up? What distro are you running, what version of Apache and mod_perl (and Koha), did you need to make any modifications to any of the scripts or modules? Thanks, -- 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

2 2

Re: [Koha-devel] RSS Aggregator?
by Partha Mukhopadhyay 20 Aug '05

20 Aug '05

Hello Friends, Here is a request to koha developers. Is it possible to add a field in the memeber record where we can add picture of the memeber (in gif, jpg or png format)? If yes, can it be displayed on ..... 1. Circulation panel; 2. User login page; and 3. Member data updation page? This facility in koha will help better circulation management. Is GD Graphics Library is required for incorporation of such facility? Partha Mukhopadhyay Vidyasagar University, India -- India.com free e-mail - www.india.com. Check out our value-added Premium features, such as an extra 20MB for mail storage, POP3, e-mail forwarding, and ads-free mailboxes!

1 0

Improved document on kohadocs
by Stephen Hedges 18 Aug '05

18 Aug '05

An expanded version of the first chapter of the Koha Users Guide is now available at http://www.kohadocs.org/usersguide. This improved version includes a section on the Koha tools, information on the new system preferences, and better graphics. -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

1 0

Koha demos at Library Conferences
by lars＠rovaniemelainen.com 18 Aug '05

18 Aug '05

I'm wondering if anyone on the Koha team is considering setting up tables or demos for any of the library conferences? A lot of library directors and key personel attend, especially the big conferences, and would not otherwise hear a thing about Koha. Many directors seem to cultivate a single representative from a single vendor and then have them provide ALL their information about what is and isn't possible, how much it costs, etc. Attending a conference would help break that cycle and may almost certainly add to Koha development. These two are a sampling of some of the ones I'm guessing would be most accessible from NZ: 3rd International Evidence Based Librarianship Conference 16 - 19 Oct 2005 Brisbane, Queensland, Australia http://conferences.alia.org.au/ebl2005/index.html The 8th International Conference on Asian Digital Libraries ** 12 - 15 Dec Bangkok, Thailand http://www.icadl2005.ait.ac.th/ There are, however, many others coming up: World Library and Information Congress: 72nd IFLA General Conference and Council 20-24 August 2006, Seoul, Korea http://www.ifla.org/IV/ifla72/index.htm 8th International Beilefeld Conference: Academic Library and Information Services: New Paradigms for the Digital Age 7 - 9 Feb 2006 Beilefeld, Germany http://conference.ub.uni-bielefeld.de/2006/programme/ American Library Association (Midwinter Meeting), *** 20-25 Jan 2006 San Antonio, TX, USA ---------------------------------------------------------------- This mail sent through L-secure: http://www.l-secure.net/

3 2

RSS Aggregator?
by Joshua Ferraro 18 Aug '05

18 Aug '05

Here's a nice looking RSS aggregator: http://www.gregarius.net Might be just the thing for our new website. 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

2 1

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