2020-03-26 Meeting notes

Date

Mar 26, 2020

Participants

  • @Phil Ewels

  • @Linus Östberg (Unlicensed)

  • Elin Kronander

  • @Pontus Freyhult (Unlicensed)

  • @Malin Klang (Unlicensed)

  • @Bjorn Nystedt

Goals

  • Summarise what has been done so far

  • Plan final details for what is needed for demo launch

  • Discuss approach for working with other partners / endorsement

  • Concluding remarks

Discussion topics

Item

Presenter

Notes

Item

Presenter

Notes

Website hosting

@Linus Östberg (Unlicensed)

  • https://coronastatus.dckube.scilifelab.se/

  • Had to hack a bunch of stuff to get it working on the deployment due to missing files

  • We will keep a dockerfile branch separate from master

  • Otherwise everything else needs to be merged to SciLifeLab:master and deployed

Localisation

Malin Klang

Proposal

@Irene Stevens (Unlicensed)

We need to choose approach

@Bjorn Nystedt @Phil Ewels

  • We have a choice now about the direction that the project moves in

    • Can be lightweight - no identification / simple survey

    • Can be heavy tracking - BankID / emails / SMS

  • @Bjorn Nystedt - questions like smoking etc. maybe not so interesting by themselves. We already have demographic information like this.

  • Advantages of lightweight approach

    • Not much more work is needed - can deploy very quickly

    • No additional privacy concerns need addressing

  • Advantages of heavyweight approach

    • Data could be much more useful - link to healthcare records such as COVID tests and backtrack to previous survey data

    • Reminders will greatly improve repeat answers to the survey and quality of longitudinal data

    • Identification will ensure proper longitudinal data and avoid people accidentally filling in the survey multiple times as fresh users

  • If using anything that is personally identifiable, probably needs to be handled together with (or entirely by) FHM (folkhälsomyndigheten)

    • @Pontus Freyhult (Unlicensed) had some ideas about auto-deletion of data after reminders etc that could sidetrack this, but FHM approach probably easiest and best.

To do before proposal

 

  • Finish deployment - @Linus Östberg (Unlicensed)

  • Translation is basically done

  • Dropdown language selector

  • More eyes on the proposal

Action items

Decisions