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

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

New KOHA3 API -design issue
by Tümer Garip 20 Jul '06

20 Jul '06

Hi all, If Joshua approves you will soon be seeing a big commit to head that changes the API of KOHA 3 very soon. Here is what I have done so that we can share comments and improvements on this. Major changes: 1-Bibliographic, Holdings and Authority records are all separate MARC records. 2-All searches rely on ZEBRA indexing and searching (Z3950 compliant) 3-Non MARC data handling is dropped. Non-marc like display is kept 4-All data is UTF-8. No other encoding supported as this support all languages 5-Change affects all data handling so for a short time breaks all modules (circulation, serials,acquistions and the lot) 6-Templates not affected More detail: Database design: 1-biblioitems, marc_words,stopwords, marc_subfield_table, autth_subield_table, additionalauthors, subjects,categories, marc_blob tables completely dropped 2- biblio table now has: biblionumber,marc,itemtype,framework 3-items table now has : itemnumber,biblionumber,barcode,marc 4- auth_header table now has: authid,marc 5- 1 new frameworks table added similar to marc frameworks for holdings marc 6- A new koha_attr table added. This one is for creating virtual fields which we do not have any more. Also helps matching your own MARC indexing rules to KOHA and ZEBRA. (More on this later) Design issues; 1- itemtype definition still kept at bibliographic level. Can be very easily converted to item level. i.e one bibliographic record with different itemtypes (book,cd,dvd etc).Open for discussion 2- All items (holdings) are single marc records, instead of all items in one marc record for the same bibliographic record. The main idea behind this is flexibility and speed. One full record for an item gives lots of fields to put all that information that you wanted to keep but did not have extra subfields left. All data including circulation data is kept within the marc records, this approach makes circulation updates faster as we do not have to reindex unchanged data related to other items again (zebra technicalities!). 3- All MARC framework designs have OPAC:show-hide Intranet:show-hide Editor:show-show collapsed-hide as dropdown selections so not to wory about what we put in these MARC fields. All handled correctly 4- Circulation speed is improved. One marc update instead of 6 sepatrate database update calls we used to have. Currently working modules: -MARC editor works - Item screen although looks the same now has multiple fields and works - authories adding editing works but needs to be improved to bibliographic editor design -Circulation works but being updated for faster handling -Serials and acquisitions needs work The new koha_attr table: We used to match our marc frameworks to table field names for both being multi-marc compliant and for template design issues. These field names now do not exist. So now we create virtula ones by a user editable screen. Although it comes filled with all the previous field names (and many more extras) to keep all koha modules and templates working you can add as many as you want when the need arise. No need to change database structures. But a table just for this feature was not needed, we could have had those names as authorised values so i added another functionality to this table. It matches your KOHA field names to ZEBRA indexing. This way the majority of koha code stays intact and field names joing our records like subcrisptionid itemnumber barcode etc can function as previous and removes the strain on programmers to either programme with PQF,CQL or CCL. A routine supplied converts everything to zebra language. This approach also release the strain on developers on trying to match what zebra is indexing and what koha thinks or should be indexed. Specially at this development stage until a KOHA minimum indexing standarts is defined this gives both the programmer and the library freedom of movement. A library may also decide to use completely inhouse designed indexing attributes and not comply with standarts like Bib-1 or Gils. All you have to do is fill you koha attr tables in sysadmin and tell koha what barcode is and what title is.Koha will continue to function. In simpler terms it does what frameworks does but compliments that table and bring ZEBRA in. I will be writing more on this issue after the commits but in the mean time expect to have your comments on all the issues regarding this upgrade. Cheers Tumer Garip NEU Grand Library

3 4

RE: SPAM- [Koha-devel] New KOHA3 API -design issue
by Tümer Garip 14 Jul '06

14 Jul '06

Hi Michael, Good point. They do not do the same thing though. There are three different framework structures currently in KOHA. Until we decide to join them all together to one MARC-KOHA-ZEBRA framework I did not want to repeat the same process of koha=>zebra conversion for three. Thats why it exists. But probably the next step will be to join them into one table.Both has cons and pros. That why this thread has been started. -----Original Message----- From: Michael Hafen [mailto:mdhafen@x.washk12.org] Sent: Friday, July 14, 2006 6:41 PM To: Tümer Garip Subject: Re: SPAM- [Koha-devel] New KOHA3 API -design issue I have one question at this point: If Koha_attr does what frameworks does, then why is the frameworks table still used? Wouldn't it be easier to drop the framework table and use Koha_attr table as a drop in replacement? Or have I misunderstood the purpose of the Koha_attr table? Ok, so that was actually three closely related questions. ;) Keep up the good work.

1 0

Planet Koha is broken
by Corey Burger 14 Jul '06

14 Jul '06

Hey all, Don't know who I should mention this to, but Planet Koha appears broken. It also appears that Planet Koha has a link to the old wiki. Corey

2 1

Re: [Koha-devel] Planet Koha is broken
by Corey Burger 14 Jul '06

14 Jul '06

On 7/13/06, Rachel Hamilton-Williams <rachel(a)katipo.co.nz> wrote: > hi > > > Don't know who I should mention this to, but Planet Koha appears > > broken. It also appears that Planet Koha has a link to the old wiki. > > Could you be a bit more specific about the brokeness? Do you not see > anything? Or is it a coding problem? > > cheers > Rachel I apologize. On futher investigation, it appears the planet is in fact, no planet at all. The source shows me some links and nothing more. As it is in the old Koha style and currently lacks content, we could remove the link from the main website until somebody fixes it (I am not volunteering, due to lack of skill). Corey

1 0