Description
comparable requires literal quality === expectedQuality and unit === expectedUnit.
Archival comparability and coverage depend on source labels, time boundaries, verification assertions and common-unit conversions. Matching text or balanced totals can support record review without authenticating sources or proving completeness.
comparable requires literal quality === expectedQuality and unit === expectedUnit.
When to use this tool
Use Archival Price Quality Unit Token when checking a supplied archival record or support convention.
How to use the tool and how it works
- Enter quality, unit, source, expectedQuality, expectedUnit. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read comparable, key. Inspect comparable before interpreting the associated values.
comparable requires literal quality === expectedQuality and unit === expectedUnit. key = JSON.stringify([source,quality,unit]).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| quality | Quality | Required. Text; maximum UTF-16 length 8192. |
| unit | Unit | Required. Text; maximum UTF-16 length 8192. |
| source | Caller-supplied source label, not independently authenticated provenance. | Required. Text; maximum UTF-16 length 8192. |
| expectedQuality | Expected Quality | Required. Text; maximum UTF-16 length 8192. |
| expectedUnit | Expected Unit | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| comparable | Comparable | Required. Boolean. |
| key | Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"quality": "grade-A",
"unit": "kg",
"source": "ledger",
"expectedQuality": "grade-A",
"expectedUnit": "kg"
},
"output": {
"comparable": true,
"key": "[\"ledger\",\"grade-A\",\"kg\"]"
}
}Limitations and assumptions
- Matching labels do not establish commodity equivalence or source authenticity. The key preserves supplied text without unit conversion, historical interpretation or provenance verification.
- 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.
Alternative or Complementary methods
Inspect the original sources and document the historical meaning of labels, dates and conversion factors.
References
Similar or alternative tools
- Hormone Unit Form Reference Token
Compare unit with expectedUnit and molecularForm with expectedForm literally; matches requires both equalities.
- Historical Price Unit Factor
targetUnitPrice = quotedPrice*targetQuantity/sourceQuantity; provenanceKey = JSON.stringify([source,dateLabel,commodity]).