Turn a deposit receipt into a durable and understandable research record
A research data archive deposit confirmation can be an important milestone. Its English matters because deposited, registered, preserved, published, open, restricted and reusable are different states.
Why this English matters now
A research data archive deposit confirmation shows that a defined dataset or record entered a defined repository process.
Readers searching research data repository, archive deposit, data preservation or dataset DOI need to know whether files are merely submitted, actually preserved or publicly accessible.
Current NTU and NUS sources checked on 28 October 2026 show institution-specific deposit, registration, retention and access arrangements.
Clear English helps future researchers find the correct evidence without weakening participant privacy or contractual rights.
Checked against the official sources on 28 October 2026. The article explains how to read a document and make a safer next decision; it does not replace the issuing institution.
The reading method
Build an archive register with institution, project, dataset, creators, final-data definition, repository, external location, version, file manifest, checksum, metadata, documentation, software, rights, access class, embargo, DOI, submission, review, confirmation, exceptions, retention and later updates.
- Read from researcher, institution, repository, participant, collaborator, funder and future user perspectives.
- Keep deposit, registration, preservation, DOI assignment, publication and access separate.
- Use a policy-inventory-documentation-deposit-verification chain.
Read with every responsible person in view
- For researchers, deposit interpretable evidence rather than an unexplained folder.
- For repository and data teams, state exactly what custody and access the confirmation covers.
- For students and families, see archives as memory systems that protect honest learning.
Different people can read the same sentence for different jobs. The student needs the next action; the administrator needs a routable record; the family needs a realistic timeline; the eventual recipient needs evidence that fits its stated purpose. Good English keeps those needs aligned without inventing authority.
Official factual floor
These first-party sources support the factual claims and should be reopened for any live transaction:
- NTU Research Data Policy
- NUS Research Data Management
- NUS Libraries Research Support
- NUS Research Data Policies Guide
Did you know?
NTU’s policy separates repository deposit from sensitive-data storage and requires external deposits to be registered through the university route. A link can therefore be part of the institutional record even when the files live elsewhere.
Full chapter index
- 1. Authenticate the deposit confirmation
- 2. Distinguish deposit, registration and publication
- 3. Read the institution-specific rule
- 4. Define final research data
- 5. Separate preservation from backup
- 6. Read access conditions
- 7. Check metadata and identifiers
- 8. Handle sensitive and third-party data
- 9. Record integrity evidence
- 10. Plan long-term usability
- 11. Read the confirmation for exceptions
- 12. Build the archive evidence chain
What this part of the document is doing
Match institution, repository, project, dataset, creator, depositor, version, deposit identifier, date and access state. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A confirmation for a supplementary spreadsheet is filed as the complete project archive. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. open repository record
- 2. match dataset
- 3. match version
- 4. save confirmation
Put into one sentence, the sequence is to open repository record, match dataset, match version, and save confirmation. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Authentication supports research integrity. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
A repository deposit stores or registers material; publication, discoverability, DOI assignment and public access can be separate states. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A private deposit receipt is announced as a publicly reusable dataset. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. name deposit state
- 2. name access state
- 3. check DOI
- 4. check public record
Put into one sentence, the sequence is to name deposit state, name access state, check DOI, and check public record. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: State vocabulary supports digital literacy. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
NTU requires final research data in its repository and/or an external open repository under stated timing; NUS applies its own data policy and selected-project registration routes. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: An NTU deadline is copied into an NUS project without checking the governing policy. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. identify institution
- 2. identify project class
- 3. open current policy
- 4. record applicable deadline
Put into one sentence, the sequence is to identify institution, identify project class, open current policy, and record applicable deadline. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Policy comparison supports education. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Identify the data, code, documentation and evidence needed to validate the reported findings rather than depositing an arbitrary folder. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: Raw data are deposited without a codebook, units or processing history. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. map findings
- 2. identify supporting data
- 3. include documentation
- 4. record exclusions
Put into one sentence, the sequence is to map findings, identify supporting data, include documentation, and record exclusions. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Explanation supports science. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
A preservation repository manages durable custody, integrity and retrieval; an ordinary backup mainly supports recovery from loss. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A laptop backup is described as the institutional archive. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. identify preservation owner
- 2. check integrity controls
- 3. check retrieval
- 4. check retention
Put into one sentence, the sequence is to identify preservation owner, check integrity controls, check retrieval, and check retention. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Systems thinking supports computing. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Open, mediated, restricted, embargoed and closed access require different requests, protections and reuse expectations. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A repository landing page is treated as permission to download restricted human-subject data. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. read access label
- 2. read request route
- 3. check ethics and agreements
- 4. record decision
Put into one sentence, the sequence is to read access label, read request route, check ethics and agreements, and record decision. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Privacy literacy supports research. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Titles, creators, dates, funders, methods, variable descriptions, licences and persistent identifiers help people find and interpret the correct version. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: Two deposits share the same title and no version label. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. use precise title
- 2. record creators
- 3. record version
- 4. verify identifier
Put into one sentence, the sequence is to use precise title, record creators, record version, and verify identifier. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Vocabulary supports knowledge work. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Personal data, confidential information, licensed datasets and partner material may need secure storage, restricted metadata or a different repository. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A third-party dataset is uploaded because it was used in the analysis. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. classify data
- 2. check rights
- 3. choose secure route
- 4. document exclusions
Put into one sentence, the sequence is to classify data, check rights, choose secure route, and document exclusions. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Rights language supports digital citizenship. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Checksums, fixity checks, file formats, manifests and version history can show whether archived files remain unchanged and complete. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A new file silently replaces the deposited dataset under the same description. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. create manifest
- 2. record checksum
- 3. version changes
- 4. retain prior state
Put into one sentence, the sequence is to create manifest, record checksum, version changes, and retain prior state. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Evidence supports data careers. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Prefer sustainable formats, explanatory documentation, software notes and migration plans where the policy or repository supports them. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: A proprietary analysis file is deposited without software or export. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. identify format
- 2. include open export
- 3. document software
- 4. test retrieval
Put into one sentence, the sequence is to identify format, include open export, document software, and test retrieval. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Future-oriented writing supports learning. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Deposits can remain under review, require metadata correction, omit large files or link to an external repository. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: An accepted metadata record is treated as custody of every file. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. read status
- 2. list exceptions
- 3. follow external links
- 4. close outstanding tasks
Put into one sentence, the sequence is to read status, list exceptions, follow external links, and close outstanding tasks. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Qualifier reading supports accuracy. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
What this part of the document is doing
Keep policy, DMP, inventory, rights review, repository submission, confirmation, identifier, access decision, integrity evidence and later updates. This is where English becomes practical: the noun names the record, the verb names the state, the date fixes the version, and the qualifying phrase limits what the reader may safely conclude. Read those pieces together. If one is missing, mark the gap instead of filling it with hope, habit or a friend’s experience.
The useful question is not merely “What does this word mean?” It is “What action does this sentence authorise, who owns that action, and what evidence would show that the state has changed?” That question turns reading into a decision tool. It also prevents a heading, notification preview or informal summary from replacing the complete operative sentence.
A realistic situation
Example: The team has a DOI but cannot show which files or rights it represents. The risk here is not a lack of intelligence. It is a state-reading error: a nearby fact is allowed to stand in for the exact fact the process needs. A calm reader goes back to the named record, matches the person, programme or transaction, and keeps the decision inside the document’s real scope.
- 1. archive authority
- 2. archive manifest
- 3. archive confirmation
- 4. archive updates
Put into one sentence, the sequence is to archive authority, archive manifest, archive confirmation, and archive updates. Doing this aloud is helpful because it exposes hidden assumptions. A student, parent or adviser can then compare the spoken summary with the official wording. If the summary sounds stronger than the source, revise the summary—not the source.
Keep a small evidence note beside the action: document title, issuer, issue date, current status, deadline, responsible office and unresolved question. This takes less than a minute and prevents screenshots, tabs and forwarded messages from becoming an unstructured pile. The note also makes a later enquiry more precise and easier for the receiving office to route.
Transfer: Records management supports public trust. The same habit works in school notices, examination instructions, applications and employment records: authenticate, classify, sequence, act, and retain proof. That is why this form of English learning travels well beyond one document.
Evidence examples: what the wording can and cannot prove
Label and operative sentence
Use a heading to locate the archive deposit confirmation, then read the whole sentence that controls the decision.
Check: Navigation words help; complete clauses decide.
Current source and saved evidence
Keep a dated copy, but reopen the official source before a live deadline.
Check: An authentic record can still be out of date.
Requirement and recommendation
Preserve must, should, may, encouraged and recommended.
Check: Modal verbs change responsibility.
Interim and final state
Record an interim state without expanding it into a promise.
Check: Evidence is reliable only within its stated scope.
Practice studio
State ladder
Sort submitted, deposited, reviewed, published and open.
- state
- owner
- identifier
- evidence
Manifest check
Match files, versions and checksums.
- filename
- format
- checksum
- documentation
Access rehearsal
Test how an authorised future user finds and understands the record.
- landing page
- request route
- metadata
- restriction
Advice for students, families and advisers
For researchers
- Deposit documentation, code and context needed to interpret final data.
- Check rights before depositing third-party or sensitive material.
For repository teams
- Record exceptions, linked external deposits and pending corrections.
- Test retrieval and integrity rather than counting files alone.
For students and families
- Practise distinguishing preservation from public sharing.
- Treat metadata as a map that makes evidence usable.
Frequently asked questions
Is a deposit the same as publication?
No.
Does a DOI mean the files are open?
Not necessarily.
Is a backup an archive?
Not by itself.
Do NTU and NUS use identical rules?
No; use the applicable institutional policy.
Can sensitive data be archived?
Yes, through an authorised secure and appropriately restricted route.
Can third-party data be redistributed?
Only when rights permit.
Why use checksums?
They help detect file changes.
Can an external repository satisfy an institutional route?
It may, when the applicable policy and registration requirements are met.
What should be saved?
Policy, manifest, metadata, rights review, confirmation and later updates.
Why English?
Because deposited, preserved, published and open are different claims.
Useful next reading
- Research Data Destruction Certificate — how authorised disposal differs from preservation
- Research Data Management Plan — how archival and access decisions are planned before collection
Closing thought
A useful archive does more than keep files. It keeps meaning: the right version, enough context, a truthful access route and an evidence trail that lets future readers understand what the data can—and cannot—show.