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

problem with using the value_builder plugins
by Robert Lyon 04 Jul '06

04 Jul '06

Hi I'm looking at using the /value_builder/ plugin feature of helping create MARC21 records using the form here /cgi-bin/koha/acqui.simple/addbiblio.pl and I'm wanting to know if the popup javascript functions related with them are meant to map data in the popup window to only one field in the MARC form or can one easily access repeatable subfields I'm wanting to add information into the 651a subfield from a plugin that has a bunch of checkboxes I can get the information added to the field 651a as a string like so -> Place 1|Place 2|Place 3 and on saving this will make a bunch of 651a subfields like so a Geographic name Place 1 a Geographic name Place 2 a Geographic name Place 3 but now how do i get the the clicking of the ... on the end of the field to grab not only the info in it's field but also the other ones related to the 651a subfield? any ideas Bob -- Robert Lyon Katipo Communications

1 0

Panjabi In notes or/Title
by Ramandeep Singh 04 Jul '06

04 Jul '06

Hello All, I've got Koha 2.2.5 running on Linux. I am trying to put Panjabi (Panjabi Unicode) value into the notes field to store some information about the Panjabi book title. So I paste the Unicode value (ਰਮਨਿਪ) in Koha admin notes field. I then query the database to see the value stored. It looks like it has stored the html code equivalent i.e #223232;#34343;etc. I also noticed that it splits this whole value into multiple rows in the marc_* table values. so tag 500a will have multiple rows with the html code values above and it is split randomly. Next, when I go back to the admin interface--the notes field it repeated multiple times with the html code values and I cannot edit the original value I had placed. I am by no means an expert/adv on Unicode but have general understanding. I would appreciate any one's input in this. BTW, I did read the posts from the achieves that did mention how to get Chinese/Arabic in the titles and it seems to be working......i need to know how I can get Panjabi to work. Thanks! Raman -- ਰਮਨਿਪ ਸਿੱਗ Ramandeep Singh RamanTX(a)gMail.com

1 0

Head & rel_2_2 merged.
by Antoine Farnault 03 Jul '06

03 Jul '06

Hi all, I 've just merged Head and rel_2_2 and i prepare a big commit soon. I think this merged version has no "Internal Server Error" but, as i'm new in the koha code, it's possible that i 've made some mistakes by resolving conflits between these 2 versions... I hope i haven't made too much errors and/or bugs ! Cheers, -- Antone Farnault antoine(a)koha-fr.org

1 0

M:F:USMARC & UTF8 problems
by Tumer Garip 03 Jul '06

03 Jul '06

Hi all, It has been months since devel-week and we are still struggling with UTF8 problems. Anyone following the IRC may have noticed that with ZOOM now working and everything looked normal and UTF8 we had a display problem when accented characters were in the search term. This was occurring when the new version of MARC::Record (version 2) package was being used. This package is regarded as a MUST for our MARC8 to UTF8 conversions and also hopefully to handle UNIMARC correctly. Well after all this time and effort I can report that the handling of UTF8 within this package is buggy. For a reason I did not understand line 170-174 of USMARC.pm says: # if utf8 the we encode the string as utf8 if ( $marc->encoding() eq 'UTF-8' ) { $tagdata = marc_to_utf8( $tagdata ); } which simply means if you have an UTF8 marc record re-decode it to UTF8. Which in itself calls Encode::decode and changes everything to bytes. In simple terms it messes all the accented UTF8 characters you may have on your template. I do not know any need of usage for this conversion and especially in KOHA_head everything being UTF8 this definitely does more harm than good. I have corrected the error with this package and a copy is sent to Joshua to raise the question with the package maintainer. In the meantime I have added another functionalty of conversion MARC8-UTF8-MARC8 to this package so one can go MARC::File::USMARC::decode($marc,&\somefunction,$encoding,$normalize); Where $encoding could be "UTF-8" or "MARC-8" and the record will get converted to that encoding as it is decomposed. Rather than the current method of converting to XML and back to MARC in order to get this. The fourth argument(is 1 or 0) is a more complicated issue of composed(precomposed) and decomposed character sets. I will not go into details of this but I suggest you supply 1 to this argument when converting to UTF8. This will make sure you get composed characters which are more browser and XML friendly.(More info on this subject can be found at Unicode::Normalize and the at the links in document) This correction resulted in another problem solved. The issue of having to use LibXML (and a specific version of that) seems to have gone away. Your SAX filter may stay as PurePerl and still your XML wont break. (see the article by Joshua http://www.mail-archive.com/address@hidden/msg01006.html) However extensive testing has to be done to make sure on this. An important note though. Whatever parser you use you must have PurePerl defined as one of those parsers in your ParserDetails.ini otherwise it will not work. I hope this problem is solved once and for all so that we can continue developing more ZOOM functionalty into KOHA. Cheers, Tumer Garip -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.9.8/380 - Release Date: 30.06.2006

1 0

HEAD code cleaning
by Paul POULAIN 27 Jun '06

27 Jun '06

Hello all, Antoine start today working on code cleaning on HEAD. we have updated the wiki to say what he will work on. For instance, he investigate existing code. But you should see the 1st commits soon. Most of it's work should be harmless, as it should be mainly : - POD documenting - useless code removal but some stuff will have to be done carefully, like sub renaming & moving from one .pm to another. Don't hesitate to update the wiki if you have some suggestions. -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

itemnotes?
by Cindy Murdock 27 Jun '06

27 Jun '06

