Notifications
Clear all
Corrections & citations
19
Posts
19
Users
0
Reactions
0
Views
Topic starter
16/01/2023 9:07 am
A cited article now has an editorial notice. How should the archive respond?
Reply scope: address the opening question, explain the supporting record or reasoning, and state the limit of the answer.
16/01/2023 10:21 am
Clarification for “Retractions and expressions of concern in an archive”: the point beginning “Link the publisher notice beside the citation, record its date and…” 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.
16/01/2023 10:43 am
Link the publisher notice beside the citation, record its date and reassess claims that relied on the paper. Do not leave the historical citation looking like unqualified current support.
16/01/2023 11:24 am
Method note for “Retractions and expressions of concern in an archive”: use “Link the publisher notice beside the citation, record its date and…” 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.
16/01/2023 12:11 pm
Limit of the answer in “Retractions and expressions of concern in an archive”: “Link the publisher notice beside the citation, record its date and…” 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.
16/01/2023 12:26 pm
Summary draft for “Retractions and expressions of concern in an archive”: the answer addresses “Link the publisher notice beside the citation, record its date and…”; the related point is “Do not leave the historical citation looking…”. 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.
16/01/2023 12:30 pm
Correction note for “Retractions and expressions of concern in an archive”: retain the wording beginning “Link the publisher notice beside the citation, record its date and…” 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.
16/01/2023 1:07 pm
Reader check for “Retractions and expressions of concern in an archive”: distinguish the discussion point “Link the publisher notice beside the citation, record its date and…” 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.
16/01/2023 1:23 pm
Clarification for “Retractions and expressions of concern in an archive”: the point beginning “Do not leave the historical citation looking…” 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.
16/01/2023 2:02 pm
Method note for “Retractions and expressions of concern in an archive”: use “Do not leave the historical citation looking…” 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.
16/01/2023 2:52 pm
Correction note for “Retractions and expressions of concern in an archive”: retain the wording beginning “Do not leave the historical citation looking…” 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.
16/01/2023 3:13 pm
Limit of the answer in “Retractions and expressions of concern in an archive”: “Do not leave the historical citation looking…” 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.
16/01/2023 3:35 pm
Summary draft for “Retractions and expressions of concern in an archive”: the answer addresses “Do not leave the historical citation looking…”; the related point is “Link the publisher notice beside the citation, record its date and…”. 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.
16/01/2023 4:01 pm
Reader check for “Retractions and expressions of concern in an archive”: distinguish the discussion point “Do not leave the historical citation looking…” 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.
16/01/2023 4:52 pm
Clarification for “Retractions and expressions of concern in an archive”: the point beginning “Link the publisher notice beside the citation, record its date and…” 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: source wording. Retain the source wording beside any paraphrase.
Page 1 / 2
Next
Share: