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

field 700
by nour eldeen 02 Aug '09

02 Aug '09

Hello, i use koha 3.00.00.094 and have problem at field 700 ,after repeat field and enter authorities then when edit any sub field ,all repeated field 700 changes to unknown word

1 0

Re: [Koha-devel] Configuring LDAP with Koha
by Sai bhalaji Dhinakaran 31 Jul '09

31 Jul '09

Hi, Go to the file Auth_with_ldap.pm located in: /usr/share/koha/lib/C4 and change the following lines of code: my $userldapentry = $search->shift_entry; my $cmpmesg = $db->compare( $userldapentry, attr=>'userpassword', value => $password ); if ($cmpmesg->code != 6) { warn "LDAP Auth rejected : invalid password for user '$userid'. " . description($cmpmesg); return 0; } To this: my $userldapentry = $search->shift_entry; my $dbuser = Net::LDAP->new( [$prefhost] ); $res = $dbuser->bind( $userldapentry, password => $password ); unless ( $db && ! $res->code ) { warn "LDAP Auth rejected : invalid password for user '$userid'"; return 0; } Also, you need to configure the koha_conf.xml file which is in /etc/ Steps to configure are available in: http://wiki.koha.org/doku.php?id=en:development:ldap I worked for us on ADS LDAP Server. Thanks and Regards, Sai Bhalaji [cid:image003.jpg@01CA11E8.36FE70D0] __________________________________________________________________________________________________________________________________ D&B TransUnion Analytic and Decision Services Pvt. Ltd. | Prince Infocity, 9th Floor, Plot No. 286/1, Rajiv Gandhi Salai (OMR), Kandanchavadi, Chennai - 600096 | Ph: +91-44-66779999 P Please do not print this email unless it is absolutely necessary. Hi, I want to configure LDAP with koha 3.2. Anyone can help in this regard? A step by step procedure to do that will be highly appreciated. Thanks. Zahoor ur Rehman Tanoli Senior Research Associate Al-Khawarizmi Institute of Computer Science UET Lahore, Pakistan Cell: +92-321-9676940 Office: +92-42-9029450 ext 813 __________ Information from ESET NOD32 Antivirus, version of virus signature database 4292 (20090730) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ________________________________ This email and any attachment(s) transmitted may contain confidential, proprietary or legally privileged information relating to D&B TransUnion Analytic and Decision Services Private Limited. The information is intended solely for the recipient. No part of this information may be disclosed, copied, reproduced, distributed or made available in any form whatsoever without prior authorization. If you have received this email in error please notify the sender electronically and delete all copies immediately. This email may contain viruses. D&B TransUnion Analytic and Decision Services Private Limited has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this email. We strongly advise you to ensure that the email and any attachment(s) are free of any virus.

2 1

How to setup ....Multiple KOHA on a single machine
by MD. Sabbir Ahmed 31 Jul '09

31 Jul '09

Hi, I am trying to setup multiple KOHA on a single machine.I have KOHA Installed on my machine now like to do this task.I came to know that this could be possible by virtual hosting,can any one let me know how to do Virtual hosting for KOHA. Thanking -- SabbIR

2 1

Configuring LDAP with Koha
by Zahoor-ur-Rehman 31 Jul '09

31 Jul '09

Hi, I want to configure LDAP with koha 3.2. Anyone can help in this regard? A step by step procedure to do that will be highly appreciated. Thanks. Zahoor ur Rehman Tanoli Senior Research Associate Al-Khawarizmi Institute of Computer Science UET Lahore, Pakistan Cell: +92-321-9676940 Office: +92-42-9029450 ext 813

1 0

New mailing list: koha-commits
by Galen Charlton 31 Jul '09

31 Jul '09

Hi, A new mailing list has been created for recording commits pushed to the main public Koha Git repository. Postings to this list are generated automatically by a post-receive hook whenever changes are pushed to any branch of the repository. This list is intended for read-only use; to discuss any commits, please use koha-devel or koha-patches. To subscribe to the list, please visit http://lists.koha.org/mailman/listinfo/koha-commits In the next day or two, current subscribers to koha-cvs will be moved to koha-commits and koha-cvs will be shut down for new messages. Thanks to Nahuel for creating the list and to BibLibre for hosting it. Regards, Galen Charlton Koha 3.2 RM gmcharlt(a)gmail.com

