Difference between revisions of "Usage-based Data Discovery - Episode 5"
From Earth Science Information Partners (ESIP)
Line 1: | Line 1: | ||
=Telecon Objective= | =Telecon Objective= | ||
− | Design the ESIP Summer Hackfest | + | Design the ESIP Summer Hackfest: Cooking with Graphs |
=Agenda= | =Agenda= | ||
==What Do We Have So Far?== | ==What Do We Have So Far?== | ||
Line 8: | Line 8: | ||
==Hackfest Plan== | ==Hackfest Plan== | ||
===Types of Teams=== | ===Types of Teams=== | ||
− | # | + | # Cooks: create an end to end application with graph database, relationship content, API, (UI) |
− | # User Experience | + | # Menu Designers: design User Experience using one or more [https://www.nngroup.com/articles/wireflows/ wireflow diagrams] |
− | # | + | # Foragers: find dataset-usage relationships underpinning the use cases |
# Other? | # Other? | ||
Revision as of 06:54, June 17, 2020
Telecon Objective
Design the ESIP Summer Hackfest: Cooking with Graphs
Agenda
What Do We Have So Far?
- Use Cases: lots
- Hackfest slots: 3
- People: some
Hackfest Plan
Types of Teams
- Cooks: create an end to end application with graph database, relationship content, API, (UI)
- Menu Designers: design User Experience using one or more wireflow diagrams
- Foragers: find dataset-usage relationships underpinning the use cases
- Other?
Questions
- Local machines or ESIP AWS?
- One team per type, or multiple?
- Team "spirit guides"?
- Suggested use case for Implementation Team?
- Suggested use case(s) for UX team?
- Let discoverers explore whatever they want?
- Mise en Place (Provisioned ingredients)
- Some dataset-usage relationships for Implementation Team(s): how many? from whom? what format?
- Icons for wireflow designing: who to supply?
- Google Slides doc(s) for UX group: who to setup?
- AWS accounts?
- Or software packages for laptops?
- Others?
Prep Work
- Assemble and preposition ingredients: who? when?
- Team signup sheet?
- Know-before-you-go: who?
- Advertisement to community: who?
- Other?