Where a value is derived rather than measured, mark it. Derived columns get treated as observations the moment the file leaves your hands.
Topic summary
Contributing data without breaching anyone's privacy
This is a generated summary. It shows the 9 most-liked posts from a topic of 72, in their original order, with the accepted answer included where one exists. It is a reading aid and it will miss nuance — the full topic is the record.
c.amankwah, post #1: Contributing data without breaching anyone's privacy Writing it up because I had to work it out twice and would rather nobody else did. Asking about contributing data without breaching directly, because I have read four threads on it and each answered a slightly different question. The version I want answered is the narrow one: given… Go to post
m.ferrand, post #2: The opening post is the version of this I will quote in future. One addition. Reproducibility: if sharing data, include enough context (compound, dose, timeframe, method) that someone reading it understands what it represents. Happy to be corrected if someone holds better data than mine. Go to post
Date every record. A dataset assembled over two years without dates cannot distinguish a change over time from a change in who was contributing.
revision_history, post #8: Adding the measurement that post #5 says would settle it. Missing data should be recorded as missing rather than as zero. The distinction disappears once the file is shared and cannot be recovered. This is the sort of thing the wiki should carry and currently does not. Go to post
Contributing data without breaching sits at the boundary between what this community can usefully discuss and what it cannot, and I think it falls on the discussable side, narrowly.
Post #48 put the caveat in the right place and I want to underline it.
On contributing data without breaching: the maintained page in the documentation commons covers the general case with citations and a review date, which is more reliable than any reply here including this one.
26 likes 5mo
That is a cleaner way of putting what I was circling around.
30 likes 5mo
Read the full topic (72 posts)
This topic was referenced in
- Cleaning a self-reported dataset and what you throw awayData & Tools › Datasets · 2 replies
- Sample size in a voluntary survey: the selection problemData & Tools › Datasets · 5 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Revisiting: Sample size in a voluntary survey: the selection problem
Revisiting: Sample size in a voluntary survey: the selection problem — setting out what I have, and where I think it stops being reliable. I have spent a fortnight trying to pin Sample size down and I want to…
|
2 | 56k | 9mo | |
|
Contributing data without breaching anyone's privacy — what changed since
On the subject in the title: Contributing data without breaching anyone's privacy — what changed since Working notes rather than a conclusion. What changes if the standard account of Contributing data without…
|
2 | 58k | 17mo | |
|
Cleaning a self-reported dataset and what you throw away — what changed since
Posting this under the heading it deserves: Cleaning a self-reported dataset and what you throw away — what changed since Everything below is what sits behind that. What changes if the standard account of…
|
2 | 2k | 1h | |
|
A community side-effect dataset, with its response rate and biases
A community side-effect dataset, with its response rate and biases — setting out what I have, and where I think it stops being reliable. Community side-effect dataset: setting out the arithmetic in full,…
|
2 | 5.1k | 19h | |
|
Aggregated purity results across four services, with caveats — a second dataset
Aggregated purity results across four services, with caveats — a second dataset — setting out what I have, and where I think it stops being reliable. Posting a small dataset on Aggregated purity results…
|
+127 | 151 | 42k | 10mo |
Related topics — sharing the tags data table, confounding, observational data
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
List price versus negotiated price versus what you pay
On the subject in the title: List price versus negotiated price versus what you pay Working notes rather than a conclusion. List price versus negotiated price — I have the observation and I do not trust my…
|
+99 | 115 | 11k | 3mo |
|
Area percent versus weight percent: the confusion that causes most arguments — what changed since
Area percent versus weight percent: the confusion that causes most arguments — what changed since Writing it up because I had to work it out twice and would rather nobody else did. What changes if the…
|
+30 | 34 | 40k | 13mo |
|
Waist circumference technique and its repeatability
Waist circumference technique and its repeatability — setting out what I have, and where I think it stops being reliable. I have spent a fortnight trying to pin waist circumference technique down and I want…
|
+55 | 60 | 11k | 5mo |
|
Shoulders, tangent skims, and defensible integration
Posting this under the heading it deserves: Shoulders, tangent skims, and defensible integration Everything below is what sits behind that. Setting out an integration problem with the actual figures, because…
|
+16 | 20 | 11k | 13h |
|
Immortal time bias in a claims-database study
Immortal time bias in a claims-database study — setting out what I have, and where I think it stops being reliable. Asking about immortal time bias directly, because I have read four threads on it and each…
|
+29 | 34 | 28k | 11mo |