-
Notifications
You must be signed in to change notification settings - Fork 5
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
field changes #653
Comments
@LucieGueuning These are not bugs (aside from some of the wording changes, which I will get onto soon) but changes from what's in the sheet, e.g. it still lists medical figures: |
@LucieGueuning operator field done (supersedes previous request in 2b) - please review in test environment. Note that operator is set automatically on event creation. |
What do you mean operator field done? Please follow the shared file in drive for field definition |
There are now two fields per comment above:
“1) mission contact person, and (2) REACH operator.”
…Sent from my iPhone
On 14 Nov 2018, at 05:32, Lucie Gueuning <notifications@github.com<mailto:notifications@github.com>> wrote:
What do you mean operator field done?
Please follow the shared file in drive for field definition
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#653 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACLqbkHiLdFJ5-Mwxmg_cxFTXVz6EudPks5uuxBQgaJpZM4XX8gK>.
|
Please follow the file and not comments above. The file shared that I never stop referring to is the right reference one!
From: Matthew Berryman <notifications@github.com>
Sent: 13 November 2018 19:04
To: MSFREACH/msf-reach <msf-reach@noreply.github.com>
Cc: Lucie Gueuning <lucie.gueuning@hongkong.msf.org>; Mention <mention@noreply.github.com>
Subject: Re: [MSFREACH/msf-reach] field changes (#653)
There are now two fields per comment above:
“1) mission contact person, and (2) REACH operator.”
…Sent from my iPhone
On 14 Nov 2018, at 05:32, Lucie Gueuning <notifications@github.com<mailto:notifications@github.com<mailto:notifications@github.com%3cmailto:notifications@github.com>>> wrote:
What do you mean operator field done?
Please follow the shared file in drive for field definition
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#653 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACLqbkHiLdFJ5-Mwxmg_cxFTXVz6EudPks5uuxBQgaJpZM4XX8gK>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#653 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYv9Q4FVRzdKJbpDaL6npOpUxKo_R944ks5uuxe1gaJpZM4XX8gK>.
|
Ok, can I suggest you keep consistency with the spreadsheet in future to minimise any errors. I have updated the wording to be "REACH Operator" per the spreadsheet but can you please double check that as I thought we were using "MSF REACH" not "REACH" consistently per other discussions? |
You are right for consistency but I won't change the wording again (for you to continue working on other deliverables). REACH operator is acceptable. For that specific operator field one: that's all good and working well. Only the order that is not followed but I guess it's coming with the field of info cleaned up. Please follow carefully all the wordings and order for each field of information into the spreadsheet shared. Awaiting for the rest to be cleaned up as per shared spreadsheet. |
"Medical Figures" should just be split into "Summary of MSF Intervention", which we fill fill out at the end of the intervention,
Mission contact person is there but it doesn't specify the event operator. Person in charge is vague. 2 fields: (1) mission contact person, and (2) REACH operator.
"Population Figures" which is necessary info at the very beginning.
"Response", should be "MSF Response"
In "Analysis of Capacity on the Ground" there is no need to put the options "medical" or " non-Medical".
Explo assessment should not be under extra details - Why explo assessment is under extra details
The text was updated successfully, but these errors were encountered: