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

Bug in MARC sync in rel_2_2
by Joshua Ferraro 13 Apr '06

13 Apr '06

Hi Paul et al, We discovered a major bug (blocker IMO) in rel_2_2: when items are edited, the marc_word table's old values are not deleted. This leads to a very strange bug where even though the record for an item is correct, searching for the old values (for shelving location for instance), brings up the record. The problem seems to be in the MARCdelitem routine, which modifies marc_subfield_table but never touches marc_word. Cheers, -- Joshua Ferraro VENDOR SERVICES 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

numeric identifier in tables
by Pierrick LE GALL 12 Apr '06

12 Apr '06

Hi koha-devel, I've seen some tables in the database where identifiers were not numeric. This kind of things scares me ;-). Internaly, an application should always manage identifiers numericaly, instead of limited alphabetic identifiers (4 characters, uppercase, A-Z only). Why don't we always use numeric identifiers? I suppose because we want users to have an easy way to remember their record. My previous experience learned me to solve this issue by having an internal identifier (numeric of course) and an external identifier (which is shown on screen, alphabetic with restrictions). Their is also a uniqueness constraint on the external identifier (which I call "code"). For example: bookfundid bookfundcode bookfundname 1234 ABCD My personnal fund 321 WXYZ My brother fund On screens, only the code would be shown, not the id. Personaly, I don't think code (easy to remember identifier) is useful, id + name are enough. Cheers, -- Pierrick LE GALL INEO media system

1 0

Managing item type images
by Owen Leonard 10 Apr '06

10 Apr '06

Hi everyone, Pierrick just committed some work on item type image management in HEAD, and his comment in the CVS log got me thinking: "new: function were added in C4::Koha to manage itemtype image location (local/remote). Warning: you must copy or symlink the itemtypeimg directory from the opac template into the intranet template." Copying or symlinking sounds like too much to have to do during an installation, so I was wondering how better to handle the item type images. Joshua made what I think is a good suggestion, to put the itemtypeimg directory inside the koha-tmpl directory. Then we create a directory for each template: /koha-tmpl/itemtypeimg/css /koha-tmpl/itemtypeimg/npl We talked about using a system preference to specify the file extension, to create item type images like this: <img src="/koha-tmpl/itemtypeimg//TMPL_VAR NAME="itemtype" -->. ...where 'extension' is '.gif,' '.png,' etc. But the current system does a directory listing of everything in itemtypeimg, so that's not necessary. I'm wondering if instead of making the item type images template-dependent (css,npl,whatever) like I suggested above, we should have them be independent, so that libraries could choose an icon set independently of their current template. The management screen on itemtypes.pl could have a drop-down list of item type sets found in /itemtypeimg/. That would give us the freedom in the future to add original sets of item type images that other libraries or developers might create. What does everyone think? Would there be any problems associated with moving itemtypeimge into /koha-tmpl ? -- Owen ---- Nelsonville Public Library http://www.athenscounty.lib.oh.us

2 1

Re: UTF8
by Joshua Ferraro 07 Apr '06

07 Apr '06

(copied to koha-devel) On Fri, Apr 07, 2006 at 07:38:02PM +0300, Tümer Garip wrote: > Hi again, > While waiting for Owens directions for CVS time is passing by and I > think we have to sort a few things out. Regarding this UTF8 I think a > little bit more work should be done. Unfortunately I do not have a Linux > system to test things but they should not be that much different than > windows platform. Is there anyone willing to try my scripts as I direct > him/her probably by email or IRC? Of course, I'd be happy to do this. Let me know of a time to be on IRC and we'll do it. > Up until now the only reason KOHA managed both Unimarc and MARC21 is > because of the existence of char_decode script in biblio.pm and unless > somebody comes up with a ready perl module doing the Unimarc charset > conversion to UTF8 everything will get delayed. In fact, the spanking new CVS version of MARC::File::XML does this nicely (you'll also need the new MARC::Charset and new MARC::Record, not available on CPAN unfortunately). You can install it by first checking out a copy of the CVS: $ cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/marcpm co -P marc-record $ cd marc-record $ perl Makefile.pl $ make $ su make install $ cd .. cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/marcpm co -P marc-charset $ cd marc-charset $ perl Makefile.pl $ make $ su make install $ cd .. cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/marcpm co -P marc-xml $ cd marc-xml $ perl Makefile.pl $ make $ su make install $ cd .. (or the equivilent on a windows system) Check the POD documentation for MARC::File::XML for how to handle UNIMARC conversions to UTF-8 (or check a message to koha-zebra from Mike Rylander with MARC::File::XML in the subject) > This script was reading UNIMARC and converting it to iso8859 so why it > cannot convert to UTF8 I do not understand. The only reason I can thing > of is that the script contains s/\xc1\x61/à/gm; for unimarc. If > somebody replaces this 'à' character to its UTF8 hexcode than it should > work. Because biblio.pm itself is iso8859 file this character is read as > iso8859-1. What I did (but not sure whether it will work with Linux) is > to save the biblio.pm as a UTF8 file. This way I did not have to write > the hexcode for the characters so they are actually UTF8 themselves. > > Can somebody try this with bulkmarcimport.pl and see what happens? It > works for me. If it does work than I'll give detailed info about because > MARC8 coming from mysql is a litle bit more tricky. I think moving forward, we want to use MARC::Charset for conversions, adding on to it's functionality rather than using our internal char_decode (which in fact, I've removed from HEAD). What do others think? Cheers, -- Joshua Ferraro VENDOR SERVICES 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

