Case 90 — Two laboratories, two percentages: are they measuring the same thing? · documentation exercise
Summary draft for “Two laboratories, two percentages: are they measuring the same thing?”: the answer addresses “Missing details should be visible…”; the related point is “Keep the original reported values beside…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
The draft summary of a fictional reading exercise moves from an animal-model observation to a proposed human benefit. Which fields would keep the literature note within the evidence?
Review focus: documentation. Distinguish an original record from a proposed record format. Use the original answer fragment “Record what the paper states and mark unreported fields…” as the discussion anchor; no new event or result is supplied.
Exercise RESEARCH-25905/91: address this question within its stated limits.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
Clarification for “Reading a preclinical paper: what belongs beside the abstract?”: the point beginning “Record what the paper states and mark unreported fields…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
Method note for “Reading a preclinical paper: what belongs beside the abstract?”: use “Record what the paper states and mark unreported fields…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Distinguish an original record from a proposed record format.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
Limit of the answer in “Reading a preclinical paper: what belongs beside the abstract?”: “Record what the paper states and mark unreported fields…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
Correction note for “Reading a preclinical paper: what belongs beside the abstract?”: retain the wording beginning “Record what the paper states and mark unreported fields…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Distinguish an original record from a proposed record format.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
Summary draft for “Reading a preclinical paper: what belongs beside the abstract?”: the answer addresses “Record what the paper states and mark unreported fields…”; the related point is “Separate the authors’ proposed mechanism from the…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 91 — Reading a preclinical paper: what belongs beside the abstract? · documentation exercise
Reader check for “Reading a preclinical paper: what belongs beside the abstract?”: distinguish the discussion point “Record what the paper states and mark unreported fields…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 92 — A correction log that survives the next archive update · documentation exercise
A archive table has a transcription error in a unit label. A later publisher notice also changes a figure. How can the correction history distinguish those two events?
Review focus: documentation. Distinguish an original record from a proposed record format. Use the original answer fragment “For a publisher notice, link the notice as…” as the discussion anchor; no new event or result is supplied.
Exercise RESEARCH-25905/92: address this question within its stated limits.
Case 92 — A correction log that survives the next archive update · documentation exercise
Method note for “A correction log that survives the next archive update”: use “For a publisher notice, link the notice as…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Distinguish an original record from a proposed record format.
Case 92 — A correction log that survives the next archive update · documentation exercise
Clarification for “A correction log that survives the next archive update”: the point beginning “For a publisher notice, link the notice as…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 92 — A correction log that survives the next archive update · documentation exercise
Limit of the answer in “A correction log that survives the next archive update”: “For a publisher notice, link the notice as…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 92 — A correction log that survives the next archive update · documentation exercise
Correction note for “A correction log that survives the next archive update”: retain the wording beginning “For a publisher notice, link the notice as…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Distinguish an original record from a proposed record format.
Case 92 — A correction log that survives the next archive update · documentation exercise
Summary draft for “A correction log that survives the next archive update”: the answer addresses “For a publisher notice, link the notice as…”; the related point is “Ask whether the changed figure affects…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: documentation. Distinguish an original record from a proposed record format.
Case 92 — A correction log that survives the next archive update · documentation exercise
Reader check for “A correction log that survives the next archive update”: distinguish the discussion point “For a publisher notice, link the notice as…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: documentation. Distinguish an original record from a proposed record format.