Description
Independently compare originalId with correctionParent and correctedVersion with originalVersion; a linked correction need not have a later version.
Farm data records connect field, event, sensor and source identifiers with observation and verification flags. Literal keys and supported-record shares help reconcile those records without authenticating a source, identifying a physical object or establishing measurement quality. Repeated IDs may need a different denominator from repeated rows.
Independently compare originalId with correctionParent and correctedVersion with originalVersion; a linked correction need not have a later version.
When to use this tool
Use Farm Work Order Corrected Source Link when checking the stated agricultural source, identity or record-support convention.
How to use the tool and how it works
- Enter originalId, correctionParent, originalVersion, correctedVersion. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read linked, laterVersion. Inspect linked, laterVersion before interpreting the associated values.
Require nonnegative whole version numbers. Independently compare originalId with correctionParent and correctedVersion with originalVersion; a linked correction need not have a later version.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| originalId | Original Id | Required. Text; maximum UTF-16 length 8192. |
| correctionParent | Correction Parent | Required. Text; maximum UTF-16 length 8192. |
| originalVersion | Original Version | Required. Safe integer; minimum 0. |
| correctedVersion | Corrected Version | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| linked | Linked | Required. Boolean. |
| laterVersion | Later Version | Required. Boolean. |
{
"input": {
"originalId": "W1",
"correctionParent": "W1",
"originalVersion": 2,
"correctedVersion": 3
},
"output": {
"linked": true,
"laterVersion": true
}
}Limitations and assumptions
- Literal identity and numeric version order do not authenticate a correction or validate its contents.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Inspect original records, authoritative identifier schemes and calibrated measurements before merging data or drawing agricultural conclusions.
References
Similar or alternative tools
- Farm Sensor Channel Code Source Pair
Return exact channel-and-source concordance with supplied expected labels.
- Crop Calendar Stage Source Key
Encode [source,edition,cropCode,stageCode] as JSON text.