Accession Number Format Validator (year.lot.item)
Validate exact ASCII YYYY.lot.item with year 1000–9999, positive no-leading-zero lot/item up to nine digits; reports malformed nonempty identifier as invalid without inventing corrected identity.
Description
An accession format expresses identity as year, lot and item.
An accession format expresses identity as year, lot and item. A format result should preserve invalid supplied strings rather than invent corrections.
Validate exact ASCII YYYY.lot.item with year 1000–9999, positive no-leading-zero lot/item up to nine digits; reports malformed nonempty identifier as invalid without inventing corrected identity.
When to use Accession Number Format Validator (year.lot.item)
Use this tool to validate exact ASCII YYYY.lot.item with year 1000–9999, positive no-leading-zero lot/item up to nine digits; reports malformed nonempty identifier as invalid without inventing corrected identity.
Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
How to use Accession Number Format Validator (year.lot.item) and understand its results
- Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
- Enter accessionIdentifier using the field table and calculation rules, then run the tool.
- Read validYearLotItemFormat, parsedYearLotItem. 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 |
|---|---|---|---|
| accessionIdentifier | Accession identifier | string | Required |
Supply a nonempty string at most 64 characters. Require year 1000–9999 and lot/item 1–999999999 without leading zeros or surrounding whitespace. Valid strings return three parsed integers; malformed nonempty strings return false and an empty list.1
valid = exact ASCII YYYY.positiveLot.positiveItem with bounded digit lengths Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| validYearLotItemFormat | Valid year lot item format | boolean |
| parsedYearLotItem | Parsed year lot item | list of number |
{
"input": {
"accessionIdentifier": "2026.12.3"
},
"output": {
"validYearLotItemFormat": true,
"parsedYearLotItem": [
2026,
12,
3
]
}
}Limitations and assumptions
Empty or oversized requests error. Format validity does not establish identity uniqueness or ownership.
Numbers and computed results must be finite; overflow produces an error. 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 Duplicate Accession Conflict Detector: Detect exact strict accession identity conflicts across source rows without silently normalizing malformed identifiers; no conflict resolution or ownership decision. For a complementary task, use Lot Number Next Available Finder: Find earliest unused lot in a declared accession year from actual strict item identifiers, allowing multiple items per lot; does not allocate or reserve a concurrent database identity.
References
Similar or alternative tools
- Duplicate Accession Conflict Detector
Detect exact strict accession identity conflicts across source rows without silently normalizing malformed identifiers; no conflict resolution or ownership decision.
- Lot Number Next Available Finder
Find earliest unused lot in a declared accession year from actual strict item identifiers, allowing multiple items per lot; does not allocate or reserve a concurrent database identity.