etapestry Data Enrichment Additional Import Options

Size: px

Start display at page:

Download "etapestry Data Enrichment Additional Import Options"

Adrian Riley
7 years ago
Views:

etapestry Data Enrichment Additional Import Options etapestry now has the following Additional Import Options: Residential Phone Append Business Phone Append Canadian Phone Append County Append

to our Phone Append processing company. When then the data is returned to us, etapestry imports the data back in into the Voice phone field on the primary persona page.

1 etapestry Data Enrichment Additional Import Options etapestry now has the following Additional Import Options: Residential Phone Append Business Phone Append Canadian Phone Append County Append Deceased Append Birthdates Append Congressional District Append Marital Status Append Append Phone Appends The Phone Append process allows etapestry to export out a customer s data and send off to our Phone Append processing company. When then the data is returned to us, etapestry imports the data back in into the Voice phone field on the primary persona page. If it was a Business phone append, the data is imported into the Business phone field on the persona page in both the Business persona and the primary persona. Persona Page o The UDF created is called etap Phone Codes 12/07/2010 with the values of Added phone number and then the values go into the Voice field or the Business phone field

For Phone Append, we create a Added phone number query that allows the user to see which accounts we added the phone number to County Appends The County Append process allows etapestry to export out

2 For Phone Append, we create a Added phone number query that allows the user to see which accounts we added the phone number to County Appends The County Append process allows etapestry to export out a customer s data and send off to our County Append processing company. When then the data is returned to us, etapestry imports the data back in into the County system field on the primary persona page. Persona Page o The UDF created is called etap County, and the value is marked County Added. The county value goes into the County field on the persona W. Airport Blvd. Suite 120 Greenfield, IN E solutions@blackbaud.com W

When then the data is returned to us, etapestry imports the data back in into the County system field on the primary persona page.

3 For the County Append, we create a County Populated on Account query that pulls any account that has the County field populated. We also create a County Added query that pulls only on the accounts we added the county to. This enables the users to pull on any accounts with a county, and just the ones we added to Deceased Appends The Deceased Append process allows etapestry to export out a customer s data and send off to our Deceased Append processing company. When then the data is returned to us, etapestry imports the data back in into user defined fields we created on the Constituent User Defined Fields page. o For the Deceased Append, we create a UDF called etap Deceased Codes with the values of Deceased with Deceased Date, Deceased Without Deceased Date, Household Match Deceased, Individual Match Deceased, and Possible Deceased Journal Note Added. This allows the user to know through querying if there is a deceased date that came back for this account, and if it was a Household match (matched on last name and address only) or if it was an individual match (matched on first and last and full address) If there was extra information, we place it in a journal note and mark that value on the field. We also have a UDF called Deceased Date if a date is returned W. Airport Blvd. Suite 120 Greenfield, IN E solutions@blackbaud.com W

This enables the users to pull on any accounts with a county, and just the ones we added to Deceased Appends The Deceased Append process allows etapestry to export out a customer s data and send off

For the Deceased Append, we create a Deceased with Deceased Date query that pulls an account we marked with a deceased value that also contains a deceased date.

4 For the Deceased Append, we create a Deceased with Deceased Date query that pulls an account we marked with a deceased value that also contains a deceased date. We create a Deceased without Deceased Date that pulls those without a deceased date. We create a query called Individual Match Deceased and Household Match Deceased that pulls the accounts that have a match for first, last and full address on the individual match deceased, and pulls the accounts on the last name only with full address match on the household match deceased. Birthdates Appends The Birthdates Append process allows etapestry to export out a customer s data and send off to our Birthdate Append processing company. When then the data is returned to us, etapestry imports the data back in into 3 User Defined Fields on the Constituent s User Defined Field page. This allows any part of the birthdate that is returned to be queried by the user. o For the Birthdate Appends, we have a UDF called etap Birthdates that have the values of Individual Match, Household Match, and Possible Birthdate Journal Note Added. This allows the user to see which accounts matched on full name and full address (individual match), just last name and address (household match) and anything else we get back we put in a journal note and mark that value on the field. The other fields we create are for the birthdate itself in 3 separate fields since the full date is not always returned. We create Birthdate Month, Birthdate Day, and Birthdate Year. These are number UDFs for querying purposes W. Airport Blvd. Suite 120 Greenfield, IN E solutions@blackbaud.com W

We create a query called Individual Match Deceased and Household Match Deceased that pulls the accounts that have a match for first, last and full address on the individual match deceased, and pulls

For the Birthdates Append, we create Individual Match and Household Match queries that pull up the birthdates where we matched on first, last and full address for the individual, and then on just

5 For the Birthdates Append, we create Individual Match and Household Match queries that pull up the birthdates where we matched on first, last and full address for the individual, and then on just last name and full address for the household match query. We also create Possible Birthdate Journal Note Added which pulls accounts that we added a journal note that contains possible birth date information. Congressional District Appends The Congressional District Append process allows etapestry to export out a customer s data and send off to our Congressional District Append processing company. When then the data is returned to us, etapestry imports the data back in into a Number User Defined Field on the Constituent Defined Fields page. o For the Congressional District Append, we create a Number UDF called etap Congressional District W. Airport Blvd. Suite 120 Greenfield, IN E solutions@blackbaud.com W

We also create Possible Birthdate Journal Note Added which pulls accounts that we added a journal note that contains possible birth date information.

For the Congressional District Append, we create the Congressional Districts query which pulls any account that has the etap Congressional District user defined field populated.

6 For the Congressional District Append, we create the Congressional Districts query which pulls any account that has the etap Congressional District user defined field populated. Marital Status Appends The Marital Status Append process allows etapestry to export out a customer s data and send off to our Append processing company. When then the data is returned to us, etapestry imports the data back in into a check box Constituent User Defined Field on the Defined Fields page. o For the Martial Status Append, we create a UDF called etap Marital Status with values of Married and Single. Queries Created: For the Marital Status Append, we create a Single query, which pulls any account that is marked as Single (a user defined value we assign during the process). We also create the Married query which pulls any account that is marked Married (a user defined value we assign during the marital status append process) W. Airport Blvd. Suite 120 Greenfield, IN E solutions@blackbaud.com W

When then the data is returned to us, etapestry imports the data back in into a check box Constituent User Defined Field on the Defined Fields page.

Email Appends With the Email Append process, we send the user a Template Permission Letter to edit according to their organization.

This is required in order to move forward with the Email Append. When we get the data back, there are 2 options we give the user.

7 Appends With the Append process, we send the user a Template Permission Letter to edit according to their organization. This letter will be sent out on the behalf of the organization to give the constituents the opportunity to opt out of any future correspondence. This is required in order to move forward with the Append. When we get the data back, there are 2 options we give the user. If there is currently a different address already in the address field on a persona, we can either append to that address with a comma (ex: current@ .com,new@ .com) or we can replace the current and put the current address in the persona note. This choice is up to the user. We update the field if an is returned with the process along with the following: : o We create a user defined field called Codes 12/06/2010 or whatever date we ran the update on. The values created are called Matched and Opted Out. If an was returned and did not opt out, we mark the Matched value. If they opted out, we still provide the new address, but mark the Opted Out value so the user is aware. Queries Created: We create Queries for the Append under the category of Codes 12/06/2010 or whatever date we run the process on. We create the Matched query that pulls all the accounts we found an address that did not opt out. We also create the Opted Out query that pulls all the s we imported that did opt out W. Airport Blvd. Suite 120 Greenfield, IN E solutions@blackbaud.com W

Utah. Medicare Cuts to Skilled Nursing Facility Care

Utah. Medicare Cuts to Skilled Nursing Facility Care The impact for the state of is as follows: National $44.0 billion $217.6 million $17,258,789 $8,148,238 290 Congressional District 1 The impact for Congressional District 1 is as follows: National Congressional