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

UTF-8
by Dorian Meid 03 Dec '07

03 Dec '07

Gentlemen, I have a problem using UTF-8 with Koha. If I import MARC-Data via z3950 special characters are treated differently ÄÜÖäüö works at some pages but not in all. ß dosn't work at any page. This is the ü I get from z3950 and this is the ü which is generated when I type it. These are two different characters. I'm using Koha 2.2.8, MySQL5 and Apache 1.3 on Mac OSX 10.4 with Firefox. I've read the notes on the Wiki and my server, Database and the tables are set to UTF-8. I also set the templates encoding variable and added the encoding to httpd.conf The z3950 server sends data UTF-8 encoded Did I miss something? Dorian Meid

3 5

Code Cleaning : Authorities.
by Henri-Damien LAURENT 13 Sep '07

13 Sep '07

Those first two are the main reason I am writing. Does anyone still use thesaurus.pl ? Considering that now frameworks allow to link Authorities with one another, I think we should drop linker down. One problem is : All linking and hierarchy code is UNIMARC and hardcoded. I would like to allow more versatility on this. But this would require those new system preferences : relation type subfield (UNIMARC 2) relation authnumber subfield (UNIMARC 3) relation authtype subfield (we should agree on using authtypes or authtypecode as value in those subfields) (UNIMARC 5) relation tag (UNIMARC 550) child flag (UNIMARC f) mother flag (UNIMARC "g") Plus would require some little modifications of auth_finder to enable relation Choice. Maybe it could interesting to enable multiple authority link for a field. This would only require to manage a list of authorities to search in. We reviewed the AuthoritiesMARC code with Paul. And thought that unification between Authorities.pm and Biblio.pm was not a worth the work. a) Authorities search is much different from biblio search. b) inner tables differs so that it would oblige us to make heavier functions. So Authorities Will stay as such. While Code cleaning it, some questions remains. GetSummary as well as Buildhererarchies is still quite customer dependant and used for display. But it Hardcodes some HTML preprinting. So that when people want This or that display, one has to modify a C4/AuthoritiesMARC. For instance : One wants that term list are displayed : /Heading/ BT /Broader Term/ NT /Narrower Term/ UF /Used For/ /Comments./ Another wants that term list are displayed : /Heading/ TG /Broader Term/ TS /Narrower Term/ EP /Used For/ Comments : /Comments/. Another wants only Heading$a -- Heading$b -- Heading$z And we have to make little changes to the code and then upgrading process is harder. Solution ? A) Using xslt ? B) using HTML::Template to "simulate xslt" Then ppl would only have to modify template for summary processing "mini" template on each record. C) keeping this as such. This would also be helpful in getting information for search resultlists in biblios more user adapted. Comments welcome. -- Henri-Damien LAURENT

3 2

IMPORTANT Koha 3.0 updatedatase and kohastructure.sql
by Joshua M. Ferraro 31 Aug '07

31 Aug '07

Hi all, For years, we've had trouble maintaining the official Koha SQL definition, it seems like every developer probably has a slightly different definition. This is fine, however, we need to decide on an appropriate process for updating the official kohastructure.sql file that forms the basis for the new Web Installer in Koha 3.0. If you look back through the history of this file: http://cvs.savannah.nongnu.org/viewvc/koha/installer/kohastructure.sql?root… You'll notice vastly different versions ... people seem to just overwrite it with a new def exported in their favorite tool (mysqldump, phpmyadmin, etc.). Recently I had to revert kohastructure.sql in CVS because it patently failed for me ... I noticed that there are some definitions missing as well, and discrepancies between versions w/respect to the constraints. For instance, I asked Paul this afternoon to send me his 3.0 SQL definition, but that didn't include the 'defaultvalue' column in the marc_subfield_structure table, and, as a result, the MARC editor is broken for new installations when using that definition. I'd also like to point out that updatedatabase should start completely blank for 3.0. IMO updatedatabase shouldn't be the upgrade path from 1.x or 2.x to 3.0 ... rather, it should be the upgrade path for 3.0 to 3.2, etc. Other thoughts? I'd like to get feedback from everyone on the best way to maintain kohastructure.sql and updatedatabase, to make sure we always have a known SQL definition and update process. Comments, ideas? 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

