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

Koha Favicon
by Russel Garlick 28 Sep '04

28 Sep '04

Hi I have made and added a Favicon to the Koha.org website. Kinda nice as it shows up in your bookmarks and stuff. If you want to grab it, it is here - http://www.koha.org/favicon.ico Cheers -- Russel Garlick Operations Manager Katipo Communications Ph 04 934 1285 Mob 027 537 1377 Web www.katipo.co.nz

1 0

OLC Annual Conference Docs
by Joshua Ferraro 28 Sep '04

28 Sep '04

Hi everyone, I've finally finished my conference handout and Koha presentation slides/notes for the OLC conference on Wednesday (http://http://www.olc.org/ann_conf.asp) and they are available on my website: Slides: http://kados.org/LibraryScience/presentations/OLC2004/koha.html (looks best in Mozilla; http://mozilla.org) Notes: http://kados.org/LibraryScience/presentations/OLC2004/koha-notes.html Handout: http://kados.org/LibraryScience/presentations/OLC2004/koha_at_a_glance.pdf (there's an html version too: http://kados.org/LibraryScience/presentations/OLC2004/koha_at_a_glance.html) There'a also a Freemind mindmap that basically contains the same general information as the handout ... but in a mindmap format: http://kados.org/LibraryScience/koha.mm http://kados.org/LibraryScience/koha.mm.html (if you don't have Freemind you can use your browser--or download http://sourceforge.net/projects/freemind) I've also put together a static Koha resources page with a few more resources listed than on the handout (due to space constraints) that I plan to point folks to for further info (since the official one isn't ready yet): http://kados.org/LibraryScience/koha.html There's still one day before the conference so if anyone has any suggestions for improving anything let me know--if you know of any resources I've not listed please drop me a note. And feel free to use and modify anything as it's all CC licensed (http://creativecommons.org/licenses/by-nc-sa/1.0/) I'm going to try to videotape the Koha presentation, our Linux Installfest and our Kohafest ... so hopefully that'll be forthcoming too. Finally, if I have time I'll spruce up the docs I've written and get them out later today ... we'll see how that goes. Joshua Ferraro

2 2

Re: [Koha] Double _items_ tags, Was: More questions for migrating to koha
by Paul POULAIN 27 Sep '04

27 Sep '04

Dana Huff a écrit : > Umm...actually the script you sent me still has the error. Here is the > corrected script with comments around the change. Dana, you're the best ;-) In fact, I use a specific bulkmarcimport when migrating french libraries. It does some specific stuff for a given library (like cleaning the XXX field, moving the YYY field, checking something...) I've fixed this bug some months ago, but I realise I never fixed the official CVS bulkmarcimport !!! I'll fix it ASAP. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Moving to Arch?
by MJ Ray 26 Sep '04

26 Sep '04

In yesterday's IRC, "CVS and Arch" was one of the last things discussed and some of the developers had to be in other places by then, so I agreed to summarise to the list and start discussion here. Please wade in with comments or questions as you see fit. Here we go! Introduction: I introduced GNU Arch http://www.gnuarch.org/ which solved the problems I had getting 2.0 under control and making tarballs from it. The move mostly consisted from making a tarball from CVS, unpacking it and then adding the files to an Archive. That's what you can get from my development page at http://www.mjr.dsl.pipex.com/ Anyone can make their own copy of the koha2 archive and publish it if they have a public file space (web, ftp or sftp for sure). That works for mirrors and for development branches. So, new developers have full revision control easily, by default, rather than needing hacks or write access to the release source tree. A release manager can merge their changes into the release tree with a simple command. Apart from merging, all operations happen on your own file space, which eliminates the wait for a central server to answer that often holds me back with CVS. Suggestion and tasks: I suggest trying to move to arch for 2.4 development if we can get it working for current developers, because it should make the lives of the release managers and new developers a lot easier. I've offered to answer questions and improve my tutorial until it's good enough. Some commented about having large amounts of CVS experience, but there didn't really any great love for CVS, more a feeling of "better the devil we know". The sticking points are likely to be users of GUI interfaces and Microsoft Windows, so I'd be very happy about offers to help with those. No other public archives for 2.0 were posted, which I think is a shame, but I guess 2.2 has all the appeal for developers now. A couple of people mentioned that they would like 2.0 commit messages to koha-cvs, so I'll try to set that up. There was a suggestion of compiling a list of benefits and drawbacks of each system, but I think that's probably already covered by http://wiki.gnuarch.org/moin.cgi/SubVersionAndCvsComparison or could be (it's a wiki). Finally, what would happen to the CVS? I'd leave it as a historical record, with some clear marking that development has moved on. You can transfer some of the history to Arch, but it's an attempt to reconstruct information that isn't really kept by CVS, so it seems more trouble than its worth. -- MJR/slef My Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ http://www.thewalks.co.uk stand 13,Lynn Carnival,12 Sep

