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

copright statements
by Tonnesen Steve 14 Aug '02

14 Aug '02

I added copyright statements to all of the .pl and .pm files in the main trunk and the rel-1-2 branches of the cvs server. Since the changes are all right at the top of the files, this shouldn't cause any conflicts, but you might want to update your checkouts to be sure. Steve.

1 0

[Bug 77] Multi-page OPAC search requires login
by bugzilla-daemon＠wilbur.katipo.co.nz 14 Aug '02

14 Aug '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=77 ------- Additional Comments From dnmeid(a)gmx.de 2002-08-14 23:06 ------- Ok, now I see the problem. Here is the solution: escape(), unescape() use CGI qw/escape unescape/; $q = escape('This $string contains ~wonderful~ characters'); $u = unescape($q); These functions escape and unescape strings according to the URL hex escape rules. For example, the space character will be converted into the string "%20". ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

2 1

Re: [Savannah-hackers] savannah.gnu.org: submission of Koha Library Automation Package (fwd)
by Tonnesen Steve 13 Aug '02

13 Aug '02

I made an attempt to register Koha with Savannah back in May and got this reply back. Just a heads up in case we decide to go that route. Steve. ---------- Forwarded message ---------- Date: Fri, 31 May 2002 12:17:14 +0100 From: "Jaime E . Villate" <villate(a)gnu.org> To: tonnesen(a)cmsd.bc.ca Cc: savannah-hackers(a)gnu.org Subject: Re: [Savannah-hackers] savannah.gnu.org: submission of Koha Library Automation Package Hi, In order to release your project under the GPL you must write copyright notices and copying permission statements at the beginning of every source code file, and include a copy of the plain text version of the GNU GPL (http://www.gnu.org/licenses/gpl.txt; copy it, for instance, into a file named COPYING). In its current state, I can see that the perl programs in Koha were written by people from Katipo, but I cannot tell if you are allowed to modify them and import them to Savannah. Please write copyright notices and copying permission statements following the advice of http://www.gnu.org/licenses/gpl-howto.html and when your are done register your project again. I also suggest that you write a README file describing your package. Regards, Jaime JaimeOn Thu, May 30, 2002 at 12:40:28AM -0400, tonnesen(a)cmsd.bc.ca wrote: > > A package was submitted to savannah.gnu.org. > This mail was sent to tonnesen(a)cmsd.bc.ca, savannah-hackers(a)gnu.org > > > Steve Tonnesen <tonnesen(a)cmsd.bc.ca> described the package as follows: > License: gpl > Other License: > Package: Koha Library Automation Package > System name: koha > This package does NOT want to apply for inclusion in the GNU project > > Description: > Koha is an open source library automation package. > > Koha is currently hosted at sourceforge and can be found at: > > http://sourceforge.net/projects/koha/ > > Other Software Required: > perl (DBI DBD-mysql) > apache > mysql > > > Other Comments: > Koha was initially developed by Katipo Communications of New Zealand for a group of libraries in New Zealand. The software was released under the GPL at the suggestion of Katipo in the hopes that it would be widely adopted and extended. >

2 2

Time to investigate Savannah seriously perhaps?
by Chris Cormack 13 Aug '02

13 Aug '02

Hi Guys Simon pointed this out to me today http://news.com.com/2100-1001-949505.html?tag=fd_top So perhaps we want to look at moving to savannah http://savannah.gnu.org/ Chris -- Chris Cormack chris(a)katipo.co.nz Programmer 025 500 789 Katipo Communications www.katipo.co.nz

1 0

[Bug 77] Multi-page OPAC search requires login
by bugzilla-daemon＠wilbur.katipo.co.nz 12 Aug '02

12 Aug '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=77 ------- Additional Comments From tonnesen(a)cmsd.bc.ca 2002-08-13 08:19 ------- Dorian. Decoding isn't really the problem as the CGI module takes care of that. It's 'encoding' the name=value pairs into the url that caused the problem here. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 77] Multi-page OPAC search requires login
by bugzilla-daemon＠wilbur.katipo.co.nz 09 Aug '02

09 Aug '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=77 ------- Additional Comments From dnmeid(a)gmx.de 2002-08-09 20:48 ------- This will help: sub decodeURL { $_ = shift; tr/+/ /; s/%(..)/pack('c', hex($1))/eg; return($_); } ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Pretty OPAC biblio record : patch
by Rob Levandowski 07 Aug '02

07 Aug '02

When I started playing around with Koha 1.2.2, I found that the biblio record display in the OPAC catalogue search detail wasn't pretty or functional enough for me. Below are diffs for the changes I made to detail.pl. They make the following changes: * the Author becomes a link to search.pl with the appropriate argument. * the Additional Author field becomes an unordered list, with each name as a link to search.pl. A substitution removes any trailing qualifiers commonly used by the Library of Congress for motion picture authorship -- that is, if "BROOKS, MEL, DIRECTION, PRODUCTION, CAST" is an additional author on a movie, the titles are removed so the search is for "BROOKS, MEL." * the Subject field becomes an ordered list, with each subject as a link to search.pl. I'll probably modify this some more to recognize " -- " and the em dash (%97) as hierarchical separators, and divide up the link, so that "PROGRAMMING -- LANGUAGES" has two links: the word "programming" as a search for that word, and the word "languages" as a search for "programming -- languages." These diffs are against the version in intranet-cgi. That version can, of course, be used in the opac-cgi location too. 10a11 > use URI::Escape; 120a122,146 > } > if ($dat->{'author'} ne ''){ > print "Author: <A HREF=\"search.pl?author="; > my $autlink=$dat->{'author'}; > $autlink =~ s/(, DIRECTION|, WRITING|, CAST|, PRODUCTION)//ig; > my $htautlink = uri_escape($autlink); > print "$htautlink\&type=opac\">$dat->{'author'}</A> "; > } > #Additional Author: > if ($additional ne ''){ > my $adstr = $additional; > my @adar = split /\s*\|/, $adstr; > print "Additional Author"; > if(scalar @adar > 1){ print "s"; } > print ": <UL>"; > my $autitem; > foreach $autitem (@adar) { > print "<LI>"; > print "<A HREF=\"search.pl?author="; > my $autlink = $autitem; > $autlink =~ s/(, DIRECTION|, WRITING|, CAST|, PRODUCTION)//ig; > my $htitem = uri_escape($autlink); > print "$htitem\&type=opac\">$autitem</A>"; > } > print "</UL>"; 122,125c148 < if ($dat->{'author'} ne ''){ < print "Author: $dat->{'author'} "; < } < #Additional Author: --- > print "\n"; 130c153,166 < print "Subject: $dat->{'subject'} "; --- > my $subj = $dat->{'subject'}; > $subj =~ s/^\s*\|\s*//; > my @subar = split /\|\s+/, $subj; > print "Subject: <OL>"; > my $subitem; > SUBLOOP: foreach $subitem (@subar) { > print "<LI>"; > print "<A HREF=\"subjectsearch.pl?subject="; > $subitem =~ s/\s*$//; > my $htitem = uri_escape($subitem); > print "$htitem\&type=opac\">$subitem</A>"; > } > print "</OL>\n"; > -- Rob Levandowski robl(a)macwhiz.com

2 1

RE: [Koha] One day to go to get this running on Windows
by Nicholas Rosasco 06 Aug '02

06 Aug '02

George has a _good_ question... actually, I've got a similar question. Has anyone else been running koha as a "standalone" (ie, not networked)? I've had some issues on Mandrake box that the install worked quite well on... except it don't seem to work right. Machine in question running on a network whose only link to outside world is MS Win connection sharing feature (which I'm guessing is NAT, or NAT like, as the linux machine claims a 192.168 ip). I'm wondering if somehow the lack of true nameserving is the issue? Or something in the virtual hosts config? Vital info: 1.2.2 Koha, Install script, Mandrake (I think 8.0 or 8.1, worst case 7 series). >I think that the install page has lagged behind the install script at this >point. the script is really 'the right way to go' at this point. If anyone knows of any issues... PLEASE tell me :) Nick ...has the httpd.conf, hosts, and assorted other files. > Is there anything else I need to do in the apache config that's > not noted on the install page. The install script for linux > shows more complicated changes being made. > Do virtual hosts have to be running properly or can I just link > to it using http://localhost??= >

