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

Paul and Steve's Excellent Adventure
by Pat Eyler 20 Jun '02

20 Jun '02

Paul and Steve have begun a Herculean merge of rel-1-2 stuff back into HEAD. This has been tremendously important, because they're getting ready to start in on the changes required for 1.4 and don't want to have to do a big merge backwards. If you're not working in rel-1-2, *please* do a cvs update before doing any more work. They're not done yet, and would probably welcom any help people can pitch there way. Please take a look at: <http://www.saas.nsw.edu.au/wiki/index.php?page=CVSMerge> and see what *you* can do to help. Paul and Steve, thanks for taking on a bear of a job and doing such a wonderful job. -pate

1 0

files remaining to be merged
by Tonnesen Steve 20 Jun '02

20 Jun '02

Here's a list of the remaining 39 files to be merged between rel-1-2 and main branches. They are sorted in order of increasing difference. The version numbers tell you if the file has been modified in both branches. For example, systempreferences.pl has never been modified in rel-1-2 (it is still at version 1.1), but has been modified in the main branch (up to version 1.3). The file modbibitem has been modified in both branches. It started at version 1.4 in the rel-1-2 branch, and has been modified once to become 1.4.2.1 (The number 2 signifies the rel-1-2 branch). In the main branch, the file has been modified 4 times since the branch was created to become version 1.8. ======================================================================== C4/InterfaceCDK.pm Lines: 3 Main 1.2 Branch1.1.1.1.2.1 C4/Stats.pm Lines: 5 Main 1.4 Branch 1.3.2.2 C4/Print.pm Lines: 7 Main 1.5 Branch 1.3.2.1 t/Input.t Lines: 8 Main 1.2 Branch 1.1.2.1 testKoha.pl Lines: 9 Main 1.5 Branch 1.1.2.7 modbibitem.pl Lines: 15 Main 1.8 Branch 1.4.2.1 admin/systempreferences.pl Lines: 40 Main 1.3 Branch 1.1 updater/updatedatabase2.pl Lines: 59 Main 1.2 Branch 1.1.2.1 acqui/addorder.pl Lines: 65 Main 1.7 Branch 1.3.2.1 database.mysql Lines: 65 Main 1.7 Branch 1.2.2.6 acqui/newbiblio.pl Lines: 68 Main 1.4 Branch 1.2.2.2 acqui/finishreceive.pl Lines: 71 Main 1.5 Branch1.1.1.1.2.1 acqui.simple/marcimport.pl Lines: 91 Main 1.11 Branch 1.6.2.23 C4/Input.pm Lines: 93 Main 1.1.1.1 Branch1.1.1.1.2.2 memberentry.pl Lines: 104 Main 1.6 Branch 1.6.2.1 updater/updatedatabase Lines: 121 Main 1.10 Branch 1.4.2.6 updatebiblio.pl Lines: 127 Main 1.2 Branch1.1.1.1.2.1 updatebibitem.pl Lines: 137 Main 1.6 Branch 1.4.2.1 search.pl Lines: 167 Main 1.9 Branch 1.6.2.1 acqui/newbasket2.pl Lines: 180 Main 1.2 Branch1.1.1.1.2.2 INSTALL Lines: 181 Main 1.2 Branch 1.1.2.7 modbib.pl Lines: 186 Main 1.4 Branch1.1.1.1.2.1 moredetail.pl Lines: 295 Main 1.7 Branch 1.4.2.1 C4/Reserves2.pm Lines: 314 Main 1.7 Branch 1.5.2.2 C4/Output.pm Lines: 330 Main 1.10 Branch 1.6.2.8 detail.pl Lines: 333 Main 1.9 Branch 1.3 circ/branchtransfers.pl Lines: 337 Main 1.9 Branch 1.3 request.pl Lines: 364 Main 1.3 Branch 1.2.2.2 acqui.simple/addbooks.pl Lines: 510 Main 1.9 Branch 1.5.2.1 installer.pl Lines: 558 Main 1.2 Branch 1.2.2.16 admin/branches.pl Lines: 648 Main 1.2 Branch 1.1 marc/marcschema.sql Lines: 649 Main 1.14 Branch 1.2 C4/Search.pm Lines: 805 Main 1.29 Branch 1.18.2.3 C4/Circulation/Circ2.pm Lines: 947 Main 1.28 Branch 1.21.2.1 C4/Acquisitions.pm Lines: 979 Main 1.18 Branch 1.5.2.10 ChangeLog Lines: 1256 Main 1.1 Branch 1.1.2.5 circ/circulation.pl Lines: 1386 Main 1.31 Branch 1.23 C4/Catalogue.pm Lines: 1748 Main 1.19 Branch 1.11.2.1 C4/Biblio.pm Lines: 1921 Main 1.1 Branch 1.1.2.1 ========================================================================

1 0

merging CVS files
by Tonnesen Steve 20 Jun '02

20 Jun '02

Those of you on the koha-cvs list may have noticed I've been attempting to merge the rel-1-2 branch back into the main branch. Some points to ponder: 1. Branching is necessary 2. Branching makes things difficult Some things to keep in mind when working on a branch: 1. Don't make any changes in the branch that could be made in the main and merged over to the branch. The goal is to keep the number of files that are different between a branch and the main as small as possible. If you are fixing a spelling mistake in a comment or some other cosmetic change, make the change in the main and merge the file into your branch. 2. Try to restrict development in a branch to a small number of files. It is easier to merge back into the main if the modified files are restricted to, for example, only circulation files. Steve Tonnesen

1 0

Re: [oss4lib-discuss] Koha 1.2.0 Released (fwd)
by Pat Eyler 20 Jun '02

20 Jun '02

---------- Forwarded message ---------- Date: Thu, 20 Jun 2002 09:38:38 -0400 From: barbara <bablumm(a)super.org> To: Pat Eyler <pate(a)eylerfamily.org> Subject: Re: [oss4lib-discuss] Koha 1.2.0 Released Pat, Do you have plans to include a serials module for serials checkin? Barbara Blummer Center for Computing Sciences Pat Eyler wrote: > Its finally here! > Nearly a year since the last release, we have a new stable release of > koha. > > 1.2.0 > > The main new features in this version are: > - Can search by dewey number > - Keyword Searches can be restricted by a dewey number > - Can restrict a catalogue search by a class of items > - Simple acquisitions module > - Deleting borrowers checks their accounts for reserves, current issues, > and fines > - New catalogue maintenance section > - MARC importing from a file, and from z39.50 > > Main Bugfixes: > - Keyword searches are a lot faster > - Combined author and title search is now also searching series title > - Combined author and title search is now also searching series title > - Adding children and institutions works as advertised > > There have been numerous little fixes and a lot of code clean up. > > The structure of the tarball has changed to a more sensible layout, and > the INSTALL document has been rewritten. > > There is also now a installer script, as well as a functioning database > update script. > > All this should mean its the easiest Koha to install or upgrade yet. > > The next release wont take nearly as long, 1.2.1 is well underway. Also > keep your eyes open for the upcoming 1.4 series with full MARC > compatability. > > Chris Cormack Pat Eyler > 1.2 Release Manager Kaitiaki/Manager > the Koha Project the Koha Project > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > _______________________________________________ > > oss4lib-discuss(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oss4lib-discuss > see also http://www.oss4lib.org/

1 0

RE: [Koha-devel] irc meeting
by Pat Eyler 19 Jun '02

19 Jun '02

On Wed, 19 Jun 2002, Nicholas Rosasco wrote: > We might want to stick the crossref'ing idea (pointing back to the catalog) > on there, if only to table it -- it has been asked for 2/3 times I can think > of. excellent point, consider it added. -pate > > Nick > > > > -----Original Message----- > > From: koha-devel-admin(a)lists.sourceforge.net > > [mailto:koha-devel-admin@lists.sourceforge.net]On Behalf Of Pat Eyler > > Sent: Wednesday, June 19, 2002 11:03 AM > > To: Koha-devel(a)lists.sourceforge.net; koha(a)lists.katipo.co.nz > > Subject: [Koha-devel] irc meeting > > > > > > Hmm, we managed to miss our meeting on the 13th (probably due to the > > crunch of getting 1.2.0 out. Shall we try again at: > > > > o When: June 27, 2002 20:00GMT > > o Where: irc.katipo.co.nz:6667 > > o Who: Open to entire Koha community > > o What: Agenda to be determined > > > > Some agenda items might be: > > > > 1.2 schedule > > 1.4 plans > > thoughts on templating > > translations > > community (Koha, and the larger OSS4lib, and the larger library > > community) > > > > thoughts? > > > > -pate > > > > > > ------------------------------------------------------------------ > > ---------- > > Bringing you mounds of caffeinated joy > > >>> http://thinkgeek.com/sf <<< > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/koha-devel > > > >

1 0

irc meeting
by Pat Eyler 19 Jun '02

19 Jun '02

Hmm, we managed to miss our meeting on the 13th (probably due to the crunch of getting 1.2.0 out. Shall we try again at: o When: June 27, 2002 20:00GMT o Where: irc.katipo.co.nz:6667 o Who: Open to entire Koha community o What: Agenda to be determined Some agenda items might be: 1.2 schedule 1.4 plans thoughts on templating translations community (Koha, and the larger OSS4lib, and the larger library community) thoughts? -pate

1 0

koha version 1.4 TODO
by paul POULAIN 19 Jun '02

19 Jun '02

Hi guys, As 1.4 Release Manager, i've added a page on the wiki about what is to do : http://www.saas.nsw.edu.au/wiki/index.php?page=ToDoMARC Every developper that has a few time to work on it can go and see what is to do. The more urgent is the merging of rel-1-2 and main branch (as soon as 1.2.1 will be released i think) Let me know if someone pick a task ;-) Thanks a lot -- Paul

1 0

Re: aah! a linux consultant!
by Pat Eyler 19 Jun '02

19 Jun '02

On Wed, 19 Jun 2002 COURYHOUSE(a)aol.com wrote: > actually this is the type of product that lends it self to pro bono effort. > many of the small schools have no budget. True, and the combined results of people making efforts like this could (will?) be enough of a koha market that schools, home schools, small businesses, and libraries may be willing to put up a little money (here and there) to improve Koha in one way or another. Enough of those small grants, sponsorships, etc and you've got a decent little cottage economy. -pate > > > > > > > > do you currently have a school you are trying to help automate? > > > > not at the moment, though i'm helping out with a couple of cases (pro > > bono) > > > > -pate > > > > > > >

1 0

Re: aah! a linux consultant!
by Pat Eyler 19 Jun '02

19 Jun '02

On Wed, 19 Jun 2002 COURYHOUSE(a)aol.com wrote: > Actually koha would be a good niche consulting market. I think it would be, and I hope we can stack up a variety of folks interested in supporting it to go this route. It would be good to see the improvements in stability that would come out of people being paid to support it (and develop it for that matter). > > Dynix!! Oh my... Glendale public library system uses that thing! > from what I understand there is a a replacement for it now.. it was amazing > in it's day though, the system they had prior to that had no key word > search.... I was in the tech services office the day one of the gals came > back in to tell everyone how neat keyword search was. The maint fees on > dynix are pretty high from what I understand on a yearly basis... My understanding is that most commercial products have pretty heavy maintenance fees. > > the openbook product or whatever the are calling it now .... well it is > interesting to see if they actually pull it off this time... the fellow in > charge is really bright on library methodology was former head of tech > services for city of Seattle.. so conceptually he should be able to come up > with something to please the market, although I think he has to pay > programmers to implementing it grovel for grants.. etc etc etc. do not think > he is a code writer..... > > it is a pity he did not team up with the effort here... I have the feeling > in his area he would put us all to shame.... > /me nods > Funny story, they were going to come out with the technical beta on the > product and were supposed to have the instructions finished and the files > posted by one afternoon.... They all blew the day off to go to a baseball > game..... meanwhile there were a bunch of folk out there (including myself) > waiting to download this thing and no code to download! > > Well, the next afternoon the files wee up and the install instructions had so > many flaws in them unless you did some deductive reasoning it would not have > worked at all. What an evening of self abuse that was! ( I was starting to > feel like the cdk pearl fellow) ouch > > do you currently have a school you are trying to help automate? not at the moment, though i'm helping out with a couple of cases (pro bono) -pate > > Ed! > > > > Subj:Re: aah! a linux consultant! > > Date:6/18/2002 10:07:32 PM US Mountain Standard Time > > From:<A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > > To:<A HREF="mailto:COURYHOUSE@aol.com">COURYHOUSE(a)aol.com</A> > > Sent from the Internet > > > > > > > > On Wed, 19 Jun 2002 COURYHOUSE(a)aol.com wrote: > > > > > aah! a LINUX consultant! > > > Heh did a google on patefamily! checked out your site ! > > > now I guess the question is what is your interest in the library system? > > > Is this to be an extension of consulting efforts? > > > > hmm, linux consultant feels kind of limiting. I see myself as more of an > > open-ended IT consultant (I'm currently doing a lot of work with AIX and > > Solaris). > > > > As to my interest in library systems, it's a long standing thing. I've > > always loved libraries, and worked for Dynix for a bit (many years ago). > > I've kept my eye out for a free library system since I first read the GNU > > request for one (in '93 or so), and have hoped to get involved with it. > > Lo and behold, I found Koha and got involved. > > > > As to my intents. I'm still looking into things. I'll stay involved with > > the larger Koha community and do my best to see it succeed. Given the > > right answers to the questions I'm asking (myself, other developers, > > Katipo, and libraries) I may get involved with a commercial venture > > working with Koha. If someone were to offer me money to subsidize my > > current efforts, that'd be fine too. ;) > > > > -pate > > > > > > > > Ed Sharpe archivist for SMECC > > > > >

1 0

Re: secure linuxen
by Pat Eyler 19 Jun '02

19 Jun '02

On Wed, 19 Jun 2002 COURYHOUSE(a)aol.com wrote: > what is scope creep? Scope creep is the gradual growth of the scope of a project (number of targets, number of featurs, etc). It is also a leading killer of projects as the developers gradually succumb to the increasingly heavy load they are placed under. > > > Yes, needs to run under windows as well the openbook folk were also > targeting this since it would team well with a gates library grant. > gates is putting a lot of servers and workstations in libraries these days. > /me nods. -pate > ed sharpe: > > > > Subj:Re: secure linuxen > > Date:6/18/2002 10:08:48 PM US Mountain Standard Time > > From:<A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > > To:<A HREF="mailto:COURYHOUSE@aol.com">COURYHOUSE(a)aol.com</A> > > CC:<A HREF="mailto:Koha-devel@lists.sourceforge.net">Koha-devel(a)lists.sourceforge.net</A> > > Sent from the Internet > > > > > > > > On Wed, 19 Jun 2002 COURYHOUSE(a)aol.com wrote: > > > > > Probably would be good to test under HPUX also. > > > > hmm, AIX, OS-X, and Solaris are all also interesting ... Win32 less so, > > but probably important nonetheless. > > > > Gaah! I hate scope creep ;) > > > > -pate > > > > > > > > Ed Sharpe archivist for SMECC > > > > > > > >

1 0