A photograph captures a moment. A field record should preserve enough context for someone else to understand that moment later.
What we want a field note to carry
As we shape FarmOS for Amanzi Life, we are starting with the everyday work of recording observations. The goal is a consistent connection between the note, its location, the trial and the person who made it.
| Record | Why it belongs |
|---|---|
| Plot and trial ID | Connect the observation to a defined place and protocol. |
| Date, time and observer | Preserve the sequence and the source of the record. |
| Observation and method | Separate what was seen from how it was assessed. |
| Conditions and exceptions | Keep changes in irrigation, weather or procedure visible. |
| Photo reference | Link the original image without relying on a filename alone. |
Keep observation and interpretation separate
Observation
A record of what was seen or measured, with its method and context.
Interpretation
A possible explanation to review against other observations and the trial design.
A field note can raise a question without resolving it. Linking that note to a product application does not, by itself, show that the application caused the observation.
Leave room for corrections
A useful record should allow an observer to correct a mistake while preserving what changed and why. Missing values should be visible, not silently treated as zero. These are design principles for the FarmOS record, not a report of a completed field deployment.