1 0

hacking Koha
by Daniel Holth 05 Aug '02

05 Aug '02

I would like to enhance Koha and contribute my changes. How should I get started? My issue is not so much Perl (shield my Pythonic eyes!), it is that the downloaded source has an entirely different structure than the installed program, and if I submit a patch what's the best way to generate it, or, what is the preferred method for editing Koha? I'm using Koha with my small (50 books in the database) library. I wanted to collect the LC Call numbers for all my books so I could organize them that way. I have and they're lovely. Photo on request. Each book now bears a little label with its call number; some unnecessarily have Koha-number barcodes fastened inside. A declawed CueCat (transmits barcodes in plaintext!) example: 314293 scans; since my library doesn't circulate this is just for fun. I think I'm using RC7 right now, the database upgrade was a little scary but all in all I like it. Well, I can add members now, but my OPAC is broke. FWIW, here's (a subset of) my wishlist in rough priority order: - LC call numbers in database, display - Properly ordered collection browsing - ISBN code should handle Bookland ISBN, Bookland+5 (price) codes, then the CueCat would be useful for acquisitions. The Perl is difficult for me here. Way down the list: - More interesting info for each book (like summaries). It could be nice to be able to back up different parts of the database separately (making upgrades easier) - perhaps books, members, preferences. The rationale would be to separate the version-specific data from the more permanent data. I imagine someone is already working on separating the data edit forms into their own widget modules. It's a good idea, because right now there seem to be different versions of a couple of very similar forms. On another note, the other day I went to the public library. Mentioned 'free library system' to a librarian (after a futile quest to extract LC Call No. related information from him), librarian responds "Koha? I was thinking about using it in my church.". Great radio bit! - Daniel Holth

1 0

Re: (Fwd) Ideas for Koha
by Pat Eyler 05 Aug '02

05 Aug '02

On Mon, 5 Aug 2002, Rachel Hamilton-Williams wrote: > ------- Forwarded message follows ------- > Date sent: Mon, 05 Aug 2002 00:42:34 +1200 > From: Des <deslov(a)infogen.net.nz> > To: rachel(a)katipo.co.nz > Subject: Ideas for Koha > > Hi Rachel, > > I saw your Koha Library software site at; > http://www.koha.org/index.html > > I do not use Koha, but I have some ideas you might like; Thanks for the ideas. I wonder why you're not using Koha (yet?). Is Koha something you might consider at some point? If not, why not? (Not trying to be argumentative, just looking for places we need to improve.) > > 1) Have an interface for the data entry section that can read the > catalogue files of publishers and sales catalogues. This would save some > time for the data entry process, and also can be used to find books that > the library system does not have by an author, or on a certain topic. > > 2) Retain the older HTML page versions, for those who do not have the > latest browser, and are using old PCs. (Is this about the www.koha.org pages, or Koha itself? I'm assuming you're talking about Koha.) Using the templates (a feature that's emerging in the 1.2 release series), it would certainly be possible to create web pages that were 'old browser friendly (to a point -- if you don't support forms, it's not going to work). > > 3) What is the lowest spec PC that is reasonable for use as a client? > Can dumb clients be made up using PCs as old as 2,3,or 486? > This depends on which interface you want to use. If you can get a resonable browser running on the PC, you can run the HTML interface on nearly anything (I'm hoping to hear from someone that they've used koha on a palmtop system). If you are willing to run a telnet interface, there's no reason you couldn't run a 286 or even a dumb terminal attached to a terminal server. The telnet interface has lagged a bit, and is in need of some love at this point, but is certainly an option. > 4) Transfer of database data from one database to another. > Useful for system and hardware upgrade processess, backing up, and > sending to other branches (It is much quicker to delete the records of > non-existant books , than to have to enter the details of the books that > are present.) Some branch libraries can all be relied upon to carry > similar stock in some categories (reference, council and regional > reports, basic reader books, magazines). > > 5) The Koha website did not appear to have any email address address for > an open ended approach (which is why I used yours). It should not be > mandatory that I should fill in a two screen length form, just to give > you a few ideas. Please feel free to send email to kaitiaki(a)koha.org (or to subscribe to any of our mailing lists) to talk about ideas, Koha, or other (hopefully related) topics. thanks, Pat Eyler manager/Kaitiaki the Koha project > > Yours > Alasdair Lovatt > deslov(a)infogen.net.nz > > ------- End of forwarded message ------- > _____________________________________________________________ > > Rachel Hamilton-Williams Katipo Communications > WEBMISTRESS ph 021 389 128 or +64 04 934 1285 > mailto:rachel@katipo.co.nz PO Box 12487, Wellington > http://www.katipo.co.nz New Zealand > Koha Open Source Library System > http://www.koha.org > > >

1 0