Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add optional "from last execution" in data query #25

Open
dariosalvi78 opened this issue May 24, 2019 · 0 comments
Open

add optional "from last execution" in data query #25

dariosalvi78 opened this issue May 24, 2019 · 0 comments

Comments

@dariosalvi78
Copy link
Contributor

dariosalvi78 commented May 24, 2019

Make the data retrieval from health stores either perfectly sampled or retriever all data since last execution.

Rationale:

I've found an issue with the way we are collecting data from healthkit.
For example, if I set a 24 hours sampling period, the actual data collection is done at the time the task is run by the user. So, for example, if I tap on "Data query" at 15:00, it will send the data from 15:00 of yesterday to 15:00 of today, but if the day after I do the same at 18:00, it will send the data from 18:00, which means that there will be a "hole" from 15:00 to 18:00 of today's data.

The a solution can be tricky.
We could set the window of time as fixed, for example from 00:00 to 23:59, but if the user sends the data before 23:59 we will miss all the data from that moment to the end of the day.

Another solution is to send the data of the doubled the sampling period (in our case 48 hours). In this case we will receive many duplicates, but we will avoid loosing any data.

Finally, another solution could be sending data between the last time the data was sent and now. This will avoid duplications, but there may be genuine cases where the researcher doesn't want a "full coverage" of the period. So this solution should be probably optional.

The "from last execution" checkbox will instruct the app to retrieve data not from now minus sampling period to now, but from last execution to now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant