Notifications
Clear all
Lab work & testing
14
Posts
14
Users
0
Reactions
1
Views
Topic starter
18/10/2023 10:34 pm
A transcription error changes the units in a figure caption. How should the archive record be repaired?
Discussion record: RESEARCH-20485.
18/10/2023 11:51 pm
Identify the original error and the corrected text, date the correction and link the source. Keep the correction visible to readers who may have saved or cited the earlier version.
19/10/2023 12:07 am
Clarification for “A correction log for an archive article”: the point beginning “Identify the original error and the corrected text, date…” 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.
19/10/2023 1:10 am
Method note for “A correction log for an archive article”: use “Identify the original error and the corrected text, date…” 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.
19/10/2023 1:17 am
Limit of the answer in “A correction log for an archive article”: “Identify the original error and the corrected text, date…” 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.
19/10/2023 1:40 am
Correction note for “A correction log for an archive article”: retain the wording beginning “Identify the original error and the corrected text, date…” 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.
19/10/2023 2:25 am
Summary draft for “A correction log for an archive article”: the answer addresses “Identify the original error and the corrected text, date…”; the related point is “Keep the correction visible to readers who may have…”. 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.
19/10/2023 2:56 am
Clarification for “A correction log for an archive article”: the point beginning “Keep the correction visible to readers who may have…” 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.
19/10/2023 2:58 am
Reader check for “A correction log for an archive article”: distinguish the discussion point “Identify the original error and the corrected text, date…” 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.
19/10/2023 3:40 am
Method note for “A correction log for an archive article”: use “Keep the correction visible to readers who may have…” 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.
19/10/2023 4:10 am
Limit of the answer in “A correction log for an archive article”: “Keep the correction visible to readers who may have…” 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.
19/10/2023 4:31 am
Correction note for “A correction log for an archive article”: retain the wording beginning “Keep the correction visible to readers who may have…” 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.
19/10/2023 5:08 am
Summary draft for “A correction log for an archive article”: the answer addresses “Keep the correction visible to readers who may have…”; the related point is “Identify the original error and the corrected text, date…”. 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.
19/10/2023 5:23 am
Reader check for “A correction log for an archive article”: distinguish the discussion point “Keep the correction visible to readers who may have…” 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: