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

Data/Study Export Functionality #277

Open
4 of 5 tasks
casaout opened this issue Jan 31, 2024 · 1 comment
Open
4 of 5 tasks

Data/Study Export Functionality #277

casaout opened this issue Jan 31, 2024 · 1 comment
Assignees
Labels

Comments

@casaout
Copy link
Member

casaout commented Jan 31, 2024

To allow users/participants to export their data and share it with the researchers after checking and (if necessary) obfuscating it, we'd like to have an export functionality.

Rough overview what we'll need:

  • A wizard with three pages:
  • First page: Information on why the collected data should be shared (see screenshot)
  • Second page: Subject can review and decide which data to share/obfuscate
    • tbd
  • Once the settings are confirmed, create an export sqlite-file is created
    • create a copy of the existing database with the filename <subject id>_<YYYY-MM-DD>_<HH:MM>.sqlite in a new folder Exports inside the app location
    • encrypt and password-protect the database file (see example implementation commit and source. Use a master password (tbd) or find a better solution.
  • Third page: The subject can review the exported data and is instructed to share it with the researchers manually

Tasks:

  • Andre: create mockups and review with Malte in progress
  • Sebastian: create export according to (rough) specification above
  • Andre: check if our python scripts can still read encrypted databases (link)
  • Test implementation
  • Andre: create a documentation page that explains subjects how to install and open the export-database-file
@casaout
Copy link
Member Author

casaout commented Feb 9, 2024

Here are the design mockups. Please feel free to make them look much nicer :)
Please note that orange boxes refer to comments; and there are several instances where the study-information from #273 is included

Slide 1:
image

Slide 2:
image

Edit: for WindowsActivityTracker, we suggest another option (details tbd): Ideally we want the user NOT to obfuscate all window titles or share nothing, but as much as possible. Hence, we thought of adding one more option which is:
A textbox where users can add a list of keywords (e.g. in a comma-separated way). The windowTitle and url (possibly also other) columns are then searched for these keywords (lower case) which are obfuscated as [anonymized] (or hash?). That way, we'd know that something was anonymized, but not what it was.

Edit 2: Obfuscation should hash the windowTitle and url

Slide 3:
image

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

No branches or pull requests

2 participants