Description
Extract the two-digit ISRC year-of-reference field from a strict twelve-character uppercase identifier; does not infer a century or recording year.
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.
Extract the two-digit ISRC year-of-reference field from a strict twelve-character uppercase identifier; does not infer a century or recording year.
When to use this tool
Use Validation: Isrc Year Field Extractor 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
- Enter isrc. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Require the implemented compact ISRC shape of two uppercase letters, three uppercase alphanumeric characters, and seven digits. Return positions six and seven as yearDigits and centuryResolved false inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| isrc | Isrc | Required. Text. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Result | Required. Object. |
{
"input": {
"isrc": "USRC17607839"
},
"output": {
"result": {
"yearDigits": "76",
"centuryResolved": false
}
}
}Limitations and assumptions
- The two-digit year is not expanded to a century. Prefix allocation, recording existence, metadata, rights ownership, and whether the code was correctly assigned are not verified.
- 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
Similar or alternative tools
- Validation: DOI Prefix Single Field Check
Check the commonly specified DOI registrant-prefix lexical shape only, without validating a suffix, registration or resolution.
- Field Dependency Activation Flag
Return dependencyActive=triggerPresent&&triggerMatches and satisfied when either the trigger is inactive or dependentPresent is true.