Like this one...would be very useful to me as well.
I'm trying to wrap my head around how this would work. Events need a start and a duration or end date in order to be displayed in the timeline. In the problem above, the unknown is just one date, that of Jon's departure from Paris. His arrival time in Tunisia gets derived from known information. My approach with the tool we currently have would be to create the following events with "straw man" or placeholder dates that mark the hard edges of your known information. * Jonathan in Paris * - give it a date range that ends on Dec 25th. * Jonathan Travels to Paris * - Make it based on (follows) completion of "Jonathan in Paris" and give it a 25-day duration. Colour code the event to signify that it has a soft date, maybe make it red so it stands out. * Battle for Tunisia *- Our next hard date of Mar 18th. It's a non-dependent event. Once you determine his actual departure date from Paris, update the first event. His travel event will automatically move and his arrival date in Tunisia will be apparent. You could refine this slightly by perhaps adding an event proper ty named "Soft Date". You could then flag fuzzy dates and filter views to highlight the dates you still haven't nailed down in your timeline. Whether the software manages to represent your fuzzy dates or you just flag an event as "fuzzy", does it not accomplish the same thing? It seems to me that fuzzy date logic would be a fairly big undertaking programmatically.
Hi, Both the ability to have more fuzzy dates and more complicated dependency systems is something we have had on our list to consider adding in the future, however it isn't on our immediate plans as yet. We do like to hear examples from people in how they would like this implemented though, as the exact detail we have not worked out yet. Jess
I'd like a fuzzy date method offering 4 possible events (similar to the now-moribund (?) SIMILE Timeline). These are best thought of as earliest/start/end/latest. The middle two represent the current status quo. The extensions could be plotted in a slightly dimmed or otherwise differentiate version of the main timeline maker for an event. If only earliest and latest dates were known (i.e. set for an event) the whole event icon/bar would be in the secondary form of render. Anywhere from 1 to all 4 of these event dates could be specified for an event. Not a 'must-have' but useful would be to toggle on/off display of the early/late portions of the event bar on the timeline (IOW, the full range or just start-end) Consider an activity, or an account on a system. It might be authorised on the 1st of March but not actually used until 15 March. Last activity might be 24 July and the account de-athorised 30 August. These 3 dates would in order the earliest/start/end/latest dates for this event. We can see the 'event' was definitely real (i.e. activity) took place 15 March-2 4 July but that there were periods both before and after that we might also need to consider. Such a feature would greatly aid visualising my research. Thanks for listening.
This sounds like a constraint satisfaction problem. Feature wise, it could be implemented as a scriptable Dependency layout algorithm where the user multi-selects several items and provides a set of predicate constraints. The algorithm would satisfice the constraints and assign the appropriate Start, End, Offset, and Dependency details. I think it would be useful as a “Apply Once” kind of tuning versus as some kind of dynamic forces field that would constantly be applied to the graph, snapping nodes to and fro as their properties changed.
Hi, You will be pleased to hear that the next version of Aeon Timeline will contain the ability to define earliest/latest start/end date for events. Jess