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

Meeting
by etome-nsr＠korksoft.com 15 Aug '02

15 Aug '02

I know a few of us are pressed for time of late, but I think we need to have a IRC meeting-- catching up on the logs I'm seeing stuff floating about undecided. MARC and Merging, some other things are waiting on decisions.... anything else? Nick ...how about next week? ------------------------------------------------- This mail sent through Korksoft WebMail http://www.korksoft.com Web Hosting Starting At $5.95/mo. WOW!

2 1

Free Software Project Approved (fwd)
by Tonnesen Steve 14 Aug '02

14 Aug '02

A Koha project has been created at Savannah. Now we just need a consensus on IF/WHEN we should move from SourceForge to Savannah. If we are planning an IRC meeting, that'd probably be the best time to bring it up. Steve. ---------- Forwarded message ---------- Date: Wed, 14 Aug 2002 18:01:05 -0400 From: nobody(a)gnu.org To: tonnesen(a)cmsd.bc.ca Subject: Free Software Project Approved Your project registration for Savannah has been approved. Project Full Name: Koha Library Automation Package Project System Name: koha Project page: http://savannah.gnu.org/projects/koha/ Please note that it may take a few hours for the system files to be updated (CVS repository creation for instance) after receiving this mail. Enjoy the system, and please tell others about Savannah. Let us know if there is anything we can do to help you. -- the GNU volunteers Post scriptum, important notes: * In order, to release your project, you should write copyright notices and license notices at the beginning of every source code file, and include a copy of the plain text version of the license. If your software is published under the GNU GPL license, you should read http://www.gnu.org/copyleft/gpl.html#SEC4 * If you plan using PHP, it would be nice to make sure it works with php3. The php4 license has restrictions that forbids distribution of modified source packages. Using PHP3 is the only way to pressure for a license change.

2 1

Re: Your message to Koha-devel awaits moderator approval
by Pat Eyler 14 Aug '02

14 Aug '02

On Wed, 14 Aug 2002, Dorian Meid wrote: > > > Pat Eyler schrieb: > > > BTW, I'm excited to hear that you're planning on working on a german > > version of Koha. Have you looked at the translation pages on the Koha > > wiki? > > What do you mean the translation pages? take a look at http://www.saas.nsw.edu.au/wiki/index.php?page=TranslationTeams and please feel free to add yourself to the page. > I've subscribed the translators mailing-list but it has verrrry low > traffic. It does indeed. Hopefully this will change as people begin working on translations ... the French version is the furthest along so far. -pate > At sourceforge I can't find a specific area up to translations. > Since I'm new to sourceforge and open-source-programming in general any > help in finding the way to the hot spots would be great. > > Dorian >

2 1

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