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

MARC Editor Visibility
by Joshua Ferraro 03 Apr '06

03 Apr '06

Hi all, thd and I have introduced some additional complexity into the MARC frameworks that offers a more complete handling of tag and subfield visibility. It's completely backwards-compatible so if you're happy with your current visibility options you don't need to do a thing and everything will behave exactly as it did before. First, I should introduce the problem: with the old scheme, there was a flag (INT(1)) that allowed hiding a subfield in the OPAC. You could also set a subfield to 'ignored' which was used for the special tags/subfields whose values are managed internally (e.g., 090). This would probably have sufficed but for the fact that thd has been working on a complete 'Standard MARC21 Framework'. In testing this framework (which includes 2/3s more fields than 2.2.5's default framework), we discovered that it was unusable due to long page loads (it's really quite a huge form with about 3,500 fields defined). (just to give you an idea of how slow it was, it took about 90 seconds to load a blank 'addbiblio' page and about 2-3 minutes to save a populated record). In addition, there is the problem of usability. With so many tags and subfields on a page it's very difficult to identify the most commonly used fields -- they are lost among the uncommon and rare fields. So we set out designing a 'visibility scheme' with three basic goals: 1. prevent very rare tags/subfields from being loaded into the MARC editor by default, but allow the user to add them if needed (with a page reload) and _definitely_ load them if they already exist in a record (ie, _no_ data lost when using the MARC editor). 2. allow uncommonly used fields to be collapsed and expanded quickly and easily without a page reload. 3. preserve the legacy 'hidden' functionality so the new framework isn't required for the upgrade to 2.2.6. As it turns out, there are quite a few possible visibility conditions that should be properly dealt with in a future version of Koha. Using the current framework's 'hidden' database definition (INT(1)) we can account for up to 19 such conditions (values -9 thru 9). Given that limitation as well as our current time constraint, we identified 17 conditions that will be defined in the new 'Standard MARC21 Framework' plus a 'Flag' condition that can be used to flag subfield definitions that will need to be revised when the framework can handle more conditions (ie, in 3.0). The scheme we devised is the following: ( ! means 'not visible' or in the case of Collapsed 'not Collapsed') -9 => Future use -8 => Flag -7 => OPAC !Intranet !Editor Collapsed -6 => OPAC Intranet !Editor !Collapsed -5 => OPAC Intranet !Editor Collapsed -4 => OPAC !Intranet !Editor !Collapsed -3 => OPAC !Intranet Editor Collapsed -2 => OPAC !Intranet Editor !Collapsed -1 => OPAC Intranet Editor Collapsed 0 => OPAC Intranet Editor !Collapsed 1 => !OPAC Intranet Editor Collapsed 2 => !OPAC !Intranet Editor !Collapsed 3 => !OPAC !Intranet Editor Collapsed 4 => !OPAC Intranet Editor !Collapsed 5 => !OPAC !Intranet !Editor Collapsed 6 => !OPAC Intranet !Editor !Collapsed 7 => !OPAC Intranet !Editor Collapsed 8 => !OPAC !Intranet !Editor !Collapsed 9 => Future use With this scheme, it's quite simple to check for the most important cases: *if (odd) { collapsed } *if (even) { !collapsed } if (>=0) { hidden in OPAC } if ((<=-4)||(>=5)) { not in the editor unless exists or is added} Those four checks take care of all the goals we set out to achieve. Of course, there are finer distinctions to be made, but we'll leave that for a future version. So just to clarify, we've implemented a subset of the scheme we devised -- a subset that doesn't comprimise where it counts (ie there won't be any data loss as with Koha 2.2.5). If you want to try out the new system feel free to use LibLime's demo: http://koha.liblime.com/cgi-bin/koha/acqui.simple/addbiblio.pl You'll notice that some tags (take 040 as an example) are listed but the subfields within them aren't -- simply click on the little + graphic to expand the fields (no page load) Likewise, some very rare tags/subfields don't appear by default. However, if you do a Z3950 search for a record and one contains them they will appear when you import the record (they will also import if they exist in records in the database). Cheers, -- Joshua Ferraro VENDOR SERVICES 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

3 5

Koha Developer Meeting Notes
by Joshua Ferraro 02 Apr '06

02 Apr '06

Hi all, MEETING NOTES FOR MONDAY MAY 3rd (20:00 GMT) Meeting Agenda: http://www.saas.nsw.edu.au/koha_wiki/index.php?page=AgendAndNotes06mar27 Present: chris,russ,hdl,paul,owen,thd,kados,slef Discussed UNICODE Status pierrick has been running utf-8 tables with no problems; kados will confirm it works for him as well thd reminded us that uft-8 doesn't work in every browser so we need a solution for such cases Zebra Integration (CQL in Koha) chris has been working on SearchMarc.pm getting the plugin working SearchMarc.pm is a drop in replacement for the SearchMarc.pm in 2.2.x PROG Template status opac PROG templates committed, mostly done, owen will continue to work on improving them RoadMap We need a plan for what we're going to do Developer's Week we need some fancy templates for the conference to demo perl-zoom chris suggested having 2 kohas running on the same machine, one with zebra, one without Program for KohaCon to be developed (done on the wiki already) slef asked why dates for kohacon were chosen for beginning of may: reason was that kados was going to be in Geneva already so it was convenient KohaCon to be announced on lists Problems with koha.org's accessiblity discussed and (hopefully) resolved -- Joshua Ferraro VENDOR SERVICES 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

borrower issues, work made twice
by Pierrick LE GALL 31 Mar '06

31 Mar '06

Hi koha-devel, circ/circulation and members/moremember are both showing a table of the unreturned issue of a borrower. The two page provides the same information, displayed with only very slight differences. I wonder why the same work is made twice. Should we have this table only on circ/circulation? and a link to circ/circulation on members/moremember? The link could give a summary of current issues (eg: "2 issues with 1 overdue"). Bye -- Pierrick LE GALL INEO media system

4 5

fieldsets in templates
by Pierrick LE GALL 31 Mar '06

31 Mar '06

Hi koha-devel, Still working on HEAD templates... Yesterday I made a commit on prog/en/circ/circulation.tmpl to make it comply with TemplateManual guidelines. (another commit to come in the day). To separate informations on the same page, I've used fieldsets. These HTML tag is made to group fields of a form in a logical way. On templates I've read so far, I mainly see multiple forms for each page, so I used one fieldset for each form. I wanted to have your feedback about using fieldsets. Bye -- Pierrick LE GALL INEO media system

3 2

Re: [Koha-devel] Koha Foundation
by COURYHOUSE＠aol.com 30 Mar '06

30 Mar '06

Greetings... I am back! There are lots of computers that get tossed here in the US .. A foundation would allow you to approach companies to set these in far away places and pick up the freight tab as a donation. Intel and other large US companies also donate stuff... Bill and Melissa gates foundation donates stuff... although the thought of them donating boxes to run LINUX on might not seem appropriate... Anyway bottom line... having a foundation or non profit corp. in the US you would be able to offer US companies and US citizens tax incentive for helping.. Sad to say ... most of the time if there is no tax incentive they will do nothing. OK now for the legal parts... > ... If you are going to incorporate in just one country II would incorporate the foundation in what ever country would offer the best donations, as you will have to be incorporated in that country to offer the citizens the tax benefit. The US with the abundance of technology stuff here seems to make sense. But you can also incorporate it in many countries just like you do a corporation for profit. Thanks, Ed Sharpe, Archivist for SMECC See the Museum's Web Site at www.smecc.org We are always looking for items to add to the museum's display and ref. library - please advise if you have anything we can use. Coury House / SMECC 5802 W. Palmaire Ave. Phone 623-435-1522 Glendale Az 85301 USA I also know many libraries in Africa that could be interested by such computers, with Koha (server or client -firefox-) installed.

1 0

No way to reorder catalog search results?
by Kyle Hall 29 Mar '06

29 Mar '06

Hey all, I've been tinkering with the search.marc/search.pl and search.tmpl files because we'd like to add 'sort' links in the table headers for the search results (like the ones used in reserve.tmpl). I noticed the variable $orderby, but it is only used in function findseealso($dbh, @tags). So, as far as I can tell, what I would like to do is not possible without modifying search.pl. Can anyone confirm or refute this for me? Thanks for the help. Kyle IT Tech Crawford County Federated Library System

2 1

(head) new features to come soon
by Paul POULAIN 29 Mar '06

29 Mar '06

Hi, I was with SAN Ouest Provence yesterday & I have some good news. The following code should reach head in April : * Borrowers improvements = see previous mail (feb, 17th). * branches identification : a new column has been added in branches. It let the library define a range of IP attached to the library. If defined, then the librarian, when identified, is automatically located to the branch where the IP is. If IP empty, no change in the behaviour. * Reserves improvements : - the librarian can reserve a given item, not only a biblio/biblioitem - many improvements in transfert management - 3 new reports to know "what the library will recieve", "what the library has sent", "what is to get in shelves and put in the transfert car". For all those reports, the library has a button to do something in a single clic (recieve, sent, transfert...) - a new systempreference has been added to remove the reserve after a <<sytempref>> day duration. Everything is done. Some tweaking needed, they should send me all code in a week or two. I'll integrate it in CVS before KohaCon (promised) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

1 0

KohaCon, wiki updated
by Paul POULAIN 29 Mar '06

29 Mar '06

Hi, i've updated the wiki, KohaCon page. Many more informations (more to come) pls read -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org)

1 0

new database update mecanism
by Pierrick LE GALL 29 Mar '06

29 Mar '06

Hello koha-devel, Last week, I explained on #koha I wanted to propose a new database update mecanism [1]. Here is my proposal, I would like some feedbacks before coding... The idea is to simplify communication between developers on database update (data and/or structure). Here follow the main points of the mecanism: - isolated updates that can be executed only once - database self aware about its update level - notification in intranet screen that new updates are available A script update/updater.pl is run from the command line. The steps are: 1. list updates already executed (reading table "updates") 2. list available updates (numeric filenames in update/updates directory) 3. execute available updates that have not been executed yet These are the basics. updater.pl will first say if there are updates to execute. For example: $ updater.pl > 2 updates are missing, choose an option: > > 1. list update details > 2. execute all > 3. execute one by one > > [1] ? updater.pl will write a log on each call. Update files will be Perl files in the update/updates dedicated directory, with numeric only filenames: $ ls -v1 updates > 1 > 2 > 2.1 > 10 About numerotation of updates, on HEAD, updates are named with a single number (1, 2, 10...), on a branch like rel_2_2, updates are named with the last update number on HEAD point a number wich starts to 1 on rel_2_2. Just as an example, we could have: +------+ | HEAD | +------+ | | +---------+ | | rel_2_2 | 43 => | +---------+ 44 => | | +-----------+ | | <= 44.1 | | 45 => | | | | <= 44.2 46 => | | | | | | <= 44.3 | | 47 => | | | | | | | | 48 => | | <= 44.4 | | <= 44.5 49 => | | 50 => | | +---------+ 51 => | | rel_3_0 | 52 => | +---------+ 53 => | | +-----------+ 54 => | | <= 53.1 | | 55 => | | <= 53.2 | | | | | | <= 53.3 | Now, let's give me your feedback please :-) [1] http://tinyurl.com/ep6nx Cheers, -- Pierrick LE GALL INEO media system

2 3

Koha with MySQL 5
by psm＠vu.ernet.in 28 Mar '06

28 Mar '06

Hello friends, I'm unable to run koha with MySQL 5 in WIndows environment. The problem is with the MySQL connection. Can somebody guide? Parthasarathi Mukhopadhyay Vidyasagar University, India

1 0