>As I began to design systems for our organization, I thought it
>would be possible to keep every communication with every person
>stored within ebase. As time went by, this seemed less and less
>possible. So now, I think, the copies of individual outgoing
>communications must be stored as Word documents (we use Word) or
>Eudora documents in files separate from ebase. Similarly, incoming
>communications must be stored properly.
>
>But, when looking at an individual record, how can one easily know
>all of the important communications there have been with that
>individual?
>
>I'd love to have your thinking on how to store incoming and outgoing
>documents, both electronic and physical, and how to reflect them on
>ebase records.
ebase is set up to store a record of constituent communications (not
the communication itself). For example, the Contacts file contains
records of letters and emails you sent to a constituent. The Actions
or Payments files contain a record of the response (sent you a
letter, made a donation, etc.) You could add fields to Contacts and
Actions to record the location of the original document. The
directory and file name for a letter, for example, or the mailbox
name and date for an email, or the file drawer for a paper copy.
You're limited only by your ingenuity and the time you can dedicate
to filing, as Walt suggests.
--
Dave Shaw Northwest Classics, Inc
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
---------------------------------------------------------------------
