contact list to be exported as csv file

[matthewberryman]

I cannot implement this as the spreadsheet can become stale within a short period of time and it's a shared legal requirement (with large fines) to use an up to date list, and also to keep it secure. There are no guarantees of either use or security once downloaded and so it becomes highly risky. If MSF wants to do this then development and all hosting must be done in house by MSF.

[matthewberryman]

Do need to support this so, for example, lists can be printed and taken to areas with poor connectivity. Workaround from a compliance side: on first line of csv file, print exported on (date) and add note to check back with REACH regularly for updates.

@mehrdadgit to work on API and client side button (from landing page contacts section) as we've done on other projects.

[matthewberryman]

@LucieGueuning just putting this into dev environment now (so will be live in a few minutes) - on landing page there's now a download link

[matthewberryman]

1. change filename on download to 'contacts list'
2. export only ones showing on map/table (sync)
3. next to download csv - can have icon (like for the share one)

[LucieGueuning]

Please check update info

[mehrdadgit]

I have added the download icon

[matthewberryman]

@LucieGueuning ready for review

[LucieGueuning]

Thanks. For consistency, please follow the opposite color with the one already there for adding contact. Thanks.

The arrow in white, the background in red.

And instead of CVS, can we change the wording to 'Download contacts list'? Does that sound better to you?

[matthewberryman]

Looking at https://www.w3schools.com/icons/bootstrap_icons_glyphicons.asp there's no inverse download icon but there is a non-inversed + icon, so for consistency it's easier to change the plus one to match.

[LucieGueuning]

I let @qclin helping you on that?

[matthewberryman]

No need. I have them consistent now.

Sent from my iPhone

On 18 Oct 2018, at 21:31, Lucie Gueuning notifications@github.com<mailto:notifications@github.com> wrote:

I let @qclinhttps://github.com/qclin helping you on that?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHubhttps://github.com/MSFREACH/msf-reach/issues/437#issuecomment-430958881, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACLqbp89-IEmDHJMvfkHGqWA9ZuCuRXhks5umFh9gaJpZM4UKzkb.

[LucieGueuning]

To be GDPR compliant (requested by HK Fin):

1. MSF staff presses the button to download contacts list on REACH landing page
2. Pop-up window (before it uploads) to accept privacy policy which stands here by ticking a box. wording: 'I read and accept MSF Hong Kong Privacy Policy'
3. It, then, downloads the file right after.
4. Having the downloaded file with at the top of the file the following sentences: a. Exported on (Thu, 01 Nov 2018 10:42:54 GMT) (Timestamp), check back on MSF REACH regularly for updates. b. Please make sure you are storing this file in a safe place c. This is for sole MSF internal use. It is strictly confidential information.

Do not develop it as MSF HK needs to approve wordings first.

[LucieGueuning]

Feedback from Hong Kong: We are new to GDRP and I have gone through the same seminar session as you can see in the video only. We believe we can ask UserGroup / Across the Cloud Pty Lid for their advice on how to process the personal information for GDPR as they have decades of experiences. And see what they have completed for GDRP related area.

So Matthew, I let the responsability to you for the above wordings approval with the objective to be compliant to the GDPR. Thanks for your support on that and we are quiete new to the subject.

[matthewberryman]

@mehrdadgit can you please work on modal. I will work on wording.