Closed gokul472 closed 3 years ago
Testing blocked waiting on #4 to get default metadata into Arranger, will carryover to Sprint 7
Arranger setup complete, testing on QA unblocked. Staging still missing Arranger project, I will try and set that up myself today. But will do initial test on QA as well. Unblocking issue.
Styling matches what is provided in Zeplin except for the following:
Smoke test on Staging to be done once release tag deployed
Open question:
What are the default fields we should be including in the default config? This is based on the SONG setup but in Arranger a total of 43 fields are available for the facet panel. Or do we not want to impose a default since we cannot assume what domain the portal is going to be used for (cancer? weather? other) and put this entirely in the hands of the configurer? However, should a reasonable default still not be defined for consistency?
Lgtm on staging. closing this ticket as feedback is captured elsewhere.
Objective
The objective of this ticket is to ensure that the facets from the demo portal are updated to match the requirement for DMS portal
Acceptance Criteria
To style the data portal as mocked up, with the functionality already in Arranger
Zeplin Links for MVP
Wiki page and for Dev tasks
https://wiki.oicr.on.ca/display/OV/UI+Specs+for+DMS+Portal#UISpecsforDMSPortal-MVPitemsforthePortal