I agree with Walt on both counts. Unless you have a compelling reason, it
isn't wise to automatically/arbitrarily exclude people who give money/time
from receiving communications. And my boss can testify to the perils of
gender-neutral names. He has had many a letter addressed to "Ms. Dorian G."
--
Beth Hynes
Parks & Trails Council of Minnesota
275 East 4th Street, #642
Saint Paul MN 55101
NEW: [EMAIL PROTECTED]
651-726-2457
> I don't know your organization but we have to cater to people who want to
> remain quite private. One we only know an address and a name of VLK
> (probably initials). Another we know essentially nothing. They wanted our
> membership card which is good for a 10% discount so they stopped by the
> office , paid cash, picked up their card and left. The card has their name
> and expiration date but nothing else. It is hard to turn down memberships
> which cost you essentially nothing.
>
> Prefix is a dangerous item to require. Can you guess whether to put in Mr.
> or Ms. for a first name of Loren? Is it worth getting it wrong?
>
>> -----Original Message-----
>> From: Shaugn Schwartz [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, August 14, 2001 9:56 PM
>> To: TechRocks Support
>> Subject: [support] Style Sheet
>>
>>
>> Helpful people:
>>
>> I'm in the mist of creating a style sheet for data entry. We are having a
>> lively in-house debate about setting mininum standards. Currently we are
>> considering setting the following mininum required fields:
>> -prefix
>> -first name
>> -last name
>> -complete home or work address (we have customize ebase to enable us to
>> put in to sets of addresses - dave's handy work!)
>> -work tel or home tel or cell tel or email
>>
>> This would enable us to send solicitations and other communications to
>> contacts using a few methods. Considerable resistance exists from
>> programming/campaigning staff to being required to input last names or
>> home phone numbers. The standards are being label discriminatory as they
>> wouldn't enable people who don't want to give all this contact information
>> access to our communications.
>>
>> I would welcome advice on what contact fields to set as required fields
>> and why? Also, does anyone have recommendations regarding the process for
>> developing/adopting a style sheet?
>>
>> regards. shaugn
>>
>>
>>
>> ------------------
>> Reminder to each recipient: To change your list account preferences, go to
>> http://email.sparklist.com/scripts/lyris.pl?enter=support and
>> enter the email address you used to subscribe to the ebase
>> support list:: [EMAIL PROTECTED]
>>
>> To unsubscribe send a blank email to [EMAIL PROTECTED]
>> ---------------------------------------------------------------------
>> ebase - Relationship Management for Nonprofits, http://www.ebase.org
>> ---------------------------------------------------------------------
>>
>>
>
>
> ------------------
> Reminder to each recipient: To change your list account preferences, go to
> http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the
> email address you used to subscribe to the ebase support list::
> [EMAIL PROTECTED]
>
> To unsubscribe send a blank email to [EMAIL PROTECTED]
> ---------------------------------------------------------------------
> ebase - Relationship Management for Nonprofits, http://www.ebase.org
> ---------------------------------------------------------------------
>
>
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address
you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
