-
Notifications
You must be signed in to change notification settings - Fork 1
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 Report 3.0 #1623
Comments
@mmusori What do you mean by this? |
@mmusori Sounds good but 2 comments: 1 - Would it be better to put those descriptions in tooltips next to each and have the field on the left describe the purpose of that action - for example - This field will allow you to select who will eventually see and have access to this form. Once selected, only the selected audience will be able to see this reports published, get notifications, and view it. You can change this later on. 2 - I wonder if it's clear to the user what the distinctions are between these fields. As I see the descriptions, they may seem confusing. Maybe something like this? RCRC Movement - Available to all members of the RCRC Movement with an active IFRC GO login For the latter it was a bit confusing - is it essentially RCRC minus ICRC or IFRC + delegates? Thanks and the rest of the updates are done minus these 2 questions. |
2: IFRC and NS": National Society Members works because we mean Staff and volunteers (But maybe not NS members) |
@mmusori https://www.figma.com/proto/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?page-id=0%3A1&node-id=316-23573&viewport=5697%2C9961%2C0.12&t=5ytejxQrkmspVAQ5-1&scaling=scale-down-width&content-scaling=fixed&starting-point-node-id=1%3A10724&hide-ui=1 Wireframes updated. Can you check if the text seems accurate? I guess the only missing point is my question about the "upload" section above. I wasn't clear on what needed to be done there. |
@mariam-yu we need another tab for uploading images/maps . The test should read "Upload images". It should be have the same functionality as the the "upload documents" tab below. |
As we don't have document and image upload option at the moment, we need to define how these will appear on the emergency page (do we show them on the emergency page at all)? Similarly, we need to define how we handle those values that are added in a FR and displayed on the emergency page? Do we change the current approach? Affected areas (districts, provinces) should be also editable somehow (emergency page vs FR). Do we need to allow additional admin levels on the FR form? |
@mmusori If the goal is just to have a place for the user to upload images, then in theory they can do within the same file, i.e. Upload additional assets (documents, images, maps), and we just need to make sure the field allows multiple uploads. Would that work? See updated in the wires: https://www.figma.com/proto/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?page-id=0%3A1&node-id=316-23951&viewport=-7352%2C25847%2C0.27&t=6WE6u2VU86I2JenX-1&scaling=scale-down-width&content-scaling=fixed&starting-point-node-id=1%3A10724&hide-ui=1 |
@tovari great questions. Let's sync on this? It would be very helpful for me to review these flows with you. Thanks! |
Background
The purpose of the Simplified Reporting Session during the KL meeting was to pow wow around the following fundamental issues.
o Identify and eliminate redundant fields across the field report, and a new Monitoring tool from the Project 3W and Emergency 3W tools.
o Ensure field names, data types, and formats are consistent between the platforms.
o Create a shared field structure to ease the data transfer between tools.
o Make fields essential for core reporting mandatory, while others are optional, reducing the burden on the users.
o Conditional questions that only appear based on previous answers can streamline the user experience.
Proposed state
The text was updated successfully, but these errors were encountered: