Description
Return dependencyActive=triggerPresent&&triggerMatches and satisfied when either the trigger is inactive or dependentPresent is true.
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.
Return dependencyActive=triggerPresent&&triggerMatches and satisfied when either the trigger is inactive or dependentPresent is true.
When to use this tool
Use Field Dependency Activation Flag 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 triggerPresent, triggerMatches, dependentPresent. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read dependencyActive, satisfied. Inspect dependencyActive, satisfied before interpreting the associated values.
Return dependencyActive=triggerPresent&&triggerMatches and satisfied when either the trigger is inactive or dependentPresent is true.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| triggerPresent | Trigger Present | Required. Boolean. |
| triggerMatches | Trigger Matches | Required. Boolean. |
| dependentPresent | Dependent Present | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| dependencyActive | Dependency Active | Required. Boolean. |
| satisfied | Satisfied | Required. Boolean. |
{
"input": {
"triggerPresent": true,
"triggerMatches": true,
"dependentPresent": false
},
"output": {
"dependencyActive": true,
"satisfied": false
}
}Limitations and assumptions
- All three booleans are supplied facts. The tool neither compares actual trigger values nor validates dependent content, and an inactive trigger imposes no presence requirement.
- 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.
- GS1 AI Fixed Field Leading Zero Preserver
Preserve a supplied field verbatim while checking numeric fixed width and counting its leading zeros.