Dataset Definitions

There are three types of dataset formats: Long, Wide, and Summary.  Here’s what each of the column headings mean in each type of dataset. 

 

LONG FORMAT 

Long format data reports are organized so that each row represents a single response to a prompt.  Columns in this format are used to report specific information about the response.  

Each column in the long format dataset is described below: 

  • Participant ID: The unique ID number assigned to every person who creates a mobile account in the LifeData system. 
  • Notification Time (NIS only): The date (month/day/year) and (hr:min) time when a notification was delivered. Data is reported using a 24-hour clock. 
  • Prompt Response Time: The date (month/day/year) and time (hr:min) when a response was given. Data is reported using a 24-hour clock. 
  • Session Name: The name given to the session to which the prompt belongs. 
  • Notification No (NIS only): Lists number of notifications in order from the beginning of an NIS until its end. (For example: the first notification for a session is 1, the second notification is 2, etc.) Notification numbers are assigned to each notification that is scheduled in the operating system of the mobile device, including notifications that the User did not respond to, or notifications that were not delivered because the User turned off notifications.  If you create multiple NIS’s, then each NIS will have its own set of notification numbers.  In other words, each unique NIS has its own set of notification numbers, beginning with 1 and continuing as long as notifications for that NIS fire. 
  • LifePak Download No: Each time a User downloads a LifePak, that download is assigned a number. Most Users download a specific LifePak once, so they usually have a download number of 1.  In some cases, a User may delete a LifePak and download the same one again.  In those cases, each subsequent download of that same LifePak is given a new download number.  For example, if a User downloads the same LifePak three times, on that third time any data that is sent to the server will be identified with a Download No of 3. 
  • Responded: Did the User respond?  1= yes, 0=no.  A “0” is assigned when a User 1) does not respond to a notification, or 2) selects “Skip” for a particular prompt.  
  • Completed Session: Did the User complete the session to which this prompt belongs? 1= yes, 0=no.  The User must respond to each prompt within a session (either by entering a valid response or selecting “Skip”) for the session to be considered complete. 
  • Session Instance No: Number assigned to each instance of a specific NIS or UIS. Each time a User responds to a notification for a certain NIS, or initiates a certain UIS, a unique number is assigned to that specific session. Session instance numbers are assigned in order, starting with 1 for the first session for that NIS or UIS.  If you create separate NIS’s (e.g., “Morning NIS” and “Evening NIS”), then each NIS will have its own set of Session Instance Numbers.  For example, the first time a User responds to the “Morning NIS” it will be assigned a Session Instance No of 1; and because the “Evening NIS” is separate, the first response to the Evening NIS will have its own set of session instance numbers, also starting with 1. 
  • Session Instance Response Lapse(NIS only): Amount of time (hr:min:sec) that elapsed between the time the notification for that session fired and the time that the User started the session. The session starts as soon as the first prompt is shown. Session instance response lapse is reported only for NISs. 
  • Session End Time(NIS only): The time at which the User completed the session. 
  • Session Length Represents the time elapsed between entrance and exit of a session. Note: The sum of the prompt response lapses for each session will yield a similar but not exact total session time because "session length" ends when the mobile User presses the "Finish" and not the "Ok" (submit) button. 
  • Reminders Delivered(NIS only): Records how many reminders were delivered before the User responded to the session instance. For example, if the reminders delivered is 2, that means that the User received an initial notification and two reminders. The User then responded, after the second reminder. 
  • Time between sessions(UIS only): Amount of time (hr:min:sec) that elapsed between the end of the previous UIS session and the beginning of the UIS session containing this prompt. For the first UIS instance, the time between sessions represents the time that elapsed between the end of the Startup Session and the first prompt of the first UIS session; or, for LifePaks without Startup Sessions, when the LifePak was downloaded. Note: Time between sessions is only reported for UISs. 
  • Prompt Response Lapse: Amount of time (hr:min:sec) that has elapsed from the time the User clicks “OK” or “Skip” for the previous prompt, and the time that they click “OK” or “Skip” for this prompt. For the first prompt in a session, prompt response lapse time is the time that elapsed between the prompt being shown to the User and the User responding to it.  
  • Order in Session: Order in which a prompt was delivered within a specific session instance.  For example, 1 indicates a prompt was delivered first. Note: Prompts are delivered in the order specified within the Blok in which a prompt is contained, except for Startup Sessions (which don’t have Bloks).  For Startup Sessions, Prompts are delivered in the order listed in the LifePak creator web application. 
  • Prompt ID: A unique identifier for each prompt within a LifePak. 
  • Prompt Type: Type of prompt (e.g., multiple choice, slider scale, picture, etc.) 
  • Prompt Label: The short name assigned to a prompt when it is created within the LifePak Creator web application. 
  • Prompt: Text of the question or prompt that was delivered to the User. 
  • Response: User response to a prompt. This is blank when a User does not respond, or for prompts that do not allow a response (e.g., a text statement or picture prompt). “#skipped#” is recorded when Users skip a prompt. 
  • GPS Latitude/Longitude: Global coordinates of the User at the moment of responding. 
  • Device ID: Provides information about the User’s mobile phone operating system (e.g., model of the phone, version of the RealLife app, etc.). 
  • Comments: Combines Session Name, Session Instance Number, and Participant ID. 