5 5

Cutting long cyrillic fields via import (record added)
by Serhij Dubyk Сергі й Дубик 30 Jul '07

30 Jul '07

Hi Problem with importing of some records with long subfield (not with all such records). In Koha (main DB or reserviour) result subfields cutted (sometime to few words). Similar results when use web GUI import and bulkmarcimport. When manually added data via Koha-Intranet - all subfiels present fully. Can it is will be connected with Koha DB's structure? (i.e. for marc_breeding table title limited to varchar(128 bytes?)) My systems: Koha 2.2.9 (and previous v.), MySQL 5, Debian 4, all utf-8 Here 1 record for test this (my initial after iso2xml.pl): http://www.nabble.com/file/p11861237/1record_to_test_bag.xml 1record_to_test_bag.xml (xml2marc.pl): http://www.nabble.com/file/p11861237/1record_to_test_bag.xml.mrc 1record_to_test_bag.xml.mrc (MarcEdit to text): http://www.nabble.com/file/p11861237/1record_to_test_bag.xml.mrk8 1record_to_test_bag.xml.mrk8 -- View this message in context: http://www.nabble.com/Cutting-long-cyrillic-fields-via-import-%28record-add… Sent from the Koha - Dev mailing list archive at Nabble.com.

1 0

New Koha 2.2 search....
by Ernesto Silva 27 Jul '07

27 Jul '07

Hi, I've said before we've developed a different search in Koha 2.2, as our Koha installation has many modifications I'm not able to send you a 2.2 working version with the new features. Anyway, I can send you our pages, templates and modules so "somebody" can make a integration-testing with actual Koha versions and evaluate. I'm attaching a ZIP file with all our new staff, please feel free to use it, test it, and finally comment on it. I don't have any other files, so if someone wants to give it a try and needs any assistance please contact me (silva(a)ort.edu.uy) or Jean Pierre Ducassou (ducassou(a)ort.edu.uy) so we can guide you. Other data: - all texts, help and comments are in Spanish, please contact us if you need any help or assistance. - we use MySQL 5.0.18, I think that any version with sub-queries support should work fine. - all templates belongs to the Intranet section, when the system is fully functional we'll make some for the OPAC. - There's a help file with an explanation of the grammar used by the librarians, the grammar which we convert to MySQL 5 queries/subqueries. - In the grammar the slowest operation is the negation of something, we have operators like "contains" and "nocontains" and that works fine, but if you use the "not" operator the queries gets slow. We are trying to find an elegant solution, but this will take some days - We used YAPP to parse the grammar and generate a perl module, the .yp file with the grammar source is also included. Finally, I know this lacks a lot of information, but please, first look at it and then contact us. Best regards, Ernesto Silva. ******************************************************************** Hi, here at Universidad ORT Uruguay we've been using koha since may'05. Andres Tarallo and I were the primary developers, Andres is still with us but working on another proyect and we've hired Jean Pierre Ducassou to continue our Koha developement. And... no Paul, Jean Pierre is not french, but his ancients were. Anyway, as our Koha 2.2 installation has it's own flavour and we were aiming to improve the search system we've made some work during 2006 but the developer we hired has gone away... pity. We've been reviewing 2006 search code (with Jean Pierre) wich was based on MySQL 5 using sub-queries and Full Text Indexing. We've got a 95% working search system, we're giving it the final tweaks. We were wondering if anyone is interested in it, we can contribute with the code, explanations and basic documentation. The basics of the systems are: - our own query language, simple but yet powerful. - a parser to convert the query language expressions to sql expressions. - a new table, similar to marc_subfield_table, but with a subfieldvalue field of blob type, and a nsubfieldvalue field of float type. - full text indexing. In our developement server (2 x PIII of 800 MHz) the new search system works very fast with 52000 bibles and 75000 items. When the system is fully functional (in 2 or 3 days I hope) we will begin the migration off the rest of our Koha installation to MySQL 5, and when this is ready we'll put into the production server, I hope we can achieve this in October. Sorry about my poor english and best regards, -- Ernesto Silva. Coordinador de Desarrollo Web y Sistemas Abiertos Centro de Procesamiento de Datos Universidad ORT Uruguay. E-mail: silva(a)ort.edu.uy Tel: (+598-2) 902-1505 ext. 206 Fax: (+598-2) 900-2952 _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

