I just ran through our "simplified parent-teacher conference" example in Airtable. It looks like the main things Object Spreadsheets has and Airtable doesn't a

I just ran through our "simplified parent-teacher conference" example in Airtable. It looks like the main things Object Spreadsheets has and Airtable doesn't are: 1. Object nesting for the purposes of the spreadsheet UI and cascading deletion. 2. Computed fields that return a set of object references (as real references that can be a starting point for further formulas, not just a string of comma-separated names), which we use to implement the "availableSlot" field in the example. 3. Computed object types, which can be used to map a formula over a set of values returned by another formula, keeping everything in context (as opposed to defining a separate database view). These are not used in the simplified parent-teacher conference. An example can be seen in the "view model" of the full parent-teacher conference, but a better example that demonstrates the need for them is described in section 4.4 of our paper (http://sdg.csail.mit.edu/projects/objsheets/objsheets-onward2016-preprint.pdf http://sdg.csail.mit.edu/projects/objsheets/objsheets-onward...). Many of the other tools we have tested, including Knack, Intuit QuickBase, and Microsoft Access, are also missing these three features.