How Community Data Works
Community Data Methodology
What community data is, how every submission is moderated, what is calculated versus user-reported, the limitations, and why community data is never confused with controlled Lab testing.
COMMUNITY SUBMISSION
USER-SUBMITTED DATA. Community data is not controlled testing. Everything below explains how this evidence type is collected, moderated and labeled.
What community data is
Community data is structured, user-submitted experience: batches, machine and model information, food type, preparation, batch weights, drying observations, rehydration results, photos, problems and lessons learned. It is the opposite of controlled testing. Each user works with their own machine, food, environment and measurement method, so every record reflects that user's conditions, not a laboratory protocol.
Community data never alters manufacturer specifications, Food Encyclopedia classifications or site safety guidance. It is shared to help other users see how results vary in the real world, not to rewrite any official source.
How submissions are moderated
Every submission is reviewed by the site owner before anything is published. There is no auto-publish, no algorithm approval, and no user accounts or login. A submission moves through one of four states:
Pending
The submission arrived and waits in the owner's review queue. Nothing is published while Pending.
Approved
The record passed review and is published as a structured community batch page with its JFD-COM ID.
Rejected
The submission was not published, for example duplicate data, obvious errors, unsafe advice or spam.
Needs Clarification
The owner asks the submitter (privately, never publicly) to correct or complete something before a decision.
Moderator notes, including the reason for a decision, suspicious values, duplicate flags and spam status, stay private. They are never exposed on the public site. Moderation happens with the site owner, not automatically, and the owner may request clarification from the submitter without exposing contact data publicly.
Approved submitters choose their own credit level. They may opt into public credit, which shows their chosen name and any promotion links they provided next to their approved records, or they may submit fully anonymously, which shows an Anonymous submission and hides the details they entered. Credit details are submitter-provided and are never presented as an endorsement or verification by Just Freeze Drying. Email, phone and street address are never collected and never displayed anywhere.
What is calculated versus user-reported
Every community number carries exactly one of four labels. The labels are never mixed, and no community value is ever labeled Lab Measured, Verified or Tested:
entered by submitter
derived from submitted numbers
subjective assessment
user reports actually performing the test
Weight Reduction % is calculated, never moisture content
The community form calculates Weight Removed, Weight Reduction %, Dry Yield % and Fresh-to-Dry Ratio from submitted fresh and dry weights and labels them all "Calculated from user-submitted weights". Weight Reduction % is never called moisture content anywhere: inferring moisture from weight loss is not a valid measurement method, and the site does not do it.
Limitations
Community submissions vary by machine, preparation, environment, food and measurement method. User-reported machine readings carry no implied sensor calibration or laboratory accuracy. Cycle fields are optional and only reflect what each machine exposes. Community data is not controlled testing and is never presented as scientific results.
Sample sizes reported honestly
Every community statistic shows n, the number of approved submissions behind it. One submission is reported as "1 Community Submission" with no typicals. With more data the site uses "Community submissions ranged from..." language, never "the correct cycle is...", and prefers the median alongside the range where enough data exists. Tiny samples are never aggregated misleadingly, and cycle ranges are filterable by machine rather than blended into one overall number.
Outlier review
A value that is very different from other community results is flagged internally as Outlier Review and is never deleted automatically. It may be:
- it is genuine, and the first record like it
- it is an input error the submitter can correct
- it is an unusual food or preparation that behaves differently
- it is a different preparation method producing a different result
Duplicate detection
The owner checks for possible duplicates before approval: the same user, machine, food, date and weights are never published twice. Obvious errors such as dry weight greater than fresh weight, a zero cycle duration or impossible unit combinations are flagged for review rather than silently corrected, and submitters are prompted to fix them where possible. Submitted values are never modified: original values and normalized values are kept separate in the record architecture.
The strict Lab distinction
This site keeps three separate evidence systems: WeFreezeDryIt Lab Data (controlled and documented in the Freeze Drying Lab at /lab/, with JFD-LAB IDs), Community-Submitted Data (moderated user records with JFD-COM IDs), and General Guidance (educational content). They are never merged. Community data is not controlled testing, is never promoted into Lab status without a real controlled process, and the site's own documented tests belong in the Lab, never inflated into the Community database.
Looking for controlled WeFreezeDryIt testing?
Community data is user-submitted experience. The Freeze Drying Lab is the separate, controlled testing program run by WeFreezeDryIt with documented records.
Approved submissions right now
n = 0 approved community submissions. The database opens at zero on purpose: no fabricated records, no fake averages, no hidden sample sizes. As real submissions are moderated and approved, each one is published with its JFD-COM ID and this methodology applies to all of them.
Be the first to submit