Improve/build a Joomla & Mosets Auto Suggestion Search Module

Project: Improve performance of existing developed auto suggestion Mosets Search module, correct so it works in Joomla 3.3 and Mosets 3.5. Joomla 2.5.8, Joomla 3.3, Mosets 3.0.9, Mosets 3.5 - Time & Cost Critical We commissioned a bespoke search module based on the standard Mosets search module. This was built to add extra functionality to the search of Mosets. However the development team could not finish the job due to limitations, however the principle works and can be seen at (Joomla 2.5 site - [login to view URL] Site Admin: username : medemo2 Password : ylt_2014_dev, e.g. type in tennis) . We are requesting a team/individual to improve an already created module in good time/time critical. We would like the efforts that have been completed so far to be used as reference but would like the best solution for a fast accurate search with auto suggestion and use a reference list. We also would like the search to take into account a list of words which we do not want to limit the results returned, e.g. the, it, a, and, '&' and so on. if a user types in 'The Tennis Centre' or 'a tennis centre' we would like the results to show results with and without these words, any order. Requirements We have two identical sites, one in the joomla 2.5 and mosets 3.0.9 where an existing bespoke search module works, but not as we would like, very slow and the search is not accurate, we also upgraded this site to joomla 3.3 and mosets 3.5 where the bespoke search module is in place from the upgrade, but doesn't work due to upgrade. A bespoke search component (Appendix 4) was created and a bespoke component to enter details into a table u7zk0_mt_itcs_referencerelation (table exists since upgrade, but component is not linking correctly in backend Error 404, should be a simple correction). In the component in the backend we assign a 'Reference Name'. In the listing details a corresponding Mosets 'Custom Field' 'Activity field' is available at the bottom and populates automatically dropdown items (Appendix 3). When a user enters Zorbing for example in the the front-end the results automatically displays 'Reference Names', 'Reference Variables' and 'Listing Names' that meet users typed in words. Basically if a reference variables is selected or entered into the field, the search will correspond that to it's parent, the 'Reference Name' and display all listings that have the 'Reference Name' in the the field. All 40,000 listings have a 'Reference Name' assigned to them, approximately 70 such names. In the component admin creates a 'Reference Name' and a list of corresponding 'Reference Variables'. The purpose of this list is to create a comprehensive search facility. In the 'Name' field on front-end, this data is drawn-in, auto suggestion displays the 'Reference Names' and 'Reference Variables' and also displays 'Listing Names' that meet users entry, placing priority to the 'Reference Name' in order and apply css styling to 'Reference Name', as this is a category (Appendix 1) and would like to highlight this to user. So if the user enters in the 'Name' field in the front-end a facility name (listing name) or a keyword, for example if a user starts typing tennis, the auto suggestion, shown in Appendix 1, displays the facility category first ('Reference Name'), which has the same words (tennis, 'Tennis Clubs & Centres' a 'Mosets Category' we have set it to correspond to the 'Reference Name'. Purpose to create a generic result, display all listings from that category, rather than a single facility if a specific listing name is not entered), followed by listing names that have the word tennis in, auto suggestion reduces as user types. Field 2 - location - Displays auto suggestion pulling data from the town, city, county and postcode Mosets fields and adds this to the name field when search is submitted. Issues with existing module that need to be addressed are highlight in attached document and NEED TO BE REFERENCED when considering this project.