Message-Id: <9403031743.AA13907@us2rmc.bb.dec.com>
Date: Thu, 3 Mar 94 12:43:05 EST
From: touche!  03-Mar-1994 1229 <groff@epee.enet.dec.com>
To: dagoura@MIT.EDU
Cc: groff@epee.enet.dec.com
Apparently-To: dagoura@mit.edu
Subject: Re: more fields 

First comments:

~How about "Mundane Middle Initials:	[]	{char[3]}"?

why 3?  (For two+ middle names? (confused because I never saw a form that
	 handled more than one...)

~ >  Titles:               	[]	{char[40]}
~ >  Awards and Offices:   	[]	{char[60]}
~ >  Group: (ie Barony/Principality/Canton/Shire etc.)    []	{char[40]}
~ >  Interests: (IE: Fencing/Dancing/Woodworking/...) 	[]	{char[60]}
~
~Axe this; this serves no purpose at this point.

Actually, no... this serves a GREATER purpose.  Think about the Rolls-Etherial. 
Think about the FUTURE.  Lets say you wanted to contact everyone "on-line" who
has an interest in music.

	select sca-name, modern-name, enet from domesday, interests where
	interests contain "Music" and enet is not null;

BANG: you have a list

Think about a query that counts number of people PER group.  That way you know 
what group to contact for MORE information.

Consider: Gregor has asked that I contact the chivalry about an upcoming
meeting.  How could I do that?  I could select the domesday for EMAIL addresses
for all Knights!

NOT HAVING THE INFORMATION is a problem.  Having too much information is 
easy to deal with.

What I am NOT DOING is limitting myself to "reform oriented work".  I see this
as a project that is MUCH BEYOND that effort.  The reform stuff started this,
but it is much bigger and better than that.

-----

BTW: You are thinking "form" and I am thinking "DB layout" so... this is a good
way of flushing out dependancies...

-----

Present "form oriented" datastructure:

SCA INFORMATION
   SCA Name:             				[R]	{char[50]}
   SCA Member # (if a member):				[R]     {int}
   Titles:               				[O]	{char[40]}
   Awards and Offices:   				[O]	{char[60]}
   Group: (ie Barony/Principality/Canton/Shire etc.)    [R]	{char[40]}
   Interests: (IE: Fencing/Dancing/Woodworking/...) 	[O]	{char[60]}

RELEASE INFORMATION {flags}
   May the above information be published in an EK phone book? (y/n) [D:N]
   May the information be made available on-line? (y/n) [D:N]

 
MODERN INFORMATION
   Mundane First Name:         	[R]	{char[25]}
   Mundane Last Name:		[R]     {char[25]}
   Mundane Middle Initial:	[R]     {char[3]}
   Address1:              	[R]     {char[40]}
   Address2:                    [O]     {char[40]}
   City:                        [R]     {char[20]}
   State/Province:              [R]	{char[20]}
   Postal (Zip) Code:           [R]	{char[10]}
   Country:                     [R]	{char[15]}
   Phone # (home):              [O]	{char[16]}
   Phone # (office):            [O]     {char[16]}
   Phone # (fax):              	[O]     {char[16]}
   E-mail:               	[O]     {char[80]}
 

RELEASE INFORMATION {flags}
   May the above information be published in an EK phone book? (y/n) [D:N]
   May the information be made available on-line? (y/n) [D:N]

 POLL
   Will you leave the Society when "pay-to-play" and the rate hike are
     implemented? (y/n/m)                                  [O]  {byte}
   Have you ever been a paid member of SCA, Inc?: (y/n)    [O]  {flag}
     If yes: Currently? (y/n)                              [O]  {flag}
             How long were/are you a paid member 
				   (in years, decimal ok): [O]	{float}
   When did you first attend an SCA event (year):          [O]	{Int}
   Number of events you plan on attending this year:       [O]	{Int}
 
 OTHER
  Comments:		[O]	{segmented string}
  Last_Update_Date:	[A]	{Date}
  History:		[A]	{segmented string}
 	containing:
 	 Date:		[A]	{Date}
 	 Update_By:	[A]	{char[80]}
 	 Type of change	[A]	{keyword}


Where:

	[O] = optional
	[R] = required
	[D:N] = default = no
	[A] = automatically filled in (no need to ask it on the form)