Re: data integrity

An example of a data integrity issue is where my web form asks for
the PI last name and the client gives me both first and last name. Or
they put their name in the PI name field (PI stands for principle
investigator - the person who got the grant that we will charge
funded), or they put an extra digit in what should be an 8-digit
string if they are here at OHSU, but could be any length if they are
from somewhere else. Or they use a grant identifier (called an
"alias") that is valid but belongs to someone else. Stuff like that.

My biggest complaint about FMP is that it can't do rollbacks. So a
simple error can lead to catastrophic loss of data. Plus, in the last
few years they've wanted to charge for upgrades about every 6 months.
OHSU used to have a site license, but dropped it.

Thanks,

Tom K
kellert(at)ohsu(dot)edu
503-494-2442

On Mar 30, 2007, at 12:57 PM, Rich Shepard wrote:

> On Fri, 30 Mar 2007, Thomas J Keller wrote:
>
>> Would one of the local gurus like to give a talk on strategies for
>> improving data integrity?
>
> Tom,
>
> How do you define "data integrity?"
>
> Rich
>
> --
> Richard B. Shepard, Ph.D. | The Environmental
> Permitting
> Applied Ecosystem Services, Inc. | Accelerator(TM)
> <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax:
> 503-667-8863
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that
> your
> message can get through to the mailing list cleanly
>