Domains are the primary classifications of Artifacts. In Luma Knowledge, domains are created based on the Organization’s structure. These can be based on departments, business units, geographical regions, teams, or any other classifications applicable to the organization. Luma Knowledge provides a list of general domains out-of-the-box. However, for every implementation, the organization’s landscape should be considered to create new Domains required to classify and manage Knowledge.
Why are Domains important?
Domains are the very first level of categorization applicable to the Artifacts. In Knowledge Graph, domains are the nodes created under Tenant and Sub Tenant nodes.
When Implementing Luma Knowledge for an organization, it is important that Domains are carefully created. Below are a few ways domains are used in the system.
Every Artifact in Luma Knowledge is curated under a specific domain. When an artifact is created, it is linked to the Topics structure available under the selected Domain.
An artifact’s domain is also used to identify relevant Knowledge for a user’s request. The ‘Domain-Topic-Artifact’ relationship forms the path of the artifact. ‘Path’ is one of the filters to find Knowledge from the Knowledge Base and is used to disambiguate in case, Artifact with a matching Topic is not found.
In Luma Knowledge, access permissions on the Artifact can be managed at Domain as well as Artifact level. Appropriate categorization ensures that the Knowledge is available to the correct set of users.
General Guidelines for Creating Domains
Following are a few guidelines for identifying domains:
Domains should represent the highest level of categorization of the organization. Use the category where the classification in your Knowledge starts.
For example:If your Knowledge is geography-based, use Regions/Countries/Geographies as your Domains. Such as APAC, EU, US, ANZ, Africa, etc.
If your organization manages its Business and Policies based on Business Units, use BUs as your domains. Such as IT, Aviation, Utilities, Networks, etc.
If your knowledge is categorized based on Departments, you can you Departments as your domains. for example, IT, Human Resource, Networks, Hardware, Finance, etc.
For a banking organization, you can use Financial services as domains. For example, Commercial banking, Investment banking, Insurance, Mortgage, etc.
Use the categorization known to the end-users. When accessing Knowledge, end-users can use the domain name to look for relevant knowledge. Do not use abbreviations or internal nomenclature as domains.
If you want to use abbreviations, add the Vocabulary. For example: When using the ‘EU’ region as a domain, add ‘Europe’ as a similar term for the ‘EU’ domain.The domain names should be a maximum of 1-2 words.
Do not use Product or application names as Domains. Use these as Topics when building Knowledge Graph.
For more information on how to create a domain in Luma Graph, refer to Knowledge Graph → Add-a-New-Domain.
Examples
Based on your organization, the domain structure is created in Luma Knowledge. Here are a few examples of Domains structures created for specific organizations:
IT Service Management
For a Service Management organization, domains should be created to represent departments or Teams. Following is a sample domain structure for such an organization.
XYZ University
When implementing Luma Knowledge for a university, domains can represent departments. Following is a sample domain structure for a university.
Hotel/Hospitality
For a Hospitality related organization such as a Hotel, domains can represent the various hospitality sectors. Following is a sample domain structure for a Hotel.
