So a common issue that I have discovered working with Raiser’s Edge is that over time, people forget or don’t understand what the various table entries mean, and therefore start using them for reasons other than their intended purpose. Some of us do our best to document definitions in order to help with data accuracy, but often times knowledge of this external resource is limited to a few, and accessed by even fewer. So my suggestion to Blackbaud is (in my mind – and I’m likely naive) relatively simple. Add an additional column to all of the Tables which will record definitions of each table entry. A prime example would be the Constituent Code Table. Currently we have the ability to record a Short Code and a Long Description. So I challenge you, if a constituent record had the code of Government, how would you define it? Would your definition affect how you use this code? Would others in your agency define and use this code the same way as you? How different would this situation be, if Raiser’s Edge housed a Definition for each table entry. GOV – Government – An org record for a political office or agency. I’m not at this time proposing a massive overhaul of the front end of Raiser’ Edge. My initial thoughts are to include the definitions in the tables window that opens when you press F7 in an associated field. If Blackbaud wanted to take this one step further, they could include the definition in a mouse roll over when you have a drop down open. Additionally, I would suggest that this information be included on the Code Tables Report. What are your thoughts or comments? I would appreciate your feedback.

I total agree with your suggestion as wehn we have new staff on board and they are entering information in the tables this feature would help ensuring that the proper codes are being used as it will give them an idea of what it is all about. I would like to see Blackbaud have this information in the next upgrade roll out.

 No kidding that a great idea!  It seems pretty silly that all the field tables have a place for long description and short description and yet the only ones of the 100+ that actually allow both a short and long description and state, country and constituent code i think - dumb!

 It's little extra touches like these that would really make RE and customizable and accessible system for users

We definitely run into this problem.

What I've done with actions and with prospect statuses is include a definition within the table entry.

 

Action Type Table Examples:

           CONSULTATION: Prospect Leads, recommendations

           APPT SET UP: appointment logistics

           EVALUATION: learning giving interest, capacity

Prospect Status Table Examples:

Identification- a lead or prospective donor

Research- assess interest and giving levels

Cultivation- prepare for solicitation