Schema/API Design Comments Ian McCurry

[ianmccurry11]

1. ERD says one and only one user per list but you can create many lists per user
2. schema order is not correct with foreign key ties
3. APIs have almost all data coming in from url when not necessary like POST for crowdsourcing
4. /lists/stores/ is a POST call instead of a GET call
5. /lists/stores/{list_id}/best should be GET
6. crowdsourcing/{posting_id}/delete is bad naming convention and should just be crowdsourcing/{posting_id}
7. APISpec.md isnt correctly formatted
8. better names for the "id"s in all the tables to help specify what idea youre talking about is a good idea (i.e. item_id, user_id)
9. "Create a new grocery list" API says it takes no input. But it requires a user_id
10. inventory should just be an int instead of text, because inventory_level doesnt get changed and is too vague
11. more descriptive names for table variables like "name" (i.e. store_name, user_name)
12. no API to create users