User case : user from Notion, with multiples database. In Notion, each database has its own properties (relations) and pages (objects). In AT, a relation or an object are in AT.
In practice, this poses organizational problems and, with the multiplication of data, will tend to create a big “mess”.
- All relation will be visible everywhere, all the time. If you have 50 databases with dozens of relations (usually specific to the db), you’ll have a list of 500 relationships to manage (add relationship → search the list…). If a relationship has the same name in different places, too bad, the relation list will display the same name several times.
- The same goes for objects and type (the person I spoke to gave me a nice explanation of the problem, but I forgot).
Hence the need to localize data that is of no interest at a global level.