Over time data has a tendency to drift off the road and even crash. The application itself might be fine, but the data is a wreck. When this happens, those depending on it no longer trust it, and start looking for something new.
One popular solution is to put a sentry at the gate of the database. This person is responsible for all data entry, reports, and maintenance. This solution helps keep data safe, but it also creates a bottleneck on use of the data. Like an accident on a 4 lane highway narrowing traffic down to one lane, church staff end up looking for detours to get their work done. Pretty soon the staff has data in so many locations they find themselves once again lacking trust in the core data.
We've felt for a long time that the database itself could become a decentralized sentry. We built reminder emails (groups, volunteers, payments) to make sure data is consistently collected. We built scheduled reports to automate communication of information.
We've also started building guardrails designed to keep data from getting wrecked. In fact, we've released seven of these in the past couple of months. Here they are along with a few other new releases.
- Guardrail for Text-to-Church registrations
- Guardrail for merging members OR families
- Member listing by household gives lots more options
- Guardrail for using mission fundraising setting
- Guardrail for deleting a custom attribute
- Guardrail for transferring people between groups
- Guardrail for changes to pledge registration
- Legal first name, birth date, and deceased date are no longer customizable
- Guardrail for merge validation based on gender
- Mass update member multi-select attributes capability expanded
1. Guardrail for Text-to-Church registrations
One problem with Text-to-Church registrations is people using their phone to register someone other than themselves (family member or friend). When they click on the registration link, the system recognizes their number and pre-fills the form with their information. If they change the information in the form to someone else's information, the system inadvertantly wrecks the data. Now, when this happens the registrant will get this warning pop-up with a link to a new form to complete for the friend or family member.
If the form allows registration of multiple people, this pop-up appears.
2. Guardrail for merging members OR families
To help distinguish the need to merge one person (member) with multiple entries from two different people who need to be merged into one family, we separated the Merge Member from the Merge Family page. The blue, information box gives more details.
When a merge is completed, the system logs a note on the person's profile with details about the merge including the person who performed it.
3. Member listing by household gives lots more options
The Family Directory report (Reports > Members > Family Directory) was designed to be a directory with demographic information. This new option under Reports > Members > Member Listing allows you to customize the data you see but is organized by families. This is helpful for families with multiple different last names especially.
4. Guardrail for using Mission Fundraising
There is a new popup after you pick a fund from the dropdown that explains further.
To help make sure that you want to delete a custom attribute we added a pop up that clarifies for you what is about to happen and the number of individual records that will be affected.
6. Guardrail for transferring people between groups
7. Guardrail for changes to pledge registration
8. Legal first name, birth date, and deceased date are no longer customizable.
9. Guardrails for merge validation based on gender
Intending to put a husband and wife into the same family and doing it on the member merge page rather than the family merge page is a fairly common mistake. It will mess up data by merging everything to one individual. We added some logic to help avoid this.
Both member IDs are included in the system log details to help with clean up in case this mistake is made.