HMDB Accession Validator

Validate an HMDB accession against a caller-specified numeric width.

Description

HMDB accession screening checks a fixed-width numeric suffix after the uppercase prefix.

HMDB accession screening checks a fixed-width numeric suffix after the uppercase prefix. Identifier width is a supplied format rule.^[1]

Validate an HMDB accession against a caller-specified numeric width.

When to use HMDB Accession Validator

Use this tool to validate an HMDB accession against a caller-specified numeric width.

Prepare the measured profile, formula counts, upstream model outputs or caller-defined reference criteria requested. Keep paired entries aligned and units, sample basis and preprocessing consistent.

How to use HMDB Accession Validator and understand its results

Prepare the measured profile, formula counts, upstream model outputs or caller-defined reference criteria requested. Keep paired entries aligned and units, sample basis and preprocessing consistent.
Enter accession, digitsRequired using the field table and calculation rules, then run the tool.
Read valid, numericId. 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
accession	Accession	string	Required
digitsRequired	Digits required	number	Required

Enter text and safe integer digit count from 1 through 15. No trimming occurs. Return format flag and numeric suffix, with zero as an invalid-input placeholder.

valid=matches HMDB followed by exactly digitCount digits

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

Output field	Meaning	Value type
valid	Valid	boolean
numericId	Numeric id	number

json

{
  "input": {
    "accession": "HMDB0001234",
    "digitsRequired": 7
  },
  "output": {
    "valid": true,
    "numericId": 1234
  }
}

Limitations and assumptions

No HMDB record lookup, metabolite identity or accession-version validation is performed.

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 KEGG Orthology Validator: Parse and validate KEGG orthology identifiers. For a complementary task, use Inchikey Format Validator: Validate the syntactic InChIKey block lengths and separators.

References

HMDB Accession Validator — tool.io

Similar or alternative tools

KEGG Orthology Validator
Parse and validate KEGG orthology identifiers.
Inchikey Format Validator
Validate the syntactic InChIKey block lengths and separators.