1 0

New.koha.org progress and translations
by Russel Garlick 27 Jul '07

27 Jul '07

Hi everyone, A couple of us have been playing with plone for the new version of the Koha site. The goal is to have a new site up and going for the upcoming release of version 3. We have an install up and going at http://new.koha.org:8080/koha/. It is using a default plone look at the moment, but as I am interested mainly in the content, I have plugged in most of the content from the current site. We have a couple of things up and going: The Plone Help Centre http://new.koha.org:8080/koha/documentation Although it seems to have a few issues, by and large this seems to be pretty nice. It covers the full gambit of docs and has some nice features which allows you to tag docs against an audience (End User, Sys Admin, Developer) and version. Multilingual Content (using LinguaPlone) In a perfect world, we would have a completely multilingual site. This is something that was going to be very difficult to do on the old platform. At the moment, I have done one page (as a proof of concept) http://new.koha.org:8080/koha/documentation/manual/koha-2.2/ introduction/view?set_language=en http://new.koha.org:8080/koha/documentation/manual/koha-2.2/ introduction-1/view?set_language=fr Unfortunately my French extends about as far as ordering a coffee and my Russian as far as identifying a book and table. So the purpose of this email? I am asking for your help, particularly with translations. If you would like to lend a hand, then please email me off list or drop me a line on #koha and we can get you set up. Cheers, -- Russel Garlick russel.garlick(a)liblime.com General Manager - Australasia +64 21 542 188 LibLime Limited www.liblime.com

1 0

New Koha 2.2 search....
by Ernesto Silva 24 Jul '07

24 Jul '07

Hi, here at Universidad ORT Uruguay we've been using koha since may'05. Andres Tarallo and I were the primary developers, Andres is still with us but working on another proyect and we've hired Jean Pierre Ducassou to continue our Koha developement. And... no Paul, Jean Pierre is not french, but his ancients were. Anyway, as our Koha 2.2 installation has it's own flavour and we were aiming to improve the search system we've made some work during 2006 but the developer we hired has gone away... pity. We've been reviewing 2006 search code (with Jean Pierre) wich was based on MySQL 5 using sub-queries and Full Text Indexing. We've got a 95% working search system, we're giving it the final tweaks. We were wondering if anyone is interested in it, we can contribute with the code, explanations and basic documentation. The basics of the systems are: - our own query language, simple but yet powerful. - a parser to convert the query language expressions to sql expressions. - a new table, similar to marc_subfield_table, but with a subfieldvalue field of blob type, and a nsubfieldvalue field of float type. - full text indexing. In our developement server (2 x PIII of 800 MHz) the new search system works very fast with 52000 bibles and 75000 items. When the system is fully functional (in 2 or 3 days I hope) we will begin the migration off the rest of our Koha installation to MySQL 5, and when this is ready we'll put into the production server, I hope we can achieve this in October. Sorry about my poor english and best regards, -- Ernesto Silva. Coordinador de Desarrollo Web y Sistemas Abiertos Centro de Procesamiento de Datos Universidad ORT Uruguay. E-mail: silva(a)ort.edu.uy Tel: (+598-2) 902-1505 ext. 206 Fax: (+598-2) 900-2952

2 1

