Notifications
Clear all
Corrections & citations
10
Posts
10
Users
0
Reactions
0
Views
Topic starter
22/12/2023 11:29 pm
A table has been copied into a new format without its source or transformation notes. What should accompany it?
| Field | Scope |
|---|---|
| Subject | Data provenance: keep source, transformation and output together |
| Exercise | Discuss the stated question; distinguish sources, interpretations and unresolved points. |
23/12/2023 12:35 am
Keep the source citation, retrieval date and a record of conversions or exclusions. Make synthetic examples explicit and never combine them silently with observed data.
23/12/2023 1:30 am
Method note for “Data provenance: keep source, transformation and output together”: use “Keep the source citation, retrieval date and a…” 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.
23/12/2023 1:34 am
Clarification for “Data provenance: keep source, transformation and output together”: the point beginning “Keep the source citation, retrieval date and a…” 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.
23/12/2023 2:16 am
Correction note for “Data provenance: keep source, transformation and output together”: retain the wording beginning “Keep the source citation, retrieval date and a…” 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.
23/12/2023 2:17 am
Limit of the answer in “Data provenance: keep source, transformation and output together”: “Keep the source citation, retrieval date and a…” 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.
23/12/2023 3:01 am
Summary draft for “Data provenance: keep source, transformation and output together”: the answer addresses “Keep the source citation, retrieval date and a…”; the related point is “Make synthetic examples explicit and never combine them…”. 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.
23/12/2023 4:03 am
Reader check for “Data provenance: keep source, transformation and output together”: distinguish the discussion point “Keep the source citation, retrieval date and a…” 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.
23/12/2023 4:13 am
Clarification for “Data provenance: keep source, transformation and output together”: the point beginning “Make synthetic examples explicit and never combine them…” 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.
23/12/2023 4:32 am
Method note for “Data provenance: keep source, transformation and output together”: use “Make synthetic examples explicit and never combine them…” 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.
Share: