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

commissioned work
by Tonnesen Steve 26 Sep '02

26 Sep '02

I've been commissioned to do some work by a donor who wishes to remain anonymous. I thought in the interests of transparancy I'd detail here what this donor needs added to Koha: 1. Optimization of the bulk marc record importing tool to facilitate importing and ongoing merging of a 500,000 record database. 2. Ability to group collections somewhat arbitrarily. The customer in this case is a group of 7 school districts with approximately 200 schools. The customer will need to see the location of an item by district and school, and also be able to search the collections of individual districts and schools. I'm hoping to use the Virtual Bookshelves concept to facilitate this feature. Steve Tonnesen

3 2

Fwd: [Koha-devel] commissioned work
by COURYHOUSE＠aol.com 26 Sep '02

26 Sep '02

> > > very important! > > ed! > > >> Ability to group collections somewhat arbitrarily. The customer in >> this case is a group of 7 school districts with approximately 200 >> schools. The customer will need to see the location of an item by >> district and school, and also be able to search the collections of >> individual districts and schools. I'm hoping to use the Virtual >> Bookshelves concept to facilitate this feature. >> >> >

1 0

Fwd: [Koha-devel] commissioned work
by COURYHOUSE＠aol.com 26 Sep '02

26 Sep '02

In a message dated 9/26/2002 9:51:13 AM US Mountain Standard Time, COURYHOUSE writes: > Subj:Re: [Koha-devel] commissioned work > Date:9/26/2002 9:51:13 AM US Mountain Standard Time > From:<A HREF="mailto:COURYHOUSE">COURYHOUSE</A> > To:<A HREF="mailto:tonnesen@cmsd.bc.ca">tonnesen(a)cmsd.bc.ca</A> > > > > Kudos Steve! > > >> Subj:[Koha-devel] commissioned work >> Date:9/26/2002 9:36:27 AM US Mountain Standard Time >> From:<A HREF="mailto:tonnesen@cmsd.bc.ca">tonnesen(a)cmsd.bc.ca</A> >> To:<A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel(a)lists.sourceforge.net</A> >> Sent from the Internet >> >> >> >> >> I've been commissioned to do some work by a donor who wishes to remain >> anonymous. I thought in the interests of transparancy I'd detail here >> what this donor needs added to Koha: >> >> >> 1. Optimization of the bulk marc record importing tool to facilitate >> importing and ongoing merging of a 500,000 record database. >> >> 2. Ability to group collections somewhat arbitrarily. The customer in >> this case is a group of 7 school districts with approximately 200 >> schools. The customer will need to see the location of an item by >> district and school, and also be able to search the collections of >> individual districts and schools. I'm hoping to use the Virtual >> Bookshelves concept to facilitate this feature. >> >> >> Steve Tonnesen >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Koha-devel mailing list >

1 0

Once again, please don't wait until the last minute
by Nicholas S. Rosasco 26 Sep '02

26 Sep '02

It is _that time again_ .... time to make the manual editor happy! As I begin to markup the first rounds of new goodies for the next edition of the manual (troubleshooting, transition from other opacs, and a tidied up installation section are started/in markup/close to ready, respectively) it is also time to make sure you are given your due.... namely, your entry in the credits file! If you are NOT IN HERE or SOMETHING IS WRONG WITH WHAT IS "AFTER THE COMMA" (description, that is) you need to email me. Posthaste. Last time I sent this out, I didn't get much in the way of response.... until we were trying to finish :) the manual for release hint hint I really would like to have this done first! Pat are we at the point where we should be crediting (besides french speakers) anyone from the nonenglish efforts? [Paul: I defer to you as to who on the french mailing list should go in....] -------------------------- Koha Credits Horowhenua Library Trust Rosalie Blake, Head of Libraries Jo Ransom Katipo Communications Rachel Hamilton-Williams, General Manager (Webmistress) Simon Blake, Technical Manager, Server Administrator Amanda Atkins, Operations Manager Chris Cormack, 1.2 release guru Olwen Williams Finlay Thompson Gynn Lomax Richard Anderson Jeremy Blake, Katipo Koha Project Manager Rebecca Holden, New Koha.org page Steve Tonnesen, MARC import/export guru Pawel Skuza, Polish Language porter Glen Stewart Paul Poulain, 1.4 release manager Pat Eyler, Kaitiaki Roger Buck Adam Thick Florian Bischof Sebastiaan Durand Andrew Hooper Mike Mylonas Mike Johnson Mike Hansen Nicolas Morin, French Translation/Traduction Française of the Documentation Nicholas Rosasco, Documentation Editor/Compiler -------------------------- On other, stranger notes, we seem to have been misfiled -- google puts us in the following category: http://directory.google.com/Top/Computers/Software/Operating_Systems/Graphic _Subsystems/Desktop_Environments/KDE/Productivity/?il=1

1 0

RE: [Koha-devel] How may I be of assistance?
by Eyler, Patrick 24 Sep '02

24 Sep '02

> -----Original Message----- > From: Nicholas S. Rosasco [mailto:nsr@etome.net] > Sent: Tuesday, September 24, 2002 11:27 AM > To: KohaDev > Subject: RE: [Koha-devel] How may I be of assistance? > > >Let me know if there are other areas that need (more) help, or how > I > >can help with the install process. > > I know that for the installer my (at least) eventual hopes were to > advance > it to the point where the "other options" (no virtual > hosts/rootless/etc) > were covered by it as well.... I'd sure like to see it cover other distros and other OSes (*BSD, Solaris, etc.) as well. -pate > > I don't know what others may be thinking on this point. > > Opinions? > Nick > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel

1 0

Re: [Koha-cvs] CVS: koha/C4 Database.pm,1.6,1.7 Koha.pm,1.6,1.7 Output.pm,1.16,1.17 Search.pm,1.36,1.37
by Dorian Meid 24 Sep '02

24 Sep '02

Output.pm, Line 261: > +# FIXME - Use 'foreach my $var (...)' Not really. Used this before, but I need every single variable after exiting the loops and so hve to declare them outside the loop. Dorian

2 1

FW: Koha 1.3.0 released (with message this time)
by Eyler, Patrick 24 Sep '02

24 Sep '02

Koha 1.3.0 has been released. This release marks the beginning of public development and testing of the MARC compliant Koha we've been Looking forward to. As the 1.3 releases stabilize and reach feature completion, they will become Koha 1.4. This is an alpha quality release only. *DO NOT ATTEMPT TO USE IT IN PRODUCTION SYSTEMS* It may cause data corruption or loss, it may confuse patrons, it may cause books to refile themselves in strange places. *IT SHOULD BE USED FOR TESTING ONLY*. (I hope that's clear enough.) If you are want to use Koha in a production setting, please stick with the stable 1.2 release until the 1.3 series stabilizes enough for us to create Koha 1.4.0. Significant new features in this release include: * Data is stored natively in a MARC based format. * Multiple flavors of MARC are supported. * Enhanced API supports both the new MARC format and the older Koha specific format. Please note though, that from a users perspective, this release should look just like a 1.2 series release. All of the work so far has been in redesigning the data format and extending the API. User visible changes will be included once the infrastructure has stabilized. It is also important to note that the simple acquisition system is currently broken. *DO NOT EVEN THINK ABOUT USING IT* The full acquisition system works correctly. Paul Poulain Pat Eyler 1.4 Release manager Kaitiaki/manager the Koha project the Koha project

1 0

Koha 1.3.0 released
by Eyler, Patrick 24 Sep '02

24 Sep '02

1 0

RE: building a community
by Eyler, Patrick 23 Sep '02

23 Sep '02