Koha Project Day Schedule Change
by Joshua M. Ferraro 20 Jul '07

20 Jul '07

Hi folks, The LibLime management team is happy to announce that we're switching Koha Project Day to Thursdays, starting next Thursday, July 26th (that's Friday in New Zealand). For those of you who are new to this list (welcome!), Koha Project Day is an initiative to foster community development and growth of the Koha project. It's an all day event that starts at 9am EST in our US office in Athens, Ohio and ends 15 hours later at 5pm NZ in our New Zealand Office in Wellington. Of course, throughout the week, we LibLimers spend the majority of our time working for our customers: writing specifications, doing development work, implementation, and support. Koha Project Day gives us a chance to give back to you -- the community that makes all of this possible! Of course, the invitation to join us is extended to you as well! Join us any time on any Thursday and pitch in, if you're able. Speaking of which, what is there to do? Glad you asked. Here's just a partial list: * organize and write documentation * write specifications for new proposed features * write technical documentation for existing Koha features * respond to questions/comments on the Koha lists * test features and report bugs * fix bugs :-) * read through the code and make comments * translate Koha into your native language * write that new feature you thought of * talk to the developers and tell them how to improve Koha Where is all of this happening? You can join us in real time on the #koha channel on irc.katipo.co.nz. If you've not used IRC before, and you're running Windows, give mIRC a shot: http://www.mirc.com/ See you Thursday! 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

Re: [Koha] attempting to install Koha at Bluehost.com
by MJ Ray 19 Jul '07

19 Jul '07

Actually, this question should go to koha-devel and s/Do/Should/ MJ Ray <mjr(a)phonecoop.coop> wrote: > Do we still use Class::Accessor, Event and HTML::Template? I see from hdl's list that HTML::Template is used only in maclesold.pl,MACLES.pl,macles.v1.0.pl - will they be in 3.0? I can't see Class::Accessor or Event. I think Event was pulled in by Net::Z3950, which is going away. I await your replies with interest. Thanks, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/

2 2

Re: How to change HTML / TMPL path prefix?
by Jack Bates 18 Jul '07

18 Jul '07

Here is the second version of a patch to support configuring intranet / opac, cgi / html base URLs: http://cgi.sfu.ca/~jdbates/tmp/koha/200707170/koha.patch3 I changed the roughly 1135 instances of /cgi-bin/koha in the English templates to use either the new intracgi or opaccgi variables. It's almost working for us! http://sfpirg6.stdntsvcs.sfu.ca/koha/opac-cgi/opac-main.pl All that remains is to hunt-and-kill the remaining 124 instances in 78 Perl scripts. Hopefully I can get to this by the end of the week. Any feedback much appreciated! Thanks, Jack > Maybe we should move this discussion to koha-devel? > http://lists.nongnu.org/mailman/listinfo/koha-devel > > Jack Bates <ms419@...> wrote: > > [...] Also, before I go > > editing template files for various translations, I assume each > > translation is built from one source file? > > I think they're built from the English template and a po file with the > tools in misc/translator. > > > I browsed the developer wiki a bit, but haven't yet found instructions > > to build a Koha distribution archive from the source repository > > (presumably this involves compiling localized versions of templates). > > In 2.2, it's misc/buildrelease and I don't think it localises templates. > > In HEAD, that is in rather a state of flux just now. It may end up > as "perl Makefile.PL && make dist" but that's not brilliant yet. > > > Please find attached the small patch I created so far and my SSH key. > > Can I please have access to clone the 2.2 git repository? > > As I understand it, you don't need ssh access to clone it: see > http://lists.nongnu.org/archive/html/koha-devel/2007-06/msg00008.html > for instructions. 2.2 is the branch origin/rel_2_2 > > Hope that helps, > -- > MJ Ray - see/vidu http://mjr.towers.org.uk/email.html > Experienced webmaster-developers for hire http://www.ttllp.co.uk/ > Also: statistician, sysadmin, online shop builder, workers co-op. > Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/

1 0