Depending on the decision for issue #11, the Django API functions will work differently. If we have decided to not do a .exe file, we can just create one HTTP request function to initialize scraping and channeling the output from the scrapes directly into our database with Django's ORM model. If we decide to use a .exe file, we probably have to create multiple API functions to handle the output from the scraping differently depending on which source we scraped them from. ** The key idea behind the functions is to convert the json data into the django models before sending them into the database. We might include some logic behind how we will update key entities like providers and sites to solve the chicken-egg problems
Depending on the decision for issue #11, the Django API functions will work differently. If we have decided to not do a .exe file, we can just create one HTTP request function to initialize scraping and channeling the output from the scrapes directly into our database with Django's ORM model. If we decide to use a .exe file, we probably have to create multiple API functions to handle the output from the scraping differently depending on which source we scraped them from. ** The key idea behind the functions is to convert the json data into the django models before sending them into the database. We might include some logic behind how we will update key entities like providers and sites to solve the chicken-egg problems