I'm passing along an issue from one of our archivists regarding the typeahead search feature. It doesn't seem to behave as expected. I'm not sure if this is a failure of the indexer, or an issue with the length of the strings and how the typeahead feature works with multiple search terms, or a combination. In the example below, the archivist is searching for a specific collection entitled "Miscellaneous Photograph Collection". I would expect the typeahead to display that result fairly early as the user enters the terms, probably by the time they've reached "miscellaneous pho".
![](https://lh3.googleusercontent.com/-0m_wgF5kL-0/WEsI5iChPdI/AAAAAAAAABQ/0pibOKrwpfcjJxJEjYC4lbgq9Tgk7wdPwCLcB/s1600/atom-search-mis.PNG)
Begin searching. The typeahead works...
![](https://lh3.googleusercontent.com/-k8S7BtU7xJs/WEsJXRQKIyI/AAAAAAAAABU/627GUcjrnvkJvWbcoFQGgOP1_oH7fxVXQCLcB/s1600/atom-search-miscellane.PNG)
![](https://lh3.googleusercontent.com/-2qV7Bm5l5RQ/WEsJgoIlynI/AAAAAAAAABY/ViCmAOGz9IEdjxwTKhYR3sVPLJ2O0nFdQCLcB/s1600/atom-search-miscellaneo.PNG)
... for the first 10 characters, until we type the 11th character and then it disappears.
![](https://lh3.googleusercontent.com/-Uqw_y0gg_3Y/WEsJ2BY3gPI/AAAAAAAAABc/4k_j_HFeI6QmYDXhCUKB1sBA7stWHM9ZQCLcB/s1600/atom-search-miscellaneous-pho.PNG)
Continuing, we expect it to turn up the desired description, at least somewhere in the top 3, but it doesn't (is it completely ignoring "miscellaneous" at this point?).
![](https://lh3.googleusercontent.com/-5TQBMXis8lg/WEsKa6mQtiI/AAAAAAAAABg/u6CRMRssOzQS7qf9DQ8njTshUF3JbohIgCLcB/s1600/atom-search-miscellaneous%2Bphotograph.PNG)
Continuing with "photograph", then "coll", still no consideration for "miscellaneous".
![](https://lh3.googleusercontent.com/-lGhiTwtnl00/WEsLL_J2J0I/AAAAAAAAABs/-fT9QDJqpZEHjOJ9FE4UsRtgKw32PpGTQCLcB/s1600/atom-search-miscellane-photo.PNG)
Yet, searching for "miscellane photograph", with only the first 10 letters in "miscellaneous", brings up a match in the typeahead (3rd from the top).
Is this a known issue, or a configuration change that can be made to fix it?
Thanks,
Damian