Optimizing Coda Databases: Normalization and Data Management

2

Hi Kavya,

I wouldn’t suggest this approach. While it might seem redundant that not all columns are used by each person type, the “View” concept in Coda makes it not-an-issue.

I would typically set this up as:

  • People DB table which is on a hidden page, or not obvious
  • People page with a People view of the People DB table tailored for that person type (irrelevant columns hidden, etc)
  • Volunteer page with a People view of the People DB table tailored for that person type (irrelevant columns hidden, etc)
  • etc

You can also create different detail views, or forms for the table which is relevant for each of the person types.

Separating out into different tables and then trying to join them on things like name (or even email which would be better) is not ideal and becomes difficult to manage and run reports on in the future.

2 Likes