google / paco

The Paco behavioral science mobile research platform
http://www.pacoapp.com/
Apache License 2.0
327 stars 93 forks source link

Ability to prevent ad-hoc self-reports? #1527

Closed wupeggy closed 8 years ago

wupeggy commented 8 years ago

Hello, I'm trying to do an ESM where subjects can ONLY subject a survey when I send a randomly timed notification and they cannot adhoc complete a survey without an associated notification. Is that possible? Thanks very much!

NickAraujo commented 8 years ago

Hi Peggy,

This is currently not enforced in the UI. We're aware of the feature request (#1432), but it is unfortunately not currently on our roadmap. For the time being, I'd suggest emphasizing this when onboarding participants, perhaps incentivizing them by linking their incentives to the % of timed notifications they respond to.

-Nick

BobEvans commented 8 years ago

Hi Peggy

In addition to what Nick said, if it is at least somewhat helpful you can see that self reports are different in the data set. So you can drop all the self reports from your analysis.

The self reports will have a value for the column “responseTime”, but, not for the column, “scheduledTime”. Signaled responses will have a “scheduledTime”.

Hope that helps until we get around to this feature.

Best, Bob

On Oct 19, 2016, at 10:47 AM, Peggy Wu notifications@github.com wrote:

Hello, I'm trying to do an ESM where subjects can ONLY subject a survey when I send a randomly timed notification and they cannot adhoc complete a survey without an associated notification. Is that possible? Thanks very much!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

wupeggy commented 8 years ago

Hi Bob and Nick, Thanks so much for your response! We'll use the work around. Best, Peggy

BobEvans commented 8 years ago

Hi Peggy,

Let us know how it works out.

Best, Bob

On Nov 4, 2016, at 6:35 AM, Peggy Wu notifications@github.com wrote:

Hi Bob and Nick, Thanks so much for your response! We'll use the work around. Best, Peggy

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.