MyLens

Renders historical events as an interactive, multi-dimensional graph where nodes represent events and edges represent causal/temporal relationships. The system likely uses a force-directed layout algorithm (e.g., D3.js or similar) to position events in 2D/3D space based on temporal distance and relationship strength, allowing users to pan, zoom, and filter by time period, theme, or actor. Events can be clustered hierarchically (by century, decade, or custom periods) and relationships are rendered as directional edges with semantic labels.

Allows users to define and visualize semantic relationships between events (causality, influence, opposition, simultaneity) beyond simple chronological ordering. The system likely maintains a relationship graph where each edge has a type (e.g., 'caused', 'influenced', 'opposed', 'concurrent') and optional metadata (confidence, source citation). Relationships are bidirectional and can be queried to trace causal chains or identify thematic clusters. The UI probably provides a relationship picker or natural-language input that maps user intent to structured relationship types.

Uses natural language processing or AI to automatically extract events and dates from unstructured text (e.g., historical documents, Wikipedia articles, research papers). The system likely accepts text input or document uploads, parses the text to identify event mentions and temporal expressions, and suggests event entries with extracted dates, actors, and descriptions. Users can review and edit extracted events before adding them to the timeline. The system may also attempt to resolve ambiguous dates or fill in missing information based on historical knowledge.

Allows users to publish timelines publicly and discover timelines created by other users. The system likely maintains a public gallery or search interface where users can browse timelines by topic, time period, or creator. Published timelines can be viewed without requiring a user account (read-only access). The system probably supports social features like ratings, comments, or follows. Users can control sharing permissions (public, private, or shared with specific users) and track views/engagement metrics.

Allows users to create alternative timeline branches that explore 'what if' scenarios or counterfactual histories. The system likely maintains a base timeline and allows users to create branches that diverge at a specific point, with alternative events and outcomes. Users can compare branches to see how different choices or events would have led to different historical outcomes. The visualization probably shows branching points clearly and allows toggling between branches. This feature is useful for teaching causation and exploring historical contingency.

Provides multi-dimensional filtering of events by time period, geographic region, actor/person, theme/category, and custom tags. The system likely implements faceted search with aggregated counts (e.g., '15 events in 1789', '8 events involving Napoleon') and allows users to combine filters with AND/OR logic. Filtering is applied client-side or via server-side query optimization to update the visualization in real-time, highlighting matching events and dimming non-matching ones. Time-range sliders enable quick navigation across centuries or decades.

Enables multiple users to contribute events, relationships, and annotations to a shared timeline with version control and attribution. The system likely tracks who added/edited each event (with timestamps), allows comments or discussion threads on events, and may support approval workflows for academic rigor. Concurrent edits are probably handled via operational transformation or CRDT (conflict-free replicated data types) to avoid merge conflicts. Users can see real-time presence indicators and edit notifications.

Provides pre-built timeline templates for common historical narratives (e.g., 'American Revolution', 'Industrial Revolution', 'Ancient Rome') that users can instantiate and customize. Templates likely include pre-populated events, relationships, and metadata that serve as a starting point. The system probably supports importing timelines from CSV/JSON files or from public template repositories, with conflict resolution for duplicate events. Users can also save their own timelines as templates for reuse.

Allows users to export timelines in multiple formats (HTML, PDF, PNG/SVG, JSON) for sharing, publication, or archival. The system likely generates static HTML pages that can be embedded in websites or shared as standalone files, with options to include or exclude interactive features. PDF export probably renders the timeline as a visual document with event details and relationships. JSON export preserves full metadata for re-import or integration with other tools. Users can customize export appearance (colors, fonts, layout) and choose what metadata to include.

Enables users to attach rich annotations, citations, and source references to individual events. The system likely supports inline citations (with links to external sources), embedded images/documents, and structured metadata (e.g., confidence level, source type). Annotations may support markdown or rich text formatting. The system probably integrates with citation managers (Zotero, Mendeley) or supports standard citation formats (BibTeX, Chicago Manual of Style) for academic rigor. Users can view citation counts and track which sources are most frequently referenced.

Allows users to organize events into thematic clusters or narrative arcs (e.g., 'Political Upheaval', 'Technological Innovation', 'Cultural Movements') and visualize them as distinct storylines within the timeline. The system likely supports hierarchical grouping (themes > sub-themes > events) and can render multiple narrative threads in parallel, showing how different storylines intersect. Users can toggle themes on/off to focus on specific narratives. The visualization probably uses color-coding or spatial separation to distinguish themes.

Integrates geographic data with timeline visualization, allowing users to see events plotted on a map alongside the temporal axis. The system likely uses a map library (Leaflet, Mapbox, Google Maps) to render event locations and may support animated playback that shows events unfolding geographically over time. Users can filter events by region, zoom to specific areas, and see how events in different locations relate temporally. The visualization probably supports both modern and historical map layers (e.g., 1789 France vs. modern France).

Enables users to compare two or more timelines side-by-side to identify similarities, differences, and synchronicities. The system likely aligns timelines by date and highlights events that occurred simultaneously across different timelines. Users can synchronize scrolling/zooming across multiple timelines to maintain temporal alignment. The comparison view probably supports filtering to show only matching or divergent events. Users can merge timelines or create a composite view that combines events from multiple sources.