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

Fines chargename field
by Jack 24 Aug '06

24 Aug '06

Dear Chris I am currently working on the fines system. At present I am looking at the chargename field, it seems this is no longer used anymore, is that right? Is anyone working on re-writing the fines and accounts system? If not this is somthing I would not mind doing as the original is a litle sparce. Thanks Jack I have changed the fines system in our Koha to work in the following manner : I have changed the fines in the following ways, please check them and let me know if they are correct. Definition >> days_overdue = the number of days that the item has been overdue. Sundays > We dont fine people on Sundays, thus, if the item is 7 or more days overdue, Koha looks at the total no of days the item is overdue, divides it by 7 which gives us the integer number of weeks the item has been overdue. We then subtract this integer number of weeks from the days_overdue amount, as each week has one Sunday. We then subtract one more day from the days_overdue to allow for the fact that we dont fine people for the first day that the item becomes overdue. Thhe fines will be run on Mon, Tue, Wed,Thur and Fri. Each time the fines are run the process is as follows > 1. Item is 2 or more days overdue : When an item has been overdue for 2 or more days a new fines account is created for the item and is updated each day from then on until the item is returned. This is the first account created for the overdue item. The name of the account in the borrowers record will be "Overdue Fine > >" From now on this account will always hold the fines for the item for as long as it is overdue. 2. Item is 7 or more days but less than 14 days overdue : If the item has been has been over due for 7 or more days AND the first fines letter has NOT been sent we will generate the first fines letter for that item. NO new account will be created and the existing account will be updated with the fact that the first letter has been generated. The fines for the item will continue to build on a daily basis until either the item is returned OR the maximum fine amount of $10 is reached. The name of the account in the borrowers record will now be "Overdue Fine > letter_no=1 >.... " to reflect the fact that the account is for overdues fine and the first letter has been sent. If the max fine limit of $10 is reached the fine will remain at $10 from then on. 3. Item is 14 or more days overdue but less than or equal to 35 days overdue : If the item is 14 days overdue AND the second fines letter has NOT already been sent, we will send out the second fine letter. The borrowers record will be updated with the fact that the second fine letter has been sent. NO new account will be created and the existing account will be updated with the fact that the first letter has been generated. The name of the account in the borrowers record will now be "Overdue Fine > letter_no=2 >.... " to reflect the fact that the account is for overdues fine and the second letter has been sent. The fines for the item will continue to build on a daily basis until either the item is returned OR the maximum fine amount of $10 is reached. If the max fine limit of $10 is reached the fine will remain at $10 from then on. 4. Item is more than 35 days overdue but less than or equal to 60 days overdue : If the item is MORE than 35 days overdue AND the third fines letter has NOT already been sent, we will send out the third and final fine letter. From this point on the item is considered lost. Thus the itemlost field in the items table in Koha will be set to 2 ( which means the item is long overdue ). And from then on Koha will treat the item as being lost. The borrowers record will be updated with the fact that the third fine letter has been sent. The name of the account in the borrowers record will now be "Overdue Fine > letter_no=3 >.... " to reflect the fact that the account is for overdues fine and the final letter has been sent. Two new accounts will be created for the newly lost item : 1. Processing fee account > This account holds the non-refundable processing fee for the item. This account will be called "Non refundable processing fee for lost item.". 2. Replacement Account > This account holds the replacement value of the item and is effectively a bill. The account will be called "Lost Item Replacement Bill >..." The fines for the item will continue to build on a daily basis until either the item is returned OR the maximum fine amount of $10 is reached. If the max fine limit of $10 is reached the fine will remain at $10 from then on. Lost Item Search List >> Koha will generate a lost item search list for each branch that will list all of the newly lost items sorted by dewey. This can then be used to do one final shelf check before sending out the final letter.

1 0

[Fwd: Re: [Koha-devel] Koha Barcode Generation]
by Pedro Faria 24 Aug '06

24 Aug '06

Joshua Ferraro escreveu: > Hi Pedro, > > On Thu, Aug 24, 2006 at 11:57:02AM +0100, Pedro Faria wrote: > >> I am using koha 2.2.5. Does anyone, using this version or other, have >> barcode generation working? >> > There's a new barcode generation module that will ship with 2.2.6, > the old one is unmaintained. If you'd like to see the new version, > please visit the LibLime demo: http://koha.liblime.com and click > on _Spine and Barcode Labels_: > > http://koha.liblime.com/cgi-bin/koha/label-home.pl > > Make sure you specify 'Code39' as the type. > > In other news, we're going to be releasing another version of the > barcode generation tool soon that will, like the old one, allow > you to specify the settings of your barcodes (size, type, etc.), > rather than rely on a limited set of supported types. > > Hope that helps, > > -- > Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE > President, Technology migration, training, maintenance, support > LibLime Featuring Koha Open-Source ILS > jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS > I tried it in the site you showed me and it looks preety good. But where can I find Koha 2.2.6? I found onlu 2.2.6rc2 which I believe it is not a "stable" version. Is there any isse using koha with mysql 5. I found some problems with sintax in sql statements. Is this going to be fixed? By the way, thank you for helping.

