Start a new topic

MergeOmatic Keeping Oldest Record

We use so many Omatic Apps now I think we have to call it Omatic RE7.  I installed MergOmatic today and sent the documentation to my staff.  I got this following comment:

Interesting.  I scanned through the pdf and it seems that you can run the program for free to identify duplicate records but you pre-pay for a set number of merges that you can use in the future (very interesting business model).  I also noticed that the app doesn’t allow you to choose which record to keep – it does a “survivor” score and automatically will keep the record with the most data.  I think that Omatic should revise that feature – you and I have discussed how it’s helpful for analysis to keep the oldest record – and that may not always be the record with the most data.”

We have other records in our db that have been merged and the newer record was kept.  When I do an analysis of donor giving analysis based on date the record was added to the RE DB it is not accurate.  I can see that there is giving with dates before the date added for the record.  We need an automated way to fix this issue.

Screen Shot Start Panel of Omatic RE7:



Hi Jeff,

This is a great question, and actually one of the significant strengths of MergeOmatic. It seemed each client we spoke with had different ways of determining which record would "survive" the merge, so we built a very configurable "Survivor Score" engine to let each organization create a very robust formula to determine which record is the survivor by default (this can be easily changed during the review). This engine lets an organization assign points to many different criteria, including extremely custom criteria using queries to assign points to nearly anything you like. 


For instance, let's say your survivor choice is defined as "the older record, unless one of the records has a newer event registration, but being a Major Donor Prospect trumps either of those". With MergeOmatic's survivor score, this is no problem. You would simply assign 100 points (or however many you like) to the "Constituent Added First" criteria. This means that, when comparing two records to calculate a survivor score, MergeOmatic will give the older record 100 points. Let's say you also put 120 points on "Event Registration added last". If neither record had an event registration none would get points, but if the newer constituent had a recent event registration it would be awarded 120 points. Finally, if either record was in the "Major Donor Prospects" query, we assign it 500 points (the "trump card"). In your case, if it's really always just the older record, simply put a 1 in the "Constituent Added First" criteria and you'll be all set. What do you think, did we hit the mark?



Yes that sounds like it will solve the issue for records we have not merged yet. We just need a standard solution for the records that have already been merged and the newer record was kept. DateCreatedOmatic? It will search records and see if there are gifts or other data elements earlier than the date added. It will then change the data added to the earliest date possible.

Sounds like that would be a data service, but Omatic could certainly help you with that!
Login or Signup to post a comment