Hello,
We have recently started working with TRG and are hoping to be able to use the results from their NCOA scrub to pull address updates back into our Tessitura database. Is anyone out there doing this and willing to share an import file format or any best practices for pulling in TRG specific returns?
Thanks,
SADIE PRATER
Systems Analyst
Perot Museum of Nature and Science
P 707.986.8377 | sadie.prater@perotmuseum.org
Hi Sadie,
Are you using the built-in Tessitura NCOA Import Utility, or have you rolled your own?
We're now using the utility for export, but still use our own tool for import, as we have a requirement that certain customers only be updated after user review. My process actually involves getting the file back from our processor (I honestly don't even know what their name is right now, it's changed about 10 times) and then running it through a python script to remove the unnecessary rows and columns, and then I have a BCP format file, but it's just for the limited column output that my python script creates.
--Gawain
Gawain Lavers, Chris Jensen, and anyone else -- would you be willing to share the code you use to save inactive copies of the old address? Please feel free to email me directly ssur@publictheater.org. Thank you in advance!
Sheela,
I just sent you our process. I went through this a few years ago and I feel like I have it down pretty solidly at this point in time. Feel free to respond if you have any questions about our process.
John
Hi Sheela,
I'm in the middle of rebuilding our system, but the broad outline is this:
1) I have a local table of constituencies that are to be skipped by the update.
2) Customers where the address has been altered since the addresses were pulled are skipped as well.
3) Customers that have been part of a merge since the addresses were pulled are also skipped.
4) I created a Contact Point Purpose Category called "Contact Point History". It has three Contact Point Purposes: "Unknown or Bad Address", "NCOA Move" and "NCOA Delete" (the first for manual use). The process then inactivates the address in question and applies one of these purposes to it. If a new address is supplied, that is added (i.e. an NCOA Move). If it's a Delete I think it might make any other active addresses primary, and if none exist, add our "default" address (i.e. Street 1 = "None", ZIP = 00000).
I will say that Tessitura doesn't approve of this use of Contact Point Purposes, but I can see no reason to not use them for things like this.