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

Re: [Koha] Barcode scanner - keyboard wedge or not
by paul POULAIN 16 May '03

16 May '03

Waylon Robertson wrote: >P.S. Would anyone be interested in perl code that creates a form letter for an individual, for overdue books? I.e, the overdue.pl says X borrower has 3 books overdue. You click alongside one, and it >pops up with a letter with their current address, city, email, the current date, "You have these books overdue:" and underneath that, has the book name, author and due date for each.. then, at the >end says "You will incurr a fine of " <overdue fine> "for each day these books are overdue. >Signed ....................................." >Ive done this code.. so if anyones interested.. i might analysis the new template system, and see if i can create it. > > AND YOU PUT THIS IN YOUR PS !!!! I almost missed it ! It's a very interesting script ! Send it to me, and i'll will add it to official Koha release. You're lucky, feature freeze for 2.0 will occur with 1.9.3 that should be released next week, so it can be included Welcome to the Koha-contributor list :-) Note : in cvs, i've just added a "zipcode" field for complete address in most-countries-even-if-kiwis-don't-care-with-zipcode :-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Author field problem
by Lerenard Michel 16 May '03

16 May '03

Hello I am currently trying to identify the Marc Record fields we will use to fill the database. (using koha 1.9.2) The default field used to fill the author name (biblio.author) is 127z. The field does not seem to be appropriate, so we are currently using another field: 410a. But we am not satisfied with this one, which seems to be the author of the collection, not the book itself. My question is: is there another unimarc field reserved for the author name ? Thanks Michel LERENARD

3 3

Koha and RSS
by Pat Eyler 14 May '03

14 May '03

A couple of us have been playing around with creating RSS feeds from Koha. We've come up with an engine which makes this pretty simple, and will be releasing it shortly (separately from Koha proper until after Koha 2.0.0 comes out). Before we do release it, I wanted to get a bit of feedback on the idea in general. If you're impatient, you can go look at http://www.kohalabs.com/rss/ for screenshots and links. ===What is it: RSS is a method for publishing small chunks of data. The first example was a list of the 15 most recently acquired items in the database (probably nice for the avid reader/fan), a different version could be written to show recently acquired DVDs, CDs, videos, etc.. Another example shows the 15 items seen least recently by the system (perhaps they've been lost or misfiled). I'm sure that there are other potential uses for both library patrons and for library staff. Nobody wants to see the raw RSS data, but there are a number of tools (called 'aggragators') which can be used to display the information in a useful way. (The screenshots linked to above show an aggregator called evolution.) ===What kind of feedback do I want: Well, something other than 'it sucks' or 'c00l d00d!'. I'd like to know if you think this might be useful. Are there other kinds of data you'd like to see in this format? Are there things you'd like to provide to your patrons like this? thanks, -pate

1 0

sample data for 2.0
by paul POULAIN 14 May '03

14 May '03

Hi, The sample data in 1.9.2 release is badly broken. I'll remove this feature from installer for instance, as I've no working sample data. does someone around there send me a dump of a working sample-english-marc21 DB, with 200-300 biblios ? Note : if nobody has one, i'll rebuild one from the actual one, but it may be an harassing task, so it won't be for now... Note 2 : to avoid bug like bug 412, could you dump the DB with "complete" option ON. It creates longer lines, but don't cares with row changes (or fires a cool error message saying 'row XXX does not exist' : INSERT INTO marc_subfield_structure (tagfield, tagsubfield, liblibrarian, libopac, repeatable, mandatory, kohafield, tab, authorised_value, thesaurus_category, value_builder) VALUES ('090', '9', 'Numéro biblio (koha)', 'Numéro biblio (koha)', 0, 0, 'biblio.biblionumber', -1, '', '', ''); -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1

Not found : blackdot.gif...
by Jerome Vizcaino 14 May '03

14 May '03

Hello I'm experiencing this annoying message in the koha-error.log file every time I access a page in Koha [error] [client x.x.x.x] File does not exist : /home/koha/intranet/htdocs/images/blackdot.gif Can anyone tell me what this file is used for. It doesn't seem to exist in my 1.9.2 version :( It is not really a major problem but pollutes the log file with many occurences... Thanks Jerome

5 8

[PERL4LIB] Interlibrary loan (fwd)
by Pat Eyler 14 May '03

14 May '03

This is a very nice development from the world outside Koha. Anyone want to look into what it would take to get this into 2.0.1 or 2.0.2 (we're too late for 2.0.0 given the nearness of Paul's feature freeze.) -pate ---------- Forwarded message ---------- Date: Wed, 14 May 2003 09:07:39 -0500 From: david <DChristensen(a)westman.wave.ca> To: PERL4LIB(a)listserv.rice.edu Subject: [PERL4LIB] Interlibrary loan Hi everyone, Well, I've got a simple package built that allows you to create a proper GS message (Simon Fraser Univeristy was able to import it - thanks, Scott!). Before I put it up on CPAN, though.... any thoughts on what namespace it should live in? I was thinking ILL::GS, or maybe LIBRARIES::ILL::GS (but there is the confusion of book-libraries vs. code-libraries). -David Christensen

1 0

Re: [Koha-devel] Koha Intranet Interface - Navigation Question
by Rachel Hamilton-Williams 14 May '03

14 May '03

Hi Paul http://katipo.co.nz/gallery/koha/Aquisitions_1 How does this look to you? Cheers Rachel_____________________________________________________________ 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

2 1

Re: [Koha-devel] Koha, coding style and templates
by Owen Leonard 13 May '03

13 May '03

> One more idea : > in templates, how to write HTML ? ... > 3- as required in w3c html : everything in right > part of a token has "" I'd be all for making templates XTHML-Transitional. Barring full compliance with that standard, I would suggest at the very least these guidlines: - All HTML tags in lower case (HTML:Template tags in uppercase is fine of course) - All attribute values are quoted (<table border="0"> instead of <table border=0> - No 'minimization' of attributes, so <input type="checkbox" checked> is changed to <input type="checkbox" checked="checked"> XHTML requires that all tags be closed, so tags like <br> become <br /> This may be too much hassle for those who don't care about XHTML-compliance, so at minimum that 'optional' end tags be used: <p></p> <li></li> <option></option> These kind of changes are only a minor alteration in normal HTML markup writing, and will make it easier for those who want to go as far as adding the XHTML DocType and moving to full XHTML compliance. What do others think? -- Owen ---- Nelsonville Public Library Koha 1.9.2

1 0

FW: [Koha-devel] Koha, Style, and Perltidy
by Anthony W Youngman 13 May '03

13 May '03

Whoops - sent to MH only - the other list i'm a lot more frequent contributor to always sends stuff to the list regardless of which reply you hit ... Cheers, Wol -----Original Message----- From: Anthony W Youngman Sent: 13 May 2003 11:07 To: 'Mike Hansen' Subject: RE: [Koha-devel] Koha, Style, and Perltidy Paul has said what he - as a major contributor - prefers. What I would suggest is that you enforce all code committed to CVS to be run through whatever the standard "perltidy" is as it's checked in. That way you enforce consistency within the codebase. I don't know if you can make the checkout run through a similar perltidy to convert it to the relevant programmer's preferences? Certainly make sure the FAQ tells them how to make it format to their preferences. Certainly, if you demand that code WILL be run through perltidy, therefore it is a requirement that it is "perltidy friendly", then I don't see that the choice of codebase formatting is of any importance. If a programmer doesn't like the default, he simply has to use perltidy to his preferences on checkin and checkout. Cheers, Wol -----Original Message----- From: Mike Hansen [mailto:mwhansen@hmc.edu] Sent: 13 May 2003 06:58 To: Koha Devel Subject: [Koha-devel] Koha, Style, and Perltidy Hello everyone, It has been suggested a number of times before that we come up with a standard style for Koha scripts in order to make the scripts easier to read. One such way of doing this is using a program called perltidy to go through and format things in a certain style. Perltidy can read its configuration from a seperate file, which would allow us to maintain consistency within the codebase.

1 0

Koha, Style, and Perltidy
by Mike Hansen 13 May '03

13 May '03

Hello everyone, It has been suggested a number of times before that we come up with a standard style for Koha scripts in order to make the scripts easier to read. One such way of doing this is using a program called perltidy to go through and format things in a certain style. Perltidy can read its configuration from a seperate file, which would allow us to maintain consistency within the codebase. Now, there are a number of options that we should decide on before we can effectively use perltidy. I will present some of the major options here along with their alternatives and some sample pieces of code formatted with the various options. 1. Line length: This setting will prevent lines of code from exceeding a maximum number of characters. The default length is 80 columns. Do we want it do be more or less or the same? 2. Indentation: There are a number of ways that perltidy handles indentation. First, you can specify a number of spaces to ident code blocks. Shown below is the indentation set to 4 spaces: if ( $flag eq "a" ) { $anchor = $header; } We can change this value to anything we would like. We can also set it to use tabs instead of spaces to indent. 3. Opening Brace Right or Left: This setting controls where the opening brace for code blocks go. Below is an exmaple with them on the right: if ( $flag eq "h" ) { $headers = 0; } and on the left: if ( $flag eq "h" ) { $headers = 0; } Which one of these should we use? 4: Cuddled Else: The cuddled else style is shown below: if ( $flag eq "h" ) { $headers = 0; } elsif ( $flag eq "f" ) { $sectiontype = 3; } else { print "invalid option: " . substr( $arg, $i, 1 ) . "\n"; dohelp(); } while the non-cuddled else is: if ( $flag eq "h" ) { $headers = 0; } elsif ( $flag eq "f" ) { $sectiontype = 3; } else { print "invalid option: " . substr( $arg, $i, 1 ) . "\n"; dohelp(); } Which one is preferable. 5. Horizontal Tightness: This controls the spacing for items in "containers." Here are the various options: if ( ( my $len_tab = length( $tabstr ) ) > 0 ) { # -pt=0 if ( ( my $len_tab = length($tabstr) ) > 0 ) { # -pt=1 (default) if ((my $len_tab = length($tabstr)) > 0) { # -pt=2 Note that that was for parentheses. There are similar options for square brackets, curcly braces, and code block curly braces. Those are a few of the major ones; however, there are more options at http://perltidy.sourceforge.net/stylekey.html. If you can think of anything else that would be beneficial style-wise, let me know. If you would please give me your comments and opinions (preferably along with why you think that way would be best for Koha), I would greatly appreciate it. Hopefully we will be able to get a standard style for Koha from this thread. Thanks, Mike -- Mike Hansen <mwhansen(a)hmc.edu>

3 3