Turn an urgent removal concern into a request a repository can assess
A research repository takedown request connects a deposited object, landing page, persistent identifier, files, rights or harm concern, requestor, evidence, urgency, interim restriction, repository policy and durable scholarly record. English matters because “correct metadata”, “replace a file”, “restrict access”, “withdraw a record”, “delete a record”, “retract a publication” and “revoke a DOI” are not interchangeable. This guide helps a depositor or affected person request a proportionate repository action. It does not decide the legal merits or guarantee deletion.
Choose the route closest to your task, or read straight through for the complete system.
People search for repository takedown request, remove dataset from repository, delete Zenodo record and withdraw DOI because exposed personal data, confidential material, copyright concerns or serious errors can demand urgent action.
A usable request identifies the repository, record and persistent identifier, exact affected files or fields, issue category, concrete harm or rights basis, requestor relationship, evidence, discovery time, urgency, requested interim and final actions, acceptable contact route and confirmation needed.
Clear English helps a repository act quickly without destroying more of the record than necessary. “Delete everything now” may be less useful than “temporarily restrict file A immediately because it contains identifiable participant names on pages 4–6 while the repository reviews permanent withdrawal.”
This guide was checked on 14 October 2026. Repository policies, laws, contracts, publisher rules and persistent-identifier systems differ. Use the repository’s current support or abuse route, minimise further exposure, and seek authorised legal, ethics or information-security advice where needed.
Did You Know? The Zenodo general policies, checked on 14 October 2026, say that an exceptionally withdrawn research object is replaced by a tombstone explaining the reason while the original DOI and URL are retained. The useful discovery is that removing public access to files may preserve enough of the scholarly record for citations and provenance to remain intelligible.
Find the section you need
Stabilise the risk · 2 chapters
Identify the object · 2 chapters
State the basis · 2 chapters
Request an action · 2 chapters
Preserve accountability · 3 chapters
1. Use the repository’s authorised reporting route
Back to contentsA public comment, social post or copied email can spread the very material the request seeks to contain.
Find the repository’s current support, takedown, privacy, security or abuse route and use its secure evidence channel.
A reporter sends the record URL and affected filenames without attaching the exposed personal-data file to a general inbox.
What to check
- Find route
- Check security
- Minimise copies
- Keep ticket
Apply this chapter to a public file containing direct identifiers. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Do not publish sensitive evidence to prove that sensitive evidence is public.
Learning transfer: Secure reporting supports cyber incidents.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
A title may appear in several repositories, mirrors, indexes and versions with different owners.
Record repository, landing-page URL, persistent identifier, version, depositor, publication date and access state.
The request names the specific Zenodo version and DOI rather than a search-result screenshot.
What to check
- Name repository
- Copy identifier
- Name version
- Check access
Apply this chapter to a copyright concern affecting one image. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: A takedown at one host may not remove authorised or cached copies elsewhere.
Learning transfer: Source identification supports copyright.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Repository staff need to know whether the concern affects metadata, one file, several pages, the whole object or linked supplementary material.
List filenames, page or row ranges, fields, checksums where useful and a safe description of the problem.
The request identifies names in rows 17–43 of one data file without repeating those names in the email.
What to check
- Name file
- Name location
- Describe safely
- Check links
Apply this chapter to a serious error requiring withdrawal rather than correction. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Broad labels such as “private information” can delay action when the exact location is safely knowable.
Learning transfer: Precision reporting supports quality assurance.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
4. Classify the concern without overstating authority
Back to contentsPrivacy exposure, confidentiality breach, copyright, malicious content, research-integrity error and personal preference may lead to different reviews.
State observable facts, the relevant policy or agreement, your interpretation and the authorised decision you seek.
A participant identifies consent-limited material and attaches the relevant approved information sheet through a secure channel.
What to check
- State fact
- Name basis
- Mark interpretation
- Request review
Apply this chapter to a record whose DOI must remain interpretable. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Calling something “illegal” is not a substitute for identifying the law, right or authorised advice.
Learning transfer: Claim discipline supports complaints.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Depositors, authors, rights holders, participants, employers and third parties may have different evidence and authority.
State your role, contact details, relationship, whether the original depositor is available and any conflict or safety reason not to contact them first.
A rights holder provides a clear ownership connection while a participant uses the privacy route.
What to check
- Name role
- Explain link
- Name owner
- Protect safety
Apply this chapter to a public file containing direct identifiers. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Being named in a record does not automatically grant power over every part of the deposited object.
Learning transfer: Role clarity supports governance.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Repositories can prioritise better when they know what is exposed, who can access it, how it can spread and which deadline matters.
Write discovery time, current access, sensitivity, likely affected people, active misuse if known and the narrowest immediate protective action.
A live dataset with direct identifiers receives an immediate restriction request while the full review continues.
What to check
- Write discovery
- Describe access
- Name harm
- Ask interim action
Apply this chapter to a copyright concern affecting one image. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Urgent language should not hide uncertainty or claim confirmed misuse without evidence.
Learning transfer: Risk communication supports safeguarding.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
Correction, restriction, file replacement, new version, withdrawal and deletion preserve different amounts of access and history.
State the requested interim and final outcome, explain why a narrower action is insufficient and invite the repository to apply its policy.
The request seeks temporary file restriction now and formal withdrawal if consent breach is confirmed.
What to check
- Name interim
- Name final
- Explain fit
- Allow policy review
Apply this chapter to a serious error requiring withdrawal rather than correction. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Do not ask for silent history rewriting when users need to know that a cited object changed.
Learning transfer: Proportionality supports records management.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
8. Anticipate persistent identifiers and tombstones
Back to contentsA DOI or handle is designed to persist, so withdrawn content may leave a landing page, citation and reason rather than vanish.
Ask what will remain visible, how the record will resolve, whether metadata changes, and how versions or related identifiers will be marked.
A withdrawn dataset DOI resolves to a tombstone explaining that files are no longer available.
What to check
- Check DOI
- Check landing page
- Check reason
- Check relations
Apply this chapter to a record whose DOI must remain interpretable. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: A persistent identifier should not be described as erased when the system keeps it resolvable.
Learning transfer: Persistence literacy supports academic citation.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
9. Provide evidence without increasing exposure
Back to contentsContracts, consent forms, licences, correspondence or screenshots may support a request but can also contain personal or confidential data.
Send the minimum necessary through the approved secure channel, label each item and explain the relevant clause or fact.
A redacted permission agreement shows the missing right while unrelated commercial terms stay hidden.
What to check
- Minimise evidence
- Label source
- Use secure route
- Explain relevance
Apply this chapter to a public file containing direct identifiers. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: An enormous evidence dump can obscure the issue and create a second data-management problem.
Learning transfer: Evidence selection supports audits.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
10. Coordinate necessary downstream action
Back to contentsRepository withdrawal may not automatically update DOI metadata, search indexes, mirrors, project pages, publications or people who downloaded the files.
Ask which systems the repository controls, identify high-risk downstream locations and assign lawful notices without promising global erasure.
The project page and repository record are updated while external index refreshes are monitored.
What to check
- Map systems
- Name owner
- Send notice
- Track refresh
Apply this chapter to a copyright concern affecting one image. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Do not send threatening mass notices before the facts and authorised route are established.
Learning transfer: Coordination supports incident response.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
11. Close the request with a verifiable outcome
Back to contentsA support reply is not completion unless access, landing page, identifier state and affected versions match the decision.
Read the record in a logged-out view, retain the decision and ticket, confirm downstream tasks and record any review or appeal route.
The requester verifies that files are restricted and the tombstone accurately identifies withdrawal without exposing the sensitive reason.
What to check
- Test access
- Check tombstone
- Keep decision
- Track appeal
Apply this chapter to a serious error requiring withdrawal rather than correction. Write the purpose, reader, verified facts, uncertainty, boundary and next action before polishing the language.
Create an ordinary case, a difficult case and a missing-information case. Preserve the governing meaning while changing detail, tone and support for the situation.
Ask an independent reader or listener to explain what they understood, what they would do next and where they hesitated. Revise, keep the evidence and compare both versions.
Boundary: Avoid repeatedly opening or downloading harmful content merely to check that it has been removed.
Learning transfer: Closure verification supports service recovery.
Write one sentence that states the evidence, one that states its limit, and one that states the next responsible action. Then test each noun, number, condition and source against the current task and verified source. Replace vague confidence with a traceable reason.
How to build this kind of English before the job title arrives
Back to contentsStudents do not need professional authority to practise the underlying language. They can learn to define scope, annotate conditions, compare versions, rebuild a timeline, match a number to its unit and explain uncertainty without embarrassment. Parents can ask calm questions: What decision is this document supporting? Which sentence carries the strongest claim? What would make that claim false? Which source would you open next?
Use a three-pass routine. First, map the document: title, owner, audience, date, sections and decision. Second, trace one claim from source to conclusion. Third, explain the limit and next action. This routine strengthens comprehension, science, mathematics, humanities and workplace readiness because it turns English into an evidence tool.
A student should never imitate professional authority. The useful goal is to recognise when a text needs a qualified reviewer, current rule or official decision. Knowing when to pause is part of literacy.
From exposed participant names to a controlled repository decision
Back to contentsRecord
Landing page, DOI, version and one affected data file identified.
Risk
Direct identifiers in a public file; no need to reproduce them in the request.
Interim
Immediate file restriction requested through the privacy route.
Final
Repository review asked to decide withdrawal and tombstone wording.
Verification
Logged-out access, DOI resolution and downstream notices checked.
Repository
Host and authorised route.
Record
Title, URL and identifier.
Version
Exact deposit state.
Material
Files, pages, rows or fields.
Concern
Privacy, rights, integrity or safety.
Requestor
Role and relationship.
Evidence
Minimum supporting material.
Discovery
Date, time and current access.
Urgency
Concrete harm and affected people.
Interim
Restriction or quarantine request.
Final
Correction, replacement, withdrawal or deletion.
Confirmation
Ticket, decision, tombstone and verification.
Use this roadmap to see how the chapters connect. Each decision names a purpose, action, observable example and limit.
1. Use the repository’s authorised reporting route
A public comment, social post or copied email can spread the very material the request seeks to contain. The practical move is to find the repository’s current support, takedown, privacy, security or abuse route and use its secure evidence channel.
Test the chapter through this example: A reporter sends the record URL and affected filenames without attaching the exposed personal-data file to a general inbox. Keep the boundary visible: Do not publish sensitive evidence to prove that sensitive evidence is public.
2. Identify the canonical record and version
A title may appear in several repositories, mirrors, indexes and versions with different owners. The practical move is to record repository, landing-page URL, persistent identifier, version, depositor, publication date and access state.
Test the chapter through this example: The request names the specific Zenodo version and DOI rather than a search-result screenshot. Keep the boundary visible: A takedown at one host may not remove authorised or cached copies elsewhere.
3. Point to the minimum affected material
Repository staff need to know whether the concern affects metadata, one file, several pages, the whole object or linked supplementary material. The practical move is to list filenames, page or row ranges, fields, checksums where useful and a safe description of the problem.
Test the chapter through this example: The request identifies names in rows 17–43 of one data file without repeating those names in the email. Keep the boundary visible: Broad labels such as “private information” can delay action when the exact location is safely knowable.
4. Classify the concern without overstating authority
Privacy exposure, confidentiality breach, copyright, malicious content, research-integrity error and personal preference may lead to different reviews. The practical move is to state observable facts, the relevant policy or agreement, your interpretation and the authorised decision you seek.
Test the chapter through this example: A participant identifies consent-limited material and attaches the relevant approved information sheet through a secure channel. Keep the boundary visible: Calling something “illegal” is not a substitute for identifying the law, right or authorised advice.
5. Explain your relationship to the record
Depositors, authors, rights holders, participants, employers and third parties may have different evidence and authority. The practical move is to state your role, contact details, relationship, whether the original depositor is available and any conflict or safety reason not to contact them first.
Test the chapter through this example: A rights holder provides a clear ownership connection while a participant uses the privacy route. Keep the boundary visible: Being named in a record does not automatically grant power over every part of the deposited object.
6. Describe urgency through concrete harm
Repositories can prioritise better when they know what is exposed, who can access it, how it can spread and which deadline matters. The practical move is to write discovery time, current access, sensitivity, likely affected people, active misuse if known and the narrowest immediate protective action.
Test the chapter through this example: A live dataset with direct identifiers receives an immediate restriction request while the full review continues. Keep the boundary visible: Urgent language should not hide uncertainty or claim confirmed misuse without evidence.
7. Choose the least misleading effective action
Correction, restriction, file replacement, new version, withdrawal and deletion preserve different amounts of access and history. The practical move is to state the requested interim and final outcome, explain why a narrower action is insufficient and invite the repository to apply its policy.
Test the chapter through this example: The request seeks temporary file restriction now and formal withdrawal if consent breach is confirmed. Keep the boundary visible: Do not ask for silent history rewriting when users need to know that a cited object changed.
8. Anticipate persistent identifiers and tombstones
A DOI or handle is designed to persist, so withdrawn content may leave a landing page, citation and reason rather than vanish. The practical move is to ask what will remain visible, how the record will resolve, whether metadata changes, and how versions or related identifiers will be marked.
Test the chapter through this example: A withdrawn dataset DOI resolves to a tombstone explaining that files are no longer available. Keep the boundary visible: A persistent identifier should not be described as erased when the system keeps it resolvable.
9. Provide evidence without increasing exposure
Contracts, consent forms, licences, correspondence or screenshots may support a request but can also contain personal or confidential data. The practical move is to send the minimum necessary through the approved secure channel, label each item and explain the relevant clause or fact.
Test the chapter through this example: A redacted permission agreement shows the missing right while unrelated commercial terms stay hidden. Keep the boundary visible: An enormous evidence dump can obscure the issue and create a second data-management problem.
10. Coordinate necessary downstream action
Repository withdrawal may not automatically update DOI metadata, search indexes, mirrors, project pages, publications or people who downloaded the files. The practical move is to ask which systems the repository controls, identify high-risk downstream locations and assign lawful notices without promising global erasure.
Test the chapter through this example: The project page and repository record are updated while external index refreshes are monitored. Keep the boundary visible: Do not send threatening mass notices before the facts and authorised route are established.
11. Close the request with a verifiable outcome
A support reply is not completion unless access, landing page, identifier state and affected versions match the decision. The practical move is to read the record in a logged-out view, retain the decision and ticket, confirm downstream tasks and record any review or appeal route.
Test the chapter through this example: The requester verifies that files are restricted and the tombstone accurately identifies withdrawal without exposing the sensitive reason. Keep the boundary visible: Avoid repeatedly opening or downloading harmful content merely to check that it has been removed.
The completed route should let another person reconstruct what the communication is for, what evidence supports it, what remains uncertain and what happens next.
Each case asks the learner to compare a quick response with a version another person can use.
Case 1: Use the repository’s authorised reporting route
Start with the worked situation: A reporter sends the record URL and affected filenames without attaching the exposed personal-data file to a general inbox. Write the tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: Find the repository’s current support, takedown, privacy, security or abuse route and use its secure evidence channel. Finish by stating why this boundary matters: Do not publish sensitive evidence to prove that sensitive evidence is public.
Case 2: Classify the concern without overstating authority
Start with the worked situation: A participant identifies consent-limited material and attaches the relevant approved information sheet through a secure channel. Write the tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: State observable facts, the relevant policy or agreement, your interpretation and the authorised decision you seek. Finish by stating why this boundary matters: Calling something “illegal” is not a substitute for identifying the law, right or authorised advice.
Case 3: Choose the least misleading effective action
Start with the worked situation: The request seeks temporary file restriction now and formal withdrawal if consent breach is confirmed. Write the tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: State the requested interim and final outcome, explain why a narrower action is insufficient and invite the repository to apply its policy. Finish by stating why this boundary matters: Do not ask for silent history rewriting when users need to know that a cited object changed.
Case 4: Coordinate necessary downstream action
Start with the worked situation: The project page and repository record are updated while external index refreshes are monitored. Write the tempting shortcut, then mark the missing reader need, condition, source, authority or next action.
Repair the communication by applying this method: Ask which systems the repository controls, identify high-risk downstream locations and assign lawful notices without promising global erasure. Finish by stating why this boundary matters: Do not send threatening mass notices before the facts and authorised route are established.
A parent, tutor, teacher or colleague can ask questions, but the learner should make the final revision in their own words and keep evidence of what changed.
Clear English is reliable when the reader can see not only what the sentence says, but also where it stops.
Boundary 1: Point to the minimum affected material
Repository staff need to know whether the concern affects metadata, one file, several pages, the whole object or linked supplementary material. Identify an exception, missing fact, reader who may need another route and change that would force revision.
Apply the observable signal—The request identifies names in rows 17–43 of one data file without repeating those names in the email.—and underline the words carrying scope, time, permission, comparison or uncertainty. Broad labels such as “private information” can delay action when the exact location is safely knowable.
Boundary 2: Describe urgency through concrete harm
Repositories can prioritise better when they know what is exposed, who can access it, how it can spread and which deadline matters. Identify an exception, missing fact, reader who may need another route and change that would force revision.
Apply the observable signal—A live dataset with direct identifiers receives an immediate restriction request while the full review continues.—and underline the words carrying scope, time, permission, comparison or uncertainty. Urgent language should not hide uncertainty or claim confirmed misuse without evidence.
Boundary 3: Provide evidence without increasing exposure
Contracts, consent forms, licences, correspondence or screenshots may support a request but can also contain personal or confidential data. Identify an exception, missing fact, reader who may need another route and change that would force revision.
Apply the observable signal—A redacted permission agreement shows the missing right while unrelated commercial terms stay hidden.—and underline the words carrying scope, time, permission, comparison or uncertainty. An enormous evidence dump can obscure the issue and create a second data-management problem.
Boundary 4: Close the request with a verifiable outcome
A support reply is not completion unless access, landing page, identifier state and affected versions match the decision. Identify an exception, missing fact, reader who may need another route and change that would force revision.
Apply the observable signal—The requester verifies that files are restricted and the tombstone accurately identifies withdrawal without exposing the sensitive reason.—and underline the words carrying scope, time, permission, comparison or uncertainty. Avoid repeatedly opening or downloading harmful content merely to check that it has been removed.
A bounded statement is useful because a reader can test it, ask a focused question and act without treating confidence as proof.
Audience adaptation changes emphasis, vocabulary and next steps; it does not authorise a different truth.
Learner
A public comment, social post or copied email can spread the very material the request seeks to contain. This person may need a different level of detail or next action.
Preserve find route, check security, minimise copies, keep ticket while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Teacher or adviser
Repository staff need to know whether the concern affects metadata, one file, several pages, the whole object or linked supplementary material. This person may need a different level of detail or next action.
Preserve name file, name location, describe safely, check links while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Parent or colleague
Depositors, authors, rights holders, participants, employers and third parties may have different evidence and authority. This person may need a different level of detail or next action.
Preserve name role, explain link, name owner, protect safety while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Authorised reviewer
Correction, restriction, file replacement, new version, withdrawal and deletion preserve different amounts of access and history. This person may need a different level of detail or next action.
Preserve name interim, name final, explain fit, allow policy review while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Future reader
Contracts, consent forms, licences, correspondence or screenshots may support a request but can also contain personal or confidential data. This person may need a different level of detail or next action.
Preserve minimise evidence, label source, use secure route, explain relevance while adapting examples and support. Do not change the underlying fact, decision or limit simply to make the short version easier.
Successful transfer preserves identity, source, status, uncertainty, boundary and responsible action while making the route easier for this reader to follow.
A polished paragraph or fluent conversation can still conceal an unclear purpose, missing condition, invisible assumption or stale source.
Purpose test
State in one sentence what the other person should understand, decide or do. Delete a detail only if its removal does not change that outcome or a necessary boundary.
Write the expected interpretation, the actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Condition test
Circle words such as if, unless, before, after, may, must and only. Add the missing role, date, version or exception beside each one.
Write the expected interpretation, the actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Independent-person test
Give the communication to someone who was not present. Ask what they think is true, unknown and required next.
Write the expected interpretation, the actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Change test
Imagine that a deadline, interface, source, role or policy changes tomorrow. Mark every sentence needing review and name who will update it.
Write the expected interpretation, the actual interpretation, the difference and one precise revision. Keep the earlier version so the learning remains visible.
Close reading is practical care: it keeps language from outrunning the audience, evidence or authority behind it.
Answer each prompt in a complete sentence tied to the current task, source, reader or authorised clarification. Write “unknown” when the available information does not support an answer.
- Find route? State the evidence, limit and narrow next action it supports.
- Check security? State the evidence, limit and narrow next action it supports.
- Minimise copies? State the evidence, limit and narrow next action it supports.
- Keep ticket? State the evidence, limit and narrow next action it supports.
- Name repository? State the evidence, limit and narrow next action it supports.
- Copy identifier? State the evidence, limit and narrow next action it supports.
- Name version? State the evidence, limit and narrow next action it supports.
- Check access? State the evidence, limit and narrow next action it supports.
- Name file? State the evidence, limit and narrow next action it supports.
- Name location? State the evidence, limit and narrow next action it supports.
- Describe safely? State the evidence, limit and narrow next action it supports.
- Check links? State the evidence, limit and narrow next action it supports.
Read or rehearse it aloud
Listen for sentences that postpone the answer, hide the actor, overload one step or imply certainty the source does not provide. Revise for meaning before tone.
Ask a real reader or listener
Invite a learner, parent, colleague or mentor to identify the purpose, strongest claim, important condition and next action. Treat hesitation as useful evidence.
Keep a small revision note
Record the source, date, change and reason. A short history helps the next writer avoid restoring an earlier ambiguity.
Can I delete any repository record I uploaded?
Not necessarily. Repositories apply their policies, especially after publication or identifier registration.
Is a metadata correction the same as takedown?
No. A correction changes descriptive fields; a takedown restricts or withdraws content because of a more serious concern.
Will the DOI disappear?
Often not. Persistent identifiers may continue resolving to a tombstone or changed landing page.
Should I attach the exposed file?
Only if the repository requests it through a secure route and the copy is necessary. A precise location may be safer.
What counts as urgent?
Describe current access, sensitive material, affected people and plausible harm rather than relying on capital letters or threats.
Can AI decide whether content violates law or policy?
No. It can help organise a request, but authorised repository, legal, ethics or security reviewers decide.
- Zenodo General Policies
- Zenodo Manage Records
- DataCite DOI States
- Why English? Writing a Repository Metadata Correction Request
- Why English? Writing a University Research Data Repository Deposit Agreement Summary
Cycle-sensitive facts were checked against current official pages on 14 October 2026. Always reopen the authority’s live page before a real decision.