-
Notifications
You must be signed in to change notification settings - Fork 15
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
Release Exploration & Analysis in its current state for EIC and GHG Center? #221
Comments
After careful review, I suggest not deploying to GHG Center.
Happy to meet to go over these concerns. Might be good for me to have a testing session with the team? |
We made the call today not to release E&A on the GHG Center and EIC instances before the upcoming official release. However, we should keep the pace and aim for a deploy on the VEDA Dashboard as soon as possible, if possible before the GHG Center launch, so it can serve as a reference for the upcoming changes for GHGC/EIC. |
Contributes to US-GHG-Center/veda-config-ghg#221 to get us close to a delivery state. Includes the work done in #744 plus changes so that custom api endpoints are supported in the exploration page. Besides the former: - Connects the data-catalog to exploration by filtering the dataset selector modal by the veda dataset name - Removes connections to previous analysis and dataset explore pages - Add info icon to dataset #747 - Ensure that the analysis range is within the current domain (bug identified in the feedback session) - Add support for vector datasets - I noticed that this was no implemented in the A&E so I added it. The zarr layer support is still not implemented, but not sure we need it immediately.
Building a new release plan in |
Yesterday (Monday) @faustoperez and @j08lue (accompanied by @hanbyul-here and @danielfdsilva) conducted four 30-minute user testing sessions for the Exploration & Analysis interface with scientists.
We gathered great insights about how the scientists approach the interface, what they find particularly valuable or nicely done and where there are challenges. These insights will feed into fast cycles of improvements and more testing in the coming weeks and months.
Could we release now?
Overall, our impression was that the interface is usable and useful.
Issues blocking release
The only blocking issue we identified was
And additional ongoing work also needs to be complete
Risks
Possible mitigation: We would need to do a lot of stress testing ahead of the release this/next week.
Possible mitigation: We can always choose not to merge this feature anyways and keep the current UI.
Acceptance criteria
The text was updated successfully, but these errors were encountered: