We have a rolodex system that I am considering refactoring a bit and I’d like to make sure the approach is sound. Basically a common need we are starting to see is to have base tables for certain things, like companies or people, that need to be worked with in different contexts with different additional information and processes.
What’s the best practice for extending a table with additional information? In programming a typical example would be in database where you might have an account table with very basic information like id, email, and then additional tables for context-specific information about that account, like account settings, or account login links, etc.
I believe the main way to do this in Coda would be with additional tables that have a lookup to the base table, and then add any additional information needed for that other context.
I put together an example of this to illustrate and perhaps help others, but I just wanted to see if there are any big problems with this approach or other, better approaches that I am overlooking. Thank you!