WIDE 

Wide format data reports are organized so that each row of data represents a session instance, and each unique prompt within a LifePak is represented in a column. Therefore, in cases where the Creator has designed multiple UIS or NIS within a LifePak, there will be many blank cells because any one session will contain some prompts but not others. 

Each column in the wide dataset is described below: 

  • Participant ID: The unique ID number assigned to every person who creates a mobile account in the LifeData system. 
  • Notification Time (NIS only): The date (month/day/year) and (hr:min) time when a notification was delivered. Data is reported using a 24-hour clock. 
  • Prompt Response Time: The date (month/day/year) and time (hr:min) when a response was given. Data is reported using a 24-hour clock. 
  • Session Name: The name given to the session to which the prompt belongs. 
  • Notification No (NIS only): Lists number of notifications in order from the beginning of an NIS until its end. (For example: the first notification for a session is 1, the second notification is 2, etc.) Notification numbers are assigned to each notification that is scheduled in the operating system of the mobile device, including notifications that the User did not respond to, or notifications that were not delivered because the User turned off notifications.  If you create multiple NIS’s, then each NIS will have its own set of notification numbers.  In other words, each unique NIS has its own set of notification numbers, beginning with 1 and continuing as long as notifications for that NIS fire. 
  • LifePak Download No: Each time a User downloads a LifePak, that download is assigned a number. Most Users download a specific LifePak once, so they usually have a download number of 1.  In some cases, a User may delete a LifePak and download the same one again.  In those cases, each subsequent download of that same LifePak is given a new download number.  For example, if a User downloads the same LifePak three times, on that third time any data that is sent to the server will be identified with a Download No of 3. 
  • Responded: Did the User respond?  1= yes, 0=no.  A “0” is assigned when a User 1) does not respond to a notification, or 2) selects “Skip” for a particular prompt.  
  • Completed Session: Did the User complete the session to which this prompt belongs? 1= yes, 0=no.  The User must respond to each prompt within a session (either by entering a valid response or selecting “Skip”) for the session to be considered complete. 
  • Session Instance No: Number assigned to each instance of a specific NIS or UIS. Each time a User responds to a notification for a certain NIS, or initiates a certain UIS, a unique number is assigned to that specific session. Session instance numbers are assigned in order, starting with 1 for the first session for that NIS or UIS.  If you create separate NIS’s (e.g., “Morning NIS” and “Evening NIS”), then each NIS will have its own set of Session Instance Numbers.  For example, the first time a User responds to the “Morning NIS” it will be assigned a Session Instance No of 1; and because the “Evening NIS” is separate, the first response to the Evening NIS will have its own set of session instance numbers, also starting with 1. 
  • Session Instance Response Lapse(NIS only): Amount of time (hr:min:sec) that elapsed between the time the notification for that session fired and the time that the User started the session. The session starts as soon as the first prompt is shown. Session instance response lapse is reported only for NISs. 
  • Session Length Represents the time elapsed between entrance and exit of a session. Note: The sum of the prompt response lapses for each session will yield a similar but not exact total session time because "session length" ends when the mobile User presses the "Finish" and not the "Ok" (submit) button. 
  • Reminders Delivered(NIS only): Records how many reminders were delivered before the User responded to the session instance. For example, if the reminders delivered is 2, that means that the User received an initial notification and two reminders. The User then responded, after the second reminder. 
  • Time between sessions(UIS only): Amount of time (hr:min:sec) that elapsed between the end of the previous UIS session and the beginning of the UIS session containing this prompt. For the first UIS instance, the time between sessions represents the time that elapsed between the end of the Startup Session and the first prompt of the first UIS session; or, for LifePaks without Startup Sessions, when the LifePak was downloaded. Note: Time between sessions is only reported for UISs. 
  • [Prompt Label]: In the Wide Format, a column is devoted to each prompt created in each NIS (or UIS) within that LifePak. The label for each of these columns is the “Prompt Label” that was assigned when the Prompt was created in the web app.  Responses to each prompt are recorded in this column.  A blank cell indicates either 1) the prompt wasn’t contained in the session represented by this row, 2) a User didn’t respond, or 3) the prompt type doesn’t allow a response (i.e., a text statement or picture prompt). “#skipped#” is recorded when Users click the skip button.  Note: In a LifePak with different NISs (or UISs), on any given row, many of these columns will be blank.  Values are provided only for answers to prompts delivered in the session instance represented in a given row. 
  • GPS Latitude Start: Latitude coordinates gathered when the User responded to the first prompt in the session. 
  • GPS Longitude Start: Longitude coordinates gathered when the User responded to the first prompt in the session. 
  • GPS Latitude Finish: Latitude coordinates gathered when the User completed the last prompt in the session. 
  • GPS Longitude Finish: Longitude coordinates gathered when the User completed the last prompt in the session. 
  • Device ID: Provides information about the User’s mobile phone operating system (e.g., model of the phone, version of the RealLife app, etc.). 

