1. Client wants a js/spry map and the spry checkboxes to work together (click the map & the corresponding checkbox automatically is checked & visa versa.)
2. We need to link the html page you worked on ([url removed, login to view]) with a search results page ([url removed, login to view])
3. There is a search details page that you probably will not need to work on but if you need it, it is ([url removed, login to view])
regarding item #2:
there are 2 searches. One that is a quick search using the field values shown when the collapsable panel is closed and the advanced search, that uses all the parameters EXCEPT the fields in the area dropdown will be overridden IF the map is used.
The contents of the amenities field will need to be buffered & EXPLODEd to (it is comma delimited within the field.)
I created a new db with one main table that contains 55 fields (columns) fed to us by NYC MLS.
There are 5 additional field that are automatically added
1. num (primary)
[url removed, login to view]
There is another important table : zipcodes
zipcodes lists all zipcodes in Manhattan and (a) matches them to 10 neighborhoods and to 6 sections that are provided in the MLS feed (in the main table described above.)
BTW you are right about the searches. There are no queries yet.
The exploded field "amenities" contains many of the search parameters such as 'garage, health club, laundry room, storage room, etc.' I have attached an excel spreadsheet containing a typical feed parsed out.
There is an identical table "featured" (identical to the 55 field main table (idxfeed)
This is for featured listings not listed with MLS.
Both tables have a field 'copyright_info'. The MLS feed ALWAYS has data in that field. The 'featured' table NEVER has data in that field. The idea is to join the tables and do a sort for any query results that show featured properties before MLS listed properties.