SLSepiaLog
Understand · SepiaLog feature

Dataset version history with notes attached to the right state

See every saved dataset state and reopen the data exactly as it was when a research note was written.

What does dataset version history preserve?

Dataset version history preserves recoverable states of research files over time. SepiaLog connects those states to the notes that explain meaningful changes, allowing a researcher to inspect the data as it existed at a specific decision point.

The research problem

A filename such as final_v3 says that something changed, but not what changed, why it changed or whether it produced the result used in a paper. Overwriting removes evidence; uncontrolled copies remove clarity.

SepiaLog timeline showing research notes and dataset versions
Genuine SepiaLog application view.

How the workflow works

  1. Work in the project folder as usual.
  2. Save a SepiaLog note after a meaningful change.
  3. Use the Timeline to inspect a version or open the data as it was when the note was created.

What SepiaLog provides

  • Built-in snapshots on every supported desktop system
  • Timeline grouped by day
  • Read-only inspection of historical file states
  • Optional Git and DataLad interoperability for advanced workflows

Common questions

Do I need Git to use version history?

No. Built-in snapshots work without Git. Git and DataLad are optional for advanced interoperability.

Does opening an old version overwrite current data?

No. Historical states are opened read-only so the live project remains untouched.

Can I branch from an older version?

Yes. A historical file state can be used as the source for a new derived dataset.