- Koha - lists.katipo.co.nz

Re: [Koha] Call for testers
by COURYHOUSE＠aol.com 29 Jan '03

29 Jan '03

Pate: congrats on the article on KOHA in the LINUX Mag. Looks great! Just got a copy off the rack at fry's electronics this evening! Feb Issue! Thanks Ed Sharpe, Archivist for SMECC See the Museum's Web Site at www.smecc.org We are always looking for items to add to the museum's display and ref. library please advise if you have anything we can use. mail: Coury House / SMECC 5802 W. Palmaire Ave. Glendale Az 85301 USA 623-435-1522

1 0

Re: [Koha] Call for testers
by COURYHOUSE＠aol.com 28 Jan '03

28 Jan '03

Thanks that helps me understand it! Ed! > Subj: Re: [Koha] Call for testers > Date: 1/28/2003 9:30:45 AM 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@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A> > Sent from the Internet > > > > On Tue, 28 Jan 2003 COURYHOUSE(a)aol.com wrote: > > >What is meant by major rewrite? > > This will be a multi-step process. > > 1) create a super solid test suite to verify functionality > 2) make a long series of very small changes, testing each one, with the > end goal of having a much more solid, much more readable code base > 3) then start adding functionality > > >Should we wait to implement until AFTER this is done? > > No, the 2.0 series should be an excellent platform to implement from. > Please use these releases (which should be out this Spring). > > >Don't really want to crawl though piles of new bugs while undergoing > >implementation during production..... > > This is one of the reasons we're looking to be very test heavy. each > change will have to pass all of the (by then) existing tests before it can > be integrated. What we'll end up with is a code base that is easier to > verify as functionally correct, easier to debug when we find new problems, > and easier to extend when we add new features. > > I hope this explanation makes sense, and helps put your mind at ease. > > I'm cc:ing the Koha list because I think that others might have the same > concerns. > > -pate > > > >Ed Sharpe archivist for SMECC > > > > > >>Subj:[Koha] Call for testers > >>Date:1/27/2003 12:08:43 PM US Mountain Standard Time > >>From:<A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > >>To:<A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A>, <A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel(a)lists.sourceforge.net</A> > >>Sent from the Internet > >> > >> > >> > >>Now that we're closing in on our 2.0.0 release (maybe in February > >>according to the 2.0 release manager), and we need to start looking to > >>the future. One of the things we really want to focus on for the next > >>release is a major rewrite/refactor. If we do this right, we can get > >>Koha test-infected, and make the development run even more quickly > >>than it already does. > >> > > > >

1 0

Re: [Koha] Call for testers
by Pat Eyler 28 Jan '03

28 Jan '03

On Tue, 28 Jan 2003 COURYHOUSE(a)aol.com wrote: > What is meant by major rewrite? This will be a multi-step process. 1) create a super solid test suite to verify functionality 2) make a long series of very small changes, testing each one, with the end goal of having a much more solid, much more readable code base 3) then start adding functionality > Should we wait to implement until AFTER this is done? No, the 2.0 series should be an excellent platform to implement from. Please use these releases (which should be out this Spring). > Don't really want to crawl though piles of new bugs while undergoing > implementation during production..... This is one of the reasons we're looking to be very test heavy. each change will have to pass all of the (by then) existing tests before it can be integrated. What we'll end up with is a code base that is easier to verify as functionally correct, easier to debug when we find new problems, and easier to extend when we add new features. I hope this explanation makes sense, and helps put your mind at ease. I'm cc:ing the Koha list because I think that others might have the same concerns. -pate > > Ed Sharpe archivist for SMECC > > > > Subj:[Koha] Call for testers > > Date:1/27/2003 12:08:43 PM US Mountain Standard Time > > From:<A HREF="mailto:pate@eylerfamily.org">pate(a)eylerfamily.org</A> > > To:<A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A>, <A HREF="mailto:koha-devel@lists.sourceforge.net">koha-devel(a)lists.sourceforge.net</A> > > Sent from the Internet > > > > > > > > Now that we're closing in on our 2.0.0 release (maybe in February > > according to the 2.0 release manager), and we need to start looking to > > the future. One of the things we really want to focus on for the next > > release is a major rewrite/refactor. If we do this right, we can get > > Koha test-infected, and make the development run even more quickly > > than it already does. > > > > >

1 0

Call for testers
by Pat Eyler 27 Jan '03

27 Jan '03

Now that we're closing in on our 2.0.0 release (maybe in February according to the 2.0 release manager), and we need to start looking to the future. One of the things we really want to focus on for the next release is a major rewrite/refactor. If we do this right, we can get Koha test-infected, and make the development run even more quickly than it already does. To really make this work, we're going to need to get a lot better at testing. I think there are two keys to this. First, I'd like to recruit someone to work as the testing manager. (I need to come up with a better title than 'manager' -- I'm afraid it scares people off.) Second, I'd love to find a couple more developers with some solid testing background, who are willing to volunteer their time on a cool FOSS project. The manager will need to be able to help outline unit and functional test suites, plan and run useability and acceptance tests, and coordinate with the 2.2 release manager to ensure that 2.2 is squeaky clean when it gets released. The developers should be solid Perl hackers who really grok testing. Being able to create tests from developer input, user input, system docs, and bug reports is going to be a key to making this process work correctly. If you match the above descriptions, and are interested in volunteering, please feel free to drop me a note at kaitiaki(a)koha.org. Pat Eyler Kaitiaki/manager migrant Linux sys admin the Koha project ruby, shell, and perl geek http://www.koha.org http://pate.eylerfamily.org

