Time: That what keeps everything from occurring at once

 MK captures events in a unique way. Since events can reference all people, places, sources, notes, organizations, tasks, projects, objects, vehicles, and alliances that are associated with the event, Memory Keeper is able to produce some interesting views. This may force you to research deeper into an event.

Ideally, events captured have a date, maybe a time, a place, and one or more people associated with the event. However, all other things are not mandatory. Maybe the event does not have a person assigned to it. A weather event might be a good example. In this case, I might identify the path of the weather event along with the start and end date/timestamp. For those who lived through the weather event, I could associate those individuals. However, this would suggest those people were also along the entire path of the event. Alternately, create a dedicated event specific to the individual(s).

My father experienced Hurricane Hazel in 1954. He provided me some of the details from his point of view. So, I created an event specific to him, with his location and date. MK allows me to associate that event with a parent event, the event about the entire weather event.

These nested events can be as complex as you’d like. Another example: I have ancestors who were killed in certain War of 1812 battles. In those cases, I create a death event for the person and associate that event with the battle event. That battle event is an event to the parent event of the War of 1812. This will generate some interesting timelines that are also nested.

The screenshot below shows the 8th event in the War of 1812 as the Battle of Thames, providing a control that can be clicked to open an embedded timeline within this battle.

MK supports custom timelines. Users can write custom filters to generate unique timelines. Timelines can also be produced to show the duration of organizations and when individuals were members of those organizations.

Expanding the embedded events generates an embedded timeline.

The embedded 9th event shows another aspect of MK events. This event is a death event. Like most vital events there can only be one name, unless, of course, multiple individuals died during this same event. However, I typically create multiple death events for each individual. This 8th event, the death of Tecumseh has a second person associated with it. In this case, we know this is not the individual who died. Rather this other person, "Richard Mentor Johnson", has a defined role in the event. I have identified him as the assailant. 

MK allows users to define roles to be used for their specific events. Users can define roles, such as doctors for births and medical events, pallbearers for burial events, and officiants and bridesmaids for marriage events.

Recommendation: do not stop at the typical attributes of an event. Do more research and capture what happened and who was present.