From 8cb1d11e409572ac21de2325624a273587e3017e Mon Sep 17 00:00:00 2001 From: mikael-lovqvists-claude-agent Date: Sun, 22 Mar 2026 15:02:32 +0000 Subject: [PATCH] future-plans: measurement dimensions and unit conversion Co-Authored-By: Claude Sonnet 4.6 --- future-plans.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/future-plans.md b/future-plans.md index eca64ec..2f03936 100644 --- a/future-plans.md +++ b/future-plans.md @@ -126,6 +126,19 @@ Currently all field values are free-text strings. Typed fields (numeric, enum/dropdown) would enable better formatting, validation, and range-aware search. Prerequisite for parametric search with range operators. +#### Measurement dimensions and unit conversion +Instead of a bare unit string on a field, associate a field with a measurement +dimension (e.g. `temperature`, `resistance`, `frequency`, `voltage`). The dimension +defines the set of valid units and the conversion factors between them (°C, °K, °R, +°F for temperature; Ω, kΩ, MΩ for resistance; etc.). + +This would allow: +- Entering values in any compatible unit and storing in a canonical unit internally +- Displaying in the user's preferred unit +- Parametric search with cross-unit comparisons (e.g. `temp_range > 200K` matching + a component with `temp_range = -73°C`) +- Catching unit mismatches at entry time + ## PDF / files ### File picker search filter