Feat/data model

[jusdino]

Description List

• Updated data model to reflect latest understanding
• Official first API version (v1)
• Updated lambda authorization logic to tie staff permissions with data access

Testing List

• Code review
• I'm happy to do a demo if needed

Closes #
#84

[jlkravitz]

• review the pull request to get oriented
  • read the description of the pull request, which should summarize the changes made
  • read through every task on the Scrum board that's encompassed by this pull request
  • read the description of the commits that comprise the pull request
• skim all new code, in the context of existing code, looking for problems (knowing that the vast majority of new code will be covered by tests)
• review all tests
  • methodically review all new tests for correctness, quality of naming
  • look at code coverage of tests
  • determine what code isn’t tested, review that rigorously
• review documentation to ensure that it matches changes
• provide comments on the pull request on GitHub, as necessary
  • for comments that are specific to a particular line of code, comment on those specific lines
  • for comments that are more general, attach the comment to a random line in README.md (as opposed to commenting on the pull request itself), to be able to use GitHub's ability to thread discussions on those comments
• run a security audit of dependencies (e.g. npm audit and pip audit) to ensure that there are no vulnerabilities that will be deployed to production (as opposed to vulnerabilities that only have an impact on the development environment)

[jlkravitz]

Woo! What an adventure. Great work on this generally: really thorough testing and documentation. Lots of little questions and nits, but hopefully we can get through them quickly tomorrow (Tuesday).

[jlkravitz]

@isabeleliassen This is good to merge!