Text matching to node destinations

This is not, strictly speaking, a Counter issue at present. But as we go through our OLab3 redesign, it will probably become so.

In OLab2, there is the option to ask the user to enter an answer, which is then compared with available destination nodes. If a match is found then that node becomes the new current node.

For example, the possible destinations from this node are "Able", "Baker" and "Enabler". These destinations were chosen for the overlap in the word "able". We are working on improving how OLab3 assesses text entered into 'type in text' Link Functions.

In my mind, if the user were to type the word "abler", OLab should match to 'Enabler' because at least part of the destination node name "Enabler" is a match. At first in OLab3, a match is made with 'Able', presumably because "able" is part of "abler" - i.e. the partial match logic is applied the wrong way round, to part of the entered phrase, not part of the destination. Am I making sense in trying to explain this?

Hmm, now since some further fixing on 11/2/13, this text matching to destination nodes is not working at all, even for unambiguous node names e.g. 'Baker'. Still some work to do here.

If you have further thoughts on how this partial text match should function, contact us at info@openlabyrinth.ca

Test out our text matching by trying various answers below. (Note that at least 4 letters are required. "ble" or "ab" will not work.)