# Alias for entities **URL:** \ **Category:** Ideas & Features\ **Created:** [May 8, 2023, 1:17pm UTC](https://community.fibery.io/t/alias-for-entities/4427 "2023-05-08T13:17:34Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [October 22, 2023, 1:50am UTC](https://community.fibery.io/t/alias-for-entities/4427/6 "2023-10-22T01:50:05Z")
This is a very interesting idea. I think aliases are very helpful and important when you are trying to manage knowledge rather than just build a databased based tool. CIDOC-CRM, an ontology that is used for cultural heritage, has an entity called [appellation](https://www.cidoc-crm.org/Entity/e41-appellation/version-6.2) which I always found very interesting an instructive since not only does it allow different names to be associated with the same entity, but it also allows for more context for how that name applies, things like the language/context/place where the name is used, the period that name was in use, … . This is a very specific application of a knowledge graph. We had some discussions on this here: > [@Anytype — Interesting app concept for PKM and teamwork](https://community.fibery.io/t/anytype-interesting-app-concept-for-pkm-and-teamwork/2085/22): > > Appellation/Name Discussion This is exactly what I ended up doing with guidance from @Chr1sG (see [Siblings as children of parents filter](https://community.fibery.io/t/siblings-as-children-of-parents-filter-self/981/6)). However, it seems rather hacky to me, partly due to some limitations of formulas and need for a few intermediary fields. How this looks in the fibery UI also leaves a lot to be desired (I know the new layout will greatly improve this): But I also feel I need to be able to this more universally/consistently for more entities such as places, people… While not exactly the same thing, I think being able to describe relationships between entities in the system that are basically fragments of the same thing (e.g. a contact in CRM, an employee in HR database and a user in the authentication database contain fragments of information about the same person): > [@"Same as" relationship](https://community.fibery.io/t/same-as-relationship/513): > > Hi everyone, I am trying to work out what is the best way of setting up entities which represent the same thing (but with different types of detail). For example employees who are also Fibery users. At the moment, I am working on setting up the various apps and testing them myself before rolling it out to other members of our team. As time goes on and more of my team work on the system, which means some (but not all) of the employees in the Employee Management app would also be users. I would … --- _[View the full topic](https://community.fibery.io/t/alias-for-entities/4427)._