Box-Folder Hierarchical Number Format Validator

Validate exact Bn/Fn hierarchy and resolve folder number against caller declared box inventory; syntactic validity alone does not prove a box/folder exists.

Description

A box/folder identifier has both a syntactic format and a relationship to a declared inventory.

A box/folder identifier has both a syntactic format and a relationship to a declared inventory. Parsing its numbers alone cannot establish that the box or folder exists.^[1]

Validate exact Bn/Fn hierarchy and resolve folder number against caller declared box inventory; syntactic validity alone does not prove a box/folder exists.

When to use Box-Folder Hierarchical Number Format Validator

Use this tool to validate exact Bn/Fn hierarchy and resolve folder number against caller declared box inventory; syntactic validity alone does not prove a box/folder exists.

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 Box-Folder Hierarchical Number Format Validator 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 boxFolderIdentifier, declaredBoxFolderCapacities using the field table and calculation rules, then run the tool.
Read validHierarchicalIdentifier, parsedBoxFolderNumbers, declaredBoxFound, folderWithinDeclaredBoxCapacity. 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
boxFolderIdentifier	Box folder identifier	string	Required
declaredBoxFolderCapacities	Declared box folder capacities	list of list of number	Required

Enter a nonempty identifier of at most 64 characters and a nonempty matrix of box-number/folder-capacity pairs. Boxes must be unique positive integers; capacities are nonnegative integers. Exact Bn/Fn syntax uses uppercase letters and 1–9 digit numbers without leading zeros. Return format validity, parsed numbers, box-found and capacity flags. Malformed syntax returns false flags and an empty parsed list.

valid syntax = BpositiveInteger/FpositiveInteger; capacity match = declared box exists AND folder≤capacity

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
validHierarchicalIdentifier	Valid hierarchical identifier	boolean
parsedBoxFolderNumbers	Parsed box folder numbers	list of number
declaredBoxFound	Declared box found	boolean
folderWithinDeclaredBoxCapacity	Folder within declared box capacity	boolean

json

{
  "input": {
    "boxFolderIdentifier": "B12/F3",
    "declaredBoxFolderCapacities": [
      [
        12,
        5
      ],
      [
        13,
        2
      ]
    ]
  },
  "output": {
    "validHierarchicalIdentifier": true,
    "parsedBoxFolderNumbers": [
      12,
      3
    ],
    "declaredBoxFound": true,
    "folderWithinDeclaredBoxCapacity": true
  }
}

Limitations and assumptions

Malformed input types or invalid capacity tables are errors, distinct from a well-supplied identifier that fails the format check. The declaration is caller data and does not prove a physical folder is present.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Matrices are limited to 128 rows and 128 entries per row; other numeric lists are limited to 100,000 entries. 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 Accession Number Year Sequence Validator: Validate strict ASCII YYYY-sequence and caller year without conflating year.lot.item or correcting leading zeros; validation does not reserve identity. 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

Box-Folder Hierarchical Number Format Validator — tool.io

Similar or alternative tools

Accession Number Year Sequence Validator
Validate strict ASCII YYYY-sequence and caller year without conflating year.lot.item or correcting leading zeros; validation does not reserve identity.
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.