Skip to content

Main content

Exhibit ID Check Token Tool

Inspect a caller-defined public exhibit namespace without identity resolution or an invented checksum.

Loading tool…

Description

Check token starts with their concatenation and return its remaining suffix, or empty text when unmatched.

Evidence records link identifiers, packaging, quantities and source assertions. Literal equality and balanced counts can reveal local inconsistencies, but they cannot authenticate physical evidence, establish custody completeness or determine legal admissibility.

Check token starts with their concatenation and return its remaining suffix, or empty text when unmatched.

When to use this tool

Use Exhibit ID Check Token when you need a scoped evidence-record or quantity-reconciliation diagnostic.

How to use the tool and how it works

  1. Enter token, prefix, delimiter. 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 prefixMatches, suffix. Inspect prefixMatches before interpreting the associated values.

Require nonempty prefix and delimiter. Check token starts with their concatenation and return its remaining suffix, or empty text when unmatched.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text; maximum UTF-16 length 8192.
prefixSupplied or returned literal prefix under the stated grammar.Required. Text; maximum UTF-16 length 8192.
delimiterDelimiterRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
prefixMatchesPrefix MatchesRequired. Boolean.
suffixReturned literal suffix; inspect any lookup or placeholder flag.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "token": "EX-12",
    "prefix": "EX",
    "delimiter": "-"
  },
  "output": {
    "prefixMatches": true,
    "suffix": "12"
  }
}

Limitations and assumptions

  • An empty suffix may also be a matched empty suffix; inspect prefixMatches. No exhibit registry, checksum or custody source is validated.
  • 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.

Alternative or Complementary methods

Review authenticated source records and the complete custody process through the appropriate professional procedure. Treat local flags as prompts for investigation rather than independent evidentiary conclusions.

References

  1. Calculation and input contract: forensic-science/exhibit-id-check-token — tool.io

Similar or alternative tools

  • Exhibit Seal Version Match Flag

    Compare recorded and expected seal/version strings exactly and return separate flags plus their conjunction.

  • Exhibit Bag Seal ID Pair

    Compare literally or after JavaScript lowercasing according to caseSensitive, and return individual flags and their conjunction.