January 2003 - Koha - lists.katipo.co.nz

version 1.9.0 delayed
by paul POULAIN 31 Jan '03

31 Jan '03

The 1.9.0 won't be released today. because of : * hdl tells me he will template circulation today. So i'll wait for it * i need to fix some mistakes in french templates Will be released next week for sure ! -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Opac searches
by Owen Leonard 30 Jan '03

30 Jan '03

I've got a lot of questions about how searching works, and I'll start here: When I go to http://opac-templates.koha.org/cgi-bin/koha/opac-search.pl and put 'melville' in the 'Author' field, the first search result that comes up is this one: http://opac-templates.koha.org/cgi-bin/koha/opac-detail.pl?bib=50027 ...which doesn't seem to have 'melville' anywhere. Does a search by author from that page do a full-record keyword search? If it's picking up information that's not displayed, then how does one get the 'full' display? -- Owen

3 2

koha-1.2.3 : problem with basic installation
by Hor Hen Ley 30 Jan '03

30 Jan '03

hi everyone, This is my last resort posting to this ml. i have tried all the all the installation methods and installing several times for version 1.2.3. However when i view the intranet index page i see somelike "http://www.bii.a-star.edu.sg/wherethelightdontshine/koha_login.html" is there something wrong ? shouldnt i be seeing the something like the librarian access module in "http://koha.org/drive/" ? any help would be great. pls anyone ? Misc info ========= /etc/koha.conf --------------------------- base=koha hostname=localhost user=koha pass=koha includes=/usr/local/koha/intranet/htdocs/includes intranetdir=/usr/local/koha/intranet opacdir=/usr/local/koha/opac kohalogdir=/var/log/koha kohaversion=1.2.3 httpduser=www-data ----------------------------- /etc/httpd.conf ----------------------------- HA's OPAC Configuration <VirtualHost 192.168.120.135> ServerAdmin webmaster(a)testing.com DocumentRoot /usr/local/koha/opac/htdocs ServerName opac.testing.com ScriptAlias /cgi-bin/koha/ /usr/local/koha/opac/cgi-bin/ ErrorLog /var/log/apache/opac-error_log TransferLog /var/log/apache/opac-access_log SetEnv PERL5LIB "/usr/local/koha/intranet/modules" Options +Includes AddHandler server-parsed .html </VirtualHost> # KOHA's INTRANET Configuration <VirtualHost 192.168.120.135> ServerAdmin webmaster(a)testing.com DocumentRoot /usr/local/koha/intranet/htdocs ServerName intra.testing.com ScriptAlias /cgi-bin/koha/ "/usr/local/koha/intranet/cgi-bin/" ErrorLog /var/log/apache/koha-error_log TransferLog /var/log/apache/koha-access_log SetEnv PERL5LIB "/usr/local/koha/intranet/modules" Options +Includes AddHandler server-parsed .html </VirtualHost> ------------------------------- -- Hor Hen Ley ( bii web team ) henley(a)bii.a-star.edu.sg my pgp publics are available at http://www.bii-sg.org/~henley/

3 7

Mail::sendmail is needed for koha-1.2.3 for updating user info
by Hor Hen Ley 30 Jan '03

30 Jan '03

hi all, i think the perl module Mail::sendmail is needed for updating userinfo. However its not essential. Shant we add it to the optional list of perl modules needed for koha ? rgds henley -- Hor Hen Ley ( bii web team ) henley(a)bii.a-star.edu.sg my pgp publics are available at http://www.bii-sg.org/~henley/

1 0

new member form template abstraction
by Erik Stainsby 29 Jan '03

29 Jan '03

Greetings, Has anyone started working on an abstraction of the new member forms? Some of the values on the lists appear to be hardcoded into the pages/templates. It would seem useful to allow a per-setup(institution) list of Town names, and localities, perhaps a list of valid Areacodes for members of the institution. It seems to me this would be best done as a small set of tables rather than in the templates themselves. My own background should illustrate my biases here: I work for a system in an urban region of about 2 Million people; my own city, the nominal "capital" of the region is about 500,000. The library I work in has 22 branches within our city, and extensive lending arrangements throughout the larger region. A new patron will register with our system in the context of a primary agency, their "local" branch. The branch records should be accessible for linking into the new patron record as a foreign key, and for display during the registration process. Further, pattern matching logic could be used against postal codes, which are nationally administered, and uniquely identify a neghbourhod (even down to a specific block). In the administrative area, a new branch would be "created" including postal area and contact info. Is any of this making sense ? Cheers, Erik Stainsby Modern Alchemy

7 6

Use and setting of userid in borrowers table
by Van Eijk, Marcel 29 Jan '03

29 Jan '03

Yesterday, I installed Koha which I hope to be using for our small internal library. I set it up in such a way that it will use cookie authentication, thus using the borrowers table. I was wondering the following: 1. Is it possible to set the userid and password from the web interface; I'd rather not use the card barcode to login to the system. 2. I saw that one can set different flags for each use to allow for access to different parts of the intranet interface. It seems, howver that one needs super librarian status to login anyway. Is this a bug, or am I doing something wrong? I hope somebody can help me. Cheers, Marcel

1 0

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