Notifications
Clear all
Lab work & testing
13
Posts
13
Users
0
Reactions
0
Views
Topic starter
30/09/2023 1:20 am
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?
Record format: question; proposed response; source or method; limitation. Use a dated correction only if the underlying wording or evidence changes. Record RESEARCH-20308.
30/09/2023 2:11 am
Use separate entries for the internal transcription correction and the publisher notice. They have different sources and may affect different claims.
30/09/2023 2:40 am
Each entry should retain the date, old text, corrected text, reason and source reference. For a publisher notice, link the notice as well as the original paper.
30/09/2023 3:41 am
Ask whether the changed figure affects the archive’s interpretation. Updating a citation alone may leave an unsupported conclusion in the opening summary.
30/09/2023 3:59 am
Keep a visible correction near the affected material and a linked changelog entry. Readers who saved the earlier version should be able to understand what changed.
30/09/2023 4:44 am
The final note should distinguish corrected data transcription, changed source evidence and revised interpretation. Preserve that distinction in subsequent exports.
30/09/2023 4:54 am
If the source is not accessible, label the revision pending verification. An unavailable document is not a reason to invent its contents.
30/09/2023 5:43 am
Clarification for “A correction log that survives the next archive update”: the point beginning “Use separate entries for the internal transcription correction…” 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: scope. Keep the stated question separate from any broader claim.
30/09/2023 6:05 am
Method note for “A correction log that survives the next archive update”: use “Use separate entries for the internal transcription correction…” 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. Keep the stated question separate from any broader claim.
30/09/2023 6:33 am
Limit of the answer in “A correction log that survives the next archive update”: “Use separate entries for the internal transcription correction…” 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: scope. Keep the stated question separate from any broader claim.
30/09/2023 6:45 am
Correction note for “A correction log that survives the next archive update”: retain the wording beginning “Use separate entries for the internal transcription correction…” 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. Keep the stated question separate from any broader claim.
30/09/2023 7:42 am
Summary draft for “A correction log that survives the next archive update”: the answer addresses “Use separate entries for the internal transcription correction…”; the related point is “They have different sources and may…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
30/09/2023 8:12 am
Reader check for “A correction log that survives the next archive update”: distinguish the discussion point “Use separate entries for the internal transcription correction…” 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: scope. Keep the stated question separate from any broader claim.
Share: