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

Manual Status Update....
by Nicholas Rosasco 11 Jun '02

11 Jun '02

http://www.saas.nsw.edu.au/wiki/index.php?page=WishlistWorkspace Operator/Librarian Manual (HLT folks :) ) Rework Hardware info into IT Staff Section (Nick) Welcome to Koha msg (Pat) Pate -- paste below?(on Wiki) Configuration Case Studies (Nick, Steve/Chris/Si?) minifaq -> faq section (Nick) (This is cut and paste... no big deal) The above is the list of remaining items I'd like/need for the manual. Chris, Steve, _any and all of you_ running Koha in production, :) I'd like a "snapshot" of your current configurations, and thoughts/comments on what works well.... Specifically Hardware (Server) -- Processor/Memory/etc etc Supporting equipment for Network What is used in library (checkout, etc desks) and patron stations Link to catalog Support hardware (backups?, scanners for barcodes) Size of library & branches (what links branches to catalog, or is there a local catalog at each branch) How you deal with book mobiles, etc. Any other commentary you might have on supporting Koha? Nick

1 0

pm structure : Acquisition.pm modifications
by paul POULAIN 11 Jun '02

11 Jun '02

the Acquisition.pm (aka : Catalogue.pm for MARC version) contains too much subs imho. It's hard to read, and not always very coherent : sub addwebsite { sub basket { sub bookfundbreakdown { sub bookfunds { sub bookseller { sub branches { sub breakdown { sub curconvert { sub deletebiblioitem { sub deletewebsite { sub delorder { sub findall { sub getallorders { sub getbiblio { sub getbiblioitem { sub getbiblioitembybiblionumber { sub getcurrencies { sub getcurrency { sub getitemsbybiblioitem { sub getitemtypes { sub getorders { sub getrecorders { sub getsingleorder { sub insertsup { sub invoice { sub isbnsearch { sub modaddauthor { sub modbibitem { sub modbiblio { sub moditem { sub modnote { sub modorder { sub modsubject { sub modsubtitle { sub newbasket { sub newbiblio { sub newbiblioitem { sub newitems { sub neworder { sub newordernum { sub newsubject { sub newsubtitle { sub ordersearch { sub receiveorder { sub updatecurrencies { sub updatesup { sub updatewebsite { sub websitesearch { It contains sub used to administer biblios (addBiblio, addBiblioitem, addItem, modBiblio...) and sub used to administer loans and orders. I propose to divide the script in 2 differents ones. the first would be Biblio.pm (used only for biblio management : biblio/biblioitems/items/additionalauthor/subtitle tables), the second would remain Acquisition.pm (Catalogue.pm for MARC) Is there someone against this idea ? -- Paul

3 4

Bug to think about when working on the MARC database
by Chris Cormack 11 Jun '02

11 Jun '02

Hi all Currently there is a bug/feature in koha when it comes to searching for titles that have a ' in them. For example on http://intradev.katipo.co.nz/catalogue/ Title search for asta's Finds asta's book. Which is fine... searching for astas finds nothing. The HLT librarians and suspect most librarians would like the a title search for astas to find asta's book. An idea I had was to have another field in the biblio table, called search title, which has the ' and - , plus stopwords such as and, the etc removed. This is the field searched . Then I thought we might not want to restrict this to just the title, we probably want it for author, and subtitle etc. So I was thinking of having a separate table, that we used for searching, which was keyed by biblionumber back to the biblio table and had entrys like biblionumber,entry,type where type = author, or subtitle or title etc. Does this fit with the work being done with MARC ? are there better ways to do this? Chris -- Chris Cormack chris(a)katipo.co.nz Programmer 025 500 579 Katipo Communications www.katipo.co.nz

2 1

Re: [PERL4LIB] MARC::Record addfields and field order
by Pat Eyler 10 Jun '02

10 Jun '02

On Mon, 10 Jun 2002, Ron Davies wrote: > Andy, > > I agree with Alan, you would ideally have two (or maybe three) options. > > 1) To add the field to the end of the block. > If I am adding a 3xx field then it should be written to the record so > it is the last field in the 3xx block, i.e. it follows the last field > with a tag beginning with 3. IMHO, this should really be the default > behaviour for add_fields(). Adding fields to the end of the record isn't > really MARC, though I am sure there are dozens (hundreds?) of > implementations that don't care. > > 2) To add the field to a particular position > Here it could be before a specified field tag and occurrence number, > or after a specific field tag and occurrence number.. but both options > would be even better. ;-) > > While you can certainly get the information from the fields(tagspec) > method, it might be nice to have a convenience method that would return > the number of occurrences of a specific tag as well, and which you could > then just plug back into the methods described in 2) above. > > Sorry about mentioning the w*rk*r**nd word. I'm implementing a new ILS > system to a tight schedule and I didn't want to impose my little > problems on the rest of you. Also I hate to disappoint, but we're only > using plain old vanilla MARC21. No Swiss chocolate at all. Ron, As you're working on an ILS system in Perl, I thought I'd ask you about your experience with Koha. If you haven't looked at us, please do <www.koha.org> and <http://www.saas.nsw.edu.au/wiki/index.php?page=KohaProject> or come talk with us on #koha at <irc.katipo.co.nz>. If you have looked at koha and decided it didn't meet you needs, what was lacking? We're currently in the process of a mjor development push, and you may find that it is easier for you to get your ILS by joining forces with us. If you don't want to go that far, you may still find that cooperating on some tasks will lead to a better solution for you. thanks, -pate Pat Eyler > > Ron >