1 0

help me
by Valerio Venturi 27 Jan '03

27 Jan '03

Almost works. Two problems: 1) Searching the opac, when trying to see the details of an item i get The requsted URL /cgi-bin/koha/MARCdetail.pl was not found on this server. In fact MARCdetail.pl is not in /path/opac/cgi-bin (ScriptAlias set to /cgi-bin/koha/ /path/opac/cgi-bin) Similar problem comes with link Try another searc: catalogue-home.pl not in cgi-bin folder of opac. However, setting temporanealy ScriptAlias to /cgi-bin/koha/ /path/koha/cgi-bin the script is found but give 500 Internal Server Error with /var/log/httpd/error_log Tag " " is not a valid tag. at /usr/lib/perl5/5.6.1/C4/Biblio.pm line 590 2)Trying to add a new member when Save changes I get 500 Internal Server Error with /var/log/httpd/error_log Missing right curly or square bracket at /path/koha/cgi-bin/newmember.pl line 162 Please help me. Thanks. Valerio

2 1

RE: [Koha] :-( and conclusion with cataloguing and acquisition th read
by Bigwood, David 25 Jan '03

25 Jan '03

I also would like to be able to add items without barcodes. We create analytics for special issues of journals, these have no barcode but provide important access to materials. For example, the journal Icarus has a special issue on the proceedings of a conference. That issue will be bound with other issues, so that particular issue will not have a barcode, the volume will. There may be several special issues in a volume, so we can not just use the barcode from the volume, unless we duplicate the barcodes for each record. And duplication of barcodes will not work since we might have to wait a year or more to get all the issues of the volume to bind. We could not guess what barcode would be used sometime in the future. Sincerely, David Bigwood bigwood(a)lpi.usra.edu Cataloging news: http://www.catalogablog.blogspot.com > 3. The ability to add items without a barcode. so that barcodes > don't have to be set aside for books that have not yet arrived. > (This may already exist but I'm not aware of it. This would be > of greater importance if acquisitions was in xhtml and there was > a chance that someone would add a book from their cell phone. > But others might find it useful. > strange thing indeed. Does someone else have something like this ? Don't you misunderstood what means : "patrons should be able to find biblios without items in the opac, to see that the book will arrive soon ", as i think it's what you ask for ? -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org) _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Re: [Koha] :-( and conclusion with cataloguing and acquisition thread
by Owen Leonard 24 Jan '03

24 Jan '03

> The 2.0 will include a full-templated koha. This means it will be > possible (and not too hard) to add as many themes as needed. Thus, > anybody could develop a xhtml theme, or even a full-xml theme, or > anything else. Converting the current default opac templates to XHTML wouldn't be difficult at all (particularly if Bobby gets his Tidy filter working). However, the issue may depend on your definition of XHTML--do you mean XHTML Transitional or Strict? Do you mean table-less layouts, full CSS positioning? I'm interested in developing both kinds of templates, but I'd like to hear more about what users of internet-enabled phones require for compatibility. -- Owen

2 1

problems to use Koha 1.3.3
by Serge Renaux 24 Jan '03

24 Jan '03

2 1

Re: [Koha] :-( and conclusion with cataloguing and acquisition thread
by paul POULAIN 24 Jan '03

24 Jan '03

cc to koha list : (sounds interesting) Erik Stainsby a écrit: >On January 24, 2003 04:41 am, paul POULAIN wrote: > > > >>> 3. The ability to add items without a barcode. so that barcodes >>> don't have to be set aside for books that have not yet arrived. >>> (This may already exist but I'm not aware of it. This would be >>> of greater importance if acquisitions was in xhtml and there was >>> a chance that someone would add a book from their cell phone. >>> But others might find it useful. >>> >>> >>strange thing indeed. Does someone else have something like this ? >>Don't you misunderstood what means : "patrons should be able to find >>biblios without items in the opac, to see that the book will arrive soon >>", as i think it's what you ask for ? >> >> > >My library (on Dynix) for many years, uses a negative-number barcode for items >ordered, not received. Patrons are able to place holds, and further staff >know not to place redundant orders (we have 800+ staff members) ... >Very much prefereable not to have to "fake" the barcode but to just have >records with blanks. "Fake" barcodes also have to follow check digit logic, >etc. There are a finite number of such - and our collections are approaching >1,000,000 items, with +/- 2M calatogue entries. > >Erik > > > > -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Suggestion
by Bigwood, David 24 Jan '03

24 Jan '03

A suggestion, Koha should be able to use the LibraryLookup bookmarklet developed by Jon Udell. http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html It would be nice if it was included and would display on the OPAC so that patrons could just drag it to their toolbar. Sincerely, David Bigwood bigwood(a)lpi.usra.edu Cataloging news: http://www.catalogablog.blogspot.com

1 0