Skip to end of metadata
Go to start of metadata

Organization inputs new contact (individual) from a non-digital source (e.g. signup sheet)

Description
  1. SM navigates to 'Add Contact' screen
  2. SM inputs person's name, home address, phone and email
  3. Module checks for possible duplicate (existing) contact record
  4. New contact inserted (if no duplicates)

Goal

Add a new contact for the organization

Scope and Level

Functionality, detailed

Preconditions
  • Staff member (SM) has valid account
  • SM has 'add-contact' permission
  • SM has contact information
  • Contact does not already exist in DB|

    Success End Condition

    Failed End Condition

    Actors

    SM or volunteer w/ valid account and permissions

    Trigger

    Individual provides contact information to organization

    Frequency

    Very frequent use
Outstanding Issues
  • Are any fields REQUIRED?
  • Email address is normally unique key - but orgs won't have email addresses for all contacts.
Alternate cases
  1. Contact info retrieved from email, vCard or other digital source
  2. Self-serve membership/mailing list/etc. sign-up (web)
  3. Synch / import batch of contacts from another digital source
Labels:
None
Edit Labels

1 Comment

Hide/Show Comments

  1. Jan 27, 2005

    Anonymous

    The precondition "contact does not already exist in DB" sounds simple, but is not. I would have something like:

    2. SM enters last name and optionally, first name
    3. Module lists any matches with sufficient info to uniquely identify
    4. SM picks a match; if no match, completes entering new contact information
    5. etc

    – Pat Dunlavey


Creative Commons License
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-Share Alike 3.0 United States Licence.