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

ALL Programmers & Template designers please note
by Tumer Garip 22 Aug '06

22 Aug '06

Hi all, Although officially KOHA runs on Unix and Firefox there is quite a lot out there that uses Windows and Internet Explorer with Koha. Especially with the new ZOOM integration KOHA is now fully Windows compatible as well. However a silly javascript error prevents current frameworks from being used in Internet Explorer. The bug (I consider it a bug in IE) is that any popup window name that contains a space throws a javascript error. So please name the popup windows in window.open scripts with no space. i.e. instead of “Koha Help” pls use “Koha_Help” or a single word. This will help those windows users like us as not to edit all the templates everytime we update. I know that officially we say Firefox but I think it’s a shame to ignore IE just because of one its bugs. Thanks all, Tumer -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.405 / Virus Database: 268.11.3/423 - Release Date: 18.08.2006

3 2

New feature (idea) for Koha 3
by Paul POULAIN 16 Aug '06

16 Aug '06

Hello, A new feature that could (should ?) be implemented in Koha 3 : biblios have the "ISBD" system preference, that contains a personnalised version of the biblio. My libraries reported that it would be nice (better) to have : 1- 1 specific "template" for each itemtype 2- a specific "template" to show the summary of the biblio in the result list (= having a different template for monographies & serials for example) 3- the same thing for authorities. (I must admit that authorities details are really awful, it's almost the raw MARC record) Unless someone declares he is already working on this, I'll do it (me or hdl or antoine, depends on who get some time to do this. I think 2 days are needed to do something working well) PS : Other ideas in the same area : - rewrite the "normal" (=detail.pl), to get rid of non MARC database - add a systempreference to enable MARC view or disable it in OPAC. Warning : "template" don't mean "HTML::Template", it means something the library can modify -- 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

4 4

FW: RDBMS like behaviour or merged result sets from ZEBRA-ZOOM
by Tümer Garip 16 Aug '06

16 Aug '06

-----Original Message----- From: Mike Taylor [mailto:mike@miketaylor.org.uk] Sent: Tuesday, July 25, 2006 12:43 PM To: Tümer Garip Cc: support(a)indexdata.dk; 'Joshua Ferraro' Subject: RDBMS like behaviour or merged result sets from ZEBRA-ZOOM Tümer Garip writes: > We have come a long way in integrating ZEBRA and ZOOM into KOHA and > first examples are already running in some libraries. That's great news. > However we now have a problem that we could not solve and wonder > whether its us or the capabilities of ZEBRA or ZOOM (probably all) > thats preventing further development. > > We have two different types of MARC records. Namely bibliographic > and holdings. These records are related to each other with uniquie > ID numbers. A bibliographic record can have multiple holdings > record related to it. > > We are having problem searching these records in RDBMS manner. i.e > Searching for say title which exists in bibliographic record and > limiting that search to a specific branch which exists in holdings > record. Let me make sure I understand what you're trying to do here. It's a two-stage search, in which you first want to search the list of works for books with a certain title, then find the holdings records for nearby libraries that have the books of that title? In a relational database, it would be something like this: select all from works,holdings where works.title = 'Harry Potter' and holdings.work_id = works.id and holdings.library_id in (45,76,102); Correct? If so, you simply cannot do this with Zebra -- it's a relational query and Zebra is not a relational database. You can't even express such a query in the Z39.50 Type-1 or SRU CQL query languages. > We tried putting all the records in the same database could not do > it. We than tried putting them in different databases (even > different servers) but could not find a way of telling zebra to > merge the results together. > > For a small resultset we can do a recursive search of ID's on the > other database and get a merged resultset but library operations > work on large numbers and that is impossible when the small set is > around 1800 records. I think you mean code like this? (WARNING: UNTESTED) $rs = $works_conn->search('title="harry potter"); foreach my $i (1 .. $rs->size()) { $rec = $rs->record($i); $id = extract_identifier_from_record($rec); $rs2 = $holdings_conn->search("id=$id and library_id=45 or library_id=76 or library_id=102"); push @holdings_records, records_extracted_from($rs2); } That approach is the obvious one to take; but, no, it doesn't scale well when the initial result set is large. > Is there any way we can actually do this with the capabilities of > ZEBRA&ZOOM? > Something like @attr 1=52 (@resultset1 @attr 1=52)? > Or may be a new z:index called linkid which joins two databases or > different records within a database. What you're talking about is certainly in the realm of the possible, but it would be a _significant_ research, design and implementation task -- one, I think, that would beyond the Koha consortium's ability to fund. I am sorry to disappoint, but I think you're going to have to work round this one. > Any idea is appreciated as the whole database design is currently > stuck with this problem. Have you considered adding redundant data, such as author and title, to the holdings records? Then you could search them directly. Not pretty, but it may be pragmatic. _/|_ ___________________________________________________________________ /o ) \/ Mike Taylor <mike(a)miketaylor.org.uk> http://www.miketaylor.org.uk )_v__/\ The Unix command to kill processes is not "kill -9". The Unix command to make a tape archive is not "tar cv". Options are optional.

4 3

Theme Structure 3.0
by MJ Ray 15 Aug '06

15 Aug '06

Our current template structure is something like: SITE/htdocs/SITE-tmpl/THEME/LANG/OBJECT where SITE = { intranet, opac } THEME = { default, npl, vanilla, ... } LANG = { <empty>, en, es, fr, pl, zh-TW, ... } OBJECT = { <empty>, includes, LANG=en?images } It's probably not ideal to have all of these in htdocs, as some aren't really for direct download. Languages and images are also subordinate to themes, which has some side-effects. I suggest splitting includes, languages and templates so we get something like: templates/TYPE/THING/SCOPE where TYPE = { htdocs, l10n, tmpl } THING = { images, includes, LANG, default, npl, vanilla, ... } SCOPE = { default, intranet, opac, ... (may grow if needed) } and language, style and theme are set independently in koha. koha then looks at templates/l10n/LANG:templates/tmpl/THEME :templates/tmpl/THEME/LANG for its files, which may include things from templates/htdocs served by the httpd. This will let koha themes, styles and translations be maintained and used independently. As this requires some rewriting of the httpd config, it should be possible to support the single-vhost installation which seems a FAQ (when you only have one hostname-port combination to run on). The downside is that we will need to provide guidelines for the themes, styles and translations and it may need some careful work to get the same performance as the current template compiler. So that we don't lose anything if it doesn't work, I will branch 3.0 when the time comes and develop/test it there. Comments? Thanks, -- MJ Ray - see http://mjr.towers.org.uk/email.html North End, Lynn, Norfolk, England Work: http://www.ttllp.co.uk/ IRC/Jabber/SIP: on request

6 7

Koha 3, new features local "includes" directory
by Paul POULAIN 14 Aug '06

14 Aug '06

Hello, During the dev_week, in May, we spoke of a new method to have personalized templates. the idea being to have something more easy to changes than a full theme of templates. It's very hard to keep a full set of templates uptodate, the difficulties we have with default & npl on rel_2_2 branch show clearly this ! HTML::Template is really smart : it contains a TMPL_INCLUDE pragma that can be used to import outside templates. The directories where the templates are taken from is defined when you open the template. We have divided our PROG templates in different conceptual parts : * the header, in doc_head_open.inc & doc_head_close.inc (we have 2 so we can put a <title> in it) * the main menu, in menus.inc * the module menu, in menu-modulename.inc. Each module (acquisition, cataloguing, authorities, circulation, members, serials, parameters, tools, reports...) has it's own included file. * the main part of the page : it's specific to each template. * the footer, in intranet-bottom.inc I just have added a systempreference, called "intranet_includes" that let you define the directory where the included files will be taken from. by default, it's the "includes" directory. BUT, if you modify the value to "includes_npl", you'll arrive to something that look like the npl templates (roughly, it's just a Proof of Concept). -- 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

3 2

Upload MARC records in reservoir
by miguel miguelito 13 Aug '06

13 Aug '06

It is the first time that I write to the list, thanks for the great work and aid to all. The concerned registries are stored in the table marc_breeding Now according to description as it looks for a new title or ISBN first looks for in reservoir and if it finds it there passes to the cutting bilio, but to my it does not work to me, talvez so that I am in version Windows and/or lack data, notices that local data do not rise, in the file iso, this file iso creates it according to the manual of koha.org, denominated Migrating to CDS/ISIS based system to koha, concretely of even the Now section the tab separated cases out using to Perl script (shown below) and convert it ace MARC! or UNIMARC. Thanks for rpta. Greetings. --------------------------------- LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com

1 0

serials management (HEAD)
by Paul POULAIN 11 Aug '06

11 Aug '06

Hello, I was reviewing antoine code cleaning & fixed some bugs in serials management. I also took a look at katipo alt-subscription-add, the one with javascript to create subscriptions through easy questions, not only through the awful numbering formula form. It seems it's so nice & contains no loss of feature. That's why I think it could be our official subscription management screen. Any comments ? If none, then I (after holidays) or some one else can overwrite subscription_add.tmpl & .pl with alt_ & remove alt_ from cvs. -- 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

translations for Koha 2.2.6
by Paul POULAIN 10 Aug '06

10 Aug '06

Hello all, i've commited an updated version of ALL translations of Koha that are on CVS for 2.2.6 I will be away for 2 weeks of holidays (from friday afternoon) & come back on august, 28th. If you have a developper access to CVS, then update your translation, i'll see the commit, but you can warn me or here. If you don't have a developper access to CVS, then update your translation & send me the .po file by mail, i'll deal with it when i'll be back. You can get uptodate translations from : http://cvs.savannah.nongnu.org/viewcvs/koha/misc/translator/po/?root=koha&o… You'll see some new translations strings : spanish, basque, ukrainian, ... -- 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

Re: [Koha-translate] Ukrainian face for KOHA
by Paul POULAIN 10 Aug '06

10 Aug '06

Serhij Dubyk / Сергій Дубик a écrit : > Hello Hello Serhij, 1st of all, I really must apologize, because your mail is 4 months old... the good news is that I never (or almost never) loose an important mail, and your was in "todo", but I could not find time to act... > Here are a few Ukrainian things: > > 1)PO's: > intranet-tmpl/default/uk > default_intranet_uk_UA.po > opac-tmpl/css/uk > css_opac_uk_UA.po > (need I send full template folders?) That's a good question... I think that yes : Koha 2.2.x is now stable enough to be sure it won't change too many times. anyway, i've added your .po files. If you could update them to be 2.2.6 compliant in the next 2 weeks, then I could release 2.2.6 with official support of ukrainian language. > 2)marc_datas > unimarc_uk > authorities_unimarc.sql > structure_def.sql Thanks, added to CVS > 3)small sql-datas > Ukrainian > stopwords.sql > stopwords.txt Thanks, added to CVS > Small count of visible string I not found, but I maybe look for it in new > Koha. > > also > > ?) Question about traslation /value_builder/, plugins..? plugins have been written initially to french directly. I could not find time (& courage) to translate them to english, then again do the translation english => french). Sorry. > ?) In unimarc_fr/structure_def.sql is present holding information (9XX) on > French, - whether I can somewhere find the names of these fields/subfields > on English? I don't know > > During a translation I collected difficult and significant words in a > dictionary, some of these words I would like to add in a > DifficultTerms-page (but whether I can to do it in a utf-8 encoding?) that's OK for me (& iirc, you already did it on wiki.koha.org isn't it ?) > In our library we use ISIS long time. Previously our ISIS-DB was accessed > for OPAC with self-programmed code (OpenISIS+Perl). > But now I do not want to invent a wheel. Hope in course of time to bring > in the deposit in Koha (what to me all anymore and liked anymore). > At this moment we are engaged in the concordance of all of our DB (on the > whole near 200.000 records) from Unimarc, in search of bugs, duplets, > farther converting in Unimarc-Slim (OpenISIS+Perl) and in Unimarc > (Perl:Marc). that would be good ! > I also am very interested in Koha CD, whether Koha CD will be let out > with an update version? I don't know. I'm not sure anyone take care of Koha CD atm... -- 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

Re: SPAM- [Koha-devel] koha 2.2.6RC2 is ...
by Paul POULAIN 10 Aug '06

10 Aug '06

Michael Hafen a écrit : Hi Michael, > Probably isn't a good thing to reply to a release announcement, but I'll > do it anyway. No problem to do this. > If I new you were working on patron pictures I would have contibuted. I > even have a script for uploading patron pictures, which I will attach. The good news : you have contributed => I have added your scripts to official release. I just have added a warning that the feature is "experimental", as i'm not sure it will work out of the box (maybe some directory permission problems may occur) > You mention the item list in the result set being changed to show the > number of (similar) items, rather than one item per line. I have a > different solution to this. A little code, and a little javascript I > use to collapse the item list if there are more than a certain number of > items to display. I will also copy that code to this message for you to > see. Maybe someone will like this better. I won't copy this code immediatly, but the idea is good. The only problem i'm afraid is that, when cataloguing a daily serial, you can have 300+ items. In this case, the html would be heavy & the javascript probably not so quick. I let your code in cc:, it will be in koha-devel history if someone want to give it a try one day (for koha 3.0) > in search.marc/search.pl and opac-search.pl > for (my $i=0; $i <= $#$results; $i++) { > my @items = @{$$results[$i]->{CN}}; > # collapse copy info column if more than a few copies > if (@items > 3) { > $$results[$i]->{collapse} = 1; > } > } > > in search.marc/result.tmpl and opac-searchresults.tmpl > <td><acronym title="click for copy > information"><a name="copies__a" > onclick="expand('copies_');" > class="expander">...</a></acronym><div style="display:none;" > id="copies_"> > -->   <i>(Checked out > until )</i> ()<br /></div></td></tr> > > ... > > function expand() { > for (e_index = 0; e_index < expand.arguments.length; e_index++) { > e_id = expand.arguments[e_index]; > e_block = document.getElementById(e_id); > if (e_block.style.display == 'none') { > e_block.style.display = 'block'; > } else { > e_block.style.display = 'none'; > } > } > } > > in intranet.css and opac.css > > a.expander { > text-decoration : underline; > cursor : pointer; > } -- 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