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

circulation rules and renewal periods
by Ignacio Javier 21 Apr '08

21 Apr '08

Hi everybody: Can currently be defined in koha periods for renewals per user and itemtype? Greetings, Ignacio Javier | Desarrollador Software Factory Coremain S.L.U. Parque Empresarial Costa Vella Rúa de Amio 128 15707 Santiago de Compostela Tlf. 902 90 55 90 ignacio.gomez(a)coremain.com www.coremain.com La información contenida en este mensaje y sus posibles documentos adjuntos es privada y confidencial y está dirigida únicamente a su destinatario/a. Si usted no es el/la destinatario/a original de este mensaje, por favor elimínelo. La distribución o copia de este mensaje no está autorizada.

1 0

Re: interest in improving automated tests with a testing database
by Andrew Moore 18 Apr '08

18 Apr '08

Hi again Koha developers - Galen and I just submitted a few patches that implement this new testing method. I'm interested in any feedback you have before they're committed. http://lists.koha.org/pipermail/koha-patches/2008-April/000172.html http://lists.koha.org/pipermail/koha-patches/2008-April/000171.html http://lists.koha.org/pipermail/koha-patches/2008-April/000173.html http://lists.koha.org/pipermail/koha-patches/2008-April/000174.html http://lists.koha.org/pipermail/koha-patches/2008-April/000175.html These create a new t/Makefile which runs a t/database_dependent.pl test script which creates a test database and runs some automated tests against it. Those tests are in the new t/lib directory and use Test::Class to organize and run them. The way that you use this is to re-run the top level 'perl Makefile.PL' which will prompt you for some information about a test database that can be built. Then, you can 'cd t' and run 'make test' in there. This will make sure that your new test database is created and used for the test suite. I expect that eventually this process will be made easier, but this is a first stab at a solution, and I'm trying to avoid interfering with normal installation as much as possible. I'm interested in hearing suggestions about how the process of setting up the database and running the zebra stuff works. I'm also interested in hearing about any of these tests that fail. I may take the opportunity to fix some of these before the code is committed, or fix them later. Thanks for your help. -Andy On Thu, Mar 27, 2008 at 1:43 PM, Andrew Moore <andrew.moore(a)liblime.com> wrote: > Hi Koha developers - > > I have caught some of you on IRC and such, but for the rest of you, > I'm a new developer at LibLime working on Koha. > > I'm interested in improving the automated test suite a little bit, and > I'm hoping to get some feedback from any interested developers and > users. There are some database specific tests in the t/db_dependent > directory, but I think they can be improved quite a bit. I'll lay out > what I'm picturing, and please let me know if you picture a different > plan, or have any ways to improve this one. > > I'd like to have a 'make' target similar to 'make test' that would > build a nearly empty, skeleton database that we could run some > automated tests against. Since this would not be the same database > that live data is held in, we wouldn't have to worry about deleting or > overwriting any useful data. The testing could insert example data and > data known to trigger past bugs to ensure that they don't recur. I > don't imagine making this a standard part of 'make test', at least at > first, since I don't imagine that all end users want to have a second > database built just to test against. I think it could be immensely > useful for us developers, though, right away. > > One useful way I've seen this done in the past is trough the use of > the Test::Class perl module. It's similar to the xUnit framework (or > jUnit or nUnit) in that it lets you run a bit of code before and after > each test to set up the environment (the test fixture). That way, you > can ensure that the database looks clean between when different pieces > of the test suite runs so that one test script doesn't interfere with > another. It also lets your test scripts inherit from each other so > that similar test scripts can share the same code to set up their > fixtures. > > I have a small working prototype of this, but before I get much > further, I want to ask if you have any suggestions or advice for this. > Please let me know if this sounds like something that would be useful > to you, and if there's anything I need to make sure I consider. > > Thanks, > -Andy > _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

1 0

Authorities searching (3 things)
by Paul POULAIN 18 Apr '08

18 Apr '08

