IOA or Dual Access Use Case
If you need two people (e.g., for IOA) to collect data on the same target but in different contexts:
Option 1: Duplicate the Program
- Create two versions of the same program (e.g., IOA playlist and Caregiver playlist).
- Assign each to its corresponding role.
Option 2: Paper Data Collection
- Print data sheets for one of the roles if duplicating programs isn’t feasible.
There is no current way to share a single target between multiple playlists and retain unique views without duplication.
Tips for Easier Setup
- Create a global parameter for your playlist tags (e.g., #caregiver #playlist #daily) to reduce typing errors.
- Always double-check capitalization.
- You can overlay targets as a clinician for comparison if duplicating for IOA.
Additional Notes
Session Role Visibility
- If a role doesn't have the playlist tag, they won’t see the playlist programs.
- Even the creator of the program must have the playlist tag to view and collect data.
- Owners can always view everything but may still be restricted from collecting data unless permissions are explicitly added.
Report Headers
- Current report headers are auto-generated.
- These include DOB, learner name, and organization.
- Logo headers on every page are not currently supported.
Report Display Order
- Programs appear in reports based on:
- Phase (e.g., Mastered first)
- Target order within the program
- There’s no current way to reorder phases at the report level.
- Best workaround: Use separate sections for active vs. mastered phases.
Randomization of Targets/Measures
Motivity does not currently support randomized target or measure presentation. However, a workaround is available:
Workaround:
- Create a link to an external randomizer (e.g., Google Sheets or web tool).
- Embed the link in the learner profile.
- RBTs use the link, get a randomized item, and then manually transition to the correct target phase.
This method works best for experienced staff (e.g., in SBT programs).
If you're interested in built-in randomization, let us know! It’s a feature request we’re tracking.