Good advice, and I would add that a "minimum" set seems to me to be
anything that enables you to contact the constituent in any way. I
have a client who uses email alerts pretty regularly. They have
migrated the list of email addresses into ebase to enable them to use
ebase to track contacts. For many of these listings they have only
email addresses and a list of contact records. This satisfies the
constituent's need to control access, and still gives the
organization a means to track their relationship with these
individuals.
Another very important aspect of a style sheet is what information
goes into what fields. Each field should have only one type of
information, and be entered consistently so searches work well.
>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
>---------------------------------------------------------------------
--
--
Dave Shaw H4 Consulting
tel: 206-954-7526 fax: 206-625-1338
------------------
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
---------------------------------------------------------------------
