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

Re: SPUG: windfall -> contest (fwd)
by Pat Eyler 03 Jan '03

03 Jan '03

I've recently come into a bit of a windfall, and I thought I might try to find a way to share it a bit more widely, and this is what I came up with. I'll pass along all of the ideas that I hear about. If anyone wants to pick up one of the ideas to implement it, please feel free. -pate ---------- Forwarded message ---------- Date: Thu, 2 Jan 2003 15:45:41 -0500 From: Asim Jalis <asimjalis(a)acm.org> To: Pat Eyler <pate(a)eylerfamily.org> Subject: Re: SPUG: windfall -> contest On Thu, Jan 02, 2003 at 01:27:32PM -0500, Pat Eyler wrote: > I write the occasional book review. Recently, I asked for a > copy of 'LDAP Programming, Integration, and Management' by > Manning Press and was a bit suprised when they shipped me a > couple of copies. I asked them what to do with the other one, > and they said I should find someone in SPUG that would write a > review of it and pass the extra copy along. > > Since I figure there are likely to be a few people that would > like a free book, I thought I'd put together a quick contest to > see who gets the free copy. I also manage the Koha project (a > free software library system), so I thought I'd tie libraries, > LDAP, and maybe even Perl into the contest. > > If you'd like to review this book, please send me an idea for > using LDAP within a library system (Patron authentication is > already a work in progress). You don't need to actaully > implement your idea, but the idea should be clearly defined so > that someone can sit down and implement it in Perl for Koha. Hello Pat, I am not terribly familiar with Koha but let me try anyway. 1. LDAP could be used to determine how to contact a patron when a book they recalled was checked in or when books they had checked out became overdue or in response to other events. For example you could contact the patron using phone, page, e-mail, internet messenger, SMS. The library user could set his preferences and these could be stored in LDAP. The user might prefer to get different kinds of notifications in different ways. She/he might prefer some over SMS and others over e-mail for example. Parents might wish to be notified by e-mail when their children checked out books. 2. LDAP is optimized for "read many, write few" while databases are usually optimized for writing. LDAP could be used to store the static attributes of the books which are unlikely to change. The checkout information and other changing state information could be stored in a database. The title, author, keywords, etc. of the books could be stored in LDAP. 3. The library staff directory could be stored on LDAP. This could include names, contact information, and possibly even pictures. A front-end in Perl could access LDAP and make this information available over the web. Those are my suggestions. And yes, I would be interested in writing a review of the book. I also had a more general question. How did you get started writing reviews for technical books? Did you just write to publishers and offer your services? I am interested in doing this also and was wondering how to break into this field. Thanks. Asim

2 1

Re: [Koha-devel] koha and testing
by Ed Summers 31 Dec '02

31 Dec '02

Hi Nathan: thanks for writing. On Tue, Dec 31, 2002 at 12:44:11PM -0500, Nathan Gray wrote: > I would prefer to use Test::Debugger over Test::More. I like the > interface of Test.pm, though it doesn't handle all the scenarios I > need. I wrote a new version of Test.pm, but Test::More beat me to > CPAN. I've use Test::More quite a bit, and have really come to like it. It also comes standard in Perl 5.8 now. I could adapt to another framework though, as long as it works :) > I am uncertain whether it would be better to have a small set of test > scripts with each module, or to have one large test suite in a > central location. I'm leaning toward a centralized test suite, but > haven't grasped Koha enough to know where to start, or where the test > suite should be kept. Yes, I'm unclear on this as well. In my current work environment we've adopted the former approach: to have component tests that are easily paired with the components they test: C4/Format.pm C4/Format.t Then we have a 'smoking' program which goes and looks for all the *.t files and runs the tests. Having them split out like this is extremely useful when adding new functionality: because you know exactly where you have to go to add or modify a test. It also uses the filesystem to illustrate which components lack tests. > Definitely all the modules which interact with the database should > have tests to make sure selects, updates, deletes, inserts are all > working correctly. > > Likewise, any module which performs searches should have tests to make > sure that the correct information is returned, in the correct order. > > A test should make sure the templating system works, especially for > the various languages which are going to be supported. Yes, these are important. I guess a test database will need to be up and running for alot of these sorts of tests. > Let me know what your ideas are. Pat Eyler will be overjoyed to have > another tester on board! We'll hear from him as soon as the holidays > are past, I am assuming. He is very good about writing. > > I hope to have Test::Debugger on CPAN in a day or three. OK, I look forward to seeing it. I know what you mean about getting bogged down in work. I feel the same way, but I want to find time to work on this. //Ed -- % perl -MData::Dumper -e "print Dumper($me)" $VAR1 = { 'WEB' => 'http://www.inkdroid.org', 'NAME' => 'Ed Summers', 'AIM' => 'inkdroid', 'EMAIL' => 'ehs(a)pobox.com' };

1 0

[Bug 84] broken link
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Dec '02

27 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=84 chris(a)katipo.co.nz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 90] delbibitem.pl missing?
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Dec '02

27 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=90 chris(a)katipo.co.nz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From chris(a)katipo.co.nz 2002-12-28 15:37 ------- Oh its already fixed in the main trunk :-) Fixed in rel-1-2 now, modbibitem.pl calls deletebiblioitem.pl ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 90] delbibitem.pl missing?
by bugzilla-daemon＠wilbur.katipo.co.nz 27 Dec '02

27 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=90 ------- Additional Comments From chris(a)katipo.co.nz 2002-12-28 15:08 ------- I think modbibitem.pl should actually be calling deletebiblioitem.pl http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/koha/koha/deletebiblioitem.pl Ill fix this in the main trunk. It uses C4::Biblio so cant be used in the rel-1-2 tree. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Customizing Barcode Checkdigit Subroutine
by Larry Currie 22 Dec '02

22 Dec '02

Under our current library system, we use 14 digit patron barcodes, and the 14th digit is determined as follows: 1. Multiply every other digit starting with the leftmost by 2 and total the digits of any multi-digit product. Sum the resulting digits. 2. Add remainder of digits (every other digit starting with the second from the left). 3. Add result of step 1 and step 2 and substract the rightmost digit of the sum from 10 to obtain the check digit. Example: Given: 2 1 1 1 2 0 0 0 6 9 8 1 3 C (C to be determined) (mult by 2) 4 2 4 0 12 16 6 sum = 26 step 1 1 1 0 0 9 1 sum = 12 step 2 Step 3: 26 + 12 ----- 38 10 - 8 = 2 = check digit. Back in January, I tried to modify the checkdigit subroutine of Input.pm to fit our circumstances, but I'm not sure that my code was completely successful. Would anyone want to take a shot at modifying this subroutine to fit our circumstances, since we would like to use our existing patron barcodes in Koha? Larry Currie -- Lawrence W. Currie User Services Librarian California Academy of Sciences Golden Gate Park San Francisco, CA 94118 lcurrie(a)calacademy.org (415) 750-7108 (415) 750-7106 fax http://www.calacademy.org/research/library/

2 1

modif in gettemplate
by paul POULAIN 20 Dec '02

20 Dec '02

I just commited a little modif in gettemplate. It now auto-replaces theme and lang template variable. This is useful if you have images in your template : <img src="/<TMPL_VAR name="theme">/<TMPL_VAR name="lang">/images/picture.gif> or <img src="/<TMPL_VAR name="theme">/images/picture.gif> in the case of a non-language dependant image. Before this fix, gettemplate only replaced a variable called themelang, which was useful for language dependant images, but didn't work with theme-only images. Note the previous behaviour is still activated (ie : themelang still works) Note also that at the moment, "common" images are not managed (even small background pictures are copied in /en, /fr and /es languages directories. This will have to be fixed for 2.0. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://fr.koha.org)

1 0

Re: [Koha-devel] Koha Serials Wiki
by Saiful Amin 20 Dec '02

20 Dec '02

Greetings, > I am a big believer in lots of keywords...... > > I wonder if there would even be enough room to jam the table of > contents for the journal in the key word area ! Ideally the table of contents (TOC) should be reflected in the Article Indexes, which is a recommended feature. Not all the libraries require this feature of course. Table of contents are used for giving Current Awareness Service (CAS), which we can use for indexing the articles. It would be nice if Koha can enable giving such CAS as a by-product rather than vice-versa. Simply adding the TOC to the keyword area might compromise search precision. > > ed sharpe archivist for smecc > >> I have just created a Wiki for the requirements in the Serials module >> in Koha. Please add your suggestions at: >> >> http://www.saas.nsw.edu.au/wiki/index.php?page=KohaSerialsModule Saiful -- DRTC Bangalore, India.

1 0

Koha Serials Wiki
by Saiful Amin 19 Dec '02

19 Dec '02

Hi all, I have just created a Wiki for the requirements in the Serials module in Koha. Please add your suggestions at: http://www.saas.nsw.edu.au/wiki/index.php?page=KohaSerialsModule Saiful -- DRTC Bangalore, India.

1 0

[Bug 148] Library branches with apostrophes in name can't be edited
by bugzilla-daemon＠wilbur.katipo.co.nz 19 Dec '02

19 Dec '02

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=148 paul.poulain(a)free.fr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From paul.poulain(a)free.fr 2002-12-20 02:46 ------- the easiest way is to just do an $test =~ /"/"/g; $template->param(test => $test); so the output would be <input type="text" name="test" value="here is "daddy""> another way is to use HTML::Templates escaping capabilities like this: <input type="text" name="test" value="<tmpl_var name="test" escape="HTML">"> which does roughly the same but with more translations. This should be the prefered solution, if you don't need extended capabilities. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0