How could a graph database structure be visualized and perceived by end users in a more helpful way than a large graph?
Chris Granger claims that showing more than 15-20 nodes at a time makes a graph view unmanageable.
Codex OS has proposed an autocomplete that prioritizes the relationships for browsing:
Expanding on that idea, I believe that, similar to Finder’s view of nested folders ( Miller Columns), we could let people traverse node–>edge–>node–>edge relationships with simple arrow commands. So in the above example, it might look like you select the Michaelangelo option and it shows you the relationship options from there, you select the relationship, then select a node from within there, and on…
Loose mockups below: