[103] in iswork

home help back first fref pref prev next nref lref last post

Database design : Projects

daemon@ATHENA.MIT.EDU (Tim McGovern)
Thu Jul 13 11:20:55 2000

Message-ID: <396DDE52.611A8FE9@mit.edu>
Date: Thu, 13 Jul 2000 11:20:50 -0400
From: Tim McGovern <tjm@MIT.EDU>
Reply-To: tjm@MIT.EDU
MIME-Version: 1.0
To: iswork@mit.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Here's what I propose we use for the Filemaker database.
It's based on the latest design from the Oracle work that Miki and I did.
If you see any rough edges due to my translation, let me know.

Tim

-----

 Field name			Field Type

 project_id			number
 start_date			date
 end_date				date
 initiative			RELATIONSHIP TO initiative
 priority				text values("high", "medium", "low")
 status				text values("Active", "Pending", "Completed", "On
                                   Hold", "Terminated", "See Comment")
 name				text [length 255]
 description			text [length 2000]
 justification		text [length 2000]
 practice				text values ("Academic", "Office", VDI Networking")
 customers			text [length 255]
 notebook_url			text [length 512]
 responsible_person	text [length 50]  
					nb. this is a kerberos id usually
 cost_object	         number
 comment				text [length 255]
 entered_date			date
 entered_by			text [length 50] 
					nb. this is a kerberos id if we have it, 
					    or it can be "itlt" for the first version
 modified_date		date
 modified_by 			text [length 50] 
					nb. this is a kerberos id if we have it, 
					    or it can be "itlt" for the first version
-----

home help back first fref pref prev next nref lref last post