---
# System prepended metadata

title: Doodle - City of Data

---

# Doodle - City of Data

## Wajahat Afzal

**Codepen Link:** https://codepen.io/wa2280/pen/GRyGqjo?editors=1010

**Firebase database:**
![](https://i.imgur.com/tqwdW76.png)

For this doodle, I've tried to convert a scene from the Hungarian Pastry Shop into a set of data. I've defined "customers" as a collection where each "customer" is a document with the fields:
* name: ""
* orderRequested: []
* orderReceived []
* billAmount: num
* billPaid: boolean
* timePassed: num

*To interact with the web application, click on the "customers" represented by different colors.*

I chose to put the data together instead of making a collection of menu items with each menu item being document, and the customers who have ordered each item being mentioned as an array field. I chose to do this since I could foresee that something like this might be used by the cafe/restaurant staff to check the status of each customer first before anything else. From here on, it may become easier to filter which customers have ordered a specific item, which customers have not paid yet, which customers have an incomplete/incorrect order, etc.

In later stages, I see users having the ability to update the data for each customer e.g. adding more items to `orderRequested` or `order
Received` and toggling `billPaid`. A method can update the `timePassed` field with every passing minute which could inform the users decision regarding which customer to address first, etc.