Start from the evidence chain your claim will need
Research data are not limited to the spreadsheet eventually submitted. A useful record can include original files, a codebook, cleaning decisions, analysis code, software details, parameters and access conditions. Some components may be public; others may require controlled access or may not be shareable at all. Transparency therefore means explaining both what is available and why a boundary exists.
The right entry point depends on the project. Interview research may prioritise consent language and disclosure risk. A simulation may need an environment record and random seed from the first run. Whichever route you take, avoid treating documentation as a narrative reconstructed from memory. Create small, dated records while the decisions are being made.
1. Govern the material before deciding to share it
Set responsibilities, storage locations, access and retention early. Consent for reuse is not interchangeable with consent to participate, and de-identification needs more than removing names. Once the shareable material is known, a licence and repository can be assessed against rights, sensitivity, disciplinary practice and the intended audience.
2. Give each research object a durable identity
A sound citation points to a particular dataset version rather than a project homepage. Creators, title, publisher or repository, year, version and persistent identifier work together. Metadata explain what the object contains and how it was produced. Software and code repositories require their own version-aware references because a moving branch cannot preserve the analytical state.
3. Record what happened between collection and result
Keep source material immutable and produce a distinct cleaned or transformed version. Each rule should explain why it was applied and which records changed. File names are useful labels, but they are not a complete version history. Spreadsheet work and statistical output also need inputs, formula or syntax evidence, manual actions and report destinations.
4. Make the analysis recoverable and understandable
A future reader needs the environment and parameters as well as the script. Record the software version, packages and any controlled randomness. Decide where analysis code belongs based on readability, size and access. Backups protect ongoing work, while a reproducibility package prepares the approved data, code, instructions and metadata for examination or reuse.
