"Uber Search" or "Federated Search"

If you have access to https://prdoas2.apps.th.gov.bc.ca/cwm/ you can see this in action. The search in the upper right hand corner queries the DataBC address geocoder, our "RFI" road layer as well as any layer from our CHRIS system which is visible.

The original idea is from Tobin Bradley's blog post http://fuzzytolerance.info/blog/2012/07/27/2012-07-27-screencast-15-ubersearch/ and I believe the better known name is "Federated Search". The difference in our implementation is that the federating is done not on the server, but on the client using Twitter's Bloodhound javascript library.

Start by reviewing the upper-right search in the linked CWM example and the client-side use of Twitter's Bloodhound library. Determine the intended federated-search scope across the DataBC address geocoder, RFI road layer, and visible CHRIS layers, then define acceptance criteria before implementation.

Written by the indexing model from the issue text.