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

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

Authorities : Tree Display.
by Henri-Damien LAURENT 31 Jul '06

31 Jul '06

Hi, I designed a display of trees for hierarchical authorities. It is based on an analysis of authority records. It is mainly hard-coded. But could get adapted if need be. (And this avoids a big bunch of system preferences.) In my case, trees were to be found for subject authorities (main heading in field250). In UNIMARC, $3 subfield contains authority number, $5 contains a code that will tell you whether the field contains a broader term ($5==g) or a narrower term ($5==h). So let's take an example. 250$3 1212 $aEurope 550$3 1213 $5 g $aContinents 550$3 1214 $5 h $aFrance 550$3 1215 $5 h $aGermany 550$3 1216 $aNATO Will be displayed : Continents+ (Europe Asia America Africa...) (Continents) +Europe+ (France Germany) hierarchy.css contains the stylesheets for these facilities. So long. -- Henri-Damien LAURENT

1 0

Frameworks in rel_2_2
by Joshua Ferraro 31 Jul '06

31 Jul '06

Hi Paul, Mainly a question for you. It looks to me like it's possible in rel_2_2 to define different mappings to the koha tables for different frameworks such that the editor ends up saving data to different fields depending on the definition. However, I don't see any search facility that uses frameworks to discover which fields to search. As a result, if you create an record using a framework that has mappings that disagree with the default framework, I'm assuming that the fields won't be searchable. If I'm correct, then we need to either: not allow frameworks to disagree on koha mappings or create a way to search using the alternate frameworks (seems very difficult). Let me know what you think ... Cheers, -- Joshua Ferraro SUPPORT 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

4 5

new behaviour for authorities (in rel_2_2)
by Paul POULAIN 31 Jul '06

31 Jul '06

Hello the list, I made some changes in rel_2_2 behaviour in authorities : - i've removed the automatic % for truncation, and added a comment to remind it, in the form. the % must now be explicit. - there are now 3 search lines : search on main entry ($a only), search on main entry (main field, all subfields), search anywhere. Those 2 changes have been requested by a library, and seems harmless & good to me. I just point them for alternate templates (npl for example), to remind you to update them. -- 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

Koha Meeting
by Joshua Ferraro 28 Jul '06

28 Jul '06

Hi all, It's that time again ... I've scheduled a Koha Developer's Meeting for Monday, July 31 at 20:00GMT. Here's the time in your area: http://tinyurl.com/kq6cd Here's the agenda ... feel free to add to it: http://wiki.koha.org/doku.php?id=agendandnotes06jul31 Cheers, -- Joshua Ferraro SUPPORT 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 1

Koha 2.3.0 (development version)
by Joshua Ferraro 27 Jul '06

27 Jul '06

Hi all, I'm happy to announce a new DEVELOPMENT release of Koha is now available for download: Koha 2.3.0. It is the first fully-functional version of Koha to include Zebra support. Apart from the Zebra-specific code, this release is identical to rel_2_2 (soon to be 2.2.6). A word of caution, the installation process is not automatic at this point, your best bet is to check out the Wiki for the latest (evolving) information on how to install this Zebra version of Koha: http://wiki.koha.org/doku.php#marc_zebra_and_encoding_notes In the coming weeks we'll be sprinting towards a full-fledged 2.4.0 release, so stay tuned. Cheers, -- Joshua Ferraro SUPPORT 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

[IMPORTANT] some time to spend on Koha 3 : what to do next ? + SAN goals
by Paul POULAIN 25 Jul '06

25 Jul '06

Hello guys, I'll have some time to spend on Koha 3 at the beginning of august. What could be usefull according to you ? (knowing that Antoine still works on code cleaning : he works on acquisition module ATM) I thought testing & debugging & unimarc'ing on dev_week could be interesting. I would also be interested by synch'ing dev_week & head, depending on the stability of dev_week. SAN goals : ----------- In september, SAN want to start working on testing & teaching librarians. The goal being to start working in production in January, 1st I told them I will make all my best to have something working in september, at least beta stage. They need zebra (dev_week)+ all what btoumi & alaurin worked on, (head) thus the merge of dev_week & head is something urgent for them. PS : dont tell me their goal is impossible to reach, they would be very unhappy with this. I told them it will be hot/hard, but not impossible. Maybe it's time for an irc meeting (next monday ? it's OK for me) -- 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

2 1

zebra config files : about default.idx
by Paul POULAIN 24 Jul '06

24 Jul '06

Hello all, i've investigated half a day on my accented problem on zebra : I had a specific default.idx, mapped to french-specific word-phrase-utf.chr config files, but... when searching for "helene" I had not the same results as when searching for "helene". This makes me mad, until I tought I was looking in the wrong direction. In fact, there is a default.idx file in /usr/local/share/zebra, and my zebra-biblio.cfg had : profilePath:${srcdir:-.}:/usr/local/share/idzebra/tab/:/home/paul/koha.dev/dev_week/zebraplugin/zebradb/biblios/tab/:${srcdir:-.}/tab/ I inverted my path and /usr/local : profilePath:${srcdir:-.}:/home/paul/koha.dev/dev_week/zebraplugin/zebradb/biblios/tab/:/usr/local/share/idzebra/tab/:${srcdir:-.}/tab/ and ... it works. Thus, it seems that profilePath directories are solved : "the 1st that fits is choosen" instead of "the last that fits has won" (like for cascading stylesheets for example) So my 2 questions : * did you encounter this problem and had the same conclusion ? * don't you think it could be reported as a problem to indexdata ? * isn't the wiki wrong on this ? (I can change it if you confirm) and yes, I know, that's 3 questions ;-) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

4 6

about recent serials commits...
by Paul POULAIN 21 Jul '06

21 Jul '06

Hello Robert, (& Chris & al), i've seen your recent commits around serials. I've taken a quick look at them, and your commit notes are quite ... small ... (+ new script don't always have a POD doc, shame on you !) could you give us some explanations on what they did ? for example : * did alt_subscription_add REPLACE the previous subscription_add, in your idea, or is it another one, the previous being still useful ? * I need some details on routing features & claims.pl (PS : thx to have commited to PROG & fresh /serials/ directory + fixed some wrong links still pointing to /bull/ !) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2 1