2. Tell us about yourself: Who are you and how
did you come to be working with Graphs?
Question:
3. Can you give us some background about the
Problem you are trying to solve?
Salmon
Background
slide:
4. too much
~100,000 projects, people, places,.
too complicated
many dimensions, each diverse:
ecology, habitat, method, management,
analysis, sociology,.
too dynamic
churn, obsolescence, lags,.
too hidden
technical reports, web pages, Excel files,.
too isolated
important connections missing.
the problem
is information
13. the human ideas
in a decision process
are types of :Idea nodes
in a knowledge graph
14. experiments
2018
who is doing what?
2019
international salmon data laboratory
2020
prototype: decision support
2021
proof: program management
15. Management Use case:
Coordination of salmon projects
Visibility: Who is doing what, where,
when?
Coordination: How do projects align or
conflict with each other, with high level
metrics, with existing knowledge?
Effectiveness: Did we do what we set out
to do? How could we do it better?
24. Organizational Challenges
- New software = new training, IT management
- Information and data are siloed inside business
units
- Cultural, political and security barriers to
engagement and implementation
- Why should I use this?
25. Technical Challenges for Neo4j
- Thousands of node types
- Some nodes and linkages are stochastic
- Some parts of the data schema need to be discovered
by the crowd
- What are some similar graph analysis use-cases?
26. Next steps for Graphish 2.0
- Make user engagement part of the technical workflow
- Identify cross-cutting problems and high value network
analyses
- Let users interact with and structure the graph
- Make it accessible to people managing the current
Salmon crisis