Description
Return correctedDay - originalDay, linked from originalId equality with parentId, and changesDate from unequal day coordinates.
Archival records often contain bounded dates, editions, and source identifiers. Arithmetic on supplied coordinates can check consistency while leaving historical interpretation and authenticity unresolved.
Return correctedDay - originalDay, linked from originalId equality with parentId, and changesDate from unequal day coordinates.
When to use this tool
Use Birth Record Original Corrected Date Pair when you need a precise date-span or source-record bookkeeping step.
How to use the tool and how it works
- Enter originalDay, correctedDay, correctionId, originalId, parentId. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read differenceDays, linked, changesDate. Inspect linked, changesDate before interpreting the associated values.
Require nonempty correction, original, and parent IDs. Return correctedDay - originalDay, linked from originalId equality with parentId, and changesDate from unequal day coordinates.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| originalDay | Original Day | Required. Safe integer. |
| correctedDay | Corrected Day | Required. Safe integer. |
| correctionId | Correction Id | Required. Text; maximum UTF-16 length 8192. |
| originalId | Original Id | Required. Text; maximum UTF-16 length 8192. |
| parentId | Parent Id | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| differenceDays | Difference Days | Required. Safe integer. |
| linked | Linked | Required. Boolean. |
| changesDate | Changes Date | Required. Boolean. |
{
"input": {
"originalDay": 100,
"correctedDay": 101,
"correctionId": "C1",
"originalId": "R1",
"parentId": "R1"
},
"output": {
"differenceDays": 1,
"linked": true,
"changesDate": true
}
}Limitations and assumptions
- The correction ID is required but not independently verified; record ancestry and date validity remain external checks.
- 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
Consult the original catalog and documented calendar or dating convention when historical interpretation matters.
References
Similar or alternative tools
- Birth Preference Superseded Choice Pair
Compare originalId to replacementParent, originalChoice to replacementChoice, and replacementRev to originalRev.
- Birth Record Duplicate Event Key
Serialize source, eventId, dayIndex, and minute as eventKey; append version for revisionKey.