2 1

New sysprefs editor
by Jesse 30 Jul '09

30 Jul '09

As demoed at KohaCon09, I have a new sysprefs editor in the works. Anyone who is interested can see the code at http://github.com/pianohacker/koha/tree/prefs . It is almost done, except for a few minor style issues, some missing sysprefs, and translation support. I hope to send out patches within the next couple of weeks. Sincerely, -- Jesse Weaver

3 2

Status of "Calculate fines in days debarred" in RFC 3.2
by Tomás 30 Jul '09

30 Jul '09

I'd like to know the status of the implementation of this: http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:fines_in_days We've been implementing that in koha on our own this year in our university libraries. I'd like to know if there's a consensus on the changes needed in the database scheme and/or the way it should be implemented so we can try to contribute some code. Our librarians asked for some flexibility for applying manual "debarring" too. Thanks. To+ -- Aparición con vida de Jorge Julio López.

2 1

Translation of SQL files
by Zeno Tajoli 29 Jul '09

29 Jul '09

Hi Ricardo and all, At 13.11 29/07/2009, Ricardo Dias Marques wrote: >I think there should be only: >- 1 (ONE) Unimarc Bibliographic SQL file >- and 1 (ONE) Unimarc Authorites SQL file > >... and NOT one of those for EACH language. The current situation, >IMHO, leads to much Copy + Paste work, when one needs to create a new >translation (both tiresome and error prone). Also, if there is one BUG >in one language setup (SQL files) - like this requirement of an >"Authority Type" called "PER" in the English one - we'll probably have >to change all the other languages (SQL files) that were copied from >that one, to correct that bug. > >I think that the descriptions (for instance "liblibrarian" and >"libopac" fields of the "marc_tag_structure" table) are the only >fields that have to be translated. These fields could, for instance: yes, the only fields to translate in Unimarc/MARC21 SQL files are liblibrarian and libopac. But how can we do the translation ? This is a problem that sometime appers in this list. I try to find a solution or an open source tool, but I never found a solution Bye Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

3 3

Koha Label Module Re-write
by Chris Nighswonger 29 Jul '09

29 Jul '09

Hi all, I've been working for a while on re-writing the label module from the ground up and am nearly complete. The new code takes a more OO approach and should make the implementation of new features easier (ie. single label printing for a single item, etc.) I'm hoping to be finished in time for the feature freeze at the end of August. The initial objective is to bring the new code up to the same specifications as the old and perform easily implimented bug-fixes along the way. I'll try to publish my repo over the next week so anyone who likes can have a look at the wip. Incidentally, this re-write will remove the patron card utility code intitially. It was only nearly finished in its current state. I plan to add it back in finished form after completeing work on the labels code. This means it will probably not make it into the next release. Kind Regards, Chris Christopher Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

3 4

Re: [Koha-devel] [Koha] Marc framework test error
by Ricardo Dias Marques 29 Jul '09

29 Jul '09

