Renaming "Organisation" to "Domain"

[pascalwhoop]

Would you be open to rename the organisation to "domain" as this seems to be a more common term we've come across at organisations. The "data domain" concept fits better IMO.

[louishourcade]

Hello,
An Organisation in data.all is just of group of Environments. An Environment itself corresponds to an AWS account (and a region). So you can see the Organisation as a group of AWS account, hence the name of Organisation which reminds how customers already manage their fleet of accounts with AWS Organisation.

In my opinion, changing the name to Domain might negatively affect customers that are already using data.all (because they are used to this name, their data.all database is filled with objects using the "organisation" naming). Also, the team is currently focused on adding missing features and fixing the bugs we encounter.

However, if you believe that changing the name is important for your usage, then you can do it on your own branch. Maybe you can implement some king of "switch" that you can put in the config file. In this way, existing customers won't be affected, but new customers that prefer "Domain" over "Organisation" can edit the config to see the change appearing in the UI/database.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[pascalwhoop]

Alternatively how about adding a layer between the conceptual terms and the UI so that people can write whatever they want in a translation file? This may also be needed for internationalisation anyways since multi language support needs to disconnect UI code from UI strings. Then we could name the concept whatever we (or others) would want. +=============================================================+ This email is confidential and may be privileged. If you have received it in error, please notify us immediately, delete the email, and do not copy it, disclose its contents or use it for any purpose. +=============================================================+

[louishourcade]

Could be an option. Does it mean having a different name for the object in the UI (the name you set for your users) and the name of the database field (which remains "organization") ?

[pascalwhoop]

Yes that could be a way to do it indeed. One could also abstract the name in the data model to “org level 1-3”. But I think a default set of terms is also valid. We’re alternatively thinking to leverage a future i18n framework to map terms to the three levels. That may make the entire application quite customisable regarding strings while keeping companies able to stay in sync with upstream since the content is not interwoven with the code base.

…

On 29 Jun 2022, at 21:01, Hourcade ***@***.***> wrote:  Could be an option. Does it mean having a different name for the object in the UI (the name you set for your users) and the name of the database field (which remains "organization") ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.