Skip to content

Main content

Birth Record Duplicate Event Key Tool

Build separate event and revision keys from supplied birth-record fields.

Loading tool…

Description

Serialize source, eventId, dayIndex, and minute as eventKey; append version for revisionKey.

Exact label matching answers whether supplied strings agree under a chosen vocabulary. It preserves a useful distinction between missing, unknown, ambiguous, and unrecognized records.

Serialize source, eventId, dayIndex, and minute as eventKey; append version for revisionKey.

When to use this tool

Use Birth Record Duplicate Event Key when you need an explicit record-label comparison or deterministic key.

How to use the tool and how it works

  1. Enter source, eventId, dayIndex, minute, version. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read eventKey, revisionKey. Use the output convention below.

Require a clock minute in 0-1439 and a nonnegative revision. Serialize source, eventId, dayIndex, and minute as eventKey; append version for revisionKey.1

Input fieldMeaning and unitsAccepted input
sourceSource identifier or source selector, interpreted under the calculation above.Required. Text; maximum UTF-16 length 8192.
eventIdEvent IdRequired. Text; maximum UTF-16 length 8192.
dayIndexDay IndexRequired. Safe integer.
minuteMinuteRequired. Safe integer; minimum 0; maximum 1439.
versionVersionRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
eventKeyEvent KeyRequired. Text; maximum UTF-16 length 8192.
revisionKeyRevision KeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "source": "A",
    "eventId": "E1",
    "dayIndex": 100,
    "minute": 600,
    "version": 2
  },
  "output": {
    "eventKey": "[\"A\",\"E1\",100,600]",
    "revisionKey": "[\"A\",\"E1\",100,600,2]"
  }
}

Limitations and assumptions

  • Keys preserve exact supplied coordinates without timezone conversion, duplicate resolution, or source authentication.
  • 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

Normalize or reconcile identifiers only under a documented policy, then verify the underlying source records separately.

References

  1. Calculation and input contract: midwifery/birth-record-duplicate-event-key — tool.io

Similar or alternative tools