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

From the Kaitiaki
by pate＠bigfun.whirlycott.com 27 Jun '02

27 Jun '02

28 June, 2002 To the Koha community; Namaskar, This week's note is a short one. Not because we haven't done much, but because we're all getting pretty busy. I'm currently talking to a couple of organizations about getting some more visibility for Koha. I don't want to tip my hand just yet, but I'm hopeful that we'll see Koha beginning to make appearances in the bigger Open Source world 'Real Soon Now'. We're also starting to see some more feedback from other library centric Open Source projects. It looks like the idea of some inter-project cooperation is gaining ground. One interesting area that came up was in helping one another in securing financing (sponsorship, hired work, or grants all come to mind) -- this will be an important area for Koha moving forward. Free Software doesn't come without a price tag, the price is just hidden better than with other software. Much of Koha is developed by volunteers in their 'spare' time. If there were funding available for given tasks, it would give the developers more time to work on Koha (because they'd need to spend less time making a living). If you're interested in helping this way, please take a look at <http://koha.org/installation/support.html> for some potential vendors. 1.2 We're still hard at work on 1.2.1. In fact, Steve Tonnesen has produced three Release Candidates this week alone. He's also made the job easier by automating this process, so expect to see Release Candidates for every future release -- it's another way we're trying to improve our process. Other big features for 1.2.1 include: * a much improved installer (it only requires 1 ip address, and creates a branch and a printer during install now) * more work on the Z39.50 programs * sample data that can be installed to test a new koha system Many thanks to Paul and Steve who've both jumped in and are making the 1.2 series really shine. Translations The first question people seem to ask when volunteering to do translations of Koha is, "Where do I start?". Since we're still on the verge of having the application readily translatable, this question deserves a thoughtful answer. There are a number of things that could be translated and provide value to the project. These newsletters, if translated, could help advertise Koha to people who don't currently know about it. The Manual could be translated to help users and developers who don't understand english. I think one of the best documents to translate would be the INSTALL document. If we could get this done in multiple languages, it would be much easier to get Koha into the hands of the people who will help us make it suitible for international use. IRC Meeting Due to some scheduling conflicts, this weeks irc meeting was postponed. We're going to shoot for 7/11 (7/4 is a big holiday in the US, so that won't work either). The proposed agenda is currently: * CVS * 1.2 schedule * 1.4 plans * thoughts on templating * translations * documentation housekeeping * community (Koha, and the larger OSS4lib, and the larger library * new koha website Community The Koha community is continuing to grow. More libraries are trying Koha out, and many of them are sticking with it. We've added more people to the developers list, several of whom are concentration on testing new Koha releases. Another exciting advance is the new <www.koha.org> website. Rachel and her team at Katipo have done a wonderful job. I'd like to hear back from people who are currently using or investigating Koha. If you've got stories, requests, or suggestions, please feel free to drop me a line at: kaitiaki(a)koha.org Dhanyabad, -pate Pat Eyler Kaitiaki of the Koha Project ps. This weeks language is Bengal. Hopefully my usage isn't too far off. Thanks Md. Aftabuddin, for helping out.

1 0

New 1.2.1 release candidate
by Chris Cormack 27 Jun '02

27 Jun '02

Continuing the trend of a new RC per day :) Heres todays one http://developer.koha.org/koha-1.2.1RC5.tar.gz Changelog is attached. Have fun Chris -- Chris Cormack chris(a)katipo.co.nz Programmer 025 500 789 Katipo Communications www.katipo.co.nz

1 0

upgrade script
by Tonnesen Steve 27 Jun '02

27 Jun '02

I managed to put together an upgrade script today that will be going out with the 1.2.1 release. The upgrade script (koha.upgrade) will make backups of your koha data, and all of the koha scripts and html files before installing the new files and making any necessary changes to the database. The upgrade script also indicates changes that may need to be made to the Apache configuration. I suspect there aren't a whole pile of production Koha systems out there yet, apart from Katipo's clients and my schools. If you _are_ using Koha in a production environment, I'd really appreciate hearing from you before the 1.2.1 release goes out. Steve.

1 0

Koha 1.2.0 (resent due to bad address)
by Pat Eyler 27 Jun '02

27 Jun '02

On Thu, 27 Jun 2002, Marcel Gagne wrote: > > Hi Pat, > > So I downloaded (and installed) Koha 1.2.0 and it still appears to have the > "ethnicity" field in member records. Have I missed something? It may have missed the 1.2.0 cut off ... Let me take this to the development list and see what we can scare up. I think we'll be seeing it in 1.2.1 BTW, we're hard at work on 1.2.1 you can see RCs at <http://developer.koha.org> which might be even nicer for you to work with > > Thanks and take care out there. > > thanks, you too -pate

1 0

[Bug 52] New: 1.2.1 will need an "upgrade" script for upgrading from older installs
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '02

27 Jun '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=52 Summary: 1.2.1 will need an "upgrade" script for upgrading from older installs Product: Koha Version: unspecified Platform: PC Status: NEW Severity: normal Priority: P2 Component: Installation AssignedTo: tonnesen(a)cmsd.bc.ca ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net Not sure how this got left so late. This will likely need some serious testing. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 46] addbooks.pl and marcimport.pl don't autogenerate barcodes the same
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '02

27 Jun '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=46 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-06-28 06:22 ------- I modified marcimport.pl in rel-1-2 to find max(barcode) and increment by 1 if the last character is a digit. Otherwise it uses biblionumber as a suggested barcode. Libraries that use preprinted barcodes will probably prefer the option to leave this field blank so they can just scan in the barcode that they actually put on the book. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 48] marcimport.pl should do a better job at guessing the itemtype
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '02

27 Jun '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=48 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|chris(a)katipo.co.nz |tonnesen(a)cmsd.bc.ca ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-06-28 06:04 ------- Applied this patch with some modifications. Original patch was against 1.11 in main branch, but most development on marcimport.pl has been going into the rel-1-2 branch in revision 1.6.2.28. Also had to patch C4/Output.pm which now contains the getkeytableselectoptions subroutine. Patch works as advertised though. Thanks. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 46] addbooks.pl and marcimport.pl don't autogenerate barcodes the same
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '02

27 Jun '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=46 tonnesen(a)cmsd.bc.ca changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|chris(a)katipo.co.nz |tonnesen(a)cmsd.bc.ca ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-06-28 04:17 ------- # Modified saas(a)users.sf.net 12:00 01 April 2001 # The biblioitemnumber was not correctly initialised # The max(barcode) value was broken - koha 'barcode' is a string value! # - If left blank, barcode value now defaults to max(biblionumber) # my $sth=$dbh->prepare("select max(barcode) from items"); # $sth->execute; # my ($maxbarcode) = $sth->fetchrow; # $maxbarcode++; # print STDERR "MaxBarcode: $maxbarcode \n"; The code that generated a new barcode as maxbarcode +1 has been commented out. I'm not sure why max(barcode) is broken just because barcode is a string value... ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 48] marcimport.pl should do a better job at guessing the itemtype
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '02

27 Jun '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=48 ------- Additional Comments From kraai(a)alumni.cmu.edu 2002-06-28 04:15 ------- Created an attachment (id=1) untested patch ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 46] addbooks.pl and marcimport.pl don't autogenerate barcodes the same
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Jun '02

27 Jun '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=46 ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-06-28 04:20 ------- It just occurred to me that Roger might think this broken because some barcodes don't _end_ in numbers so the +1 trick will fail. Maybe we should add a test to see if the last digit is a number before adding 1. We should also probably have a test to ensure that the new barcode generated is, in fact, unique after adding 1. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0