Hi all, We've noticed that there's an 'itemnotes' field where messages about materials can be stored, but there doesn't seem to be any way to view or edit them from within Koha. Is anybody doing anything with that? Cindy -- _________________________ Cindy Murdock Network Administrator Meadville Public Library | Crawford County Federated Library System meadvillelibrary.org | ccfls.org

3 2

Help-Sistem commercializing
by Roxana Luz Fleipaz 26 Jun '06

26 Jun '06

Hello to all. I am new in est system, it is excellent!. I found out about this system across a partner of Uruguay. This system they are commercializing in Argentina in the university of the Plata, across Emiliano Marmonti. He would wish them to help me I am a director of a library and I need to execute this system. Thank you. Paraguay

3 2

Required Perl Modules
by Mike Mylonas 20 Jun '06

20 Jun '06

Hi All Time for an updated release of the CPAN bundle for KohaSupport. Could someone please confirm for me the required modules for the upcoming 2.26 version Koha... the list I have is taken from the Install.pm and the latest cvs version of the 2.26 release notes. If someone could also confirm if the modules that have version numbers beside them, are the required version only or the required minimum version The list I have at the moment includes DBI Date::Manip DBD::mysql HTML::Template Digest::MD5 MARC::Record Mail::Sendmail PDF::API2 Net::LDAP Event Net::Z3950 LWP::Simple XML::Simple Class::Accessor (0.25) XML::SAX (0.14) MARC::File::XML (0.83) MARC::Charset (0.95) Thanks in advance M

3 5

Auth With Windows AD
by Acty Chen 19 Jun '06

19 Jun '06

use <userid>@abc.corp instead of anonymous bind 1. Search the "# LDAP connexion parameters" # LDAP connexion parameters my $ldapserver = 'dc01.abc.corp '; # Base DN for users my $name = "dc=abc,dc=corp"; # Bind uses the users full DN, if uid doesn't work try my $ldap_binddn = "$userid\(a)abc.corp"; my $ldap_secret = $password; my $db = Net::LDAP->new( $ldapserver ); 2. change my $userdnsearch = $db->search(base => $name, filter =>"(a-login=$userid)", ); to my $userdnsearch = $db->search(base => $name, filter =>"(sAMAccountName=$userid)", ); 3. search "## HACK LMK" change if( ( $cmpmesg -> code != 6 ) && ! ( $password eq "kivabien" ) ) { warn "LDAP Auth impossible : wrong password"; return 0; }; change ##if( ( $cmpmesg -> code != 6 ) && ! ( $password eq "kivabien" ) ) { ## warn "LDAP Auth impossible : wrong password"; ## return 0; ##}; <Result> diff Auth_with_AD.pm Auth_with_ldap.pm 32,33c32,33 < use Net::LDAP; < use Net::LDAP qw(:all); --- > # use Net::LDAP; > # use Net::LDAP qw(:all); 506,514c506,509 < my $ldapserver = 'dc01.abc.corp'; < < # Base DN for users < my $name = "dc=abc,dc=corp"; < # Bind uses the users full DN, if uid doesn't work try < < my $ldap_binddn = "$userid\(a)abc.corp"; < my $ldap_secret = $password; < --- > my $ldapserver = 'your.ldap.server.com '; > # Infos to do an anonymous bind > my $ldapinfos = 'a-section=people,dc=emn,dc=fr '; > my $name = "a-section=people,dc=emn,dc=fr"; 518,523c513 < my $res =$db->bind($ldap_binddn, password => $ldap_secret); < < #if (!defined($db)) { < # print STDERR "Connection au serveur LDAP impossible!\n"; < # return 0; < #} --- > my $res =$db->bind(); 530c520 < filter =>"(sAMAccountName=$userid)", --- > filter =>"(a-login=$userid)", 542,545c532,535 < ###if( ( $cmpmesg -> code != 6 ) && ! ( $password eq "kivabien" ) ) { < ### warn "LDAP Auth impossible : wrong password"; < ### return 0; < ###}; --- > if( ( $cmpmesg -> code != 6 ) && ! ( $password eq "kivabien" ) ) { > warn "LDAP Auth impossible : wrong password"; > return 0; > };

1 0

MARC Editor in 'stable' CVS Badly Broken
by Joshua Ferraro 19 Jun '06

19 Jun '06

Hi Paul et al, This morning I updated my working "stable" CVS repo to take a look at the recent MARC editor commits and I discovered that things are very badly broken: * repeated fields are not saved separately, but under one field eg, 650$a$b$c 650$a$b$c becomes 650$a$a$b$b$c$c!! (you will not see this bug unless you have 'LabelMARCView' set to 'standard') * repeating fixed fields in a previously saved record causes a 500 error * tabindex is broken * the back button is broken such that if you save something then go back your repeated 650 jumps into the 651!! * editing a record sometimes causes fields to show up in the right place, but be saved in the wrong place After 6 hours of attempting to track down the cause of these and other bugs I didn't take notes on, I have given up. I'd like to request that we revert the stable CVS MARC editor to the previously working versions: Biblio.pm 1.115.2.54 addbiblio.pl 1.52.2.40 addbiblio.tmpl (not sure, many unrelated changes committed at the same time) I will repeat that MARC::File::XML can handle iso-8859-1 encoding if you specify that you're working with non-MARC21 data (and if you have 8859 encoding, you don't have MARC21 data) IF YOUR XML PARSER CAN HANDLE 8859 ENCODING. Someone with non-MARC21 data should take a look at the latest Sourceforge version of MARC::File::XML to see how this is handled and modify Koha's editor accordingly (I may have a chance to do this at some point, but I'm a bit burned out on this at the moment). 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

2 2