SUMMARY 

Summary datasets provide a way to view a statistical summary of Users’ responses to prompts that gather numeric data, including range slider, multiple choice, rating scale, numeric entry and number wheel prompts.  The data is formatted so that each row represents a summary for a participant and each column heading provides a statistical summary for a single prompt. For each prompt, you will see three column headings identified with the Prompt Label and then the associated statistic for that prompt. 

Definitions for each column heading within the summary dataset are listed below: 

  • Participant ID: The unique ID number assigned to every person who creates a mobile account in the LifeData system. 
  • All NISs/UISs: This column heading is used to identify which data are reported in the summary dataset. If all NIS or all UIS instances are summarized, then “All NISs” or “All UISs” will show in the first column, after USER ID.  If you choose to report only selected UIS or NIS instances (e.g., Sessions 1-10) in a summary file, then this will be displayed in the column heading.  The rest of this column will be blank. 

Note: Each of the columns below are provided for each prompt that contains numeric data within a NIS/UIS session which has been selected for summary.  

  • [Prompt Label] (Mean): The mean for the specific prompt identified with that Prompt Label.  The value represents the average score for the User across all of their responses to this specific prompt. 
  • [Prompt Label] (SD): The standard deviation for the specific prompt identified with that Prompt Label. The value represents the standard deviation in responses for the User across all of their responses to this specific prompt. 
  • [Prompt Label] (Ct): The count represents the number of times a User responded to the specific prompt identified with that Prompt Label. 

STARTUP 

Startup data is organized so that each row provides a single User’s responses to prompts delivered once, at the beginning of LifePak use. 

  • Participant ID: The unique ID number assigned to every person who creates a mobile account in the LifeData system. 
  • [Prompt Label]: Each prompt is assigned a Prompt Label during LifePak creation, which is used to identify it in the dataset. Users’ responses to a startup prompt are listed under the column heading for that particular prompt label. 
  • LifePak Download No: Each time a User downloads a LifePak, that download is assigned a number. Most Users download a specific LifePak once, so they usually have a download number of 1.  In some cases, a User may delete a LifePak and download the same one again.  In those cases, each subsequent download of that same LifePak is given a new download number.  For example, if a User downloads the same LifePak three times, on that third time any data that is sent to the server will be identified with a Download No of 3. 
  • Beginning time: Date (month/day/year) and time (hr:min) at which the Startup Session was initiated. 
  • Ending time: Date (month/day/year) and time (hr:min) at which the Startup Session was completed. 
  • Device ID: Provides information about the User’s mobile phone operating system (e.g., model of the phone, version of the RealLife app, etc.) 
Have more questions? Submit a request

Comments