Today, we’re trying to solve the problem to localize the names of the objects in our platform.

We’ve created an internal naming convention. So each object gets two names:

  • Our internal name, which follows the rules described in the object categorization page.
  • The public name, which is generated by the system based on the location of the property and our internal name.

This allows us to have a homogeneous naming acrosss all objects in the system, while showing the clients the name that makes more sense to them.

Let’s see this with an example, the theater set in Hilton London Metropole. We set up the object using our internal naming convention, that is just “Theater”:

Now the system is able to infer the best name based on the location of the property. As this hotel is in the UK, it’ll assume that Theatre is preferred over Theater, so this is what’s shown on the public side:

Note that it’s displaying “Theatre Set” rather than just “Theatre”, this is useful when we use the object name in the model progress timeline so the object can be distinguished from the Theatre Layout.