Currently, users can use the advanced search form without choosing a borough.

Let's require them to choose a borough from the dropdown menu. Also, set "Bronx" as the default value, just like in the homepage's search form.

See Issues #23 and #26

• Make input field for restaurant name the biggest.
• Decrease size of other input fields.
• Add input validation. Mainly for ZIP code.

Let's reduce page load times by delivering images, etc. with CDN. AWS S3 and Cloudinary are two options.

I'm leaning towards Cloudinary. It has a free tier. Plus, it can deliver optimal image formats (WebP and JPEG-XR) to supported browsers.

Divide cuisines into optgroup via http://materializecss.com/forms.html

Examples: Popular food; ethnic food, Asian food ...

Issue #7

Let user search for restaurants by parameters (i.e. business name, borough, cuisine, street address, critical/not critical violations, etc.) Related to Issue #3.

As @OmenwolF suggests, we can replace Handlebars.js with React, converting the website into a single-page application. The goal is to reduce server requests for site rendering.

When users search for a restaurant's records, the server should look for those records in the Redis cache first. If the records aren't there, only then would the server send a GET request to the external NYC Open Data API. This decreases the number of HTTP requests sent to the API.

Let's use Socrata functions for querying inspection records by restaurant name or partial search term. The Socrata Open Data API is available for open-government databases maintained by NYC and other governments. Related to Issues #8 and #12

Currently, server.js returns up to 999 records that match query parameters such as borough and zipcode. server.js then filter those results by the name search term.

This process is flawed. The user might be looking for a restaurant that's not among those first 999 records.

The Socrata "like '...'" function solves this problem.

There is a specific endpoint for making queries with Socrata: https://data.cityofnewyork.us/resource/9w7m-hzhe.json

Query strings must be all uppercase. Ex. https://data.cityofnewyork.us/resource/9w7m-hzhe.json?$where=DBA like '%25SUSHI VILLAGE%25'

If user searches for restaurants like Katz's, Socrata throws an error.

That's because in SoQL, string literals are created using a single quote ('). Socrata documentation says: "To escape a single quote within a string, double it."

Let's check if a name contains a single quote. If it does, then add another quote mark.

Related to issue #15.

When users search for a restaurant by submitting only part of its name, the API should still return results. Ex. "Panda King " should return "Panda King Restaurant".

Currently, users must submit a restaurant's exact name, or they get a "no matching results" error.

Related to issue #7.

Improve page-load speed by replacing jQuery with vanilla JavaScript.

morgan is set to 'dev' mode but runs on production

the issue arose during artillery.js test run and required middleware to be commented out due to a reduction of 12 RPS

Add links to NYC government site where users can file complaints against restaurants.

https://www1.nyc.gov/apps/311universalintake/form.htm?serviceName=DOHMH+Food+Establishment
http://www1.nyc.gov/nyc-resources/service/1723/food-safety-or-poisoning-complaint

Add routes for accessing and searching NYC's restaurant inspection database. Include calls to Yelp API. Related to issue #5.

Return records for restaurants near users' current location. This works only if users allow browser geolocation.

Add active class to <li> tag in navbar to denote current page that user is on. Like this: <li class="active">

active is from the Materialize library.

Make map with Leaflet.js or Google Maps. Related to issue #3.

Related to Issue #2

Results page are no longer being rendered due to a change on the OpenNYC database

borough column is now empty

Make templates for displaying search results. Use EJS or Handlebars.

Pages would list health inspection results for popular NYC restaurants.

Materialize v1.0.0 doesn't need jQuery as a dependency. (See issue #34)

v1.0.0 cuts these dependencies: jQuery (84kb), Hammer.Js (21kb) and Roboto font. See Materialize team's blog post on Medium, "Materialize: To 1.0 and Beyond".

Get Yelp ratings and other restaurant information. Related to Issue #2.

Let users make searches with additional parameters (ZIP code, cuisine, etc.) This form would be different from the homepage's basic search form. It should be on its own page.

Should it have its own API route? Or should it still use the existing POST /search route?

See issue #23

Visitors see a new background image each time. Make homepage look fresh and new. Because variety is the spice of life.

Let users search restaurant by name in search bar.

Currently, users can use the search form on the homepage without including a restaurant name.

Let's require them to include a name in the search form. This is similar to the Better Business Bureau search form.

If they submit a query without a name, a modal with an error message should pop up. This is also similar to BBB's form.

See Issue #23

Currently, API returns a maximum of 999 reports per search. This can lead to unexpected results. Some examples:

• If a user looks up "sushi" as the business name without giving additional parameters, the API returns a "no results found" error.
• Searching for "Sushi Village" in "Queens" returns no results. But a search for "Sushi Village" in "11358" does return results.

The NYC database does not have a restaurant's neighborhood (this would be the city/town in the mailing address.) It only has the building number, street name, ZIP code and borough.

This isn't helpful to users. Let's add neighborhood names to search results. Perhaps by using Google's geocoding API.

Related to issue #2