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

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

Problems with Koha 3.0.3 download
by Chadwick, John, DCA 28 Jul '09

28 Jul '09

Last week I downloaded Koha 3.0.3 from the link on the www.koha.org <http://www.koha.org/> home page. The command I used was: wget http://download.koha.org/koha-3.00.03.tar.gz at the linux command file. The download went smoothly. The extraction and build were successful. When we went to build the application and install the mysql tables, the version number indicated that we had version 3.00.02.012. I tried the download again today. Same problem. The kohaversion.pl script is showing 3.00.02.012 as the version. So, what are we installing? Is it 3.0.3 or is it 3.0.2.12 Thanks, John +----------------------------------------------------------------------- -----+ John Chadwick, Ed.D. Information Technology Manager New Mexico State Library 1209 Camino Carlos Rey Santa Fe, NM 87507 Phone: 505-476-9740 Cell: 505-629-8116 Fax: 505-476-9761 john.chadwick(a)state.nm.us http://www.nmstatelibrary.org Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. Confidentiality Notice: This e-mail,including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review,use,disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the MessageLabs Email Security System.

3 3

Re: [Koha-devel] Label Bug 2944
by Chris Nighswonger 28 Jul '09

28 Jul '09

Would someone (maybe from BibLibre) verify that this bug has been fixed on a NoZebra Koha? http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2944 Kind Regards, Chris Christopher Nighswonger Faculty Member Network & Systems Director Foundations Bible College & Seminary www.foundations.edu www.fbcradio.org

1 0

New bugzilla default assignee for labels
by Galen Charlton 28 Jul '09

28 Jul '09

Hi, Chris Nighswonger has volunteered to be the default assignee for the label printing component. Since the previous assignee was mason.james(a)liblime.com, which is a defunct address (though not a defunct person. Hi Mason!), I've made this change. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Bound Volume
by chirag purohit 28 Jul '09

28 Jul '09

Greetings, Can anyone suggest how "Bound Volume" feature can be implemented in Koha? Thanking you in anticipation, -- Purohit Chirag

1 0

virtual hosting on different databases
by Zico 27 Jul '09

27 Jul '09

I am trying to run two virtual koha on same server. That means, i am differentiating this by two different port numbers. 8080 & 8085. Now, if i want to use *two different database* for two ports, what i need to do? I think, i can clear my needs. Situation will be like this: If one wants to access: 192.168.1.233:8080 --> he/she will work on *koha * database If another one wants to access: 192.168.1.233:8085 --> he/she will work on *koha1 *database. Is it possible? -- Best, Zico

5 6

Letters.pm
by Colin Campbell 27 Jul '09

27 Jul '09

I've been looking at C4/Letters.pm as the templating fails to generate useful output for claimissues. I can certainly get it to work with some code changes but I started wondering if a better use of long term effort might be to replace the home grown templating with a tried and tested perl module. It could use Template Toolkit for instance without changing the user interface, but resulting in more maintainable code. Thought I'd float that suggestion for comments. Cheers Colin -- Colin Campbell Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campbell(a)ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com

3 2

To maintain documentation about MySQL level of Koha
by Zeno Tajoli 27 Jul '09

27 Jul '09

Hi to all, I'm on the path to improve CILEA effort on maintain Koha MySQL level documentation. I think that tha starting point could be the wiki page http://wiki.koha.org/doku.php?id=en:development:dbschema Many documents are not more avaible. Link about 2.2.0, 2.0.0 and 1.3.3 are not valid 2.2.0 [<http://www.koha-fr.org/presentation/MCD_version2_2_0.sxd>http://www.koha-fr.org/presentation/MCD_version2_2_0.sxd 15KB], [<http://www.koha-fr.org/presentation/MCD_version2_2_0.pdf>http://www.koha-fr.org/presentation/MCD_version2_2_0.pdf 230KB] 2.0.0 [<http://www.koha-fr.org/presentation/MCD2.sxd>http://www.koha-fr.org/presentation/MCD2.sxd 15KB], [http://www.koha-fr.org/presentation/MCD.pdf 230KB] [<http://www.koha-fr.org/presentation/MCD1.jpg>http://www.koha-fr.org/presentation/MCD1.jpg page 1, 160KB] [<http://www.koha-fr.org/presentation/MCD2.jpg>http://www.koha-fr.org/presentation/MCD2.jpg page 2 170KB 1.3.3 [<http://irref.mine.nu/user/dchud/koha-schema/>http://irref.mine.nu/user/dchud/koha-schema/ available here] I think that Paul Poulain could find them but I'm not sure. So, could anyone send me those files ? I will insert the file in a specific file dir of the site www.koha.it and I will insert the link the wiki page http://wiki.koha.org/doku.php?id=en:development:dbschema I will insert the files in the site www.koha.it because the wiki in http://wiki.koha.org could host only images, not files. But if situation change, no problem to insert files in http://wiki.koha.org. Bye Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

1 0