Description
Compare recordDay with effectiveDay using ≥ for inclusive or > otherwise.
Metadata obligations and relations apply to a declared record scope. Field presence, source coverage, cardinality, and value correctness are independent properties.
Compare recordDay with effectiveDay using ≥ for inclusive or > otherwise.
When to use this tool
Use Controlled Vocabulary One Deprecation Date when you need a narrow metadata consistency or coverage check.
How to use the tool and how it works
- Enter recordDay, effectiveDay, inclusive, replacementPresent. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read deprecated, replacementApplicable. Inspect deprecated, replacementApplicable before interpreting the associated values.
Compare recordDay with effectiveDay using ≥ for inclusive or > otherwise. Mark replacementApplicable only when deprecated and replacementPresent.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordDay | Record Day | Required. Safe integer. |
| effectiveDay | Effective Day | Required. Safe integer. |
| inclusive | Inclusive | Required. Boolean. |
| replacementPresent | Replacement Present | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| deprecated | Deprecated | Required. Boolean. |
| replacementApplicable | Replacement Applicable | Required. Boolean. |
{
"input": {
"recordDay": 20,
"effectiveDay": 20,
"inclusive": true,
"replacementPresent": true
},
"output": {
"deprecated": true,
"replacementApplicable": true
}
}Limitations and assumptions
- This applies a supplied date threshold without validating a replacement identifier or a vocabulary's actual deprecation policy.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Apply the complete metadata profile and inspect field values and provenance before accepting a record.
References
Similar or alternative tools
- Metadata Field Obligation Flag
Set obligationApplies when both inScope and required are true; missingRequired additionally requires present false.
- Metadata Source Coverage Share
Deduplicate requiredKeys, count those present in sourceKeys, and count those present in both sourceKeys and verifiedKeys.