Hello, 3 questions/problems/suggestions : === 1 === Previously, one could search on authorities : - on the $a of the heading. Useful to find "Mister John" by not having all firstname "john" - on the heading itself - anywhere in the authority Those 3 possibilities are still in the staff client, but ... the underlying code treat $a as "Heading", and the result is the same as for heading. I don't know in MARC21, but in UNIMARC, the possibility was very important and interesting. I volunteer to reintroduce it, but I must know if it has been removed by mistake, or if there is something specific to MARC21. === 2 === Ordering authorities. Actually, the order is done on heading $a. That's not enough : when you search the author "Martin" (our french "Doe"), you get zillions results, unordered on the firstname. So we need to introduce a 2nd level of ordering. In UNIMARC, usually on the $b of the heading. === 3 ==== the authority-search.inc : there are 3 tabs, to search on heading ($a), heading, anywhere. libraries prefer the previous interface, that displayed the 3 lines, to show that you can search : heading ($a) : _______________ Heading : _______________ Anywhere : _______________ and you can search the 3 simultaneously. for example : heading ($a) : john, heading : Owen will find only surname john and firstname owen. the new behaviour is not clear enough for the users imo. how could we reintroduce the clear choice of the 3 input fields available at the same time ? Your opinion welcomed. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 2

Installing on Ubuntu 7.10
by Ed Veal 18 Apr '08

18 Apr '08

I am attempting to install Koha on Ubuntu 7.10 and am getting some dependency errors. I have solved most of them but still have a few outstanding. Here is what I am getting after I run installer.pl +++++++++++ MISSING PERL MODULES You are missing some Perl modules required by Koha. Please run this again after installing them. They may be installed by finding packages from your operating system supplier, or running (as root) the following commands: export LC_ALL=C perl -MCPAN -e 'install "ZOOM"' perl -MCPAN -e 'install "You will need Net::LDAP if you want to authentify patrons through a LDAP"' ++++++++++++ I have tried running the above commands from root but still get errors. Any assistance? Ed **************************************************************** Edward Veal (eveal(a)mail.ci.lubbock.tx.us) System Administrator Lubbock Public Library http://www.lubbocklibrary.com Mahon Library 1306 9th St. Lubbock, TX 79401 voice: 806-775-2849 fax: 806-775-2827 *******************************************************************

3 2

RFC : Subscription management : Getting a more scalable way to manage numberings
by Henri-Damien LAURENT 14 Apr '08

14 Apr '08

Hi, I am planning to adapt subscription-add.pl in order to get rid of bugs that makes subscription-add quite a burden to use. 1st : one cannot add a new numbering method friendly 2nd : One HAS to click on irregularities and re enter irregularities any time one edits the subscription. 3rd : Nonnumerical method is strange to me. To accomplish 1st and 3rd, I propose to add those tables : ***frequency table :*** id label : short description Unit : day/week/month/year frequency (integer defaulted to 1, would record the count of days for a bi-weekly for instance.) issuesperunit expectedissuesperyear ***numberingpattern table :*** id label : tinytext(256) description : text add1 numbering1 every1 whenmorethan1 setto1 basedonpublisheddate1 add2 numbering2 every2 whenmorethan2 setto2 basedonpublisheddate2 add3 numbering3 every3 whenmorethan3 setto3 basedonpublisheddate3 basedonpublisheddate : This field would allow people to begin a subscription in the middle of the year without having to edit the numbering table to edit lastvalues and innercounters. ***nonnumericalnumbering table :*** code number labeltodisplay Example : season 0 Spring season 1 Summer season 2 Fall season 3 Winter day 0 Sunday day 1 Monday day 2 Tuesday day 3 Wednesday .... daytime 0 morning daytime 1 noon (would it be useful ?) daytime 2 evening month 0 January .... But this solution would not solve : - roman numeration for more than ten elements, unless the table would get huge. Moreover, I couldnot get a PERL module managing numbers to roman numbers conversion. But I cannot think it has not already been done. - period from date to date displaying (i.e. From 2. to 9. February, for a weekly issue) And add those fields to subscription table : numbering1, numbering2, numbering3 : If not NULL, then is filled with a Code from nonnumericalnumbering table and will be used in GetNextSeq. countperunit : records the count of issues per day/week/month so that it could be recorded (Date::Calc donot allow floats date adding. For instance, say : I receive a subscription twice a day, I have to count how many times I have received this subscription before adding a new day) then we would pass the tables in Js and use them to create our numbering. fixedissuedates : If a subscription is irregular BUT has fixed dates for release, will store figures like irregularities receive on 1 and 3rd day of week, 1st and 3rd day of month, .... depending on frequency. Irregularities would be optional and display in a window the expected issues periods based on frequency and one could check the periods an issue is not published. -- Henri-Damien LAURENT