1 0

more publicity
by Pat Eyler 10 Jun '02

10 Jun '02

(Georg Greve, the author of Brave GNU World, is interested in writing about Koha. He's asked that we fill out an information page. I've started working on it, but would appreciate feedback from any/all of you on my answers.) * What is it? Koha is a system for managing libraries (the kind with books in them). It provides a card catalog like interface (OPAC), with many forms of searching. It also provides managment tools for librarians, handling issues like: acquisitions, circulation, and patron information. * Who would use it? Koha is an appropriate solution for small to mid-sized libraries now (including home or office libraries should people so desire), and work is being done to allow it to scale up to large libraries in the very near future (state or national libraries). * Why would they use it instead of similar projects? * (Programming) language used in this project? Koha is written in Perl. * Special features/strengths? ***Someone up to writing a blurb here?*** * Special problems? Koha is in an active development cycle, pending changes may require DB modifications. Koha currently lacks a novice friendly installation tool. The documentation is also lacking right now. All of these issues are known, and work is being done to mitigate them. * Who is working on it? Koha is being actively developed by an interantional team. Pat Eyler is the current project leader, Chris Cormack is the release manager for 1.2, and Paul Poulain is the release manager for 1.4. * History of the project? ***Katipans, can you help out here*** * Plans for the close and distant future? We're planning on releasing 1.2.0 this week, with additional 1.2 series releases occuring over the next couple of months. In the fall we're going to release 1.4.0, which will include our internal use of MARC as well as additional improvements. For more details, please feel free to look at <pate.eylerfamily.org/geek/Koha.html>. * Do you need help? If so: of what kind? We're looking for Perl programmers, web designers, and documentation writers. Particular skills we need are: i18n/l10n, HTML::Template, MySQL/PostgreSQL, and a working knowledge of common library procedures and technologies (MARC, Z39.50, and the like). * Interesting/fun stories that might juice up the story? ***Anyone have stories that could go here?*** * Website/FTP addresses? http://www.koha.org * License?! GPL * Standard documents to read in this context? Please take a look at the koha website (esp. the FAQ) for information about Koha. <www.oss4lib.org> is a good place to learn more about Free Software in libraries. * Anything you would like to see mentioned? ***Thoughts, ideas, ???*** * Answer to a question I forgot? ***What's the favorite snack of koha developers? Or, is there something else that would be more worthwhile to put here? ;) NOTE: Everything you want me to read should be sent to me by mail because very often I will take my mail with me and read it where I don't have access to the net. > > Regards, > Georg > >

1 0

Spam on the list
by Chris Cormack 10 Jun '02

10 Jun '02

Ahh what a pain, First piece of spam on the list. I guess I'll need to make the list members only post now. Do we have any big objections to that? Chris -- Chris Cormack chris(a)katipo.co.nz Programmer 025 500 579 Katipo Communications www.katipo.co.nz

2 1

ADV: Direct Email Blaster, email addresses extractor,maillist verify, maillist manager ...........
by targetemailextractor＠btamail.net.cn 09 Jun '02

09 Jun '02

1 0

koha website - help (or not :-)
by Rachel Hamilton-Williams 09 Jun '02

09 Jun '02

Hi http://keadoc-edit.katipo.co.nz Is some help documents we have on how to use Kea to edit the Koha site, you'll need the same username and password to check it out. http://keadoc-edit.katipo.co.nz There have been some changes since these were done. and I'm sorry I don't have an up dated version (changes done in weekend), but they should show you the general idea. Cheers Rachel _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications WEBMISTRESS ph 021 389 128 or +64 04 934 1285 mailto:rachel@katipo.co.nz PO Box 12487, Wellington http://www.katipo.co.nz New Zealand Koha Open Source Library System http://www.koha.org

1 0

New Koha website
by Rachel Hamilton-Williams 09 Jun '02

09 Jun '02

Hi - We have a new Koha website in development, and have got to the "need proper content" stage, and was wondering who could help. We've got it in a content management system so you'll need this username and password to take a look at it http://koha-edit.katipo.co.nz/ username koha-dev(a)koha.org password: woomonoo Pat and Nick I've taken the liberty of assuming you won't mind putting in some text so have made you individual usernames and passwords to be able to edit the content yourselves, and I'll e-mail them off list. But if others would like to have a bash then the more the merrier. Cheers Rachel _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications WEBMISTRESS ph 021 389 128 or +64 04 934 1285 mailto:rachel@katipo.co.nz PO Box 12487, Wellington http://www.katipo.co.nz New Zealand Koha Open Source Library System http://www.koha.org

1 0

New 1.2.0 Tarball
by Chris Cormack 09 Jun '02

09 Jun '02

Ok I have modified the Changelog and the INSTALL file, added all of allans clean ups and tarred up what a release candidate 2 for 1.2.0 Its sitting at http://developer.koha.org/koha-1.2.0-rc2.tar.gz I think what we are still missing before we release it to the world is some update docs. And to finish the installer Chris -- Chris Cormack chris(a)katipo.co.nz Programmer 025 500 579 Katipo Communications www.katipo.co.nz

3 5