Closed KatieOC closed 4 years ago
GEND_GBV OU Level and Global are agree with MSDs. GEND_GBV Mechanism is still defaults to 2018. Panorama and the MSDs don't agree with DATIM, but because it seems to be an issue with the DATIM cleaning favorite not including TA results, I've filed a DATIM ticket, #30850, on the helpdesk for DATIM.
@erinschelar
On OVC_SERV Coarse Age Comparison Chapter, the wrong StandardDisaggregates are selected in the dossier, thus creating a discrepancy with the Targets. The Dossier has "Total Numerator" selected as the disagg, but it should be "Age/Sex" and "Age/Sex Program Status" For the Dashboard:
@shabeenally
Dossier: SIMS-MER Integrated Analysis Chapter/Page: Partner Performance - SIMS 4.0 Assessments by Partner OU: Botswana (small) Issue: Title has a large space between the words "by" and "Partner"
@shabeenally
Dossier: SIMS-MER Integrated Analysis Chapter/Page: Site Level Analysis - SIMS 4.0 Site Performance Over Time OU: Botswana Issue: Can't select more than one Organisation Site - no checkboxes
@shabeenally
Dossier: SIMS-MER Integrated Analysis Chapter/Page: SIMS 4.0 Snapshots - Elective CEE Performance OU: Botswana Issue: Can't select more than one SIMS Set Name in drop down menu above, but can select more than one SIMS set name on side - do we need two drop down menus that are the same?
Dossier: Cervical Cancer Global Chapter/Page: Cervical Cancer Cascade - Cervical Cancer Cascade Results by OU Issue: When user first opens page, they can't see CXCA_TX_N results in table unless they scroll to side
Hi @kayla-z - I am reviewing item: https://github.com/ICPI/DIV/issues/158#issuecomment-558361267
No data is displaying for Botwana for the three metrics CXCA_SCRN_N, CXCA_SCRN_POS, and CXCA_TX_N in the grid as there are no values for Botswana in the graph (CXCA_SRCN_D is not in the graph); if you scroll down to Eswatini, there are values there
By default, it is my understanding that the Funding Agency should be set to a default of 'All' - is that correct? We can fix the Funding Agency selector to display all Funding Agencies by default.
Hi @randyyee - we researched the following item: https://github.com/ICPI/DIV/issues/158#issuecomment-558357507
We found that the Target display value is rounded (to account for larger numbers), such that the 2K value is 1,778 and aligns with the left access. Please let us know if you have any questions.
Dossier: Testing: Single OU Chapter/Page: HTS_TST_POS, Pos: Pos trends by age/sex OU: Mozambique Issue: Extra "n/a" on x-axis
Hi @EAwong - for the issue https://github.com/ICPI/DIV/issues/158#issuecomment-559272793
Dossier: Testing: Single OU Chapter/Page: HTS_TST_POS, Pos: Pos trends by age/sex OU: Mozambique Issue: Extra "n/a" on x-axis
Fix: the N/A has been filtered out in the visualization.
Fix availability: This fix will be available in Panorama Production for the 12/2/2019 Fast Follow Release.
Hi @cnichols3h for the issue https://github.com/ICPI/DIV/issues/158#issuecomment-558594436
Dossier/dashboard name: TB Screening and TPT: Single OU Chapter/page: CH2 D1 and CH2 D2. OU: Kenya Our html code does not work on these pages. For ex, one should be able to enter a # and that will return the appropriate # of listings/rankings.
Fix: We found that there is no metric behind the filter selector, such that entering a # will not impact the results on the grid. This has been modified to use the percentage metric for filtering on those pages and those now filter the grid based upon the selection.
Fix availability: This fix will be available in Panorama Production for the 12/2/2019 Fast Follow Release.
Chapter 2 - D1:
Chapter 2 - D2: Note: The Highest 7 are more than 7 values as there are many 100% that would all rank the same.
Hi @nmcarloni and @HoustonJamie - regarding ticket https://github.com/ICPI/DIV/issues/158#issuecomment-558388110
Review/Findings: I compared the values in the Treatment Summary Table to the Treatment Dossiers and found that the Treatment Summary Table value is filtered for Q4 (2019) and the Treatment Dossier value is filtered upon 2019 (not specifically for Q4:
The visualization filter for Retention Proxy is Years Ago = 0 (Similar to other visualizations on the page).
If I can the visualization filter to Quarters Ago = 0 (Q4 FY2019) to test this out, the value is then the expected 92%:
Hi @Yabayabadoo - regarding ticket comment: https://github.com/ICPI/DIV/issues/158#issuecomment-558730431
Dossier: Health Services: Single OU Chapter/Page: HRH Support Overview/HRH Above Site comparison OU: SA Issue: Y axis generating odd intervals
Finding: The values for the particular selection require display of decimal places:
Hi @Yabayabadoo - regarding https://github.com/ICPI/DIV/issues/158#issuecomment-558728177
Dossier: Health Services: Single OU Chaper/Page: HRH Support Overview/HRH Coverage Comparison OU: South Africa Issue: No data displaying for any fiscal year
Findings (from Renee): The visualization filter as it is excludes results because HRH_STAFF does not have results for Disaggregate = CadreCategory/FinancialSupport:
See red box below.
Fix: Fix availability: This fix will be available in Panorama Production for the 12/2/2019 Fast Follow Release.
Changed the filter to the following:
(Indicator = 'HRH_CURR' AND Disaggregate = 'CadreCategory/Financial Support') OR (Indicator = 'HRH_STAFF_NAT' AND Standardized Disaggregate = 'CadreCategory')
The filter upon (Indicator = 'TX_CURR' and Standardized Disaggregate = 'Total Numerator') appears to be extraneous (per Naveen) - the results are the same if we remove that from the filter.
Screenshot in Pano Dev, per the visualization filter changes:
Hi @Yabayabadoo - https://github.com/ICPI/DIV/issues/158#issuecomment-558744969
Dossier: Health Services: Single OU Chapter /Page: HRH_CURR Cadre Mix/Average HRH team composition OU: South Africa Issue: left to right scrolling not working on this page. Visuals truncated
The visualizations on this page are set to custom settings to only display values between 0 and 2 (0 and 200%), such that is the reason that the visuals only display values between 0 and 200%.
If the custom setting is removed, all points are displayed on the visual (however, with no scrolling), as follows:
We are researching if there is a way to display a portion of the graph and allow scrolling.
Hi @Yabayabadoo - https://github.com/ICPI/DIV/issues/158#issuecomment-558726643
Dossier: Health Services: Single OU Chapter/Page: HRH Support Overview/HRH At a Glance- OU OU: All Issue: No Scroll bar for page, visual truncated
We reviewed this item and found that the visualization is compressed; the visualization doesn't allow for scrolling as it returns the all of values in the heat map within the visualization display (compresses the content): If you hover over the last heat map box on the far right, the value displays in the hover: If expanded, this returns the same 7 breakouts:
Additionally, we tested this with a different attribute with more values to test how this will return and with more values and the values are compressed and returned within the particular space allocated:
@janholcombe @pilarbullis Dossier: Prevention Global Page: Prevention continuum by KP OU: All
KP_PREV isn't populating as the first bar in the bar charts. It is populating in the Prevention Single OU dossier.
@kimisatoPC After the two fast follows post 11/22 release, all issues found in Panorama production need to be submitted to Panorama support: https://pepfar-panorama.zendesk.com/hc/en-us
Thank you.
The issue with Prevention Global has been logged in Zendesk: https://datim.zendesk.com/agent/tickets/30917.
Testing Timeline and Instructions
Timeline
Friday 11/15 - initial Q4 clean data entry closes in DATIM Tuesday 11/19 - Wednesday 11/20 QC Pano dashboards/dossiers in dev Friday, 11/22 - Pano Q4 release
Scope - Instruction
See PPT (does not include log in info) FY19Q4 Pre-Clean_Panorama_QC_Testing_no password.pptx
Testing Assignments/Dashboard PoCs
Testing Assignments/Dossier PoCs
PRIME Led Dossier QC
PQ Led Dossier QC
If a PoC is unavailable during the proposed testing time period, they are welcome to transfer testing responsibilities to another colleague by editing the above comment and assigning the new tester, and writing a new comment to inform test leads that a new assignment has been made.