That new database smell... What would you do with a brand-new blank RE database?

Options
Hi... I've been given a rather unique opportunity with a small non-profit organization that is starting from scratch.  They've been running off the simple Google sheets and various docs for the past few years and essentially doing the bare minimum amount of record keeping.


That's all changed recently they've purchased a BRAND NEW Raiser's Edge/NXT database.... And since there is really no conversion needed I've been tasked to help them essentially build a new database from the ground up.  It's exciting and cool and it's REALLY weird to see a Raiser's Edge database with no attributes, no solicit codes, no constituency codes and exactly ZERO constituent or gift records.  


We'll of course have to enter some of the historical data, but even that is open to interpretation and discussion...  So I'm going to toss this out to all you database administrators out there who wish you could start over:


If you were given the chance to start a brand new database from scratch, what ONE thing would you do differently to make your life so much easier?


 

Comments

  • As mentioned take in what stakeholders say, take it into account, but keep in mind you are building this for all -- and for others to read/interpret/understand and move forward and grow over time after we all have fallen off the planet -- so when setting this up always ask yourself if the codes/tables/codes in the tables, abbreviations (ick!) will make sense to anyone else beyond who might be seeing/using them today.  


    After inheriting some really, really messy undocumented codes and abbreviations... make sure you write stuff out instead of abbreviate where you can as much as possible and document/keep a log/journal of the acronyms and abbreviations and what the heck they are for (what program/project, when it was etc.)
  • I agree with all these suggestions and will reiterate the importance of documenting definitions for code tables, const codes, attributes, etc.  Additionally, creating procedures for processes and tasks is essential.  I recently started a new position and there is not a lot of documentation.  That's made the learning curve steeper since I've had to either find the right person to ask (which isn't always the logical person to ask) and or figure things out on my own.  


    The two things I would add here are:
    1. Training 
      • Be sure to train the users well.  Be thorough and thoughtful in your lessons and find a way to make them fun.
      • Don't only teach them the hows, but also explain the whys.  I find that people are typically more willing to do things the right way if you explain why it's important things are done a specific way and the consequences of not following the process.
      • After the training, be sure and check daily/regularly to ensure that people are following procedures/processes and provide retraining or additional instruction as required.  This will help you catch any issues right away and prevent people from getting into bad habits.  Plus, nothing is worse than having to go back and fix several months' worth of bad data because you didn't check and make sure people were doing things right from the get-go. 
      • If someone is making the same mistake over and over, have them help you fix their mistakes.  This is one of the best ways to help people learn how to do things correctly, and if they understand the work involved in correcting issues, they'll be more conscientious of doing things correctly the first time.
    2. Quality Checks
      • Set up queries for the most likely/common errors that you encounter during training and run those queries often to identify records that need to be corrected.  As mentioned before, have the person who made the mistake help you fix the problem.
      • Every time you find a problem in a record, set up a query to find any other records with this same issue.  My experience has been that 99.9% of the time, the old adage, "where there's smoke, there's a fire," typically rings true - if you find one record with a problem, there are almost always other records with the same problem.
      • Run these QC queries regularly - daily/weekly/monthly depending on your processes - and document the reason for each one and how to fix the issues each query identifies.  For ease of corrections, it's typically best for each query to only identify a single issue in a record. 
    Have fun dreaming!


    Laura
  • I'm a big fan of housing all of my quality control queries, exports and reports in one place using the queue feature (even though I don't schedule the queue), add the queue to my favorites/home page and  I run it each Tuesday (even block time on my calendar to do it!).


     
  • Wonder if the full list of database view fields dropped from NXT suggested above by Catherine Burns‍ has been made available? Would be so useful.


    We are just embarking on our journey with NXT...wish us luck! And thnkyou all for this insightful thread, it has been most useful.
  • JoAnn Strommen
    JoAnn Strommen Community All-Star
    Ancient Membership 2,500 Likes 2500 Comments Photogenic
    I actually was looking for that info last week.  Could not find anything.


    Thought about creating a post/thread where users could create the list since BB hasn't. :)  Think I will - you've motivated me to do so.
  • Well, I'm A LOT jealous...That being said, only let ONE person create table entries.  I agree with other comments, use tables as much as possible for fields so they stay consistent.  I'm still cleaning up messes created when several of my supervisors said 'anyone can enter data, it'll get done quicker that way'...ugh!  I'm happy to say that is no longer the case, but I don't think anyone (besides me) realized how long it would take to clean up messes made by people who are now long-gone and had no idea of what they were doing.


    Limit constituent codes as much as possible

    Limit the areas where your Development Officers can add....notes, actions, etc.

    Detailed data entry should be just one person.  


    Wow!  What an opportunity!  Good luck!
  • Lucky you, Tom Klimchak‍! Great suggestions to everyone who commented. Now that you're a year into it, Tom, let us all know how it's going!
  • Hi.. I wanted to thank everyone for all the great advice on this post and I wanted give a little update on how things have gone...

    It's been a year since we set up an RE NXT database from scratch. Setting up the database was incredibly easy. We sent in the signed paperwork, had a few quick meetings and within two weeks we were given the login to a new, totally empty database. The hardest part of the whole process was convincing various people at Blackbaud that no, we didn't need any sort of "data conversion" work because the organization had only been formed a year before and only really had a few spreadsheets filled with contact info.

    The very first thing we did was set up some basic security classes and send invites to the Advancement Services staff and a few key IT people. While our IT department worked on setting up the posting process the Advancement Service staff worked on setting up basic code tables. We also spent a few hours in a meeting with the stakeholders where we talked out some scenarios and thought up some constituency codes and report ideas. Interestingly, the policies, constituency codes and some of the reporting ideas were different than those we used for our University. Each organization is going to customize Raiser's Edge to their unique need, and RE NXT makes that fairly easy.

    Next we set up two Campaign codes, then we entered the two Funds and a couple appeal codes. After those were in place we created about 10 constituency codes which we had discussed in those initial setup meetings. With those basic things in place my experienced staff started compiling the constituent and gift info we needed to transfer into the new database.

    That first day of real data entry went slowly because we hadn't even considered some of those little code tables we all take for granted. We added in new titles, a few new phone types, another constituency code (all the planning in the world doesn't always prepare you for reality), a bunch of relationship codes and even a couple basic attributes.

    We manually entered about 30 board members and existing donor constituent records. Next we moved on to entering our existing gift records (less than two dozen) and we finished out the day by building a few reports where we could total our gifts and compare to our existing records, just to make sure we didn't miss anything.

    Over the next six months we ran some imports of constituent records from Excel spreadsheets and we spent about three hours training the BSACAM staff on how to do basic constituent data entry. They picked it up rather quickly and they all found RE NXT to be very approachable.

    A year later we now have a little over 2,000 constituents, a few more gifts and a few more reports. We have all our basic code tables in place, we have about twelve different constituency codes and only three custom fields/attributes (so far!). The BSACAM staff can build their own lists in RE NXT and they feel pretty confident in basic data entry.

    We keep the stakeholders involved with monthly meetings where we just touch base, have a short training session on a particular topic and usually work through some questions and make policy decisions.

    We have some basic documentation, mostly from our meetings, but we haven't written out any expansive instructions because we're still not sure how all the staff positions and roles will play out once we get back into the office in person.

    Overall, it's been exciting first year of using our new RE NXT database. As jaded professionals we may not be impressed by simple database functions, but some of the staff were simply amazed by basic reports and lists that were not possible in their old Excel spreadsheets. They love that RE NXT is web based and they can even look up things on their phones. The staff members of our new organization have had an incredibly positive experience and they're excited about seeing their data presented in such an accessible and professional way.

  • JoAnn Strommen
    JoAnn Strommen Community All-Star
    Ancient Membership 2,500 Likes 2500 Comments Photogenic
    Impressive! Thanks for the update, Tom Klimchak
  • Congratulations Tom Klimchak‍, thanks for sharing. Probably the only org on the planet not complaining about the ideas of others.

Categories