Skip to content

Main content

Exhibit Bag Seal ID Pair Tool

Exact or Unicode lowercase identifier comparison without trimming or punctuation removal; matching labels do not authenticate an exhibit.

Loading tool…

Description

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

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.

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

When to use this tool

Use Exhibit Bag Seal ID Pair when you need a scoped evidence-record or quantity-reconciliation diagnostic.

How to use the tool and how it works

  1. Enter recordedSeal, observedSeal, recordedBag, observedBag, caseSensitive. 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 sealMatches, bagMatches, pairMatches. Inspect sealMatches, bagMatches, pairMatches before interpreting the associated values.

Require four nonempty seal/bag identifiers. Compare literally or after JavaScript lowercasing according to caseSensitive, and return individual flags and their conjunction.1

Input fieldMeaning and unitsAccepted input
recordedSealRecorded SealRequired. Text; maximum UTF-16 length 8192.
observedSealObserved SealRequired. Text; maximum UTF-16 length 8192.
recordedBagRecorded BagRequired. Text; maximum UTF-16 length 8192.
observedBagObserved BagRequired. Text; maximum UTF-16 length 8192.
caseSensitiveCase SensitiveRequired. Boolean.
Output fieldInterpretationReturned shape
sealMatchesSeal MatchesRequired. Boolean.
bagMatchesBag MatchesRequired. Boolean.
pairMatchesPair MatchesRequired. Boolean.
json
{
  "input": {
    "recordedSeal": "S12",
    "observedSeal": "s12",
    "recordedBag": "B4",
    "observedBag": "B4",
    "caseSensitive": false
  },
  "output": {
    "sealMatches": true,
    "bagMatches": true,
    "pairMatches": true
  }
}

Limitations and assumptions

  • No trimming or locale-specific comparison occurs. Matching strings do not authenticate packaging, condition, possession, or custody history.
  • 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-bag-seal-id-pair — 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.

  • Evidence Package Seal Share

    Count distinct packages, any sealed IDs and any IDs with a sealed-and-verified row; divide verified count by all, or flagged undefined zero.