Database Description

Usability

The biggest obstacle to having well managed information is the time it takes to get and enter accurate data. The cure is two-fold:

  1. Make the data entry easier than a paper form.
    People take notes when interviewing a volunteer, and expect to do a little work making their notes readable and sharable after the interview is done. Entering data in the database replaces the task of filling out a paper form, and is more flexible and more automated. The same is true when talking with clients or managing projects.
  2. Don't ask for too much.
    If the database gets too detailed, then it feels overwhelming and becomes a dreaded task that fosters procrastination. We must guard against trying to make the database "do everything for everyone."

Data retrieval and analysis are the payoffs. With the appropriate password, any staff member can get current, accurate information whenever they need it.

Password levels

The database can be accessed from an internet web link, or typing in a web address on any browser (Internet Explorer, Firefox, Safari, Opera, Netscape, etc.). There are four user levels:

  1. Public - contact request form on a web site.
  2. Staff - Detailed read and edit access to all Volunteer, Client and Project data.
  3. Admin - Change settings are non-technical in nature.
  4. Manager - Low level access for installation and maintenance, including settings of a technical nature.

The public interface is for potential clients or volunteers to express interest by filling out simple contact request forms. A person from our program should then respond to the request. Public access could also include a featured "Project of the Month". No other access to any data. Clients do not have access to the data.

The Staff has access to all info. It's for anyone who contacts clients, interviews volunteers, facilitates projects or manages our program, but not for the volunteers. Since the data is in an SQL database, most data analysis tools (like spreadsheets and low-end database managers) can read and manipulate the data. So these people can get data for any special analysis purpose that arises, without effecting the rest of the database.

The Admin user can change non-technical setting like the email address of the person notified when web requests come in, or the wording of the

The Manager has access to a additional settings primarily used during the initial installation of the database.

Database Structure

Tasks

We all engage in many tasks that generate information with long term value. We might for example:

Too often in non-profit organizations, the information gained is captured on paper, photocopied, distributed and ultimately filed in a drawer. Information from one task is not connected to the other tasks.

The "More Than a Coin" database software has clear sections that support each of the above tasks. Capturing information is at least as easy as writing it on paper. But tremendous labor savings are realized because the data is dynamic and accessible. Information is never entered twice. Reports are always up to date.

Data Structure

The basic data structure is centered on three major data tables:

  1. Organizations - one record for each Client NPO or other organization.
  2. People - one record for each Volunteer or contact.
  3. Projects - one record for each time a Volunteer works for a Client.

Much of the data is pretty routine stuff like names and addresses. The database currently has "info" notes that are clicked from the form as context-appropriate documentation. Although it seems quite obvious, it is important to talk to other staff members to ensure that everyone is clear about what data goes where. Different people can look at the same data field, and even read the info note explaining it, but arrive at a different conclusion about what to enter. This becomes very important as the database expands.

It is vital that users never put data where it does not belong. This can cause any number of embarrassing effects like a stray comment showing up on an automated email to a client, or inaccurate outcome metrics being presented to a generous donor. There are "Comments" boxes for every project, person and client organization. Use them for odd items and keep the structure clean. One last plea: be careful to never, ever enter the same person or same organization twice. This is very confusing to users and the software alike. Lots of things start to break!

Workflow

One advanced piece of data deserves special attention. Each client, volunteer and project has a "status" that is used to drive workflow. "More Than a Coin" provides live data on what is at which status at all times!