Skip to content

Main content

Validation: DOI Prefix Single Field Check Tool

Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.

Loading tool…

Description

Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.

Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.

Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.

When to use this tool

Use Validation: DOI Prefix Single Field Check when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.

How to use the tool and how it works

  1. Enter prefix. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Check prefix against 10. followed by four through nine ASCII digits. Return prefixShape and registrationVerified false inside result.1

Input fieldMeaning and unitsAccepted input
prefixPrefixRequired. Text.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
json
{
  "input": {
    "prefix": "10.1000"
  },
  "output": {
    "result": {
      "prefixShape": true,
      "registrationVerified": false
    }
  }
}

Limitations and assumptions

  • This is the tool's lexical prefix subset only. No registrar lookup, allocation verification, DOI suffix, resolution, or publisher metadata is checked.
  • Outputs are nested inside result. The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.

Alternative or Complementary methods

Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.

References

  1. Calculation and input contract: validate/doi-prefix-single-field-check — tool.io

Similar or alternative tools