# The Look of Spine* ## Approaches for a Re-Design
[Ole Mussmann](mailto:o.mussmann@esciencecenter.nl) | [Suvayu Ali](mailto:s.ali@esciencecenter.nl)
=== # Planning ? --- ## 0. Identify User Groups 👩🏼👨🏾🧑🏽‍🦳🧑🏻 **Who is using Spine Tools?** - Beginners, Professionals, etc. - What are their goals? - How do Spine Tools support their workflow? - How do Spine Tools fail to support their workflow? --- ## 1. Requirements Research 🧐 - Collect pain points, wishlists and dreams - Performance boundaries: minimal/ideal - Listen to user feedback - But also: watch people use Spine Tools - Create and analyze user videos --- ## 1.1 Example: Network Graph of the Spine Model 🕸️
- Do we need different views? - GIS? - Logical arrangement? - Algorithm to reduce edge cross-overs? - Layout persistance? Sharing? - Is that needed with "good" views?
--- ## 2. Create User Requirements 📝
"As a user I would like to ...
so that I can ..."
- Requirements based on user _needs_ - ... which might be different than user _desires_

  • 🙏 Arranging nodes and edges takes a lot of time, I'd like to be able to save views to save time in the future
  • 💡 Working with large network graphs should be better facilitated by Spine Toolbox, see Smarter Network Graphs
--- ## 3. Invent Possible Solutions 💡 - Create solutions to user needs - Keep feasability in mind --- ## 4. Proof of Concept 🛠️ - Create proof of concepts - Test and discuss with users - Which frameworks are in scope? - Are we aiming for decoupling frontend and backend? - Can we fulfil Antti's dream? 🌈🦄 - Do we need a web GUI? === # Smarter Network Graphs 🍬 Eye candy! 🍭 --- ## GIS Layer
https://energytransition.gitbook.io/esdl/
--- ## Repelling Nodes
https://github.com/eisman/neo4jd3
--- ## Hierarchical Edge Bundling
https://vega.github.io/vega/examples/edge-bundling/
--- ## Edge Crossover Avoidance