Define schema to store app data
Types of data:
- Hotel data: This will have a predefined shape and is relatively easy to model.
- External sources (weather, flights, ect...): We don't need exact tables for these yet but how can we generalize a pattern for external sources? Will they all live in separate tables? Do we have to change the schema on a case by case basis? How can we avoid redundancy and having to create table on each new factor?
- Model output (ex. mapping hotel room to price): This is yet to be decided so no need for a schema but just keep in mind we will need this in the future.
Acceptance criteria:
- Pydantic + SQLAlchemy models for hotel data
- Documentation for how to approach external factor data
- Explain what data is there and how it can be useful
- Be ready to present findings next meeting (09/23)
Define schema to store app data
Types of data:
Acceptance criteria: