Interactive graph
Graph View Analytics
Table of Contents
Graph view analytics reads the link map for orphans, over-connected hubs, and forgotten gaps.
Key Concept
- Read the link map for orphans and over-linked hubs before they skew the garden.
- Graph is the live map; Issues is where you fix what the analytics flagged - not vanity link counts.
- Orphan notes and hub sprawl both signal a graph that needs pruning.
- The orphan list is a fix-this-week queue - not a pretty poster.
Level 1 - Recognize
Graph view analytics reads the link map for orphan notes and over-linked hubs before they skew the garden.
Level 2 - Explain
Like a city map showing dead streets and one overcrowded intersection - lonely pages and hubs everyone fights over.
Level 3 - Use
Open the graph view and fix orphan notes and overloaded hubs before they distort how you navigate the garden.
Level 4 - Connect
Orphans and over-linked hubs skew the whole garden - spot them early or maintenance chases symptoms instead of causes.
Level 5 - Create
Create a graph-health routine that turns orphan and hub counts into specific link repairs, then extend the checks when a new failure pattern appears.
Examples
- I laid out the shift-change chart and three tasks had zero arrows to an owner - the orphan list was my fix-this-week, not a pretty poster.
- Five notes in the graph had no inbound links - I linked three and archived two before closing the tab.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Maps of Content | when link counts beat a hand-curated index |
| extends | Linking by Meaning | Link-rank sorting shows which notes actually anchor the links you built |
| extends | Network Analysis | Graph metrics borrowed from network science |
