Offsite Storage Transport Manifest Box Count Reconciler
Reconcile stable expected/arrived box identities including duplicates, not mere equal counts or inferred transport chain of custody.
Description
A transport manifest reconciliation compares actual identities rather than total counts.
A transport manifest reconciliation compares actual identities rather than total counts. Missing, unexpected and duplicated arrivals represent distinct discrepancies.1
Reconcile stable expected/arrived box identities including duplicates, not mere equal counts or inferred transport chain of custody.
When to use Offsite Storage Transport Manifest Box Count Reconciler
Use this tool to reconcile stable expected/arrived box identities including duplicates, not mere equal counts or inferred transport chain of custody.
Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.
How to use Offsite Storage Transport Manifest Box Count Reconciler and understand its results
- Prepare the inventory, measurements or policy dates for the collection and reporting period. Confirm units, record order and any independently established thresholds or permissions.
- Enter expectedManifestBoxIds, observedArrivalBoxIds using the field table and calculation rules, then run the tool.
- Read missingExpectedBoxIds, unexpectedArrivalBoxIds, duplicateArrivalBoxIds, exactManifestReconciled. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| expectedManifestBoxIds | Expected manifest box ids | string | Required |
| observedArrivalBoxIds | Observed arrival box ids | string | Required |
Paste expected and arrived box IDs one per line; empty inventories are allowed. Expected IDs must be unique. The tool counts arrivals, reports missing IDs in expected order and unexpected/duplicate IDs in first-arrival order. The exact reconciliation flag is true only when all three discrepancy lists are empty.
reconciled = no missing expected IDs AND no unexpected arrivals AND no duplicate arrivals Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| missingExpectedBoxIds | Missing expected box ids | list of string |
| unexpectedArrivalBoxIds | Unexpected arrival box ids | list of string |
| duplicateArrivalBoxIds | Duplicate arrival box ids | list of string |
| exactManifestReconciled | Exact manifest reconciled | boolean |
{
"input": {
"expectedManifestBoxIds": "A\nB\nC",
"observedArrivalBoxIds": "B\nC\nD"
},
"output": {
"missingExpectedBoxIds": [
"A"
],
"unexpectedArrivalBoxIds": [
"D"
],
"duplicateArrivalBoxIds": [],
"exactManifestReconciled": false
}
} Limitations and assumptions
Identity comparison is exact and case-sensitive. Blank interior lines or surrounding whitespace are input errors. Reconciliation does not prove contents, condition or chain of custody, and does not update an inventory system.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Original Order Preservation Deviation Flag Checker: Audit actual original/current matched stable identities through displacements and pair inversions, rather than infer archival integrity from moved count; missing/duplicate identity is unresolved, not accepted. For a complementary task, use Collection Code Prefix Uniqueness Checker: Audit exact and leading-prefix collection-code ambiguities under explicit case policy; prefix comparisons are bounded to 1000 records, not authority registry validation.
References
Similar or alternative tools
- Original Order Preservation Deviation Flag Checker
Audit actual original/current matched stable identities through displacements and pair inversions, rather than infer archival integrity from moved count; missing/duplicate identity is unresolved, not accepted.
- Collection Code Prefix Uniqueness Checker
Audit exact and leading-prefix collection-code ambiguities under explicit case policy; prefix comparisons are bounded to 1000 records, not authority registry validation.