This would change the Restaurant Inspections API to the Health Inspections API.
If the model (db columns) are the same, the first step could be as simple as adding more csv file targets to the cron task (url for hotel csv data).
I would create a separate cron job for hotels, just so that the restaurant data crawling can finish and then we can scan the hotel data.
Also, it would be great to rename the project (Health Inspections API? something else?) and rename the namespaces as well (to something shorter, even.. right now it's restaurant-inspections-api which is super long) when this change lands.
And last, one of the database tables is called "restaurants", whereas we expose the concept of "businesses". After we figure out if this information is actually info on the "license" or "business" we should rename the restaurant model to business or license.
See http://www.myfloridalicense.com/dbpr/sto/file_download/public-records-lodging.html
This would change the Restaurant Inspections API to the Health Inspections API.
If the model (db columns) are the same, the first step could be as simple as adding more csv file targets to the cron task (url for hotel csv data).
I would create a separate cron job for hotels, just so that the restaurant data crawling can finish and then we can scan the hotel data.
Also, it would be great to rename the project (Health Inspections API? something else?) and rename the namespaces as well (to something shorter, even.. right now it's restaurant-inspections-api which is super long) when this change lands.
And last, one of the database tables is called "restaurants", whereas we expose the concept of "businesses". After we figure out if this information is actually info on the "license" or "business" we should rename the restaurant model to business or license.
See http://www.myfloridalicense.com/dbpr/sto/file_download/public-records-lodging.html