Blender: Smoothing and streamlining incoming dataflows, saving time and money down the line. Most charities…
NAPSAC: a new level of control to duplicate management and data integration
In an ideal world of perfect supporter stewardship, you would have – at your fingertips – information on every interaction you have ever had with every single one of your donors. But in the real world, with multiple simultaneous data streams, silos and channels, surely this is a pipe dream?
Now NAPSAC changes things.
Treating the same person as several different donors simply because he or she has had separate interactions with your organisation makes you look inefficient (at best), so duplicate records need to be controlled. But a ‘one size fits all’ duplicate-catcher can cause as much damage as having none at all – the system needs to be visible, adjustable and clever.
NAPSAC brings a new level of control to duplicate management and data integration, and is specifically designed to be effective in environments where multiple streams of supporter data are being processed and analysed more or less continuously.
In essence, NAPSAC works by identifying duplicate supporters and then deciding whether they can be merged on a case-by-case basis using rules supplied by the charity. It’s not intended to replace good business practice, which must always be an essential prerequisite in preventing duplicates being introduced in the first place, but of course in the real world this is very hard to achieve.
NAPSAC takes feeds from the host database and operates as a separate service, returning metrics and merge tables to the host system for further processing. This relieves stress on the often fragile systems that are relatively commonplace in the charity sector.