From: dagoura@MIT.EDU
Message-Id: <9403030956.AA19132@al-burro.MIT.EDU>
To: touche! 03-Mar-1994 0330 <groff@epee.enet.dec.com>
Subject: Re: more fields 
In-Reply-To: Your message of Thu, 03 Mar 94 03:36:57 -0500.
             <9403030836.AA02890@us2rmc.bb.dec.com> 
Date: Thu, 03 Mar 94 04:56:15 EST


 >MODERN INFORMATION
 >  Mundane First Name:         	[]	{char[25]}
 >  Mundane Last Name:		[]      {char[25]}
 >  Mundane Middle Initial:	[]      {char}
 >

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

 >
 >  Address1:              	[]      {char[40]}
 >  Address2:                     []      {char[40]}
 >  City:                         []      {char[20]}
 >  State/Province:               []	{char[20]}
 >  Postal (Zip) Code:            []	{char[10]}
 >  Country:                      []	{char[15]}

Oops, yeah (duh!)

 >  Phone # (home):               []	{char[16]}
 >  Phone # (office):             []      {char[16]}
 >  Phone # (fax):              	[]      {char[16]}
 >
 >  E-mail:               	[]      {char[80]}
 >
 >SCA INFORMATION
 >  SCA Name:             	[]      {char[50]}
 >  SCA Membership #:		[]      {int}

Let's change this to "If paid member, SCA Membership #:"  I just had a
heck of a day convincing Mitgaardi that it was really ok for them to
sign the petition in support of the Crown, even if it did have a space
for "membership #".

 >  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.

 >RELEASE INFORMATION {flags}
 >  May the above information be published in an EK phone book? (y/n) []
 >  May the information be made available on-line? (y/n) []
 >  May the information be made available to the Crown of the East? (y/n) []

OK, here's my big problem.  While this whole schema is a neat
arrangement, it lost some contextual meaning from my last draft.  I
had a heirarchy, where by it was possible to release only SCA info OR
to release both SCA and mundane info.  We need to maintain that
somehow.

Also, if it is not a serious problem, I would like to have the SCA
info first.  

 >POLL
 >  Will you leave the Society when "pay-to-play" and the rate hike are
 >    implemented? (y/n/m)                                  []    {byte}
 >  Have you ever been a paid member of SCA, Inc?: (y/n)    []    {flag}
 >    If yes: Currently? (y/n)                              []    {flag}
 >            How long were/are you a paid member:          []	{Int}

    Insert "(in years)" in there; can {Int}s hand decimals? I assume not.

 >  Number of events you plan on attending this year:       []	{Int}
 >  When did you first attend an SCA event (year):          []	{Int}
 >
 >OTHER
 > Comments:		[]	{segmented string}
 > Last_Update_Date:	[]	{Date}
 > History:		[]	{segmented string}
 >	containing:
 >	 Date:		[]	{Date}
 >	 Update_By:	[]	{char[80]}
 >	 Type of change	[]	{keyword}


OK, so I would revise it so that it flows:

SCA INFORMATION
  .
  .
  .
RELEASE OF SCA INFORMATION {flags}
  May the above information be published in an EK phone book? (y/n) []
  May the above information be made available on-line? (y/n) []
MODERN INFORMATION
  .
  .
  .
RELEASE OF MODERN INFORMATION {flags}
  May the above information be published in an EK phone book? (y/n) []
  May the above information be made available on-line? (y/n) []
POLL
  .
  .
  .
OTHER
  .
  .
  .

I deliberately left off the question about release to the Crown.  That
should already be acquiesced to.  We need to have the form have the
relevant statement: "Submission of information to the EK Domesday Boke
consitutes granting of permission for that information to be
distributed within the guidelines of the Distribution and Access
Policy."  I'll go tighten up the policy.


Tibicen