pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kenneth Gonsalves <lawgon@thenilgiris.com>
To: Iain <iain@mst.co.jp>
To: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: surrogate key or not?
Date: Wed, 28 Jul 2004 07:44:50 +0530
Message-ID: <0407280744502B.01150@thenilgiris.com> (raw)
In-Reply-To: <001f01c47442$4dd673a0$7201a8c0@mst1x5r347kymb>
References: <1090325769.3241.27.camel@dicaprio.akademie1.de>
	<04072711335024.01150@thenilgiris.com>
	<001f01c47442$4dd673a0$7201a8c0@mst1x5r347kymb>

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



view thread (44+ messages)  latest in thread

Message-ID: <0407280744502B.01150@thenilgiris.com>
Permalink:  ../0407280744502B.01150@thenilgiris.com/
Also on:    postgresql.org/message-id/0407280744502B.01150@thenilgiris.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: lawgon@thenilgiris.com, iain@mst.co.jp, Karsten.Hilbert@gmx.net
  Subject: Re: surrogate key or not?
  In-Reply-To: <0407280744502B.01150@thenilgiris.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox