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

error when adding vendor
by mallikarjun dora 13 Oct '08

13 Oct '08

Dear ALL Koha error The following fatal error has occurred: Undefined subroutine &main::AddBookseller called at /usr/share/koha/intranet/cgi-bin/acqui/updatesupplier.pl line 92. Apache Server version: Apache/2.2.8 (Linux/SUSE) Server built: Jun 6 2008 23:42:07 Koha 3.00.00.107 Koha DB 3.0000107 MySQL mysql Ver 14.12 Distrib 5.0.51a, for suse-linux-gnu (i686) using readline 5.2 OS Linux susekoha 2.6.25.5-1.1-pae #1 SMP 2008-06-07 01:55:22 +0200 i686 i686 i386 GNU/Linux Perl 5.010000

3 2

Authority Control RFC
by Brian Harrington 09 Oct '08

09 Oct '08

I was reading over the RFC for authority control enhancements in 3.2, and they look like great changes that we would love to see. I do have a quick question though. Will there be any provision for preserving local changes in an authority record when merging the imports. Maybe something as simple as preserving fields that have a subfield 5? Thanks, Brian -- Brian Harrington Content and Resource Development Coordinator Project MUSE The Johns Hopkins University Press brian(a)jhu.edu

1 0

Problem in /koha/members/memberentry.pl?
by Nahuel ANGELINETTI 09 Oct '08

09 Oct '08

Hi, An user of intranet ask me why there is two "E-mail (home):" input in /koha/members/memberentry.pl. After reading the code, only one of the three e-mail adresses asked in this form is saved : " elsif ($newdata{email} =~ /\w\@\w/) { $emailaddr = $newdata{email} } elsif ($newdata{emailpro} =~ /\w\@\w/) { $emailaddr = $newdata{emailpro} } elsif ($newdata{B_email} =~ /\w\@\w/) { $emailaddr = $newdata{B_email} } " Can you tell me why 3 e-mails are asked(with a duplicate input) and only one is saved? Why there is no asked only one e-mail? The member can choose which one he want to give. And there are more than one B_email input in the form (cf : Alternate address). I think it's strange to ask too much informations and keep only a bit. Regards, -- Nahuel ANGELINETTI

2 1

Koha 3 Hosting
by zang＠zang.co.za 08 Oct '08

08 Oct '08

Can anyone please help with Koha 3 Virtual hosting issues? We are currently hosting Koha2.2.9 without a problem. I basically copy the Koha 3 database and change the database name in koha-conf.xml. On running the web page on port 8080, the system comes up with the installation page. Is there anything else to be changed? Thanks for any advice.

3 7

RFC: support for 3M RFID reader 810 in koha
by Dobrica Pavlinusic 04 Oct '08

04 Oct '08

Last week I was playing with reverse engineering protocol of 3M 810 RFID reader to make it integrated with our Koha installation. Currently I understand enough protocol to detect and read tags, but programming and blanking is just a matter of (free) time. Current source code (if anybody wants to take a look) is available at: http://svn.rot13.org/index.cgi/RFID Now I'm in stage where I would love to integrate it in Koha, so I'm seeking for feedback. Since machines on which reader is connected are Windows, and data which can be gathered are usable only when paired with data from Koha, I have two possible solutions: 1) Connect RFID reader serial port to some kind of Windows service (suggestions welcomed!) which would allow my perl script to connect it over network and drive reader (this has additional benefit that all pages in web browser come from my Koha server, so I don't have problem with same origin policy in browser). 2) install perl on windows and run reader driver there, integrating with Koha using frame set (one frame Koha window, another frame reader) This would require to have some kind of REST API for Koha which I could use from JavaScript within browser. I would like to support following user interaction with Koha (and reader): * putting book on RFID reader opens it's record in Koha (this would probably require some kind of long-poll from browser to Koha so that server can update browser window as soon as RFID tag is detected) * button which allows you re-program RFID tag of book on reader by clicking on button beside bar-code in Koha interface. Sound indication would provide feedback about finish of programming. I would prefer solution (1), but solution (2) would allow me to use firefox -remove to change browser URL and I would be able to generate sound notification easily (without some kind of flash which would be needed to make sound identification work in first possible solution) However, making less moving parts on 30 machines which have reader connected to them seems like good enough reason to move all logic to server driven readers. I could probably write few more pages about this, but this might be enough for this message. Your comments are greatly appreciated :-) -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

1 0

Re: [Koha-devel] [Koha] Creating reports in Koha 3.0
by Jesse Weaver 01 Oct '08

01 Oct '08

On Wed, Oct 1, 2008 at 10:06 AM, Kathy Rippel <kdr(a)ckls.org> wrote: > I agree, Marie. The list should have terms that librarians will recognize, > not programmers. The underlying structure can still use the programming > terms. > > Kathy > > > At 03:41 PM 9/30/2008, Nicole Engard wrote: > > As far as I know there isn't a list. It's sort of hit or miss. I usually > find out just testing different fields. I'm CCing the Koha List in case > they have any ideas. > > > --- > > Nicole C. Engard > Open Source Evangelist, LibLime > (888) Koha ILS (564-2457) ext. 714 > nce(a)liblime.com > AIM/Y!/Skype: nengard > > http://liblime.com > http://blogs.liblime.com/open-sesame/ > > > On Tue, Sep 30, 2008 at 4:20 PM, Marie Wardall <MWardall(a)dce.k12.wi.us > > wrote: > Hi Nicole- > I'm looking at our test data for our school district and am trying to get a > handle on creating some custom reports because some of the reports in the > Wizard just don't pull enough or the right data. > > When I go into the custom report area I'm getting confused as to what a;; > of the things mean in Step 3 where you select columns for display. Is there > someplace that describes each of these so that I can make a good choice? > > Any help you could give me would be appreciated. > > Thanks, > > > Marie J. Wardall > Library Media Specialist > Mountain Bay Elementary School > 8602 Schofield Ave. > Weston, WI 54476 > mwardall(a)dce.k12.wi.us > Phone: 715-355-0302 ext. 5824 > > Change Today, Change Tomorrow, Keep Changing > > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > > Kathy Rippel > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > As far as I know, this is due to the columns.def file not being up to date with the Koha database. A while back, we discussed using MySQL's COMMENT option to put descriptive information in the table schema. We have a couple of options: * Update columns.def so that it has all of the columns referenced by the guided reports tool. * Using a db update, add comments to all of those columns. These can be gotten by SHOW FULL COLUMNS FROM <table>. This has the advantage of being more "proper", but is yet another displayed string in the database that would have to be translated... somehow. My vote is for columns.def, since it's under the template tree and therefore easily internationalized. Thoughts? -- Jesse Weaver Software Developer, LibLime

2 1

SOPAC2 & Koha
by Paul POULAIN 01 Oct '08

01 Oct '08

Hello, does anyone around have taken a look at SOPAC ? and plans to work on a connector to Koha (Locum) ? That's something we could investigate in the very next future, as we are working on Drupal. So, if anyone is already working on that, we would be happy to join the effort. cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08

1 0

RFC 3.2: stop copying item data to MARC and MARCXML
by Galen Charlton 01 Oct '08

01 Oct '08

Hi, Currently, item record data exists both in the items table and as MARC fields in the bib record (in biblioitems.marc and biblioitems.marcxml). The MARC serialization of the item record is controlled by the MARC framework, and unless one wants a maintenance headache, the same mapping of item fields to MARC subfields must be used for all frameworks. This has several deleterious effects: * updating an item record (e.g., in circulation), forces the ISO 2709 and MARCXML versions of the bib record to be recreated. This is an expensive operation, and if a bib record has several hundred items a checkout or return can take several seconds (or longer) to complete. * If a bib has a large number of items, the ISO 2709 version can go over the maximum length - see bug 2453. * unless one makes a special effort, one is stuck with the same MARC item mapping for both import and export. Some libraries need to import bib records from more than one source and don't always have the ability to dictate that their Koha item field mapping be used by the record supplier. * maintaining two versions of the same data can and has led to bugs. * changing the item field mapping requires one to change Zebra (and NoZebra) index definitions. * this is a denormalization of the database schema, and one that doesn't provide any performance gains. Consequently, I propose the following changes, in order of priority: 1. Take item data out of biblioitems.marc*. Instead, whenever item records need to be embedded in a MARC bib record (primarily during Zebra indexing or record export), do it on the fly. If a bib record has lots of items, this will still be an expensive operation, but it will take place in a batch job or indexing daemon. 2. Separate the item field mapping from the rest of the MARC framework. Allow multiple item field mappings, each identified by a code, and add the ability to specify a mapping to be used during record import, export, or indexing. 3. Switch to Zebra's DOM filter and supply item data for indexing outside of the MARC bib record; instead, define an XML schema to wrap bib, item, and summary records without force the last two to be embedded in the MARC. This is similar to an idea that I believe Tümer Garip proposed back in 2006. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

3 6

koha code cleaning bug?
by Marc Chantreux 01 Oct '08

01 Oct '08

hello all, the code that ends this email comes from zebra_rebuild.pl. It can be rewritten as: for('',qw( lock register shadow tab key )) { next if -d; $created_dir_or_file++; system("mkdir -p $authorityserverdir"); print "Info: created $authorityserverdir/$_"; } That is not a bug but it is currently written makes the things harder to read and maintain and it discourages to provide a patch to improve the code(imho). I would like to provide a patch to clean this code. This code is not the only one and so i wonder if the koha communauty wants to have this kind of patch. I also wonder how to do this because of the "fill a bug first" policy. It can be possible to create a "code cleaning" bug that will stay unfixed and our patches can be related to this one. regards, unless (-d "$authorityserverdir") { system("mkdir -p $authorityserverdir"); print "Info: created $authorityserverdir\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/lock") { mkdir "$authorityserverdir/lock"; print "Info: created $authorityserverdir/lock\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/register") { mkdir "$authorityserverdir/register"; print "Info: created $authorityserverdir/register\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/shadow") { mkdir "$authorityserverdir/shadow"; print "Info: created $authorityserverdir/shadow\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/tab") { mkdir "$authorityserverdir/tab"; print "Info: created $authorityserverdir/tab\n"; $created_dir_or_file++; } unless (-d "$authorityserverdir/key") { mkdir "$authorityserverdir/key"; print "Info: created $authorityserverdir/key\n"; $created_dir_or_file++; ... -- Marc Chantreux http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc

9 24