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

[Design / UX] Gather requirements to understand scientist/decision maker workflows #1028

Closed
faustoperez opened this issue Jul 2, 2024 · 3 comments
Assignees

Comments

@faustoperez
Copy link

faustoperez commented Jul 2, 2024

Description

In recent conversations with NASA, there is a need to target decision-makers as well as scientists on the US GHG Center website in the short-mid term.

Acceptance criteria

  • Understand the needs of the decision-maker group of users.
  • List goals and expected outcomes of the US GHG Center website visit.
  • Understand how the experience is different from scientific users.
  • List the existing content we can surface to improve their experience.
@faustoperez
Copy link
Author

This ticket is being reviewed together with https://github.com/US-GHG-Center/ghgc-architecture/issues/290

@aboydnw
Copy link
Contributor

aboydnw commented Aug 7, 2024

@faustoperez based on the meeting today, I don't think we are going to get meaningful review time from the GHG team on this topic until after R3. Should we close this out?

Alternatively, maybe we can review with @freitagb since part of this speaks to the longer term vision of the product. What do you think?

@faustoperez
Copy link
Author

faustoperez commented Aug 8, 2024

I think both options are compatible.

I am linking the Figma with the exploration work we did a few weeks ago for future reference 👉 https://www.figma.com/design/tcCUA06Knwq7nA9DUOlplo/US-GHG-Center-test-file?node-id=50-480&t=NVZ0Nn7FPw46DbOa-1 and invited @freitagb

I'll close the ticket for now 🙂

hanbyul-here added a commit that referenced this issue Oct 30, 2024
…mpty (#1218)

**Related Ticket:** #1028 

### Description of Changes
- It turns out that there are datasets (such as globalscope bluetarp)
that should not have any titiler parameters.
Bluetarp data from stac backend:
https://staging.openveda.cloud/api/stac/collections/blue-tarp-planetscope

### Notes & Questions About Changes
This makes me wonder about if we can validate anything about render
parameters - ex. When there is no render parameter at all from stac
back-end points, is there any way to be sure that this dataset is meant
to be without render parameters ? - Tagging @smohiudd for this question.

### Testing
Test this branch with veda-config's globalscope bluetarp dataset.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants