Addressee and Salutation fields - major clean up required
I’m sure you can imagine how vexing and tiresome this has become in a short while. So much so, that I'm considering a full overhaul of all the preferred Addressee and Salutation fields. Before I go there, I thought I’d invite your advice and/or tales of caution. Have you done a full overhaul? Did you use Global Change or go the Import route? What kinds of checks did you like best to confirm changes? How much time was needed for every 10K records?
Comments
-
We did an overhaul where we changed some of our addressees when we updated our standards. I did an export that included the last name of the individual and the spouse, as well as gender and titles for each, then created an attribute to identify which standard the person would be getting (Mr. John Doe who was married to Mrs. Jane Doe would get Mr. and Mrs. John Doe; Mr. John Doe married to Ms. Jane Smith would get Mr. John Doe and Mrs. Jane Smith, etc.) and imported the attribute, then used global change to add the appropriate addressees and salutations based on a query for each type of attribute. I then deleted the attribute.1
-
I've done this with Global and it works very well if:
1) you set up your queries VERY carefully
2) your add/sals are not checked for "Edit"
If the Edit checkbox has been used, your clean up project will be far more difficult, but it is still doable.
I would recommend that you build a list of very definde standards, build those Add/Sals in Config and then do as much as you possibly can via Global.0 -
Carolyn Moatz:
We did an overhaul where we changed some of our addressees when we updated our standards. I did an export that included the last name of the individual and the spouse, as well as gender and titles for each, then created an attribute to identify which standard the person would be getting (Mr. John Doe who was married to Mrs. Jane Doe would get Mr. and Mrs. John Doe; Mr. John Doe married to Ms. Jane Smith would get Mr. John Doe and Mrs. Jane Smith, etc.) and imported the attribute, then used global change to add the appropriate addressees and salutations based on a query for each type of attribute. I then deleted the attribute.You can also set up queries based upon gender, title, spouse title/gender, spouse connection to your org, etc. You may still have to do a separate pull to sort out spouses with different last names, but that can be pretty easily done and then you can just import those. The attributes will definitely work though and are a great idea - especially if you're concerned about missing something in building out that many queries.0 -
Hi Eleonore,
Are you looking at all records, or all active records?
I might suggest first breaking down the task by only looking at the active records. From there, I might suggest looking at some of my best donors (high givers, frequent givers, etc.) and determine how I want the addressee and salutation fields to look (ie spouse, no spouse) and address those inconsistencies that you reference in your post. I would then make a plan and set up the addressee/salutation table so the addressees/salutations that you want to now use are listed.
Once you have a documented plan on how you want the records to read, you can start to divide them in groups using query. For example, you could run a query for all records that contain a non-deceased spouse and make them a group. Make a second group of individuals with no spouse, etc. You can make as many queries as you want to divide your donors.
From there you can use these queries in Admin to globally replace the exitsting Addressee/Salutation with your new chosen formula. You could look at each query again after you apply your global changes and see if there are any individual records that need to be tailored.
After finishing your cleanup, I would suggest revisiting those best donor records and make sure their addressee/saluations are correct. I'm always extra cautious with those
It's not perfect - but I think it's "directionally correct". We did something similar here a few years ago and were met with success. I hope all of this makes sense - please let me know if it does not.
Thanks,
Susan
1 -
After using RE for a couple of years I felt need to get all our add/sal standarized. I admit I put it off thinking it would be much more difficult that it was. Biggest thing to me was determining the default set of add/sal that we wanted on every record. Once that list was decided (single formal, single informal, joint formal, joint informal, salutations to go with each, last name/first name single, and last name/first name joint) there were added. We have spouse records in our db so if I remember correctly we had 4 groups: standard records-male HOH, records with female HOH, records with spouse having different last name, and those who we do not have gender/title data on. I believe we did by global function. We did not do a separate format/default set for single individuals as using smart function in add/sal the joint add/sal will show as John Brown and then if a spouse is added to record, that add/sal will auto update and we don't have to go add another. Yes, it just means there are two add/sal that appear to be the same at initial glance at the record but are actually not. Don't know what issue would be for only adding to active records. I would do them all-just my opinion. Also, if you've unchecked the spouse link box when you marked a record as deceased, you shouldn't have to worry about add/sal pulling in names from deceased spouses.
As add/sal doesn't have ability to use first name when there is no nickname, the one thing I wish I had done was to populate nickname field with first names so that I would be able to use that field more effectively. Oh, well. Someday maybe I'll tackle that.
We use informal add/sal for 99.9% of our work.
There have been a number of post about how to use the add/sal table and set it up.1 -
Two things: One, I learned the hard way that spouse relationships where one is deceased really mess you up if you haven't queried for that!
Two, our policy is:
ADDRESSEE: Mr. and Mrs. John Smith (completely formal & Ms. Manners)
SALUTATION: Mr and Mrs. Smith (unless we know them - then we use nicknames/first names: "Katie and Bob" (her name first when it's informal)
We add a VERY helpful Salutation called "Informal" and it lists a couple by both known names: "Katie and Bob Jones." This Salutation has come in VERY handy.... when I pull lists for management it helps to have both names. We use this for addressing invitations. We use it on year-end giving statements for the IRS..... LOVE this one!1 -
Susan Maida-Church:
Hi Eleonore,
Are you looking at all records, or all active records?
I might suggest first breaking down the task by only looking at the active records. From there, I might suggest looking at some of my best donors (high givers, frequent givers, etc.) and determine how I want the addressee and salutation fields to look (ie spouse, no spouse) and address those inconsistencies that you reference in your post. I would then make a plan and set up the addressee/salutation table so the addressees/salutations that you want to now use are listed.
Once you have a documented plan on how you want the records to read, you can start to divide them in groups using query. For example, you could run a query for all records that contain a non-deceased spouse and make them a group. Make a second group of individuals with no spouse, etc. You can make as many queries as you want to divide your donors.
From there you can use these queries in Admin to globally replace the exitsting Addressee/Salutation with your new chosen formula. You could look at each query again after you apply your global changes and see if there are any individual records that need to be tailored.
After finishing your cleanup, I would suggest revisiting those best donor records and make sure their addressee/saluations are correct. I'm always extra cautious with those
It's not perfect - but I think it's "directionally correct". We did something similar here a few years ago and were met with success. I hope all of this makes sense - please let me know if it does not.
Thanks,
Susan
One other group that may or may not crop up in your query for spouses with different last names are same sex couples. I have run across same sex couples that use the same last name and those that use different last names, so make sure you keep them as a list. I also found, if you are in an institution with a large populous of clergy, you need to work with those as a separate query and handle the salutations a little differently.1 -
Thanks for your thoughts/suggestions everyone. I'm encouraged to hear that I might not have as much to dread as I feared.0
Categories
- All Categories
- Shannon parent
- shannon 2
- shannon 1
- 21 Advocacy DC Users Group
- 14 BBCRM PAG Discussions
- 89 High Education Program Advisory Group (HE PAG)
- 28 Luminate CRM DC Users Group
- 8 DC Luminate CRM Users Group
- Luminate PAG
- 5.9K Blackbaud Altru®
- 58 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 409 bbcon®
- 2.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- donorCentrics®
- 1.1K Blackbaud eTapestry®
- 2.8K Blackbaud Financial Edge NXT®
- 1.1K Blackbaud Grantmaking™
- 527 Education Management Solutions for Higher Education
- 1 JustGiving® from Blackbaud®
- 4.6K Education Management Solutions for K-12 Schools
- Blackbaud Luminate Online & Blackbaud TeamRaiser
- 16.4K Blackbaud Raiser's Edge NXT®
- 4.1K SKY Developer
- 547 ResearchPoint™
- 151 Blackbaud Tuition Management™
- 1 YourCause® from Blackbaud®
- 61 everydayhero
- 3 Campaign Ideas
- 58 General Discussion
- 115 Blackbaud ID
- 87 K-12 Blackbaud ID
- 6 Admin Console
- 949 Organizational Best Practices
- 353 The Tap (Just for Fun)
- 235 Blackbaud Community Feedback Forum
- 55 Admissions Event Management EAP
- 18 MobilePay Terminal + BBID Canada EAP
- 36 EAP for New Email Campaigns Experience in Blackbaud Luminate Online®
- 109 EAP for 360 Student Profile in Blackbaud Student Information System
- 41 EAP for Assessment Builder in Blackbaud Learning Management System™
- 9 Technical Preview for SKY API for Blackbaud CRM™ and Blackbaud Altru®
- 55 Community Advisory Group
- 46 Blackbaud Community Ideas
- 26 Blackbaud Community Challenges
- 7 Security Testing Forum
- 1.1K ARCHIVED FORUMS | Inactive and/or Completed EAPs
- 3 Blackbaud Staff Discussions
- 7.7K ARCHIVED FORUM CATEGORY [ID 304]
- 1 Blackbaud Partners Discussions
- 1 Blackbaud Giving Search™
- 35 EAP Student Assignment Details and Assignment Center
- 39 EAP Core - Roles and Tasks
- 59 Blackbaud Community All-Stars Discussions
- 20 Blackbaud Raiser's Edge NXT® Online Giving EAP
- Diocesan Blackbaud Raiser’s Edge NXT® User’s Group
- 2 Blackbaud Consultant’s Community
- 43 End of Term Grade Entry EAP
- 92 EAP for Query in Blackbaud Raiser's Edge NXT®
- 38 Standard Reports for Blackbaud Raiser's Edge NXT® EAP
- 12 Payments Assistant for Blackbaud Financial Edge NXT® EAP
- 6 Ask an All Star (Austen Brown)
- 8 Ask an All-Star Alex Wong (Blackbaud Raiser's Edge NXT®)
- 1 Ask an All-Star Alex Wong (Blackbaud Financial Edge NXT®)
- 6 Ask an All-Star (Christine Robertson)
- 21 Ask an Expert (Anthony Gallo)
- Blackbaud Francophone Group
- 22 Ask an Expert (David Springer)
- 4 Raiser's Edge NXT PowerUp Challenge #1 (Query)
- 6 Ask an All-Star Sunshine Reinken Watson and Carlene Johnson
- 4 Raiser's Edge NXT PowerUp Challenge: Events
- 14 Ask an All-Star (Elizabeth Johnson)
- 7 Ask an Expert (Stephen Churchill)
- 2025 ARCHIVED FORUM POSTS
- 322 ARCHIVED | Financial Edge® Tips and Tricks
- 164 ARCHIVED | Raiser's Edge® Blog
- 300 ARCHIVED | Raiser's Edge® Blog
- 441 ARCHIVED | Blackbaud Altru® Tips and Tricks
- 66 ARCHIVED | Blackbaud NetCommunity™ Blog
- 211 ARCHIVED | Blackbaud Target Analytics® Tips and Tricks
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- Luminate CRM DC Users Group
- 225 ARCHIVED | Blackbaud eTapestry® Tips and Tricks
- 1 Blackbaud eTapestry® Know How Blog
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
- 1 Blackbaud K-12 Education Solutions™ Blog
- 280 ARCHIVED | Mixed Community Announcements
- 3 ARCHIVED | Blackbaud Corporations™ & Blackbaud Foundations™ Hosting Status
- 1 npEngage
- 24 ARCHIVED | K-12 Announcements
- 15 ARCHIVED | FIMS Host*Net Hosting Status
- 23 ARCHIVED | Blackbaud Outcomes & Online Applications (IGAM) Hosting Status
- 22 ARCHIVED | Blackbaud DonorCentral Hosting Status
- 14 ARCHIVED | Blackbaud Grantmaking™ UK Hosting Status
- 117 ARCHIVED | Blackbaud CRM™ and Blackbaud Internet Solutions™ Announcements
- 50 Blackbaud NetCommunity™ Blog
- 169 ARCHIVED | Blackbaud Grantmaking™ Tips and Tricks
- Advocacy DC Users Group
- 718 Community News
- Blackbaud Altru® Hosting Status
- 104 ARCHIVED | Member Spotlight
- 145 ARCHIVED | Hosting Blog
- 149 JustGiving® from Blackbaud® Blog
- 97 ARCHIVED | bbcon® Blogs
- 19 ARCHIVED | Blackbaud Luminate CRM™ Announcements
- 161 Luminate Advocacy News
- 187 Organizational Best Practices Blog
- 67 everydayhero Blog
- 52 Blackbaud SKY® Reporting Announcements
- 17 ARCHIVED | Blackbaud SKY® Reporting for K-12 Announcements
- 3 Luminate Online Product Advisory Group (LO PAG)
- 81 ARCHIVED | JustGiving® from Blackbaud® Tips and Tricks
- 1 ARCHIVED | K-12 Conference Blog
- Blackbaud Church Management™ Announcements
- ARCHIVED | Blackbaud Award Management™ and Blackbaud Stewardship Management™ Announcements
- 1 Blackbaud Peer-to-Peer Fundraising™, Powered by JustGiving® Blogs
- 39 Tips, Tricks, and Timesavers!
- 56 Blackbaud Church Management™ Resources
- 154 Blackbaud Church Management™ Announcements
- 1 ARCHIVED | Blackbaud Church Management™ Tips and Tricks
- 11 ARCHIVED | Blackbaud Higher Education Solutions™ Announcements
- 7 ARCHIVED | Blackbaud Guided Fundraising™ Blog
- 2 Blackbaud Fundraiser Performance Management™ Blog
- 9 Foundations Events and Content
- 14 ARCHIVED | Blog Posts
- 2 ARCHIVED | Blackbaud FIMS™ Announcement and Tips
- 59 Blackbaud Partner Announcements
- 10 ARCHIVED | Blackbaud Impact Edge™ EAP Blogs
- 1 Community Help Blogs
- Diocesan Blackbaud Raiser’s Edge NXT® Users' Group
- Blackbaud Consultant’s Community
- Blackbaud Francophone Group
- 1 BLOG ARCHIVE CATEGORY
- Blackbaud Community™ Discussions
- 8.3K Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
- 5.7K Jobs Board