Associations, but for Events

Even events of these types are hierarchical — because each event is a sub-event of the divorce. Even if events occur in parallel, they still belong to the overarching context. For example:

“The Divorce” – Hierarchical Breakdown:

  • Initial misbehaviors (if blame is relevant)

  • Partner one blames partner two

  • Partner two hits partner one with a frying pan

  • Partner one gets angry

  • Moving out

  • Court appearances

    • Time together in court

    • Time partner one is in court

    • Time partner two is in court

  • Retrieving remaining belongings (whoever moved out last)

Just because something happens in parallel in life doesn’t mean it can’t be placed into a hierarchy. That said, I agree — it’s extremely useful for both fiction-based and historical events to be connectable via named, directional or non-directional relationships.

I actually do this in Obsidian using the wiki-link system.
For example: If two ships sail from the same port on the same date, they’re linked via the port and date.
That also links them to the sailors who went ashore during that timeframe — until proven otherwise. So every link or relationship should carry a citation and classification: proven, not proven, unproven, etc.

To be honest, this is Network Graph and advanced Gantt Chart territory.
That’s why I primarily use Obsidian, Foam for VS Code, and Aeon Timeline for research — alongside Gramps.
These tools help visualize complex interconnections, even though many of them could technically be modeled as relationships in Gramps notes.

Two events happening in parallel can still be sub-events of a shared parent — for example, the lifespan of an object.
But it’s not always necessary to link every event. Sometimes the connection is a person, a place, an object, or another entity.

If two parallel events are both connected to the same object, they’re sub-events of a broader context — with the object’s lifespan as the top-level container.
That said, this isn’t always a practical way to think. That’s why timelines and network graphs are essential research tools.

In genealogy, everything is hierarchical in some way — the shape of that hierarchy depends entirely on the observer’s perspective.

I just posted a few print screens of my Zotero and Obsidian structure as a comment in another post:


I’ve used TiddlyWiki in the past, but the single-HTML-file format didn’t scale well for large projects. I’ve also tried Twine, Causality, Freeplane, Scapple, Scrivener, yWriter, and Segrada — but ultimately landed on Obsidian, Foam for VS Code and Aeon Timeline as my core tools.
I also have Zettlr and Joplin installed…

I always use software tools far beyond what they were originally designed for. Thinking creatively isn’t optional — it’s essential if you want to build robust, scalable solutions.
And sometimes, you just hope others see the value in your adaptations and consider integrating those features natively.


Note:
This post was originally drafted in Norwegian and refined with the help of Microsoft Copilot. The translation process included grammatical adjustments, restructuring for clarity, and stylistic polishing to improve flow and readability in English. The content remains true to the original intent, with all technical and conceptual details preserved.