> -----Original Message----- > From: Rhyno Art [mailto:arhyno@server.uwindsor.ca] > Sent: Monday, September 23, 2002 6:57 AM > To: discuss(a)callimachus.org > Subject: Re: building a community > > Wow, very impressive, Koha is doing great and is a much needed > success > story for OSS in libraries. Thanks, it's always nice to hear kudos. > I am involved in two library-related > open > source projects, one called PYTHEAS > <http://www.uwindsor.ca/library/leddy/people/art/pytheas> and > another > called WIBS <http://wibs.sourceforge.net>. PYTHEAS started out > somewhat > similar to Koha, it had some PHP instead of Perl, but used MySQL on > the > backend, and even had a middle layer written in C. I managed to get > a 6 > month study leave to work on OSS, about half of which I used to > study the > current trends in how to put enterprise systems together. Thanks to > initiatives like Koha and Avanti, my feeling was that the options > for small > to medium sized libraries were becoming much better defined, but 15 > years > of working in a university environment had made me yearn for an > option for > large academic libraries, and one that plugged into other > environments. It > has always bothered me from a systems viewpoint that universities > constantly replicate systems between departments and that mainstream > software, such as LDAP servers, were very rare for university > administrative systems. I agree, it would be nice to see more emphasis on getting LDAP and similar tools into libraries. Perhaps turnkey system approaches built from OSS are the key to proving that this kind of tech not only works, but is a good fit for libraries. > > Anyway, my study leave led me to look closely at Enterprise Java > Beans > (EJB), which latter lead to Web Services and SOAP. I was also trying > to > maximize the use of XML since one of my first tasks as a systems > librarian > was working on a MARC editor for Stanford's SPIRES database and > rather than > repeating the experience, I felt that XML was the key to freeing > MARC from > quirky editing applications. None of this is an attempt to convince > anyone > of the benefits of Java, XML, or middleware infrastructures like > EJB, but > one area where I think we could share some of our efforts is in how > we map > our data structures. For example, I think Koha's MARC work, at one > time at > least, used an early version of the table layout defined for > PYTHEAS. Lots > of work and mistakes since then have led to numerous changes in the > layout > and I would be very interested in seeing if some of this learning > process > would be of use to anyone else. For that matter, any of the projects > that > use an RDBMS on the backend could probably benefit from sharing > ideas on > mapping and information retrieval with relational systems. > I agree, this might be an excellent place for callimachus to shine. > WIBS was based on the MRBS (Meeting Room Booking System) and was a > much > simpler endeavor. In fact, it was mainly put together to avoid > coming up > with the outrageous amounts that the commercial options for > workstation > booking seemed to require. Like MRBS, WIBS is a PHP/MySql > application but I > am currently reworking it to use the University of Washington > Calendar > Server. Is this an ICal (and related tech) thing? Do you have an URL for it? > Again, this ventures into Java territory, but my switch is > motivated by similar concerns. We would like to pass booking > information > between the university's main calendar systems (Lotus Notes) and > personal > calendar systems, and a true calendar server provides the plumbing > to > easily support iCalendar and other standard data formats for > calendar > information. This could all be built by hand in PHP but my minimal > amount > of time for OSS activities is already shrinking and it didn't make > sense > for me to rebuilt what others have done. I am also keen to keep in > line > with the Java in Administration Special Interest Group (JA-SIG) > <http://www.ja-sig.org/> and Java is a key part of this (though as I > have > told Pat, if I had my druthers, I would be working in nothing but > Python!). > > I have found that in a university environment, Java tends to open a > lot of > doors, not because of anything intrinsic to the language, but > because it > has such a rich and evolving set of APIs. Still, I have been through > more > grief trying to help people set up Java-based applications like > Tomcat than > anything I have seen with PHP, Perl, or other common types of OSS > solutions, so I am glad to see a variety of options available for > libraries > installing systems. Unlike Koha, my sharing of code has largely been > directly with other universities, and most of the projects I have > seen from > this have been very low profile. I am blown away by how well keeping > the > project in the public eye has served Koha and my hat is off to Pat > and all > the folks who have made this happen. Remember, I am still hoping at > least > one spokesperson for Koha might be at the upcoming Access conference > <http://www.access.uwindsor.ca> and could give an update at the > software > rodeo we are trying to put together. I'd like to get us there. Any volunteers from the devel list? Thanks, -pate > > art > --- > Art Rhyno, Systems Librarian > Leddy Library, University of Windsor > Internet: arhyno(a)uwindsor.ca > Tel: (519) 253-4232, EXT. 3163 > FAX: (519) 973-7076 > WWW: <http://www.uwindsor.ca/library/leddy/people/art>

1 0

buildrelease
by Andrew Arensburger 21 Sep '02

21 Sep '02

I've been looking at the 'buildrelease' script, and have a few comments and questions about it. For one thing, it looks for ".kohaautobuild.conf" and "docs/" in root's home directory, rather than in the current user's home directory or the CVS build directory. I assume these are considered bugs. Also, it uses "cp -a", which isn't portable (neither FreeBSD's nor Solaris's 'cp' take a "-a" option). The way it builds the distribution directory (which will be tarred up as the distribution tarball) is to copy everything from the CVS build directory into /tmp/koha-1.2.3/intranet-cgi, and then move things around, or delete unwanted files. The problem with this is that it can leave an awful lot of cruft in the intranet-cgi directory, which might therefore wind up in the end-user's internal/cgi-bin directory. I don't know about y'all, but I tend to generate a fair number of temporary files that shouldn't wind up in the release. For instance, if I find a security hole in "somescript.pl", I might make a backup copy "somescript.pl.buggy" for reference before fixing the bug. The way 'buildrelease' and the installation instructions are currently written, "somescript.pl.buggy" will wind up in a number of end-users' internal/cgi-bin directories. And since the source and revision history are there for all to see, it'll be fairly easy for a black-hat to write an exploit. A better approach, IMO, would be to have a file that specifies which files are to be included in the distribution, and where: ChangeLog* . search.pl intranet-cgi search.pl opac-cgi koha-html/intranet-html/index.html intranet-html ... So that all of the ChangeLog* files will be copied to /tmp/koha-1.2.3, "search.pl" will be copied to both /tmp/koha-1.2.3/intranet-cgi and /tmp/koha-1.2.3/opac-cgi, koha-html/intranet-html/index.html will be copied to /tmp/koha-1.2.3/intranet-html, and so forth. If people tell me, "you found the bug, you fix it", I will. Oh, and a general comment about Koha: none of these CGI scripts perform taint checks, even though they take user input. IMO this is a Bad Thing. -- Andrew Arensburger This message *does* represent the arensb(a)ooblick.com views of ooblick.com Reality? But there are DIRTY DISHES in Reality!

2 1