Skip to content
Skip to main content
Mobile Extractions Operational Explainer

How should I build a timeline from several applications?

Order relevant events on a common time basis while retaining every original timestamp, source, event meaning and uncertainty.

Normalise transparently

Select sources that answer the proposition rather than exporting every time. Record stored and displayed values, zone or offset, source path, clock issues and conversion rule. UTC is useful for ordering, but do not guess an unknown local zone; preserve the original and mark a range or uncertainty.

Do not flatten different events

Creation, submission, delivery, reading and notification are separate stages. Distinguish recorded events from analytical inference and avoid treating several parser views of one database event as independent corroboration. Keep a transformation column so corrected or converted values remain auditable.

Key takeaway

A defensible timeline shows how unlike systems and clocks were aligned without concealing source, meaning or precision.

Reference: MEX-016Mobile Extractions