5 12

Re: [Koha-devel] Moving to Arch?
by Owen Leonard 24 Sep '04

24 Sep '04

> Yes, arch basically stores the repo as a tar.gz of sources > and a tar.gz of patchfiles and some instructions; along > with that goes some metadata like the email-style log > file. Does that mean you can't do an update on an individual file? Thanks for bearing with me, I haven't had a chance to read any of the docs yet. -- Owen

4 4

Re: [Koha-devel] Moving to Arch?
by Owen Leonard 23 Sep '04

23 Sep '04

> > So does this mean that I can't merge back into the main > > branch ... that you > > have do do that? In CVS anyone with devel privs could > > commit to the main repo ... or am I mising something? > > Either the RM or their automaton will need to do the merge. > This is a deliberate model change from CVS which both allows > more people to do more development tasks without waiting for > approval, and allows the RM to say "show me the code" before > accepting it into the final release tree, if they want. It sounds like this is quite a shift of power, if I understand correctly, from a group of trusted developers to a single director who chooses what goes in and what doesn't. Do I understand correctly? Have we had problems in the past that will be alleviated by this shift of power? -- Owen

3 2

Re: [Fwd: Re: [Koha] Koha Documentation Project]
by Joshua Ferraro 23 Sep '04

23 Sep '04

I missed the Koha IRC meeting due to a really unfortunate miscalculation of 1900 GMT, so I didn't get a chance to chime in on the documentation discussion... > The original manual covered Sysadmins (mainly install, when parameters > were much simpler) and staff, and developers (we had a handy chunk of > why/how-stuff-is-done info -- some architectural info for > presentation/explanation wouldn't hurt either -- never occured to me until > recently how hard it was to explain some of the webserver/perl/db > potential issues etc until I looked over some of the more typical > questions). Here's the current index of the sysadmin guide that I've been working on: (I'm hoping for feedback ... so if you see something you don't like or you don't see something that should be included let me know) Koha Systems Administrator Guide Introduction Further Reading and Resources Part I: Installation and Migration Introduction hardware software 1: Installing Koha on Debian (jferraro) 2: Installing Koha on Redhat AS (shedges) 3: Installing Koha on Fedora (jferraro) 4: Migrating to Koha (shedges) 5: Customizing Koha's Template System (oleonard) Part II: Maintenance and Troubleshooting 6: Updating Koha setting up a testing environment(jferraro) setting up CVS symlinks(jferraro) tracking arch (mjr) 7: Backups (jferraro) backing up and restoring the database role of replication as backup backing up and restoring the filesystem 8: Optimization (jferraro) optimizing MySQL load balancing with replication 9: Troubleshooting (jferraro) Koha's error reporting database corruption worst-case scenario: utilizing the statistics table Part III: Participating in the Koha Community 10: Communicating with the developers(jferraro) mailing lists IRC Wiki 11: Reporting Bugs (jferraro) 12: Submitting Code (jferraro) 13: Koha Translating (??) Part IV: Introduction to Libraries for Sysadmins 14: haven't given this much thought but we need a section on MARC. Appendix: Installing the Z3950 Server (jferraro) Cleaning up the issues data (shedges) Renewals (shedges) Reserves (shedges) Handling Overdue Items (shedges) MJ suggested part IV, "introduction to libraries for sysadmins" which would be a great addition but we need someone to write it ... So the initial draft of this document is slated to be released on Monday or Tuesday of next week (in time for OLC annual) but not all the above chapters will be finished by then :-). > Also needed, and always a problem, is work re the FAQ and troubleshooting > info -- come to think of it, some newer hardware recommendations wouldn't > be amiss (CMSD I think gave us their original specs). Thoughts? I've slid a hardware section into the intro of Part I ... great idea! > I'm thinking MARC and associated questions will need special handling. > Possibly a "Cataloging In Brief" for the MARC-uncomfy... also, some wise > words on tags wouldn't kill us. That'd fit nicely into the "introduction to libraries for sysadmins" part ... anyone want to write it? > Ditto something on translating. If someone writes it that'd be a great addition too (ch 13 in the above scheme). > In the past (formal) docs have been in DocBook SGML/XML.... advantage here > is that it permits easy multi-format output, and is relatively easy to > translate the raw XML for other languages (we successfully handed the file > over to people with them returning translations of stuff between tags). > And gives a nice, clean look and feel. Opinions? I've never used DocBook but from what I've heard it's a good medium ... I'll check it out this weekend if I have time. I've been thinking that it might be a good idea to use a Wiki for at least the initial editing of the document (so that any of us can make changes/additions to the content) and then when we're all satisfied we can move the text to more universal formats (maybe through Docbook) ... how does that sound? Flames, comments, suggestions: all welcome. Thanks, Joshua

