Is there aliasing in the search bar? Or whitespace handling?

[JohnnyD-Rage]

Specifically, something we struggle with in the shop is searching for things like "0.1 µF". Most people don't know the keystroke for the "µ" character and are used to using "u" in place. It doesn't seem like PartDB can alias things like this, so a suggestion one of my techs had had was to put the aliases in all the part notes. Seems messy.

Similarly, if you put "0.1uF" versus "0.1 uF" you get very different results. With suppliers following different schemes for the part description, this gets a bit challenging. I assume this is just a problem of data sanitization, but I wanted to see if anybody had any suggestions to clean this up?

Another question is the conversion between things like 100nF and 0.1 µF. I know that would be a pretty complex problem, but I figure it's worth asking if this is something that can be done?

[virtadpt]

Yes, please. I have a wiki page that has a µ character available to copy-and-paste for this very reason.

[jbtronics]

The "extensive search" mode since the most recent work might help with that, as then the full search string does not has to appear in a single field. But ultimately its ultimately very hard to do search normalization in a more semantic way.

Sqlite by design also has some issues with the different unicode versions of the micro symbol, and does not treat them as equal when searching, that can also lead to unexpected behavior. But that is an limitation of Sqlite.

[JohnnyD-Rage]

Thanks Jan. It looks like the "extensive search" will help with the whitespace issue.

I figured the aliasing problem would be too complicated, but I figured I would ask — just in case!