Hi Zeno, and list, [ I'm adding "Koha -Devel" back to the "Cc:" list because I think that this discussion has REALLY "moved" to code (programming) considerations. I further suggest that, in followups, we remove the koha "regular" mailing list from the "Cc:" list ] ZENO: Thank you very much for your reply! :) My comments follow inline. On Tue, Jul 29, 2009, I wrote: >>Where does the "| Authority:PER, " in the "Constraints" part of >>Subfield "a" (Entry Element) come from? And on Wed, Jul 29, 2009 at 08:12, Zeno Tajoli<tajoli(a)cilea.it> replied: > This definition comes from english Unimarac setup of Koha. > Go to the file > installer/data/mysql/en/marcflavour/unimarc/ > mandatory/unimarc_framework_DEFAULT.sql > line 1362: > ('700', 'a', 'Entry Element', 'Entry Element', 0, 0, '', 7, '', > 'PER', '', 0, 0, '', '', '', NULL), > > The string 'PER' is the link to authority for subfield 700$a Excellent! Thank you very much for that information. > But in the english Koha definition of Unimarc Authority there isn't a > specific structure for Personal Name. > You can see this situation in the file > installer/data/mysql/en/marcflavour/unimarc/ > mandatory/authorities_normal_unimarc.sql Right again. In the case of the French definition for UNIMARC Authorities, located at: /usr/share/koha/intranet/cgi-bin/installer/data/mysql/fr-FR/marcflavour/unimarc_lecture_pub/Obligatoire/autorites_norme_unimarc.sql ... there is this line (line 29 for Koha 3.0.3): INSERT INTO `auth_types` (`authtypecode`, `authtypetext`, `auth_tag_to_report`, `summary`) VALUES ('NP', 'Auteur', '200', '[200a][, 200b][ 200d][ ; 200c][ (200f)]'); ... and, the line for the "UNIMARC Bibliographic" French definition (for the default "MARC Bibliographic framework") does NOT force a specific code for Authors, like the English one does: Line 28: INSERT INTO `marc_tag_structure` (`tagfield`, `liblibrarian`, `libopac`, `repeatable`, `mandatory`, `authorised_value`, `frameworkcode`) VALUES ... Line 197: ('700', 'Auteur principal', 'Auteur', 0, 0, '', ''), So, I'm thinking that this obligation to have an Authority framework with a code called PER in the English framework should be reported as a bug in Koha's Bugzilla. > Well, in version 3.0.x the only place where the name of Authority is > hardcoded, as I know, > is in unimarc_framework_DEFAULT.sql (as I write above). > The suggestion of Joe is correct. Agreed. > In fact the english setup of Unimarc has problems and not only here, > also in Zebra defintions and in fields used for items > information. > I think that a general check of english unimarc setup is a must, also > to use it as a starting point for translation in different > languages. > But who want ot use Unimarc ? > Italy (I) > Portugal (Ricardo Dias Marques) > France (Biblibre, but the fr-FR section is correct I think) Well, according to the Wikipedia article about UNIMARC - http://en.wikipedia.org/wiki/MARC_standards - "[UNIMARC is] the official MARC in France, Italy, Russia, Portugal, Greece and other countries." So, it would be important (for the Libraries of those countries) that Koha implements well UNIMARC, if they are considering / using Koha. I think there should be only: - 1 (ONE) Unimarc Bibliographic SQL file - and 1 (ONE) Unimarc Authorites SQL file ... and NOT one of those for EACH language. The current situation, IMHO, leads to much Copy + Paste work, when one needs to create a new translation (both tiresome and error prone). Also, if there is one BUG in one language setup (SQL files) - like this requirement of an "Authority Type" called "PER" in the English one - we'll probably have to change all the other languages (SQL files) that were copied from that one, to correct that bug. I think that the descriptions (for instance "liblibrarian" and "libopac" fields of the "marc_tag_structure" table) are the only fields that have to be translated. These fields could, for instance: Option A - Be added as additional fields (eg: liblibrarian-en, librarian-fr...). I think this would NOT be elegant at all! Option B - Move the "liblibrarian", "libopac" to another table (call it something like "marc_tag_structure_descriptions_translations") with fields "tagfield", "liblibrarian", "libopac" and "language" (and maybe "frameworkcode" also... I'm not sure regarding this last one). For instance: INSERT INTO `marc_tag_structure_descriptions_translations` (`tagfield`, `liblibrarian`, `libopac`, `language`) VALUES ('102', 'Country of Publication or Production', 'Country of Publication or Production', en), ('102', 'Pays de publication ou de production', 'Pays de publication ou de production', 'fr-FR'), ('102', 'País de publicação ou produção', 'País de publicação ou produção', pt-PT'), ... There may be other options that are even more elegant and/or practical than this last one. Any suggestions? I understand that this may require relatively large changes in code in SQL files and Perl code ("refactoring"), so it would take a while to implement. But I also think that it could SAVE us time (and lots of trouble) in the long run. What do you (all) think? Am I totally wrong here? Cheers, Ricardo P.S: - ZENO: if you spend holidays in Portugal, send me an e-mail, so I can buy you a beer! :)

1 0