High priority:

• #446
• #447
• #448

Medium priority:

• #449
• #450
• #451

Low priority:

• #452

The GO Workplan url is broken on the Resources page.
The correct url:
https://ifrcorg.sharepoint.com/:b:/s/IFRCSharing/EWuCMne44ipEvbSHud6H38oB7mba_gaJxtwHelN909FEgg?e=uIdBu5

Description of the ticket

This Risk Watch ticket contains a number of hot fixes to address issues related to the GO rewrite as well as the introduction of several new features, some of which are related to the Montandon-GO integration.

Hot Fixes (Highest priority)

• Risk information for certain hazards is not appearing on global/regional pages (applies to many countries, not only the DRC):

• Risk information for an entire region (here Africa) is showing up on the bar chart:

• #453

• Normalisation and coping capacity features not working on global and regional pages (seasonal risk tab): when you toggle those on and off, the bar charts do not update.

• Missing information on global/regional pages: When only "flood" hazard is selected, the results look like an alphabetical list of countries and not a ranking of risk (see screenshot below):

• #454

• GDACS Imminent Event forecasts: In the pop-up box just have one link "More information" which would (in this case) redirect to the GDACS report (e.g., https://www.gdacs.org/report.aspx?eventid=1102364&episodeid=1&eventtype=FL). In other words, remove the URLs/links associated with what is currently shown for "More Details" and "Geometry" -- just keep the link for what is currently show as "Report" and rename "Report" as "More information"

• No imminent event forecasted. When there is no imminent event forecasted, remove the map on the country page altogether; if that is too difficult, then replace the text with "No imminent event forecasted" but don't ever show this:

If I try to start local development via docker-compose up, it fails with:

Starting go-web-app_react_1 ... done
Attaching to go-web-app_react_1
react_1  | yarn install v1.22.19
react_1  | [1/4] Resolving packages...
react_1  | success Already up-to-date.
react_1  | Done in 0.34s.
react_1  | yarn run v1.22.19
react_1  | error Command "dev" not found.
react_1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
go-web-app_react_1 exited with code 1

Recommended fix in docker-compose.yml:

-    command: sh -c 'yarn install && yarn dev --host'
+    command: sh -c 'yarn install && yarn start --host'
+    env_file:
+      - .env

Is your feature request related to a problem? Please describe.
Multiple Heads of Delegations told they want to see multi-country/regional appeals on country pages. E.g. South Sudan is part of the Africa Hunger Crisis appeal, but the South Sudan country page doesn't show any active appeals, which is confusing to users. At the moment, users have to look at both the country page and the region's page to figure out if a given NS has any active appeals ongoing.

Describe the solution you'd like
All multi-country/regional appeals should also appear on country pages that are part of those appeals (in addition to Regions' pages). Also, Luke confirmed this would be the preferred behaviour.

Would be great to understand the costs and required resources to setup and maintain a Training environment.
This would be a copy of PROD with options of data sync from PROD on demand as well.

The purpose is that users would use this to learn and explore the platform.

So, would be good to see approximately:

• costs of setup
• yearly infra costs
• required resources to setup (hours)
• resources of maintenance (yearly) in hours

for the Allocation Form export, when a DREF type in the online form is "Loan" (this can be a DREF application or Ops Update form), the field "DREF Allocation is requested for" should say "Emergency Appeal" instead of "DREF Operation

• #401
• #402
• #403
• #404
• #405
• #408
• #410
• #411
• #412
• #413
• #414
• #415

cc @tovari @marcovvu1

There are still a few places on the frontend where we make unbounded API calls (i.e. where we set the limit parameter to the API to a really high number to ensure we fetch "all" results") instead of paginating through API responses and fetching a sane amount, say 100, elements at a time.

This is a blocker to us removing support for high limit values on the API - ideally, we would lock-down the API to not allow more than, say, 200 items in a single request.

We need to:

• Identify all places in the frontend code where we make unbounded calls
• Look for ways to change the logic to not need an unbounded call
• For cases where we do need to fetch "all" items, implement request pagination on the frontend, similar to how we are handling CSV downloads on the frontend now.
• Once the above is done, give warning to all API users, and then implement a limit restriction on the API.

I can start enumerating places where we are making unbounded calls on the frontend.

cc @frozenhelium @tovari @szabozoltan69

Please remove these 2 videos from https://go.ifrc.org/resources

• Field Report COVID-19
• Preparedness for Effective Response Module

IFRC Presence and ICRC Presence

Figma link

• IFRC Presence: https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-28752&mode=design&t=n8Be8fXTYRRoXjk3-4
• ICRC Presence: https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-28759&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://drive.google.com/file/d/1QkqMjDdlBoLATQcFFjCHji4DdX1abOhZ/view?usp=drive_link

Country where data are available

https://go-web-ifrc.dev.datafriendlyspace.org/countries/27/profile/supporting-partners

Key takeaways

Available data

• IFRC Presence
  • Name
  • Designation
  • IFRC Legal status link
  • IFRC disaster law link
• ICRC Presence
  • Key Operations links for available countries (24 countries)

Unavailable data

• IFRC Presence
  • Contact Information
  • Email ID
• ICRC Presence
  • None

Remarks

• For IFRC Presence, the data is pulled from the XML file attached in the Figma

Contacts

Figma link

• https://www.figma.com/file/myeW85ibN5p2SlnXcEpxFD/IFRC-GO---UI-Current---1?type=design&node-id=15913-238285&mode=design&t=Y94ci9gob6cJakvd-4

Google Colab link

• https://colab.research.google.com/drive/13XdiBTHqM3Z7L18kaZlbGevR5Ulft6y8?authuser=0#scrollTo=xZ3C00wW15rD

Country where data is available

• https://go-web-ifrc.dev.datafriendlyspace.org/countries/14/profile/supporting-partners

Key takeaways

Available data

• IFRC
  • First Name
  • Last Name
  • Country
  • CON Title
  • Email ID
• International Partners

Unavailable data

• None

Remarks

• Where are we pulling data from for International Partners?

Is your feature request related to a problem? Please describe.
Feature request to add contextual information to the disaster categorization field.

Describe the solution you'd like
I've spoken to users that are confused about the "Disaster Categorization" field under Emergency Overview on emergency pages. I think either converting that label to a link, or having help text icon (accessible via hover) that provides access to guidance on the definitions and implications of each color code would be helpful.

Additional context

These two documents capture the information I'd like to have accessible:
IFRC Global Tools Review Final Report.pdf
IFRC Leading Emergency Assessment and Planning.pdf

On the “IFRC Global Tools Review Final Report English” doc, check page 7. On “IFRC LEAP approach Sept. 2018”, check page 33.

Should there be any restrictions around viewing or updating information related to this feature
No

Can we add a .nvmrc so its clear what version of node is required?

cc @tnagorra

Ticket description

If you find issues or have any feedback on the Country Pages, please add them in the comments. While commenting, please add them with Task list/ checkboxes (and with screenshots and URLs if possible).

Post-release changes

• #1007
• #1008
• #1009
• #1010
• #1011

Hide PII in Local Units Information

• #896

Add Wiki hook points (29th April)

• #894

Additional changes (22nd April)

• #884

Feedback from Daniel added in the comments of #492

• #662
• #663
• #664
• #665
• #666
• #667
• #668
• #669
• #670
• #671
• #672

Commented by Daniel (4th March)

• #730

Additional feedback by Daniel (4th March)

• #741
• #742

Additional feedback (12th March)

• #759
• #760
• #761
• #762
• #763
• #764

26th March

• #800
• #801

Based on #360 (comment)

• #805

8th April

• #834
• #835

17th April (Based on feedback from Mariam & Alex)

• #867
• IFRCGo/go-api#2111
• #869
• #870

Filters going up when scrolling is a strange interaction. Can we have it just push down the page a bit. So, if I click on a filter bar is just slide up a bit to give space to the dropdown.

Issue

Sentry tries to send most of the data to the server to provide additional context related to errors. Right now sentry is also sending the API response which sometimes can cause 413 errors. We should have a check to make sure we scrub the data if it hits the limitation.

How to fix

We can use sentry SDK to clean up data before sending using the beforeSend hook.
https://docs.sentry.io/platforms/javascript/guides/react/data-management/sensitive-data/#scrubbing-data

Context

There was an error on the DREF page which is not showing in sentry. https://go-stage.ifrc.org/account#my-dref-applications. It is being rejected by a sentry with the error envelope exceeded size limits (https://develop.sentry.dev/sdk/envelopes/#size-limits)

Additional info

We can see how many sentry events are rejected from the stats page in sentry.

https://sentry.northeurope.cloudapp.azure.com/organizations/ifrc-go/stats/

abcdef

The map export button on each emergency pages became inactive:

Its not possible to generate the png.

cc: @davidmuchatiza

NS Local Units

Country where data is available

• United Kingdom: https://go-web-ifrc.dev.datafriendlyspace.org/countries/3/ns-overview/context-and-structure
• Gautemala: https://go-web-ifrc.dev.datafriendlyspace.org/countries/76/ns-overview/context-and-structure
• United States: https://go-web-ifrc.dev.datafriendlyspace.org/countries/4/ns-overview/context-and-structure
• Costa Rica : https://go-web-ifrc.dev.datafriendlyspace.org/countries/51/ns-overview/context-and-structure

NS Directory

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-32028&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://colab.research.google.com/drive/13XdiBTHqM3Z7L18kaZlbGevR5Ulft6y8?authuser=0#scrollTo=xZ3C00wW15rD

Key takeaways

Available data

• First Name
• Last Name
• Country
• CON Title

Unavailable data

• None

Remarks

• All the required data for this section is available

Key Documents

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-32276&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://colab.research.google.com/drive/1cwlmvs91Yz8zWxqrk07btxdGCa8oR6Xf#scrollTo=Dg_JwpifPHcH

Country where data is available

https://go-web-ifrc.dev.datafriendlyspace.org/countries/3/ns-overview/context-and-structure

Key takeaways

Available data

• Name
• Language
• url
• thumbnail
• year
• Document Type
• Year text

Unavailable data

• None

Remarks

• All the required data for this section is available

National Society Indicators

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-31956&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab links

• https://colab.research.google.com/drive/1DhS_lV9Kii2Tfff9xnmFAMq7bySP4w4a?usp=sharing
• https://drive.google.com/file/d/14aJPluXTJvmSjAahofNwDh-hS0ngcPD9/view?usp=drive_link

Key takeaways

Available data

• Income (CHF)
• Expenditure (CHF)
• Staff
• Volunteers
• Trained in first aid
• Date Founded
• Branches
• Youth 6-29 years

Unavailable data

• Multipurpose Cash*
• Sectorial Cash*

Remarks

• For Youth 6-29 years, data for 18 and above is available
• Multipurpose Cash and Sectorial Cash
  • We have used the Consolidation worksheet from CC Consolidation sheet listed in the Figma.
  • We have multiple rows under multi_purpose_cash. Are we totaling them and displaying the sum?
  • We could not find any related data for Sectorial Cash in the sheet. Are we totaling the Project Objective (Sector) (except multi_purpose_cash) for Sectorial Cash?
  • For People Reached, are we displaying the sum of the Total beneficiary column?
  • For CHF distributed, are we displaying the sum of the Total cash expended (CHF) calculated via Exchange rate sheet column?

NSD Initiatives

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-32253&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://colab.research.google.com/drive/1NLfwu1B1XovbE-i76AYaTg8ojDHKqeSS#scrollTo=nhfvDSjYYZIA

Country where data are available

https://go-web-ifrc.dev.datafriendlyspace.org/countries/21/ns-overview/context-and-structure
https://go-web-ifrc.dev.datafriendlyspace.org/countries/121/ns-overview/context-and-structure

Key takeaways

Available data

• Id
• NationalSociety
• Year
• Fund
• InitiativeTitle
• Categories
• AllocationInCHF
• FundingPeriodInMonths

Unavailable data

• Funding type

Remarks

• The data for Funding type is not available.
• We have called 3 APIs for different fund names, so it might take a bit of time to load

Main source of income (Last 3 years)

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-32147&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://colab.research.google.com/drive/1E8xhhGagwbpCmMdgsQ0E5B7GwkkqN2sR#scrollTo=WKfdTKO7N3_f

Key takeaways

Available data

• Income (CHF)
• Year
• Organizations

Unavailable data

• None

Remarks

• The design says last 3 years but in the Colab link, we have pulled all the data. Can be filtered out as per need
• The design only shows 3 organizations, but multiple organizations are available in the external source. This too can be filtered out
• For the cases where the income data is unavailable or 0, FDRS is showing them as n/a

Country Key Indicators

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-26948&mode=design

Google Colab link

• https://drive.google.com/file/d/1N6mamCNH0x8yV30z7_0jZyLWtPHPcQg9/view?usp=drive_link

Key takeaways

Available data

• Population
• Population over 65
• Urban pop
• GDP
• GNI/CAPITA
• Poverty (% POP)
• Life expectancy
• Literacy
• Gender inequality index (GII)
• Population under 18

Unavailable data

• Number of people under poverty rate
• Number of people in disaster-prone zones

Remarks

• Population under 18 not found but Population ages 0-14 is found. Can we consider them the same?
  Link: https://data.worldbank.org/indicator/SP.POP.0014.TO.ZS?view=chart
• Is Number of people under poverty rate is same as the indicator Poverty headcount ratio at national poverty lines (% of population)? Please confirm. Link: https://data.worldbank.org/indicator/SI.POV.NAHC?view=chart

Seasonal Calendar

Figma link

• https://www.figma.com/file/uRgMamNHRi5KhhroYDwuxN/%5BOLD%5D-IFRC-GO---Wireframes?type=design&node-id=20331-10792&mode=design&t=Ku18qN8MYgXiKCzI-4

Google Colab link

• https://drive.google.com/file/d/1MatVjc7wfpCny0OdlUgDUFffzW6nhB_y/view?usp=drive_link

Key takeaways

Available data

• Country
• Months
• Event
• Event_type
• Label

Unavailable data

• None

Remarks

• All the necessary data are available

Population Map (including key climate events and key dates)

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-26948&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://drive.google.com/file/d/1QkqMjDdlBoLATQcFFjCHji4DdX1abOhZ/view?usp=drive_link

Key takeaways

Available data

• None

Unavailable data

• Population Map
• Key Climate Event
• Key Dates

Remarks

• Data source used for Population Map : World Bank
• No data available for Key Climate Events and Key Dates

Changes needed:

General

• Change icon for "Shelter" in all exports
  
• Add a new option ONLY to Planned interventions called “Coordination and Partnerships” using this icon for the export
  
• For “Needs and Gaps”, “Planned interventions” and “Actions taken by National Society”, the sectors should follow this order in the export:

1. Shelter , housing and settlements
2. Livelihoods
3. Multipurpose cash
4. Health
5. Water, Sanitation and hygiene
6. Protection, gender and inclusion
7. Education
8. Migration
9. Risk reduction, climate adaptation and recovery
10. Community engagement and accountability
11. Environmental sustainability
12. Coordination and partnerships (only planned interventions)
13. Secretariat services (only planned interventions)
14. National Society Strengthening (only planned interventions)

• From Needs and gaps, remove the option for “Shelter Cluster Coordination”
• Add an option to download “Assessment Report” and “any supporting documentation if relevant (description for the event for imminent)” from the export and from the form. For the export add it as a link, Assessment report at the end of the section "Needs (Gaps) Identified" and supporting documentation at the end of "Description of the event".
• Move the "Numeric details" from "Essential Information" to “description of the event” under “date of the event”
• “Submission and contacts” section change name to “Operational timeframes and contacts”
• Add the following question at the end of “Risk and security considerations” section, “Has the child safeguarding risk analysis assessment been completed?” (Yes/No question) – Should also appear on the exports.
• For all dates, format should be day-month-year. (For all exports)
• In section "planned Interventions", on the list of activities, bullet points are only appearing for the first activity
• Make the content font 11 in size (tittles look ok)
• Bring back GO logo at the bottom of the pages in the export

Application

• Do not transferred anything from Field Report to ICRC actions.
• Government has requested international assistance is not transferring from Field Report to DREF application.
• In “description of the event” section, the field “date of disaster/date when the trigger was met” should appear in the export.
• In “Current National Society actions” section the field start date of national society actions should appear on the export.
• Add an option to upload a document below “Crisis category” (optional), field should be named “If available please upload Crisis categorization Analysis”. Make it also available to download in the export
• In Previous Operations section, make the hyperlink to the Operational learning dashboard more obvious and change the text to: “To access the Operational Learning Dashboard and check learnings for the country, click HERE”, make it in red if possible.
• In Previous Operations, if “Has a similar event affected the same area(s) in the last 3 years?” if No, hide the rest of the questions (except lessons learned), if yes, show “Did it affect the same population groups?”, if no, hide the rest of the questions (except lessons learned), and so on with the other 2 questions.
• In the Plan activities section, transfer the total budget from the Overview (first page).
• In Event details, Description of the event, after scope and scale of the event add two new fields called “Sources of information (optional) name” and “Sources of information (optional) link” with the possibility to add more (like in the Risk section), with the following guidance below: Add the links and the name of the sources, the name will be shown in the export, as an hyperlink. This should be visible in the export and the sources should be numbered.
• Needs and Gaps, the field called Any gaps/limitations in the Assessment should not appear if empty.
• In targeting strategy, add option to upload a file called “Upload any additional support documentation (Optional). Should be able to download in the export (using the link). Any type of file

Ops Update

• When the application was a type “assessment” or “imminent” add a pop out asking if the DREF is changing to response
• In “Current National Society actions” section the field start date of national society actions should appear on the export.
• Budget is not appearing in export.
• In the Timeframes Section, add the Reporting timeframe field, with the option to add to dates. In the export this field will appear in the cover page as shown below:
  

Final Report

• Remove the word "New"
  
• In the Implementation sections, below Persons Targeted field, add a Field called Persons reached, keep male and female disaggregation as part of the persons reached section.
  
• In the Targeting strategy, change the question “Who will be targeted by this operation” to “Who was targeted by this operation”

Sorry for the loooooong ticket!! :) @udaynwa @frozenhelium @tovari

README can be super basic for now with node version required and how to start. And would be good to also add LICENSE, can be same as the one for go-frontend - https://github.com/IFRCGo/go-frontend/blob/develop/LICENSE

cc @tnagorra

- [ ] DREF super ticket (improvements and bugs in the current process) (2023)
- [ ] Imminent template (2023)

• Translations
• History of changes on the front-end
• Import template (excel)
• EAP process

• Form Summary
• Field Report for activation (creates Emergency page)
• Operational Update
• Final Report
• Front end changes to host the full EAP and all the info

• Prompt to the user to link Application with a filtered list of Field Reports
• Indicators
• New allocation request
• Analytics page
• DREF Emergency pages
• Monitoring tool
• Master Sheet 2.1

Country pages - Risk watch tab - Seasonal risk

Risks by Month timeline

There are 2 March, February is missing:

Yesterday, we had an error on production after an Appeal was ingested without having a Country attached. We need to make sure this cannot happen again.

If it is legitimate / possible that Appeals can be without a Country, then we should make sure the frontend does not fail if an Appeal is missing a Country.

However, I think in all likelihood, we just want to ensure on the backend that this cannot happen that an Appeal is created without a Country.

We should probably:

• Remove the null=True for country on the Appeal model, so that the database does not allow null values: https://github.com/IFRCGo/go-api/blob/develop/api/models.py#L895 - this will require checking all existing appeals in the database and writing a migration if needed.
• During the Appeal ingestion script, if the incoming data does not have a country attached to the appeal or the country lookup fails, output an error log, but do not attempt to insert that record into the database. For that I guess here instead of returning a None country, we should raise an exception: https://github.com/IFRCGo/go-api/blob/develop/api/management/commands/ingest_appeals.py#L191 and I guess catch the exception here and just skip inserting this record in case of failing country lookup: https://github.com/IFRCGo/go-api/blob/develop/api/management/commands/ingest_appeals.py#L206 ?

We should discuss this - if we think that we want to continue allowing Null values for country on the backend in case the country look-up fails, then we would need to rather make changes on the client to deal with null values for country.

For this particular Appeal where we had the country come in as null, we should investigate why that happened: was this information missing in the upstreeam data, or did we fail to match the country code correctly, or .. ?

cc @frozenhelium @thenav56 @szabozoltan69 @tovari

This is a requirement for YU to scope and provide a light recommendation to implement to support users.

Risk Seasonal Map

Metrices

People Exposed

Data Sources

• Raster displacement data
  • Cyclone
  • Flood
• IPC
  • Food Insecurity

People at Risk of Displacement

Data Sources

• IDMC
  • Cyclone
  • Flood

Risk Score

Data Sources

• INFORM (Modified by Justin)
  • Drought
  • Cyclone
  • Flood
• GWIS
  • Wildfire

Severity

We have 5 category fot the severity

1. VERY HIGH
2. HIGH
3. MEDIUM
4. LOW
5. VERY LOW

Calculation for Severity

People Exposed

For each country,

• We have exposure population by the hazard.
• We further disaggregate them into the months.
• We calculate the total population by the SUM of population from selected hazards for the selected months.
• Then, we categorize the severity according to the predefined population brackets as follow:

VERY HIGH: exposure > 10,000,000
HIGH: exposure > 1,000,000
MEDIUM: exposure > 100,000
LOW: exposure > 10,000
VERY LOW: exposure <= 10,000

People at the Risk of Displacement

For each country,

• We have population at the risk of displacment by the hazard.
• We further disaggregate them into the months.
• We calculate the total population by the SUM of population from selected hazards for the selected months.
• Then, we categorize the severity according to the predefined population brackets as follow:

VERY HIGH: exposure > 1,000,000
HIGH: exposure > 100,000
MEDIUM: exposure > 10,000
LOW: exposure > 1,000
VERY LOW: exposure <= 1,000

Risk Score

For each country,

• We have risk score by the hazard from 2 different source with different range.
• We further disaggregate them into the months.
• We calculate the final risk category by taking the MAX value from selected hazards for the selected months
• Then, for Wildfire data from GWIS, we categorize them based on this Article. Summary of the article can be found here.
• And, for the data from INFORM, we categorize them based on the official categorization.

Normalize by population

• We find the max population, and we calculate a normal population factor for each contry as: Population factor = Population of the Country / Max Population
• We then multiply the risk score by this population factor

Include coping capacity

• We have value of Lack of Coping Capacity (LCC) for each country with a range of 0 - 10
• We then normalize the value of LCC
• We then multiply the risk score by the normalized value

Map

The map shows the calculated severity of selected hazards for the selected months

Sidepane

The sidepane shows the stacked bar chart for the relative risk of the selected hazards for the selected months

Feature Request

Overview

The integration would provide Go developers with a straightforward way to conduct end-to-end testing within the context of Go.

Use Case

As a developer working on web applications, I often find the need for robust end-to-end testing solutions to ensure the reliability of the application. Integrating Playwright directly into Go would streamline the testing process, offering a convenient and efficient way to conduct these tests.

Proposed Feature

The proposed feature involves creating a set of functionalities that allow developers to easily set up and execute Playwright tests within Go. This could include:

• #1046
• #1047
• #1048
• #1049
• #1050
• #1051

Acceptance Criteria

• Playwright is successfully integrated into the project.
• An example test case is running successfully across all supported browsers.
• Documentation is available and clear for developers to add and run tests.
• CI pipeline runs Playwright tests as part of the build process.

Expected Benefits

The integration of Playwright into Go would offer the following benefits:

1. Developers can easily set up and execute end-to-end tests without the need for complex configurations.
2. Playwright's multi-browser support ensures that Go can be tested across various browsers.
3. Comprehensive end-to-end testing contributes to improved code quality and reliability of Go.

Issue

There is a change on backend that makes possible to change/add Sectors and SectorTags: IFRCGo/go-api#1693
According to that we should avoid using constants on frontend, like https://github.com/IFRCGo/go-frontend/blob/develop/src/root/utils/constants.js#L23-L200
Maybe the color representation could be a new column in backend table.
There are endpoints to scan the values on staging (and will be on prod later):
https://dsgocdnapi.azureedge.net/api/v2/primarysector
https://dsgocdnapi.azureedge.net/api/v2/secondarysector

Section “Event Details”, there is a field called “Approximate date of impact” doesn't show up on the export.

Redirection from country page to region page doesn't work when there is an additional parameter (e.g: operations) in the URL
https://go.ifrc.org/countries/283/operations

The search results page shows NOT ongoing deployments under the 'Ongoing rapid response deployments':

There is an 'Ongoing' attribute of the deployments that should be used to filter deployments in this list.

Similarly 'Open Surge Alerts' section should not how archived alerts:

Issue

Users receive the 'Invalid username or password' error, even when their account is not active.

Steps to reproduce

You need two GO user accounts (A1 and A2), and their passwords. One of the accounts should have admin permission (A1).

1. Login to the goadmin page with the account A1, go to the users section, search the user account A2, and uncheck the 'Active' box
2. Login to the go page with the account A2, and try to login with its credentials
3. You will receive the 'Invalid username or password'*

Expected behaviour

Display to the user a message saying "Your account is deactivated, contact the IM team at [email protected] for more information."

Impact

We usually receive more than one message per week, of users trying multiple times to reset their passwords not successfully.

Severity

They can not log in to GO.

Is there a workaround?

They contact [email protected]

This is a list of items to be improved, reported in the staging audit by YU:
https://docs.google.com/document/d/1lwOeYkeOasYQlrILpS51KNoQivdX43Qr1VHvDo7Bd0c/edit#heading=h.3wreak3fwz2d

Please check the document for more detail about each item.

High priority:

• #351
• #385
• #386

Medium priority:

• #387
• #388
• #389
• #390
• Main nav items - distance of items - Main nav
• Main nav- search bar styling - Main nav
• Nav item hovers and interactions - Main nav
• Country dropdown style - Main nav
• Dropdown height - Main nav
• Cards: styling - Components
• Tabs: styling - Components
• Dropdown: styling - Components
• Tables: sorting icon styling - Components
• External links: styling (country pages) - Componets
• Tooltip: interaction - Components
• Highlighted emergency cards: style - Components
• Key numbers: style - Components
• Section headers: style - Components

Low priority

• Map data points - crisis categorisation - Homepage
• Map Legends: styling - Components
• Filters: styling - Components
• Primary button: styling - Components
• Secondary button: styling - Components
• Pagination: styling - Components
• Breadcrumbs: styling - Components
• Checkbox: styling - Components
• Map: style - Components
• Side menu: style - Components
• Info cards on “Surge”: style - Component
• Side panel by the map: style - Component
• Data is not available! - Component
• Popup: style - Component

cc: @mariam-yu

Hi team,

Please could we add a PDF, exported from this Google Doc:
https://docs.google.com/document/d/113o0M98OUy7DVBPPGkIyPivs8iNCg0vqPhPtohu7E20/edit?usp=sharing
to the GO Resources page? Anywhere you think best, as it's only important that the report is linked somehow to IFRC and GO to gain credibility.

This report is to support a blog post that IFRC are putting forward for COP28. Luke approved for me today that we stick the document up there. Ideally, the document should be live as soon as possible, as they're planning on publishing the blog post soon, and this should be live before then. Apologies for adding more work on your plate!

@szabozoltan69

Many thanks,
Hamish

Can we have the entire card on hover and clickable and not just the title? Also, no need to separate between targeted population link and main link. Entire card should go to the emergency (hover on title not needed, but on the card).

Some users have reported that permissions for DREF are not working as expected, this user (Melina Miele) can see DREFs from Africa, when she doesn’t even has Regional Admin rights, she should only be able to see DREFs she has been added to. I tested and can't reproduce the problem.

@tovari @udaynwa

The page margins are much tighter than they should be in the designs (margins are 80px for 1440 screen).

We need to display 'Kosovo' on the map and also add a specific disclaimer.

The typography should be somewhat lighter than the normal country names (e.g. font light version, or grey)

The map disclaimer text:
The name and boundaries of Kosovo are consistent with UN Security Council Resolution 1244 and the ICJ's Advisory Opinion on the Unilateral Declaration of Independence in Respect of Kosovo.

@frozenhelium, What are the display options for disclaimers? Can we show based on map view, zoom scale? Can we specify text in the disclaimer box based on the page url (e.g. showing it only on the map on the Serbia page)?

We have noticed a few weird cases after the first few FRs got translated:

• #531

• the styling codes may appear not only in Arabic, but in other languages as well. In this example https://go.ifrc.org/emergencies/6542#surge , the code is not displayed in the input language (French), but appears in the 3 other languages.

• part of the text may not be translated (https://go.ifrc.org/emergencies/6542#surge):
  The French input:
  
  The English translation contains some French (however the same text is translated in other places of the text):
  
  The Spanish translation even contains English translations weirdly, besides the not translated French strings:
  

• #529

• #530

Tasks

• IFRCGo/go-frontend#2890
• IFRCGo/go-frontend#2891
• IFRCGo/go-frontend#2892
• IFRCGo/go-frontend#2900

We need:

1. UI to ask users to accept T&Cs and can be linked to the license of each database pulled into Monty
2. Add field to Users to accepted_monty_terms, including another field for RC data access authorisation (e.g. exclusive access to Field Reports)
3. GO issues JWT token for user
4. Monty API uses shared secret to validate token

For point 2, we also need to build in the ability for users to insert external database tokens and their usernames that can be used to allow the user to also extract data from non-open access database (such as EM-DAT). However, need to be careful about storing these tokens...

Double check the designs of other nav items with the latest in Figma. Note the gray area and removal of button style, replacing with red to highlight the forms. Arrow to show the selected one and hovers are missing. Lastly, check the spacings with the design and placement of the title (e.g. Surge Deployment should be on the left and not right and IFRC gray 50% in color). In some cases the title is not there at all.

Also double check the gray text size styling from Figma (Light font, black).

Noting down some issues with the Surge Gantt chart, for example on this page: https://go.ifrc.org/emergencies/6700/surge

• The line representing "today" is missing a label -- space is a bit crunched, but it would be nice to have a label indicating what that line is - I think we used to show the current date above that line.
• Problems with pagination: So, on the old site, we did not do pagination on this Surge table in order to have the Gantt chart in one place. The idea with the Gantt chart is that you want to see all the deployments from the first to the last of an operation in one place - i.e. the start date should represent the start date of the first deployment to the operation and the end date the last date of the last operation. Currently, with the pagination, it shows the start and end dates for "deployments on this page" rather than overall start and end dates.

My recommendation for this would be to just not paginate on the Surge Deployments table on the Emergencies page. From conversations, it would be rare to have a very large number of deployments for an emergency, and I don't see how we could make the Gantt chart realistically work while maintaining pagination.

Let me know if that makes sense. @anamariaescobar @frozenhelium

• User should be redirected to "Account Information" page if they arrived to login page from the "Home" page
• User should be redirected back to the original page where they arrived from to the login page
• Account information page should have the "Operations following section"

Is your feature request related to a problem? Please describe.
Currently, GO 3w allows National Societies to submit population figures within a 3w project, either for people targeted or people reached. Disaggregation figures available in GO are basic: Male, Female, and Other.
One of the recommendations provided by Geneva FDRS team, was to align the disaggregation approach with FDRS platform. National Societies report in FDRS on an annual basis, following special disaggregation principles and guidelines, particularly when reporting population figures.
GO 3w to be aligned with FDRS in regards disaggregation in population figures, allowing National Societies to report on a single structure in both platforms, and avoiding extra steps and time with additional calculations.

Describe the solution you'd like
To agree on additional data points needed to align with FDRS population figures, and include them in GO 3w.
To revise current data points (People Targeted - Male, People Targeted - Female, People Targeted - Other, People Reached - Male, People Reached - Female, People Reached - Other) and integrate FDRS population figures in gender, disabilities, and age groups (if applicable).

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Potential changes in data structure in regards population figures. It may need to expand/add age groups, population with disabilities, and gender disaggregation. This may affect current data points, and will need to modify current 3w records/submissions.

Where does the data come from and how is it maintained?
3w data comes from National Societies, Partner National Societies and IFRC sectoral leads. It is maintained by themselves.

Should there be any restrictions around viewing or updating information related to this feature
any considerations around permissions e.g. public vs only logged-in RCRC users should be able to see this

Links to documentation
FDRS videos that show data disaggregation: https://www.youtube.com/playlist?list=PLf2g_NkFyyv6_tXhWfA71vHfW7ZS8LFpz

EN FDRS User Guide 2020 (3).pdf
Technical Note On Counting People Reached.pdf

I have a couple of new role profiles (attached) to be added to the catalogue of surge services in GO.

• Deputy Supply Chain Coordinator and Mobilisation Officer
Can you please upload the above mentioned role profiles to this area in the catalogue of surge services
https://go.ifrc.org/surge/catalogue/logistics

• National Society Response Capacity Coordinator
Can you please upload the above mentioned role profile to this area in the catalogue of surge services and delete both of the existing profiles in this area.
https://go.ifrc.org/surge/catalogue/other/preparedness-effective-response

Rapid Response Profile NS Response Capacity Strengthening Coordinator.pdf
Rapid Response Profile Deputy Supply Chain Coordinator.pdf
Rapid Response Profile Mobilization Officer.pdf

Organisational capacity

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-29436&mode=design&t=n8Be8fXTYRRoXjk3-4

Google Colab link

• https://drive.google.com/file/d/1EjVYA3YAn0tg3cQgadV5F2rb-HEuGZzW/view?usp=drive_link

Country where data is available

https://go-web-ifrc.dev.datafriendlyspace.org/countries/27/ns-overview/capacity

Key takeaways

Available data

• There are 4 sub-sections in the designs. Data is partially available only for few countries for each section
• For Leadership Capacity, there are 40 records. Out of them, descriptions are available for only 8 of them
• For Volunteer Capacity, there are 38 records. Out of them, descriptions are available for only 30 of them
• For Youth Capacity, there are 38 records. Out of them, descriptions are available for only 37 of them
• For Financial Capacity, there are 38 records. Out of them, descriptions are available for only 12 of them

Unavailable data

• Partial availability

Remarks

• Partial availability of data
• Excel file is being used for the analysis. So, you need to download the file from the link: https://ifrcorg.sharepoint.com/:x:/s/APPSK/EVCVrmWRua5Aj_VAGYYMwFkBpGb2-yocVt2_xblabluP-Q?email=mariam%40yllwu.com&e=xmyNea . Then you need to upload the file in the Google Colab and rename it to capacity.xlsx

Capacity strengthening and development process

Figma link

• https://www.figma.com/file/H9mZfGeXtlzK6HPzttYoci/IFRC-GO---Wires-Current---1?type=design&node-id=82-29157&mode=design&t=2hWWm5GMkFZShuID-0

Google Colab link

• https://drive.google.com/file/d/1lWcTojQ1qtKYMVYnn57woDmCJegDL7y9/view?usp=drive_link

Country where data is available

https://go-web-ifrc.dev.datafriendlyspace.org/countries/27/ns-overview/capacity

Key takeaways

Available data

• In, OCAC Assessment,
  • YearOfAssessment
  • SubmissionDate
• In, BOCA Assessment, BranchName is available

Unavailable data

• In, OCAC Assessment and BOCA Assessment,
  • Last Updated

Remarks

• We have SubmissionDate. Are we assuming SubmissionDate as Last Updated date?
• We do not have month related date. Do we extract it from the SubmissionDate?
• Where are we directing users to after clicking on View details button?
• For BOCA Assessment, we do not have Local Units/Branches data, but we do have the branch names. So, do we count them as Local Units/Branches numbers?

Google Colab link, available & unavailable data, and remarks

• #334
• #335
• #336
• #337

Tasks

For all DREF forms (DREF Application, Operations Update, Final Reports) and their exports: In the sections: “Current National Society Actions”, “Needs (Gaps) Identified” and “Planned Interventions”, change the sector, in the dropdown menus, called “Migration” to “Migration and Displacement”, keep the icon.