Skip to content

Main content

Activity Log Manual Device Duplicate Key Tool

Calculate activity log manual device duplicate key from explicit caller-supplied inputs.

Loading tool…

Description

Validate a real Gregorian date and startMinute in 0-1439, then serialize date, activity, and startMinute as a JSON-array key.

Personal health and activity records use supplied observations, labels, and time intervals. A formatter or simple summary can organize those records without assessing health, diagnosing a condition, or recommending treatment.

Validate a real Gregorian date and startMinute in 0-1439, then serialize date, activity, and startMinute as a JSON-array key.

When to use this tool

Use Activity Log Manual Device Duplicate Key when you need a bounded personal-record calculation with explicit units and date conventions.

How to use the tool and how it works

  1. Enter date, activity, startMinute. 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 key. Use the output convention below.

Validate a real Gregorian date and startMinute in 0-1439, then serialize date, activity, and startMinute as a JSON-array key.1

Input fieldMeaning and unitsAccepted input
dateGregorian date in the exact accepted precision and grammar.Required. Text; maximum UTF-16 length 8192.
activityActivityRequired. Text; maximum UTF-16 length 8192.
startMinuteStart MinuteRequired. Safe integer; minimum 0; maximum 1439.
Output fieldInterpretationReturned shape
keyKeyRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "date": "2026-10-26",
    "activity": "walk",
    "startMinute": 480
  },
  "output": {
    "key": "[\"2026-10-26\",\"walk\",480]"
  }
}

Limitations and assumptions

  • Source type is intentionally absent from the key, but key equality alone does not prove duplicate activity or justify merging or deleting records.
  • 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

Review the original observations and consult an appropriate health professional for clinical interpretation or care decisions.

References

  1. Calculation and input contract: health/activity-log-manual-device-duplicate-key — tool.io

Similar or alternative tools