IMP FS General: Data Integration Reports Overview

 

Data Integration Reports Overview

Both the Data Integration Stage Site review and Production Run reports are provided to help you understand how the diocesan and parish data was integrated.  We recommend that the Parish and Arch/Diocese work together on these reports to resolve the following scenarios: 

A missed match and merge from the integration process.

If you find a family on the list that truly is a duplicate of one of your existing records that family will need to be merged by the Diocese with your family record after your data integration production run. Please note the family DUID of the parish family record and the family DUID of the non-matched diocesan record and provide those to the Diocese so the records can be properly merged.

A family you recognize and would like as part of your parish data.

Following your data integration production run you may import the family through the Add Family function in ParishSOFT so they are associated with your parish. You may choose to add them as Registered or Not Registered, whichever is appropriate.

A family that you currently have no interest in.

You do not need to do anything with these records. 

Report Overview

Please be sure to review each tab in the Excel file(s) on the reports. Details on what information is provided in each report are included below.

Matching Detail Report

Weight Summary Tab

This report provides a summary of the field weights applied during the matching process between your records and the diocesan records. This information is used to determine whether or not families are considered a match and are merged together during the integration process.

Log Summary Tab

On this report, you can find a list of the counts at various stages of the process. Each of the fields on this report is described below:

  • Source Family Count: This is the number of families in the parish data prior to running the Data Integration Process.
  • Families Matched: This is the number of families in the parish data where a match was identified in the diocesan data.
  • Families Moved: This number corresponds to the number of families in the diocesan data NOT matched to the parish data. 
    • If your diocese is using a holding tank organization these families have been moved to the holding tank organization for manual review at the end of the process.  If they are deemed to be relevant to the parish, the parish can re-add them to their organization following integration.
    • If your diocese is not using a holding tank organization no families are moved.
  • Families Inserted: This is the number of families we did not find a match for so they have been inserted into the ParishSOFT diocesan database from the parish data. 
  • Retained: Same as “Families Matched”.
  • Moved: Same as “Families Moved”. It is the number of families moved to the holding tank organization for manual review following the integration process.  These families will not show in the parish data in ParishSOFT but will only appear in the diocesan holding tank organization following the integration process. 
  • Original AIM Count: This is the number of families in the diocesan database marked as sourced by the parish organization ID before the integration process began.

Matching Summary Tab

This report groups the common combinations of fields for “Matches On”, “Diverges On”, and “Null On”. The number of families in each of these combinations is summarized in the “Match Count” column. This provides insight at an aggregate level.

Matching Detail Tab

This lists every single family in the parish source data deemed as having a potential match in the diocesan data base. These potential matches are then assigned a Weight value. Our standard cutoff for this weight value is 70. Any record listed below the weight threshold of 70 would be considered a non-match. 

  • If your diocese is using a holding organization the non-matched diocesan record will be moved to the holding organization and the parish record will be added as a new family to ParishSOFT.
  • If your diocese is not using a holding organization the diocesan record will remain in the parish/organization view and the parish record added as a new family to ParishSOFT. If these records are later deemed a match the parish will work with the Arch/Diocese to have these records merged.

Unmatched Families

This report is only generated if unmatched families are moved to a holding organization.  The report contains a listing of all of the unmatched family records that were eligible for matching.  (Note: See No Potential Match Families below for explanation of family records not eligible for matching.)  The report includes the potential matches from the matching detail report that fell below the matching threshold of 70 (those in pink) along with all of the families who did not have a potential match between the diocesan and parish data.

No Potential Match Families

These are family records that are mapped to another parish within the diocesan database and are therefore ineligible for matching.

  • If your diocese is using a holding organization these types of records have been moved out of the parish/organization view.
  • If your diocese is not using a holding organization these records will be left in the parish/organization view.

Following your data integration production run any of these families that are deemed a matched may be merged by the diocese.

 

3767 Ranchero Drive, Suite 100 | Ann Arbor, MI 48108 | Toll Free 866.930.4774 | Fax 734.205.1011
www.parishsoft.com

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.