1 0

locale dependencies and perl
by Ignacio Javier 14 Apr '08

14 Apr '08

Hi developers, just a thing I thought could be very interesting, please read this in a latin1 capable e-mail agent: Aparently marc8 records with latin1 extensions are being correctly stored in database, when marc8 is specified as source encoding, for z3950 records that come in that format. *** Well..., not so. *** Internet Explorer renders correctly the not so correct marc8 to utf8 transformation where chars from latin1 character repertoire are recognized in the transformation. What is really doing koha, when doing marc8 decoding/MARC21, is to store in database a sequence of: base character + unicode form of (tilde|cute|grave...etc) ...that is: a´, a`,n~, etc... ...with ` or ´ or etc... in UTF-8 (using 3 native bytes instead of 2 native bytes) Instead of: á, à, etc... (2 native bytes) Internet Explorer, not surprisingly for me, renders a´ as á, etc... but no other tools do it this way, for example firefox renders í as i with an upper to the dot acute. Ignacio Javier Gómez Rodríguez Analista - Programador Tfno: 902905590 - Fax: 981571425 ignacio.gomez(a)coremain.com www.coremain.com _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 2

Koha 3 Beta 2 - Second step of Web Installer returns blank page for Portuguese language (pt-PT)
by Ricardo Dias Marques 14 Apr '08

14 Apr '08

Hi list, I'm finishing my installation of Koha 3 ("Beta 2"), in a virtual machine - that I created from scratch (again) - running Linux (openSUSE 10.3). I'm using the "default" Apache (2.2.4) and the "default" MySQL (5.0.45). After I managed to: 1- run perl makefile.PL 2 - install all the required package dependencies (Perl packages - mostly from CPAN - and RPM packages) 3 - create the koha (MySQL) database and the kohaadmin user and the koha system user 4 - run make test and make install 5 - ... I finally reached the first step of the Web Installer, available at: http://hostname:8080/cgi-bin/koha/installer/install.pl That took me to a login screen. I logged in with my kohaadmin username and password (using Mozilla Firefox). That worked and took me to the "Web Installer > Step 1" page (the URL remained the same), to choose a language from a dropdown list. I gladly saw that "famfamfam" is NO longer available as a language - see http://lists.koha.org/pipermail/koha-devel/2008-April/007395.html - and that, now, a long list of languages appear, including pt-PT (for Portuguese), which appears in second place in the list! :) HOWEVER, if I select that "pt-PT" language and then click the on the "Next >>" button, I get a BLANK page. The URL stays the same. If I view the HTML source of that page, I also get no output. Then, I checked the Koha error log, located at: /var/log/koha/koha-error_log I saw the following output: _________________ [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.language_descriptions' doesn't exist at /usr/share/koha/lib/C4/Languages.pm line 324. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/C4/Languages.pm line 325. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: Use of uninitialized value in string eq at /usr/share/koha/lib/C4/Languages.pm line 297. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.language_descriptions' doesn't exist at /usr/share/koha/lib/C4/Languages.pm line 318. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/C4/Languages.pm line 319. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.language_descriptions' doesn't exist at /usr/share/koha/lib/C4/Languages.pm line 324. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at /usr/share/koha/lib/C4/Languages.pm line 325. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: Use of uninitialized value in string eq at /usr/share/koha/lib/C4/Languages.pm line 297. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: DBD::mysql::st execute failed: Table 'koha.systempreferences' doesn't exist at /usr/share/koha/intranet/cgi-bin/installer/install.pl line 705. [Wed Apr 09 20:15:16 2008] [error] [client 191.112.105.34] [Wed Apr 9 20:15:16 2008] install.pl: HTML::Template::Pro:template /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/pt-PT/modules/installer/step1.tmpl not found! at /usr/share/koha/intranet/cgi-bin/installer/install.pl line 714 ________________ That last line of the output made me think that maybe there was a missing folder for "pt-PT" under /usr/share/koha/intranet/htdocs/intranet-tmpl/prog In fact, by doing a "ls -1 /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/" (-1 stands for single column output), I get the following output: de-DE el-GR en es-ES es-VE fr-FR hu-HU hy-Armn img kn-Knda lo-Laoo nb-NO nl-NL nn-NO pl-PL ru-RU sr-Cyrl sv-SE tr-TR uk-UA zh-Hans-CN zh-Hans-TW So, I think there should be a "pt-PT" directory there, but it seems to be missing. Am I right? Thanks in advance! Best wishes, Ricardo Dias Marques lists AT ricmarques DOT net

