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

iso-8859-2 - probelm
by Benedict 19 Jan '03

19 Jan '03

Hi all, I don't know whether this is a Konqueror problem or a Koha flaw...but each time I access this page http://localhost:8080/cgi-bin/koha/members-home.pl Konqueror reverses to iso-8859-1 and polish characters get scrambled. I tried to insert <meta http-equiv=...> tag but to no avail. Isn't there a perl script in Koha that inforces iso-8859-1 everywhere in the "output"? regards, Benedict

5 9

Re: [Koha-devel] Re: A Win32 circulation client (beginning stages)
by Ambrose Li 19 Jan '03

19 Jan '03

Hi, [It seems that you are not cc'ing to the list.] On Sun, Jan 19, 2003 at 08:37:33PM +1300, Patrick Quinn-Graham wrote: > I've started to look at the circulation.pl script (certainly > not the nicest of the perl scripts I've seen in my > life time. Can some one tell me why it has to be _one_ > script? Couldn't there be a borrower_prompt.pl issueing.pl > issuebook.pl that would be way easier to read...) - and lots > of things are pushed through to C4::Circulation::Circ2, so > it could feasibly have a wrapper put around the necessary > functions. Perhaps a WebService? I'm sure you can do those in > Perl. I can't say I like sending things like that over the > HTTP, even if it was going over https. Perhaps I just don't > like programming in that model (open connection, make request, > close connection). yes, Koha's perl code is not very pretty. In 1.3.x Koha is being "templatized" (I mean separating the presentation from the code using HTML templates), and this is not finished yet; and unfortunately circulation.pl is one of those that has not yet gone through "templatization", so it is messier than most other scripts. There are quite a few other important scripts that are still "untemplatized" and thus can't be localized into another language. (Of course by this I don't mean Perl can't do localization any other way, just that the Koha developers had decided on a certain way to localize Koha.) > I'm not really familiar with getting perl to do something over > a network other than through a webbrowser, so I don't know how > much I could help in that regard. If you don't mind working within the existing framework for the moment, then you don't have to worry about knowing how to send things over the network. A CGI-type script doesn't have to directly send things to the network; it only communicates with the web server using an API that involves only sending and receiving through standard input, standard output, and the environment (the CGI "protocol"). With perl you don't even need to worry about the input and the environment. Same thing with communicating with the SQL server; all is done through API's provided by classes. > A shame about the telnet-type-client being broken... > > But then, a lot seems to be broken (using the web-based demo > is kind of tragic, my local copy still gives JavaScript errors > in the catalogue editing section). Could you file a bug report in bugs.koha.org about these JavaScript errors? > My biggest issue right now: authenticating users... how does > Koha do it? I can't quite seem to figure it out just by > looking at the code. I believe the logic is mostly in the C4::Auth module; of course the scripts need to be written a certain way in order for authentication to work. I believe the user names and passwords are in a MySQL table, and at the "browser" level the user sees it as a cookie-based authentication. -- Ambrose Li <a.c.li(a)ieee.org>

3 2

Re: [Koha-devel] Re: A Win32 circulation client (beginning stages)
by Ambrose Li 18 Jan '03

18 Jan '03

Hi, On Sun, Jan 19, 2003 at 05:16:57PM +1300, Patrick Quinn-Graham wrote: > That would be a good idea, although to a certain extent it's > just as easy to directly connect to the database. The problem with directly connecting to the database is that you will need to duplicate all the logic in the existing CGI code. So, since there is no code reuse between the CGI scripts (written in Perl) and the Win32 client (written in VB), when people start adding functionality to the CGI, you will need to add identical functionality to the VB client. After a while, this might get frustrating. About the telnet client I mentioned earlier, it seems that it is broken quite badly and will need to be rewritten. But it would likely not be rewritten until Koha is better modularized. > I'm not sure how to go about starting to help with > modularization... But m willing to give anything a go. > > How far away is 2.1 likely to be? My main reason for doing > stuff now is that I'm currently unemployed (I'm a student, and > it's summer), and while doing a course, it's not anywhere near > full time (again, it's summer). > > Likely by the time it is released, I'll be back in a full time > course. I think someone else might be better to answer these. -- Ambrose Li <a.c.li(a)ieee.org>

1 0

[Bug 161] New: buildrelease gives error messages during normal operation
by bugzilla-daemon＠wilbur.katipo.co.nz 18 Jan '03

18 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=161 Summary: buildrelease gives error messages during normal operation Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Installation AssignedTo: a.c.li(a)ieee.org ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net During normal operations, running buildrelease gives mv: /tmp/koha-1.3.2/intranet-cgi/misc/bulkmarcimport.pl: No such file or directory I would have copied the docs from from /root/docs, but I couldn't find it. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

Re: [Koha-devel] Koha and testing
by Nathan Gray 18 Jan '03

18 Jan '03

Test::Debugger has made it to CPAN. I would like to have it considered as the testing module for Koha, because it is backwards compatible with Test.pm, which has been a part of the standard Perl distribution since Perl 5 came out. I personally prefer the Test.pm interface to the Test::More interface. However, since Test::More has made it into the standard Perl distribution starting with version 5.8.0, it may be preferable to use that module. The part of Test::Debugger that I value most is the debugging it logs. I do not know what logging capabilities Test::More has. Ed Summers may know, as he has used it for other projects. Once we come to a consensus, we should pick a few key modules and write a few tests for them. Ideally, each module should have at least one test script (if it doesn't do anything worth testing, why is it a module?). Most modules shouldn't have much of a test script, but a few will probably undergo a rather intense testing process during 'make test.' So which modules do we test first? And Ed, Pate, and the group, which test module shall we choose? kolibrie On Wed, Jan 08, 2003 at 08:56:10AM -0600, Ed Summers wrote: > PS. I'd be interested in hearing what your motivation was for creating another > testing framework and how it is different from Schwern's Test::More.

1 0

A Win32 circulation client (beginning stages)
by Patrick Quinn-Graham 18 Jan '03

18 Jan '03

Firstly: let me apologise - I posted this to koha-win32 as well. I've only come across Koha in the last few days, and am certainly excited by what I see: it's about time there was an opensource project like this. My one thing is: I'm not entirely sure I like the idea of doing Circulation type things through a web browser. So, here's the bit where I risk being unpopular: I've started writing a Windows client, for now I've only just started, but intend to do at least issueing/returning of materials. It's written in VisualBasic, so unfortunately probably won't be easily ported anywhere else, but so far doesn't use any non-standard controls, so it could be possible. It's currently sitting at a measly 132kb. (Plus, of course the VB stuff). It access the Koha system by connecting directly to the mySQL database using Microsoft Remote Data Objects and the myODBC connector, and authenticates based on the auth table. (I'm not sure how passwords are protected in there at the moment, as I just made up that part of my application - it md5's them, and stores them that way). Would any one else find this useful? If I release it, it will be under the GPL - it's not really based on Koha code, but I think it's only right. Just a little bio on me: I'm an 18 Software Engineering student at Victoria University (Wellington, New Zealand) - 2003 will be my second year, did all the Library Automation software stuff at my old High School - there we used the MUSAC Library Manager software, so have a reasonable understanding of at least the areas I'm working on here :-). If you want to try a really really early version of it, I'll put one up on my website (just need to recompile). Thanks for your reading time! Patrick.

1 0

[Bug 160] New: New book funds don't show up in list unless they have a budget
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Jan '03

17 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=160 Summary: New book funds don't show up in list unless they have a budget Product: Koha Version: 1.2.3 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Parameters AssignedTo: tonnesen(a)cmsd.bc.ca ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net When you add book funds, they don't show up in the list until you have added a budget for them. This makes it seem like the book fund addition didn't work. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 159] New: Item search during full acquisitions doesn't display results properly
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Jan '03

17 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=159 Summary: Item search during full acquisitions doesn't display results properly Product: Koha Version: 1.2.3 Platform: PC OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Acquisitions (Full) AssignedTo: chris(a)katipo.co.nz ReportedBy: tonnesen(a)cmsd.bc.ca QAContact: koha-devel(a)lists.sourceforge.net Searching for a record when making acquisitions shows a list of hash references instead of a list of matching items. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

RE: [Koha-devel] fulltext searches
by Anthony W. Youngman 17 Jan '03

17 Jan '03

Another thing to watch out for, which google has fallen into ... When looking for an EXACT MATCH, eg "The Lord of the Rings", the google search page comes up and says "words like 'of' and 'the' are extremely common and will be ignored"! Huh! I asked for an EXACT MATCH !!! Cheers, Wol -----Original Message----- From: paul POULAIN [mailto:paul.poulain@free.fr] Sent: 17 January 2003 09:44 To: Tonnesen Steve Cc: koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] fulltext searches >Just something to be aware of. > yep, thx to point this, which i ignored ! This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333.

1 0

fulltext searches
by Tonnesen Steve 17 Jan '03

17 Jan '03

IRC Discussion about fulltext searches: http://www.haz.cmsd.bc.ca/cgi-bin/kohalog.pl?date=15Jan03&refresh=&firstlin… The one caveat I found is that search terms of three characters or less are discarded. So if you do a fulltext search for "rabbit fur" you will get results regarding rabbits, but with no relevance placed on the word fur. Also, doing a fulltext search for the word "fur" will always return 0 hits. Searching for "furs" may return some hits, because it is a four letter word. In my current setup, I am using "like" searches if one or more search terms are three letter words, and fulltext searching if all search terms are longer than 3 letters. Just something to be aware of. The database I'm working on has about 600,000 records (almost 2,000,000 items), and initial "like" style searches complete in about 10 seconds or less, while fulltext searches complete in under 2 seconds. I don't know how fair this comparison really is as I used "car" for my like-style query nd "cars" for my fulltext query, but it gives you an idea of the difference in speed. I've also got caching working, so subsequent searches on the same term (ie looking at page 2 of the results) complete in under a second. Steve.

2 1