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

Field Report 3.0 #1623

Open
mmusori opened this issue Jan 9, 2025 · 14 comments
Open

Field Report 3.0 #1623

mmusori opened this issue Jan 9, 2025 · 14 comments
Assignees
Labels
Draft This issue is currently being drafted and has not been finalized yet.

Comments

@mmusori
Copy link

mmusori commented Jan 9, 2025

Background

The purpose of the Simplified Reporting Session during the KL meeting was to pow wow around the following fundamental issues.

  1. Reduce Field/Question Count:
    o Identify and eliminate redundant fields across the field report, and a new Monitoring tool from the Project 3W and Emergency 3W tools.
  2. Standardize Data Interoperability:
    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.
  3. Use Required/Optional Fields:
    o Make fields essential for core reporting mandatory, while others are optional, reducing the burden on the users.
  4. Implement Dynamic Forms:
    o Conditional questions that only appear based on previous answers can streamline the user experience.

Proposed state
Image

@mmusori mmusori added the Draft This issue is currently being drafted and has not been finalized yet. label Jan 9, 2025
@mmusori
Copy link
Author

mmusori commented Jan 9, 2025

@mmusori
Copy link
Author

mmusori commented Jan 10, 2025

Image

This is missing in the crisis profile.

@mmusori
Copy link
Author

mmusori commented Jan 10, 2025

Image

Another tab for uploading images

@mmusori
Copy link
Author

mmusori commented Jan 10, 2025

Image

H+1 should be household

@mmusori
Copy link
Author

mmusori commented Jan 10, 2025

Image

This should only appear if the NS ticks NS Request International Assistance.

@mmusori
Copy link
Author

mmusori commented Jan 10, 2025

Image

We need to keep it as below:
Image

@mariam-yu
Copy link

Image

Another tab for uploading images

@mmusori What do you mean by this?

@mariam-yu
Copy link

Image

We need to keep it as below: Image

@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
IFRC Secretariat - Available only to IFRC members with an active IFRC GO login
Public - Available to all the users accessing the GO platform without login
IFRC and NS - Available to both IFRC and National Society members (not ICRC)

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.

@mmusori
Copy link
Author

mmusori commented Jan 17, 2025

  1. Yes tooltips would be better.

2:
Under IFRC Secretariat:
We could change IFRC members to, "...IFRC Staff with an active IFRC GO login."

IFRC and NS": National Society Members works because we mean Staff and volunteers (But maybe not NS members)
So that could change to "...National Society Staff and volunteers." For : IFRC and NS - Available to both IFRC and National Society members (not ICRC). We could remove (not ICRC) it would still mean the same that is IFRC Secretariat + National Societies.

@mariam-yu
Copy link

@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.

@mmusori
Copy link
Author

mmusori commented Jan 22, 2025

@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.

Image

@tovari
Copy link

tovari commented Jan 23, 2025

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)?
Especially when multiple FRs are attached to an emergency page. Do we show all images and documents from all FRs, or only from the last one? Can we manage (delete) these documents on the emergency page, or we need to edit the FR where the document was uploaded?
How we handle multi-country emergencies? Any document will appear from the child emergencies on the main (parent) emergency?

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?

@mariam-yu
Copy link

@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.

Image

@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

@mariam-yu
Copy link

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)? Especially when multiple FRs are attached to an emergency page. Do we show all images and documents from all FRs, or only from the last one? Can we manage (delete) these documents on the emergency page, or we need to edit the FR where the document was uploaded? How we handle multi-country emergencies? Any document will appear from the child emergencies on the main (parent) emergency?

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?

@tovari great questions. Let's sync on this? It would be very helpful for me to review these flows with you. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Draft This issue is currently being drafted and has not been finalized yet.
Projects
None yet
Development

No branches or pull requests

3 participants