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.

Description

Accession identifiers can encode a year and sequence under a local convention.

Accession identifiers can encode a year and sequence under a local convention. Format validity and matching the expected accession year are separate checks.^[1]

Validate strict ASCII YYYY-sequence and caller year without conflating year.lot.item or correcting leading zeros; validation does not reserve identity.

When to use Accession Number Year Sequence Validator

Use this tool to validate strict ASCII YYYY-sequence and caller year without conflating year.lot.item or correcting leading zeros; validation does not reserve identity.

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 Accession Number Year Sequence 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 accessionYearSequence, callerExpectedAccessionYear using the field table and calculation rules, then run the tool.
Read validYearSequenceFormat, yearMatchesCallerExpectation, parsedYearSequence. 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
accessionYearSequence	Accession year sequence	string	Required
callerExpectedAccessionYear	Caller expected accession year	integer	Required

Enter a nonempty identifier of at most 64 characters and an expected integer year from 1000 to 9999. Accept exact ASCII YYYY-sequence, with a 1–9 digit positive sequence and no leading zeros. Return format and year-match booleans plus parsed numbers; malformed syntax returns false and an empty list rather than an input-type error.

valid format = four-digit-year + '-' + positive sequence without leading zeros

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

Output field	Meaning	Value type
validYearSequenceFormat	Valid year sequence format	boolean
yearMatchesCallerExpectation	Year matches caller expectation	boolean
parsedYearSequence	Parsed year sequence	list of number

json

{
  "input": {
    "accessionYearSequence": "2026-12",
    "callerExpectedAccessionYear": 2026
  },
  "output": {
    "validYearSequenceFormat": true,
    "yearMatchesCallerExpectation": true,
    "parsedYearSequence": [
      2026,
      12
    ]
  }
}

Limitations and assumptions

This is a year-sequence convention, not year.lot.item notation. No identifier is reserved, uniqueness checked or accession date verified.

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 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. 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

Accession Number Year Sequence Validator — tool.io

Similar or alternative tools

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.
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.