Return-Path: X-Sieve: cmu-sieve 2.0 Received: from hermes.ort.edu.uy (hermes.ort.edu.uy [164.73.96.24]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "hermes.ort.edu.uy", Issuer CN "hermes.ort.edu.uy" (verified OK)) by correo.ort.edu.uy (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id 86EC69CFC1; Fri, 8 Jul 2005 15:09:43 -0300 (UYT) Received: from hermes.ort.edu.uy (hermes [127.0.0.1]) by localhost.ort.edu.uy (Postfix on RedHat 7.3 (i386)) with ESMTP id 5A745B710C; Fri, 8 Jul 2005 15:10:40 -0300 (ART) Received: from daddy-mx.katipo.co.nz (daddy.katipo.co.nz [202.50.109.200]) by hermes.ort.edu.uy (Postfix on RedHat 7.3 (i386)) with ESMTP id CCCCCB7484; Fri, 8 Jul 2005 15:10:38 -0300 (UYT) Received: from localhost (localhost.katipo.co.nz [127.0.0.1]) by daddy-mx.katipo.co.nz (Postfix) with ESMTP id 1EFAAE6ECE; Sat, 9 Jul 2005 06:05:04 +1200 (NZST) Received: from daddy-mx.katipo.co.nz ([127.0.0.1]) by localhost (daddy.katipo.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17868-05; Sat, 9 Jul 2005 06:05:02 +1200 (NZST) Received: from localhost.katipo.co.nz (localhost.katipo.co.nz [127.0.0.1]) by daddy-mx.katipo.co.nz (Postfix) with ESMTP; Sat, 9 Jul 2005 06:05:02 +1200 (NZST) Received: from localhost (localhost.katipo.co.nz [127.0.0.1]) by daddy-mx.katipo.co.nz (Postfix) with ESMTP id C7F24E6E99 for ; Sat, 9 Jul 2005 06:04:56 +1200 (NZST) Received: from daddy-mx.katipo.co.nz ([127.0.0.1]) by localhost (daddy.katipo.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15775-09 for ; Sat, 9 Jul 2005 06:04:55 +1200 (NZST) Received: from ipex1.johnshopkins.edu (ipex1.johnshopkins.edu [162.129.8.141]) by daddy-mx.katipo.co.nz (Postfix) with ESMTP for ; Sat, 9 Jul 2005 06:04:55 +1200 (NZST) Received: from jhuml1.jhmi.edu (162.129.8.66) by ipex1.johnshopkins.edu with ESMTP; 08 Jul 2005 14:09:11 -0400 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.93,274,1115006400"; d="scan'208"; a="75248863:sNHT20103152" Received: from jhuccp.org (jhuccp.jhuccp.org [162.129.225.189]) by jhuml1.jhmi.edu (PMDF V6.2-X20 #30839) with ESMTP id <0IJB007CAMFAWN@jhuml1.jhmi.edu> for koha@lists.katipo.co.nz; Fri, 08 Jul 2005 14:09:10 -0400 (EDT) Received: from jhuccp-MTA by jhuccp.org with Novell_GroupWise; Fri, 08 Jul 2005 14:09:10 -0400 Date: Fri, 08 Jul 2005 14:08:49 -0400 From: KEVIN ZEMBOWER To: koha@lists.katipo.co.nz Message-id: MIME-version: 1.0 X-Mailer: Novell GroupWise Internet Agent 6.0.4 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Content-disposition: inline X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at katipo.co.nz Subject: [Koha] Documentation of database structure for Koha 1.? X-BeenThere: koha@lists.katipo.co.nz X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion list for the Koha Library system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: koha-bounces@lists.katipo.co.nz Errors-To: koha-bounces@lists.katipo.co.nz X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at katipo.co.nz Greetings, all. I'm working on a Koha system that I think has been heavily hacked to work = in both Arabic and English. I was told that it's version 1.1 or 1.2 or = 1.2.3. Is there any way to tell definitively? I can access the Intranet = interface, but don't see where the version information would be listed. I = can also shell into the host. Because of the effort that went into changing this version to work in = Arabic, I don't think that there's any desire to upgrade it to the current = versions. However, if the current versions work 'out of the box' in = Arabic, they could possibly be persuaded. Any chance of this? I'm trying to import a set of data representing items in a database of = Health Communication materials (posters encouraging people to use condoms, = for example). This data isn't in MARC format, unless I convert it myself. = There's too much material, over 1,000 items, to input them one at a time = through an acquisitions page. What advice would you offer on how to = efficiently input records like these? I'm pretty good with perl and MySQL = and can transform the records however needed. If I wanted to just input the records directly into the MySQL tables of = Koha, I need some documentation on the tables. Do diagrams or descriptions = of the tables that make up this version of Koha exist anywhere? I'm = thinking of things like entity relationship diagrams, or relation schemas, = ideally. Thank you for all your advice and suggestions. -Kevin Zembower ----- E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha