Define User Data

[gordonkoehn]

Define the data we have about a user.

• What information is helpful for the matching?
• What information do we need for accounts /authentication?

[Philnue]

https://dbdiagram.io/d/653ceb27ffbf5169f0a2027a)

[Philnue]

https://supabase.com/docs/reference/python/initializing

https://planetscale.com/

@flalom @gordonkoehn

[gordonkoehn]

• Name
• email
• password
• Location
• Timeslot

[gordonkoehn]

• Department (to exclude)

[Philnue]

The password and maybe email should be stored to the auth provider not in plain db

[flalom]

Interest, Age?

[Philnue]

We could use supabase for db and auth. Then we have a solid background and it is simple

[gordonkoehn]

• Conversation Preference: Light Lunch Banter / Professional Get to Know and Collaboration

[Philnue]

Interest, Age?

Yes, lets talk for it later when we a reworking for the db part

[flalom]

perhaps additionally, data on familiar status (married, children)? It could be interesting for matching

[flalom]

https://excalidraw.com/#room=f49968a90961dd28e2d3,dNmKi_XLHe6T1Cg3yMPBWA

[flalom]

https://github.com/TobiasSchaeuble-EH/LunchHeroes