I was given a request to implement a way to store DOB for name1 and name2 of a constituent record. They also want marital status for the constituent record.
Is this normally built-in to Tessitura? Our install here doesn't seem to have it.
I find it strange that a family association has a birthdate.
Also, is it possible just to store month and day? Some people may not give us a year.
We have keyword in called Birthdate_1 and Birthdate_2 that sets this as an attribute for both our N1 and N2 Constituents.
You could cover all your bases this way - Make entries in your t_keyword system table like - N1_BirthMonth (as a string), N1_Birthday(as a number), and the same for the N2 constituent (second) name.
The same could be done for Marital Status. Set up a keyword called Marital Status and assign values in t_kwcoded values associated with that keyword like - Married, Single, Divorced, etc. Again, if you wanted to associate that with both Name 1 and Name 2 you could create a keyword for each i.e. N1_Marital_Status, etc.
There may be more elegant ways to handle it, but it works for us.
Dave K.
Would this just show up in the attributes tab then?
Yes it would. These would be available for building list criteria and possibly used in custom reports.
If it is important that you see it somewhere a little more obvious than the attribute tab when navigating the constituent record, you could customize the donor header and display the values there.
Of course that probably means sacrificing precious real estate on the header. This is nice if you have a very specific group of users who need to see that information.
Build a custom header that would be assigned only to that group of users. The more specialized your group the more it increases the likelihood of finding some fields on the standard header that this specific group might be willing to give up for the attributes they want to see.
I hope that helps.
Cheers,
Dave Knerler
To clarify, you would use the new attribute records you have created for DOB and Marital Status to call the values into the custom header for the constituent.
-dk
I now have an idea of what we are going to do. Thank you very much for you help.