2 1

plugins for editor and collection (for Koha-doc)
by Paul POULAIN 23 Sep '04

23 Sep '04

Hi, I've just commited a new version of the plugin 210/225 adapted to the 2.2 version (with MARC authorities) How to set up value builder for 210c (editor) and 225a (collection) : * create a authority category called "EDITORS" * set : 200$a => ISBN 200$b => editor 200$c => (repeatable) collection. Then enter, for example : $a 23 $b Hachette Litterature $c collection1|collection2|collection3 Map your "editor" field to plugin 210c, your "collection" field to plugin 225a Once you arrive on the editor field, if the beginning of the ISBN exists, the editor is automatically found. Once you arrive on collection field, click on ... you can choose in the collection list. The 210c / 225a comes from the UNIMARC editor/collection field, but should work as well with MARC21. (Note the 200$a $b $c are hardcoded, but everything else is not) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

RE: [Koha-devel] Moving to Arch?
by Anthony Youngman 23 Sep '04

23 Sep '04

Not that I'm aware of ... What it is, is that Koha is getting bigger, and CVS doesn't scale ... just look at linux and bitkeeper. Arch means basically that any developer can maintain their own tree, without worrying about treading on any body else's toes. With CVS you always have the worry that either you are going to be unable to work because somebody else has checked out the module you want, or somebody checks in a module and blows away someone else's work because they both had the same module checked out at the same time ... okay CVS is meant to prevent the latter, but that only works when you have a PHB handing out tasks ... CVS is excellent for a tightly managed project - in other words NOT a big distributed FLOSS project. Arch, bitkeeper, ?subversion? et al are designed to handle distributed development. And at the end of the day, even with CVS, don't you need a single director in order to prevent anarchy? :-) Cheers, Wol -----Original Message----- From: koha-devel-admin(a)lists.sourceforge.net [mailto:koha-devel-admin@lists.sourceforge.net] On Behalf Of Owen Leonard Sent: 23 September 2004 15:49 To: koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] Moving to Arch? > > So does this mean that I can't merge back into the main > > branch ... that you > > have do do that? In CVS anyone with devel privs could > > commit to the main repo ... or am I mising something? > > Either the RM or their automaton will need to do the merge. > This is a deliberate model change from CVS which both allows > more people to do more development tasks without waiting for > approval, and allows the RM to say "show me the code" before > accepting it into the final release tree, if they want. It sounds like this is quite a shift of power, if I understand correctly, from a group of trusted developers to a single director who chooses what goes in and what doesn't. Do I understand correctly? Have we had problems in the past that will be alleviated by this shift of power? -- Owen ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel **************************************************************************** This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 8272 5300, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333. ****************************************************************************

1 0

Incorrect mapping of Copyright between Breeding Farm and Koha Tables?
by Rachel Hamilton-Williams 23 Sep '04

23 Sep '04

Hi I'm going to report this as a bug, but I thought I should check here as well as I'm not that strong in this area... Details: Koha V 2.0 on Windows, Vanilla Templates, MARC OFF, Simple Acquisitions I think that this is a problem in the scripts or the template.Basically the person gets their record in from their national library (Kinetica) into their breeding farm, and it comes with a copyright date, but when they select it to use and drag it into Koha the copyright date doesn't come accross. I *think* this is either a template problem, or a mapping problem, but I'm not sure which - or if there is anything she can do about it - is there a test I can run to make sure it's not the data though? Any help would be appreciated I'm sorry they don't have their intranet available for looking at - but I'd hope that others would know if this is a problem they've had to? Cheers Rachel -- _____________________________________________________________ Rachel Hamilton-Williams Katipo Communications MANAGING DIRECTOR 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

2 1