addbiblio & cloneTag
by Paul POULAIN 07 Apr '06

07 Apr '06

Hello all, A few days ago I have introduced a cloneTag javascript for cloning tags, like the cloneSubfield is cloning subfields in the MARC editor. It did not work well for authorities entries : the authority reported was based on the hardcoded number of the subfield with the ... I rewrote it and now, it's better : there is a <div id="tagXXX"> for each tag. The report is done on every subfields under the <div id="tagXXX"> A last problem remains : the "tagXXX" is hardcoded in the openAuth entry. So when you duplicate a field, the ... still points to the 1st entry "tagXXX". You can search an authority, but if you report it, it's reported to the 1st tag in the biblio ! (the duplicated tag has a <div id="tagXXtagXX">) I see 2 possibilities to solve this : - rename the link when cloning the tag - calculate the id of the <div id="tagXX"> only when the user clic on the ... But I don't see how to solve this problem. I'm happy with what I learned (thx to joshua for some useful links), but i'm still a dummy at javascript & would be happy if someone could take the ball & fix it definetly. hint : addbiblio.pl, line 188 is where the link (...) is builded, it's not in the template, don't look at it here ;-) PS : I won't release 2.4.0 until this problem is fixed. We also have a problem with MARC21/UNIMARC and unicode/iso8859-1, that kados should look at soon. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

1 0

XML-UTF8-UNIMARC
by Tümer Garip 07 Apr '06

07 Apr '06

Hi, I have seen commits of retrieving a marc record converting it to xml and back to marc to convert MARC8 to UTF8. Well as far as I know Unimarc is not MARC8 so whether it will work with that I'am not sure. Also what I am surprised is that we already have a char_decode script in biblio.pm which is supposed to do this i.e. Convert from UNIMARC and MARC (separately) to previously iso-8859 and now it should to UTF8. Being on a windows platform this actually works for me but I dont know linux issues. So here is the solution(!) I came up with. The records coming from breeding farm into addbiblio.pl are MARC8 and with every communication set to UTF8 they become gibberish because both are double byte characters and mysql assumes them to be UTF8 while they are not. Of course not a problem with the ascii character world. So when I am reading from the breeding farm I set the communications to latin1 temporaryly and suprisingly enough mysql does not try to do any funny conversion on double byte characters and just passes them through as they are. Going through my char_decode they properly get converted to UTF8. If am not mistaken this should work for UNIMARC as well. I do not know the mechanics behind all this but a hint. Just some food for thought for UTF8 gurus, Cheers Tumer

1 0

New Feature: Zebra Plugin
by Joshua Ferraro 06 Apr '06

06 Apr '06

Hi all, If you've been following the development of late you probably know we've been working hard on getting a Koha Zebra Plugin ready to allow libraries to have the stability of the rel_2_2 series (soon to be rel_2_4) and the speed and search flexibility of Zebra. The plugin is finally here, and has reached a state of maturity suitable for public consumption. There's even an install doc: http://www.kohadocs.org/Installing_Zebra_plugin.html So please, if you have a spare test server, give it a shot. Let us know what you think. Your feedback will be invaluable as we move towards 3.0. Cheers, -- Joshua Ferraro VENDOR SERVICES 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

New IndependantBranches feature.
by Henri-Damien LAURENT 06 Apr '06

06 Apr '06

You all know IndependantBranches feature and its influence on Acquisition. Now, when IndependantBranches is set, a new control on circulation has been designed for 2.4.X It prevents a librarian from a branch to issue items held by other branches (unless librarian is a superlibrarian). If he tries to do so, an error message is displayed. -- Henri-Damien LAURENT

1 0

pagination bar
by Pierrick LE GALL 06 Apr '06

06 Apr '06

Hi koha-devel, 2 days ago, I've commited a new function pagination_bar in C4::Output module (was it the right place?). This function builds the HTML code of a pagination bar: CVS Log> improved: C4::Output::pagination_bar builds an HTML pagination CVS Log> bar with no language dependency. This function hugely CVS Log> simplifies templates and offers a standard pagination method. CVS Log> This function also improves preformances. The idea is to always use the same function to create a pagination bar. The pagination bar will always look the same. What I've seen so far in templates is N pagination bars, each one using a slightly different algorithm. One pagination bar was even picture based! (limited to 16 pages). So far, only 2 pages are using the new pagination bar : authorities/authorities-home.pl (for search results) and admin/stopwords.pl. You can find required code in the corresponding files. You'll see it's very simple, you just need to give the URL for each link, the name of the offset/page/startfrom URL parameter, the number of pages and the current page number. Cheers, -- Pierrick LE GALL INEO media system

1 0

MySQL specific queries
by Pierrick LE GALL 06 Apr '06

06 Apr '06

Hi koha-devel, Working in admin/stopwords.pl, I've found an SQL query I didn't know : "REPLACE stopwords (word) values (?)". I've searched in my MySQL cookbook and found what was the purpose of this statement (it's great by the way, too bad I didn't know it, it would have saved me many code lines). What the cookbook also told me is that "INSERT IGNORE" and "REPLACE" are MySQL specific statement. Maybe we already use "SELECT ... LIMIT X,Y" but this one is much more difficult to /translate/ into standard SQL. What is the official coding guideline concerning SQL queries? Can we use such specific statements? Cheers, -- Pierrick LE GALL INEO media system

2 2