08. Mapping PPI Data (v3.1 and above)

Introduction

Starting in TaroWorks 3.1.1, new Progress out of Poverty Index(PPI) templates have made been available to include some demographic questions so you can analyze your PPI data with these responses as well as tie them to the respondent's records in your system.

The PPI Result object stores the results of a PPI survey. This is a snapshot in time so the demographic data may not reflect the current state, but rather reflects the state at the time the survey was conducted. Lookups to custom objects can be added to allow for reporting against the custom data gathered alongside the PPI. Individual fields can also be added to allow for the same.

The following topics will be covered in this article:

• A. Demographic Questions - A review of the questions that where added to the PPI Templates.
• B. Scenario: New Client - Walks through the scenario where you are registering a new client in the same Job that you are collecting their PPI Data, by entering their client id.
• C. Scenario: Existing Client - Walks through the scenario where you are collecting PPI for an existing client for which you already have their demographic information, and are passing this information into the survey using the hierarchy drill-down.
• D. Scenario: Anonymous Client - Walks through the scenario where you are collecting anonymous PPI data, and do not want to tie it to any possible client records in the system.

Before you Begin:

• You can edit the wording of Client ID and Demographic Questions to suit your use case.
• You can change the order of the questions in the survey if needed.
• You CANNOT delete any questions from the PPI templates. Your mobile users will not be able to sync. If you accidentally do this, you must recreate the survey from the PPI template.
• You can choose to hide any of these questions, by using skip logic with a condition that is always true.
• In a future release, you will be able to generate an ID for a new client at the same time you are collecting their data form the PPI template. Currently, this is not supported.

 

A. Demographic Questions

 

Original Question Number	Original Question Wording (English)	Description	Question Type	Field in PPI Result Object
Q1	What is the ID of the beneficiary being surveyed?	ID of the respondent There is no automatic generation of Client ID so the instructions can be edited  the question should be skipped if you want the PPIs to be anonymous, otherwise you should enter a Client ID of some form (or pass it in) in order to ensure that PPIs are attributed to the right person You can only edit the wording, not the type of question, so if you use barcodes to identify your clients, this question cannot be used at this time.	Free Text	Client ID
Q2	What is the gender of the beneficiary being surveyed?	Gender of the respondent  Options are Male and Female	Single Select	Gender
Q3	What is the age of the beneficiary being surveyed?	Age of the respondent in years Maximum 999	Number	Age
Q4	How many people live in the beneficiary's household?	Household size of the respondent Maximum 99	Number	Household Size
Q5	What date did the beneficiary start receiving products, services, or benefit from the organization?	Onboarding date of the respondent	Date	Joined Date
Q6	Capture the GPS location of this beneficiary's household	Household location of respondent	Geolocation	Geolocation

B. Scenario: New Client

• Field Mapping: 
• Map Client ID field in survey to ID field in object where customer information will be stored  
• Map some or all of demographic/PPI responses to object/fields in object (Optional)

 

• Job Creation:
• No hiearchy drill-down/passing of stored information necessary
• Result:
• Responses to demographic and PPI questions are stored in PPI Results Object
• Client ID stored in PPI Results Object
• Any PPI reports generated correctly include these PPI results
• If Field Mapping was applied to Demographic/PPI questions, then that data is correctly stored in designated object
• Responses to user added questions are stored in designated object

C. Scenario: Existing Client

• Field Mapping: 
• To pass in the demographic information of an existing client, no field mapping is necessary
• Map some or all of PPI responses to object/fields in object (Optional)

• Job Creation:
• Add object containing client information to hierarchy drill-down
• In the collect data task, map ID of object containing client information to Client ID question
• In the collect data task, maps in all of the stored demographic information to the corresponding PPI Demographic questions

• Result:
• Responses to PPI questions are stored in PPI Results Object
• Demographic information that was passed through from existing client object are stored in PPI Results Object
• Client ID is stored in PPI Results Object
• Any PPI reports generated correctly include these PPI results
• If field mapping was applied to PPI questions, then that data is correctly stored in designated object in customer org

D. Scenario: Anonymous Client

• Field Mapping: 
• None Required

• Job Creation:
• No hierarchy drill-down required
• No mapping of field on the task required

• Result:
• Responses to demographic and PPI questions as entered by enumerator are stored in PPI Results Object
• Any PPI reports generated correctly include these PPI results
• Results are not stored anywhere outside of PPI Results Object

Conclusion

In summary, you can map data into the demographic questions of PPI surveys for existing clients so that the PPI data can be analyzed by demographic characteristics witht the field officer only having to select the record on the hierarchy drill-down. You can also map any of the information collected in any custom object. All of the data collected in the template questions will be stored on the PPI Result object.