X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EF85CD1C9E8 for ; Wed, 28 Jul 2004 01:07:44 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34582-02 for ; Wed, 28 Jul 2004 04:07:36 +0000 (GMT) Received: from sharp.noc24x7.com (unknown [69.56.128.138]) by svr1.postgresql.org (Postfix) with ESMTP id BCF74D1B7A7 for ; Wed, 28 Jul 2004 00:55:51 -0300 (ADT) Received: from [61.1.218.208] (helo=thenilgiris.com) by sharp.noc24x7.com with asmtp (Exim 4.34) id 1BpfXg-0001RD-M9; Wed, 28 Jul 2004 09:25:50 +0530 Received: from localhost (localhost [[UNIX: localhost]]) by thenilgiris.com (8.11.2/8.11.2) id i6S2Eqk32260; Wed, 28 Jul 2004 07:44:52 +0530 Content-Type: text/plain; charset="iso-8859-1" From: Kenneth Gonsalves To: "Iain" , "Karsten Hilbert" , Subject: Re: surrogate key or not? Date: Wed, 28 Jul 2004 07:44:50 +0530 X-Mailer: KMail [version 1.2] References: <1090325769.3241.27.camel@dicaprio.akademie1.de> <04072711335024.01150@thenilgiris.com> <001f01c47442$4dd673a0$7201a8c0@mst1x5r347kymb> In-Reply-To: <001f01c47442$4dd673a0$7201a8c0@mst1x5r347kymb> MIME-Version: 1.0 Message-Id: <0407280744502B.01150@thenilgiris.com> Content-Transfer-Encoding: 8bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sharp.noc24x7.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - thenilgiris.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/234 X-Sequence-Number: 18486 On Wednesday 28 July 2004 06:59 am, Iain wrote: > > couldnt you do something like, let them write the 'long flaky text', and > > at > > > the same time mark a certain number of key words or key phrases which > > could > > > be stored and retrieved? > > I was thinking along similar lines. On one hand, you need the "long flaky > text" (love that expression), on the other, you want to ensure that you can > locate appropriate data, and that the required details are available. By > available, I mean that it was entered in the first place, and that it is > retrievable. I imagine a system whereby you define keywords and attributes > for them (attributes would be an episode date, or dosage, etc). The memo, > is checked for keywords and the doctor prompted to supply the attributes > for them. If your parsing was smart, and the memo formated a little, you > could conceivably pull a lot of this out of the memo as defaults. The > processing could also be done retrospectively by an intern or researcher, > but I imagine it would be best to have the doctor do it at the time. simpler, as a first stage and easily implemented, give him some way he can tag words and phrases he feels important. save these in a table along with a foreign key identifying the source. as a second stage keep analysing the words and phrases chosen and empirically build up a database of significant words and phrases relevant to that specific installation (or doctor), and as a third stage, highlight these as he types in the data -- regards kg http://www.onlineindianhotels.net - hotel bookings reservations in over 4600 hotels in India http://www.ootygolfclub.org