1 0

kohadocs.org Updates
by Joshua Ferraro 24 Aug '06

24 Aug '06

Hi all, Stephen has just finished a new version of the index page for kohadocs.org. This one validates, and all the style information has been moved to the css file (submissions for a new stylesheet are therefore welcome ;-)). Thanks Stephen! Additionally, the new index page links to the new Arabic documentation as well as documentation on the Katipo corpSerials module that is finished and will appear in 3.0. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Koha Barcode Generation
by Pedro Faria 24 Aug '06

24 Aug '06

I am using koha 2.2.5. Does anyone, using this version or other, have barcode generation working? If so, could you aswer attaching barcodeGeneration.pl? All I get so far (following previous help) is a file recognized as HTML wich I must open in web browser to be able to open it in pdf view and all I see is a small label , no black and white bars! Please, any help! Thanks to all

2 1

[Fwd: Re: [Koha-devel] Problems with barcode generation]
by Pedro Faria 24 Aug '06

24 Aug '06

Michael Hafen escreveu: > I had the same problem. To get the barcodes I had to use a different > function entirely. > > I've actually made a lot of changes to this script, but I will post the > relevant bit for your benefit. > > ------------- CUT -------------- > > my $zone = length($code) - 5; > my $barcode = $pdf->xo_3of9(-font => $tr, # The font object to use > -code => $code, # Text to codify > -ext => 1, # extended character set > -extn => '012345', # Barcode extension (if it is aplicable) > -umzn => 9+$zone, # Top limit of the finished bar > -lmzn => 9+$zone, # Bottom limit of the finished bar > -zone => 3+$zone, # Bars size > -quzn => 0, # Space destinated for legend > -ofwt => 0.5, # Bars width > -fnsz => 9, # Font size > -text => '' > ); # umzn +, lmzn +, zone +7 > > # Assigns a barcode to $gfx > my $scale = ($labelConfig{'labelWidth'}-2)/$barcode->width(); > $gfx->formimage($barcode, $x, $y, $scale); > # Assigns the additional information to the barcode (Legend) > if ($text_under_label) { > my @lines = split("\n",$text_under_label); > $title = $lines[0]; > $author = $lines[1]; > } > while ($text->advancewidth($title) > ($labelConfig{'labelWidth'} - 2)) > { > chop $title; > } > while ($text->advancewidth($author) > ($labelConfig{'labelWidth'} - > 2)) { > chop $author; > } > > my ($x_adjust_1, $x_adjust_2, $y_adjust) = (0, 0, 0); > if ($text->advancewidth($title) < ($labelConfig{'labelWidth'} - 5)) { > $x_adjust_1 = (($labelConfig{'labelWidth'} - 2) - > $text->advancewidth($title)) / 2; > } > if ($text->advancewidth($author) < ($labelConfig{'labelWidth'} - 5)) { > $x_adjust_2 = (($labelConfig{'labelWidth'} - 2) - > $text->advancewidth($author)) / 2; > } > $y_adjust = ($labelConfig{'labelHeigth'} - $barcode->height - 18) / 2; > $y_adjust = 5 if ($y_adjust < 0); > $y_adjust += $barcode->height; > > $text->translate($x + $x_adjust_1, $y + $y_adjust + 9); > $text->text($title); > $text->translate($x + $x_adjust_2, $y + $y_adjust); > $text->text($author); > > ------------- CUT -------------- > > Hope that helps. > > > > ------------------------------------------------------------------------ > > Assunto: > SPAM- [Koha-devel] Problems with barcode generation > De: > Pedro Faria <pjf(a)eurotux.com> > Data: > Wed, 23 Aug 2006 18:10:09 +0100 > Para: > koha_mailing_list <koha-devel(a)nongnu.org>, koha(a)lists.katipo.co.nz > > Para: > koha_mailing_list <koha-devel(a)nongnu.org>, koha(a)lists.katipo.co.nz > CC: > > > Dear all,f - Numéro d'inventaire > Want to thank Henri-Damien LAURENT to fabulous help! > Now I am trying to generate barcodes. > First I wanna know if "Inventory code" asked to generate the barcode > is the same that we enter when adding an item (f - Numéro d'inventaire > in additem.pl)? Because I give the same number (1000) and it says that > there was any with that code (using Individual Codes in generator). If > I select Continuous Range of Items from 0 to 1000 it proceeds...A bit > odd :). Any ideas? > > However it still was not ok. First I had to change some scripts > becouse PDF::API2 has changed a bit and things are not anymore in the > same place (e.g PDF::API::Utils is now PDF::API2::Basic::PDF::Utils). > This I figured out myself. But now I got > > Can't locate object method "barcode" via package "PDF::API2::Content" > at /usr/local/koha/intranet/cgi-bin/barcodes/barcodesGenerator.pl line > 259 > > and this one I still couldn't solve. Anyone can help? > > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)nongnu.org > http://lists.nongnu.org/mailman/listinfo/koha-devel > ------------------------------------------------------------------------ > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)nongnu.org > http://lists.nongnu.org/mailman/listinfo/koha-devel > thax for aswering. Can you attach the full barcodeGenerator.pl? This piece of code should replace the code under continuous generation 'if' and the correspondant 'else'?

1 0

Problems with barcode generation
by Pedro Faria 24 Aug '06

24 Aug '06

Dear all,f - Numéro d'inventaire Want to thank Henri-Damien LAURENT to fabulous help! Now I am trying to generate barcodes. First I wanna know if "Inventory code" asked to generate the barcode is the same that we enter when adding an item (f - Numéro d'inventaire in additem.pl)? Because I give the same number (1000) and it says that there was any with that code (using Individual Codes in generator). If I select Continuous Range of Items from 0 to 1000 it proceeds...A bit odd :). Any ideas? However it still was not ok. First I had to change some scripts becouse PDF::API2 has changed a bit and things are not anymore in the same place (e.g PDF::API::Utils is now PDF::API2::Basic::PDF::Utils). This I figured out myself. But now I got Can't locate object method "barcode" via package "PDF::API2::Content" at /usr/local/koha/intranet/cgi-bin/barcodes/barcodesGenerator.pl line 259 and this one I still couldn't solve. Anyone can help?

2 1

UTF-8 problems : a summary and some solutions
by Henri-Damien LAURENT 23 Aug '06

23 Aug '06

Hi, I investigated quite hard into finding a solution to our utf-8 problems. It seems we CAN come to a solution. What is the problem ? ------------------------------ On my right : values from xml records utf-8 encoded. Correctly displaying them is only a matter of making PERL aware of the fact that he is using utf-8 values, that is : - either use perl -CS or perl -CIOE instead of just simple perl on the first line of the script. That toggles perl into utf-8 for STDINPUT, STDOUTPUT and STDERR. - or add binmode STDOUT, ":UTF-8" or binmore STDOUT, ":utf8" (Be warned that those two different descriptions ARE NOT equivalent. see http://perldoc.perl.org/Encode.html#UTF-8-vs.-utf8 I would suggest that we always use utf8 rather than UTF-8) Simple, clear, efficient (remember though to use libxml2 as stated Joshua in a previous mail http://www.nntp.perl.org/group/perl.perl4lib/2369) On my left : values from Mysql coded in utf-8 and stored as such in MysqlDatabase. When using ("SET names=UTF-8") on the database just after the connection, Everything goes... WELL !!!! Bibliothèque   ¥ · £ · € · $ · ¢ · ₡ · ₢ · ₣ · ₤ · ₥ · ₦ · ₧ · ₨ · ₩ · ₪ · ₫ · ₭ · ₮ · So What is the problem ???? The problem is that left goes well PROVIDED that you DONOT set binmode STDOUT,":utf8" and PERL believes he is processing ISO-8859-1 data. If you launch test_mix.pl on your system without perl -CS : xml data wil be badly displayed BUT Mysql data Well displayed !!! <datafield tag="200" ind1=" " ind2=" "> <subfield code="a">(L') �ole des p�es</subfield> <subfield code="b">R</subfield> <subfield code="f">Bazin, Herv�/subfield> </datafield> <datafield tag="210" ind1=" " ind2=" "> <subfield code="c">�itions du seuil</subfield> </datafield> If you launch test_mix.pl on your system with perl -CS : xml data will be well displayed BUT Mysql data badly (encoded TWICE) !!! BibliothÃ¨que   Â¥ Â· Â£ Â· â¬ Â· $ Â· Â¢ Â· â¡ Â· â¢ Â· â£ Â· â¤ Â· â¥ Â· â¦ Â· â§ Â· â¨ Â· â© Â· âª Â· â« Â· â Â· â® Â· OK. we've got a problem. Where does it come from ? It comes from DBD::mysql and DBI which provides utf-8 data to PERL without Telling him. In perl, Utf-8 data has a flag that tells OK, I am utf-8. If this flag is not set and output is UTF-8 Perl will "magically" but unfortunately re-encode the values. See http://www.mail-archive.com/dbi-dev@perl.org/msg04319.html and following... Solutions. ------------- you can have a look at http://www.simplicidade.org/notes/archives/2005/12/utf8_and_dbdmys.html There are three solutions : - find out EVERYWHERE in the code we receive data from mysql and set the flag on |if (! utf8::is_utf8($message)) { utf8::decode($message); }| Is there a volunteer ? ;) - patch DBD-MYSQL code so that it makes perl utf-8 aware and use {*"*mysql_enable_utf8*"*=>1} options when connecting to database. There is a patch here (version 2.90008 http://lists.mysql.com/perl/3563 and here http://rt.cpan.org/Public/Bug/Display.html?id=17829 version 3.000006 ) And it seems that people in the DBD-MYSQL team will incorporate this patch in next DBD::mysql version. - Use (http://dysphoria.net/2006/02/05/utf-8-a-go-go/) UTF8DBI.pm for any database connections rather than DBD-mysql. Advantage : If we incorporate those package tightly to C4 and Koha, we may improve UTF-8 compliance and stability. Disadvantages : Module is not supported by anyone, not official, and would require quite HEAVY transformations in our code. You may have felt which solution seems to me the most reasonale one. The only problem being... Are we finished with utf-8 problems ? I HOPE So. But we can reasonably think there still may be hidden ones. Why ? - http://www.mhonarc.org/archive/html/perl-unicode/2006-07/msg00004.html and http://www.mhonarc.org/archive/html/perl-unicode/2006-07/msg00008.html seems to point out some CGI input problems with UTF-8. (It is a fact I DIDNOT test data input with binmode UTF-8 set or with the DBD-MYSQL hack.) So I go on testing. If you need test files, you can get them on http://hdlaurent.paulpoulain.com/test_mix.pl http://hdlaurent.paulpoulain.com/test_mix_fixed.pl http://hdlaurent.paulpoulain.com/testsrecord.xml -- Henri-Damien LAURENT

2 4

Adding item e - niveau de localisation
by Pedro Faria 23 Aug '06

23 Aug '06

Dear all, I'm trying to add an item to Koha, from a MARC record via z3950 searches. It works fine till the moment of filling in mandatory fields in .../cgi-bin/koha/acqui.simple/additem.pl?bibid=6&frameworkcode= there is one, namely e - niveau de localisation which does not have any value to choose from? What is this value? Where can I add values to that dropdown box? Other question? Why are some templates in french, even when I choose only en language?

1 0

Testing Z3950 searches
by Pedro Faria 22 Aug '06

22 Aug '06

Dear all, I am having serious problems with Z3950 searches. I'm trying to make some searches on pre-added z3050 searches but it keeps giving No results found when it should give some results! I read something about a deamon which is in koha/intranet/scripts/z3950daemon/ . Can someone explain me what I need to do to set this up?

1 0

Re: Re Re: [Koha] Koha reports not working
by Mohamed Imran K R 22 Aug '06

22 Aug '06

Hi i have attached the Auth.pm file. pls look into the same and solve my ldap query the problem it does let the users in to opac, but it gives out a warning in the logs as [Tue Aug 22 14:54:29 2006] [error] [client 192.168.1.2] LDAP Auth failed server not responding or wrong user password [Tue Aug 22 14:54:29 2006] [error] [client 192.168.1.2] combination at /usr/local/koha/intranet/modules/C4/Auth.pm line 529. i checked the members section on the lib interface and it has indeed added a user. also i am not able to fetch any data from my ldap server and populate the koha db pls do look into this On 8/22/06, Chris Cormack < chris(a)katipo.co.nz> wrote: > > Henri-Damien LAURENT wrote: > > Mohamed Imran K R a écrit : > >> there are thousands of users and more provisioned. so i just want the > >> changes to be reflected as and when the users change info about > >> themselves. for manual sol, i have to synchronize every now & then > >> hoping that there is no loss. > >> > >> the koha ldap module fetches & fills in the data from the ldap into > >> the borrower table of koha db. i dont how is it related to MARC! > > It is not. > > koha_ldap modules, as far as I know, was designed by someone who needed > > it once, neither by me nor by paul (iirc). And it seems NOT populating > > borrowers table with data from LDAP. LDAP is merely used as a login > > facility. > > > > > > But paul will come back next week I can ask him. > Hmmm > > Looking around line 575 it seems that it updates the borrowers table, or > creates a new borrower if one doesnt exist. > > But we should probably continue this discussion on the koha-devel list. > > Chris > -- Regards Mohamed Imran K R

2 2