4 8

Koha 3.00Beta, language template provided (to joshua)
by paul POULAIN 13 Apr '08

13 Apr '08

Hello Joshua, I just see that in the 3.00beta package, the templates are not provided in the different languages. Thus, to get Koha 3.00beta in French, you have to use tmpl_process3.pl and generate the french templates. This is not explained in the install notes, unless i'm mistaken Have I missed something ? why didn't you generate localized templates before releasing ? I think, at least for a stable version, we should provide localized templates, even at the prize of a .tar.gz growth cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

2 1

changing the language files localy
by Axel Bojer 12 Apr '08

12 Apr '08

Hi! We have successfully installed Koha beta2, and are proof reading it now. What would be nice were if we could change the language files manually on our installation, just to check our translation before we submit it toy you. Is this possible? For other programs there are *.mo-files in /usr/share/locale-langpack/ but there are no koha/staff/opac-files there. All I find is tmp-files with some localised language-strings, like: nb-NO/modules/installer/auth.tmpl I suppose this mean the answer to my question is now, then? So, if not: Will the language files be updated for the RC-versions? If yes, when is then the last day we can send new language files for RC1? Best regards Axel Bojer

2 2

FW: [Koha] Fines for Short Loan Items
by Bernard Shiundu 12 Apr '08

12 Apr '08

Bumped into the mail below on the general list, just cross-posting with a small comment/question I had this same issue and solved it in rel2_2 (which I'm currently running in production) by porting the reserve circulation code from koha neu. The way it worked/works is that items circulating on the hour are issued in a separate circulation module (similar to the 'normal' one) with the data being stored in reserve circulation table and overdue fines being calculated on the fly and posted to accountlines when the item is returned rather than as a cron job. Before I start working on porting it to Koha 3 and submitting my code, is anybody working on this for Koha 3? Don't want to re-invent the wheel ;) ====================== Bernard Shiundu Systems Librarian, Strathmore University ________________________________ From: Ayoku Ojedokun [mailto:aaojedokun2003@yahoo.co.uk] Sent: Friday, April 11, 2008 11:35 AM To: Koha Mailing List Subject: Re: [Koha] Fines for Short Loan Items If this is the case, I suggest that the issue be looked into. Jesse <pianohacker(a)gmail.com> wrote: I'm afraid not; all of the fining and checkout code in Koha works in days. -- Jesse _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ________________________________ Yahoo! for Good helps you make a difference<http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http:/us.rd.yahoo.com/e…>

2 2