Difference between revisions of "Usage-based Data Discovery - Episode 5"

From Earth Science Information Partners (ESIP)
Line 3: Line 3:
 
=Agenda=
 
=Agenda=
 
==What Do We Have So Far?==
 
==What Do We Have So Far?==
# Use Cases: lots
+
# Use Cases: [https://docs.google.com/presentation/d/1u1dvqEB0ZZmxRqKDPN4DrIu4f9_r6TfYAlcVUAJUtMM/edit?usp=sharing lots]
 
# Hackfest slots: 3
 
# Hackfest slots: 3
 
# People: some
 
# People: some
 +
 
==Hackfest Plan==
 
==Hackfest Plan==
 
===Types of Teams===
 
===Types of Teams===

Revision as of 12:58, June 18, 2020

Telecon Objective

Design the ESIP Summer Hackfest: Cooking with Graphs

Agenda

What Do We Have So Far?

  1. Use Cases: lots
  2. Hackfest slots: 3
  3. People: some

Hackfest Plan

Types of Teams

  1. Cooks: create an end to end application with graph database, relationship content, API, (UI)
  2. Menu Designers: design User Experience using one or more wireflow diagrams
  3. Foragers: find dataset-usage relationships underpinning the use cases
  4. Other?

Questions

  1. Local machines or ESIP AWS?
  2. One team per type, or multiple?
  3. Team "spirit guides"?
  4. Suggested use case for Implementation Team?
  5. Suggested use case(s) for UX team?
  6. Let discoverers explore whatever they want?
  7. Mise en Place (Provisioned ingredients)
    1. Some dataset-usage relationships for Implementation Team(s): how many? from whom? what format?
    2. Icons for wireflow designing: who to supply?
    3. Google Slides doc(s) for UX group: who to setup?
    4. AWS accounts?
    5. Or software packages for laptops?
    6. Others?

Prep Work

  1. Assemble and preposition ingredients: who? when?
  2. Team signup sheet?
  3. Know-before-you-go: who?
  4. Advertisement to community: who?
  5. Other?