Data Analytic Investments
RIPPLE book coverRIPPLE — the book·numbered first edition·$29Buy now
Regulation

Research data files: a timestamp before the analysis

For students and researchers: why to record a raw data file before analysing it, how to version cleaned data and analysis plans, and what a public timestamp adds to good data practice. Informational content.

D
Data Analytic Investments
••2 min read
Research data files: a timestamp before the analysis

In research, the order of events matters: the data was collected, then the plan was written, then the analysis was run. Good practice keeps a record of each step. A public timestamp is one simple way to record which file existed when.

Three files worth recording

  • The raw data file — exactly as it came from the survey, the instrument or the export, before any cleaning.
  • The analysis plan — the questions and methods you decided on, before seeing the results.
  • The cleaned dataset — the version the analysis actually used.

Step by step

  1. Keep the raw file read-only. Make a copy for cleaning; never edit the original.
  2. Name every version with a date and a short description: for example 2026-10-17_survey_raw.csv, 2026-10-20_survey_clean_v1.csv.
  3. Timestamp the raw file at DAS Proof on the day you receive it. The fingerprint is calculated in your browser; the data itself does not leave your device — useful when the data is confidential.
  4. Write the analysis plan, export it to PDF and timestamp it before you run the analysis.
  5. Timestamp each cleaned version that feeds into results.
  6. Keep a data log: file name, date, what changed, transaction reference.

What the timestamp adds — and what it does not

The record shows that a file with exactly this fingerprint existed no later than a given moment. It says nothing about whether the data is correct, complete or ethically collected; that remains the researcher's responsibility and the subject of your institution's rules.

The fingerprint comes from a hash function in the Secure Hash Standard (FIPS 180-4, NIST). Changing even one value in a CSV file produces a different fingerprint.

DAS Proof writes a file's fingerprint (SHA-256) into a public XRP Ledger transaction; the file itself never leaves your device. The timestamp shows the file existed in exactly this form no later than a given moment — it does not establish authorship or ownership. Anyone can verify it, free: dataanalyticsystem.com/proof/verify

Related: What is a hash: a file fingerprint in 5 minutes · How we write a file fingerprint to the XRP Ledger · DAS Proof

Informational content. Not legal advice.

Explore Topics

#DAS Proof#research#data#versions
D

Written by

Data Analytic Investments

Content creator and writer sharing insights and stories.

Share · Megosztás:XFacebookLinkedInWhatsAppTelegramE-mail