Hi Chris / Mark, My eyes lit up at the thought of a catalogue maintenance module being written! Mark - if you are interested in pursuing this I'd be very happy to write down the kind of things we would like to have included. We are cataloguing all our acquisitions into koha which helps us identify glitch areas. Also, I tend to get the problems resulting from imperfect cataloguing practices in our original system that have been discovered since being converted to koha. just sing out - Jo.
On Tue, 5 Sep 2000, Chris Cormack wrote:
Are you also using the SLang Toolkit by Joey Hess (Term::Stool)? When do you think you'll have your returns/issue converted over to slang and have made another release/set up anon CVS?
Yep, thats indeed what we are using. It has been pretty much all converted over it just needs some serious testing. The conversion only affects a small number of modules namely all those in Circulation/ and Circulation.pm itself. The rest of the modules have been untouched.
Work had stalled for a little while, as I was away all last week, but I should be able to work some more on it this week.
Im not entirely sure what I will do with Slang modified modules ... whether I fork the cvs tree, or give them new names and add them.
I could tar them up and pop them on www.koha.org for download I guess, until they have been tested. Then if its all good they can replace the CDK based modules.
I'm not entirely sure what to suggest, ideally there should be a strong separation between the modules that do the work and those that deal with the interface. For curiousitys sake, can you tell me more how the HLT have Koha setup? How split are you development/production environments?
My next major conumdrum is where to start working on Koha, any suggestions?
I know Benedict from poland is very keen to work on localising koha. He has offered to write some locale files in polish. So that koha can be modified to uses locales::gettext. He's not a programmer tho, so he will need help on editing the perl scripts to use gettext.
That shouldn't be two difficult, I'd be glad to help out here. (mental note for self: this'll be good for changing all the Aussie jokes to New Zealander ones :) )
Hmmm, there are also some bugs/glitches in acquisitions. One of the biggest being, the librarians often want to order some books with the same title but in a different format. Eg A video, a talking book and a paperback copy of the same title. The also might want each one of these to come out of a seperate bookfund. At the moment there is no easy way to do this, and they would have to place 3 separate orders.
I'll start having a closer look at that.
Another section that needs work is what im calling a catalog maintenance section. So, somewhere you can go to edit/delete subject headings in the subject authority file. Or edit the other authority files. Were you could tidy up mistakes easily, like merge two identical biblios. And anything else the librarians need :-)
This may well fit into your goals below.
If any of the areas I mentioned seem like a good place to start, let me know and we can work out a good way to go about it.
There are also lots of other things to work on. So let me know what you think.
Chris
All three sound good, where shall we start? On Tue, 5 Sep 2000, Joann Ransom wrote:
Hi Chris / Mark,
My eyes lit up at the thought of a catalogue maintenance module being written!
Mark - if you are interested in pursuing this I'd be very happy to write down the kind of things we would like to have included. We are cataloguing all our acquisitions into koha which helps us identify glitch areas.
Also, I tend to get the problems resulting from imperfect cataloguing practices in our original system that have been discovered since being converted to koha.
just sing out - Jo.
Fire away - it would probably have to be done eventually, if not for me, but for any other programmer who wished to tackle that aspect of the code. Yours Mark -- Mark Tearle - mark@tearle.com Stone: Let's stick to established procedures. -- The Andromeda Leavitt: Establishment gonna fall down and go boom. Strain (1971)
* Mark Tearle <mtearle@tartarus.uwa.edu.au> [000906 03:15]:
On Tue, 5 Sep 2000, Chris Cormack wrote:
Im not entirely sure what I will do with Slang modified modules ... whether I fork the cvs tree, or give them new names and add them.
I could tar them up and pop them on www.koha.org for download I guess, until they have been tested. Then if its all good they can replace the CDK based modules.
I'm not entirely sure what to suggest, ideally there should be a strong separation between the modules that do the work and those that deal with the interface. For curiousitys sake, can you tell me more how the HLT have Koha setup?
Ok, at hlt we having Koha split over two machines. This is mainly because the issues and returns machines, plus the opacs in the Levin library are diskless 486's so they run off one of the servers (dewey). Dewey also has all the telnet code, ie issues and returns. Ronnie the other server, runs the webserver and the mysql database. We also have dewey set up to run a replica of the database (for backup purposes). Anohter purpose of the rewrite was just that, to move all of the interface code into one or two modules. So that it would be simple to change the interface to a web based one, or back to curses, or whatever took someones fancy. In the hectic run up to new years day, some of our good intentions werent followed through and a lot of the code dealing with issues and returns ended up with calls to CDK in it.
How split are you development/production environments?
Basically HLT is production, and we do most of the development on our own server. Having said that, things often go into "production" at quite an early stage. As it is quite hard for the librarians to test them without live data. The core things like issues and returns tho get tested on our server quite heavily before shifting live. (Last thing we want to do is lose books :-) )
My next major conumdrum is where to start working on Koha, any suggestions?
I know Benedict from poland is very keen to work on localising koha. He has offered to write some locale files in polish. So that koha can be modified to uses locales::gettext. He's not a programmer tho, so he will need help on editing the perl scripts to use gettext.
That shouldn't be two difficult, I'd be glad to help out here.
(mental note for self: this'll be good for changing all the Aussie jokes to New Zealander ones :) )
*grin*
Hmmm, there are also some bugs/glitches in acquisitions. One of the biggest being, the librarians often want to order some books with the same title but in a different format. Eg A video, a talking book and a paperback copy of the same title. The also might want each one of these to come out of a seperate bookfund. At the moment there is no easy way to do this, and they would have to place 3 separate orders.
I'll start having a closer look at that.
That would be excellent
Another section that needs work is what im calling a catalog maintenance section. So, somewhere you can go to edit/delete subject headings in the subject authority file. Or edit the other authority files. Were you could tidy up mistakes easily, like merge two identical biblios. And anything else the librarians need :-)
This may well fit into your goals below.
If any of the areas I mentioned seem like a good place to start, let me know and we can work out a good way to go about it.
There are also lots of other things to work on. So let me know what you think.
Chris
All three sound good, where shall we start?
Hmmm, how about the catalogue maintenance section? This will be a whole new section, but will probably make use of some of the functions in C4::Search and C4::Acquisitions Both of which are current in 1.04 So it might be good to work on this, while we sort out anon cvs, etc? You could send me the files uve written, and patch files to any of the existing code if you like. Let me know if this is feasible. Thanks Chris
Hi all, I would like to know whether it is neccesary to add gettext() function in line like this: # print $input->header; # Secondly where if anywhere should one insert gettext() function in this example: print <<printend <FONT SIZE=6><em>Account for $data->{'firstname'} $data->{'surname'}</em></FONT><P> <center> <p> <TABLE CELLSPACING=0 CELLPADDING=5 border=1 > <TR VALIGN=TOP> <td bgcolor="99cc33" background="/images/background-mem.gif" colspan=2><B>FINES & CHARGES</TD> [....] printend Is "FINES & CHARGES" subject to localization by gettext() or is it part of the HTML Code and cannot be localized here? Also should $data->{'firstname'} change into $data-
{gettext('firstname')} in the obove example?
How about the formatting strings of type: "<br>" and other html code strings, are they to fall within or outside of the gettext() function? Any help will be appreciated. May be a bunch of examples? -, pozdrawiam Benedykt P. Barszcz ------------------------------------------------------ Miss Internetu: "Poznaj mnie! Obr�� mnie! Wygraj mnie" http://miss.onet.pl/ ------------------------------------------------------
On Thu, 7 Sep 2000, Benedykt P. Barszcz wrote:
Hi all, I would like to know whether it is neccesary to add gettext() function in line like this: # print $input->header; #
You should be able to safely ignore that (mostly) at the moment.
Secondly where if anywhere should one insert gettext() function in this example: print <<printend <FONT SIZE=6><em>Account for $data->{'firstname'} $data->{'surname'}</em></FONT><P> <center> <p> <TABLE CELLSPACING=0 CELLPADDING=5 border=1 > <TR VALIGN=TOP> <td bgcolor="99cc33" background="/images/background-mem.gif" colspan=2><B>FINES & CHARGES</TD> [....] printend
Is "FINES & CHARGES" subject to localization by gettext() or is it part of the HTML Code and cannot be localized here?
Also should $data->{'firstname'} change into $data-
{gettext('firstname')} in the obove example?
How about the formatting strings of type: "<br>" and other html code strings, are they to fall within or outside of the gettext() function?
Any help will be appreciated. May be a bunch of examples? -, pozdrawiam Benedykt P. Barszcz
I've attached a quick example. printf and sprintf would be the way I'd tackle this problem. In the format, the %s are replaced with the strings returned by gettext. use POSIX; # for setlocale() use Locale::gettext; # bindtextdomain("my_domain", "."); # setlocale(LC_MESSAGES, "de"); # textdomain("my_domain"); # # $firstname="Mark"; $surname="Tearle"; $format = <<printend; %s <FONT SIZE=6><em>%s $firstname $surname</em></FONT><P> <center> <p> <TABLE CELLSPACING=0 CELLPADDING=5 border=1 > <TR VALIGN=TOP> <td bgcolor="99cc33" background="/images/background-mem.gif" colspan=2><B>%s</TD> printend printf $format, gettext("Welcome to my program"), gettext("Account for"), gettext("FINES & CHARGES"); And trying it out.... 21:40 0 mtearle:phregia[626]:/tmp/example>perl test.pl Welcome to my program <FONT SIZE=6><em>Account for Mark Tearle</em></FONT><P> <center> <p> <TABLE CELLSPACING=0 CELLPADDING=5 border=1 > <TR VALIGN=TOP> <td bgcolor="99cc33" background="/images/background-mem.gif" colspan=2><B>FINES & CHARGES</TD> 21:40 0 mtearle:phregia[627]:/tmp/example>setenv LANG de 21:40 0 mtearle:phregia[628]:/tmp/example>perl test.pl Willkommen in mein Program <FONT SIZE=6><em>Acount fur Mark Tearle</em></FONT><P> <center> <p> <TABLE CELLSPACING=0 CELLPADDING=5 border=1 > <TR VALIGN=TOP> <td bgcolor="99cc33" background="/images/background-mem.gif" colspan=2><B>Geldstrafen und Ladungen</TD> It should be quite easy to get Koha supporting many dialects once you've finished, Koha in Klingon anyone? Let me know if this doesn't make any sense to you. (Chris, C4 needs a file we can put global config options in such as the path to the .mo translation files?) Yours Mark -- Mark Tearle - mark@tearle.com Stone: Let's stick to established procedures. -- The Andromeda Leavitt: Establishment gonna fall down and go boom. Strain (1971)
On Thu, 7 Sep 2000, Mark Tearle wrote:
I've attached a quick example. printf and sprintf would be the way I'd tackle this problem. In the format, the %s are replaced with the strings returned by gettext.
And I've remembered to attach the file this time.... Yours Mark -- Mark Tearle - mark@tearle.com Stone: Let's stick to established procedures. -- The Andromeda Leavitt: Establishment gonna fall down and go boom. Strain (1971)
It should be quite easy to get Koha supporting many dialects once you've finished, Koha in Klingon anyone?
Let me know if this doesn't make any sense to you.
(Chris, C4 needs a file we can put global config options in such as the path to the .mo translation files?)
Yep, ur right. A config.pl script would be just the ticket i think. Then make the C4 modules require it. At the moment there are some config variables in C4::Database, and C4::Output But it would be better to put them all into a single file. Im going to be doing some work on Koha today. The librarians at HLT have prioritised some bugs for me to work on. So hopefully will have a new tar ball on monday. The module ill be working on mostly is C4::Search. Subject search is not behaving correctly, and I need to get dewey searching going. Ill put up a list of any files that have been change when I put up a new tar ball. Thanks Chris -- Chris Cormack Katipo Communications Programmer/Sys Admin chris@katipo.co.nz 025 500 789 www.katipo.co.nz
participants (5)
-
Benedykt P. Barszcz -
Chris Cormack -
Joann Ransom -
Mark Tearle -
Mark Tearle