Knowledge Graph

The knowledge graph is the visual representation of the topic and Artifact entities available in Luma Knowledge and the directional relationship between these entities. Each entity in Luma Knowledge like Topic, Artifact, QnA is denoted as a Node and the link between the nodes represents the hierarchy. The graph provides the ability to search and navigate through the graphical view of connected Artifacts, a visually navigable ontology. Metadata in nodes and relationships in links allows fast browsing and access to Artifacts.

Ontology generated (Parent Topic and Topic) for an Artifact during the Curation process is used to plot the Knowledge Graph.

As a Curator, it is important to verify the Ontology information for every Artifact. This ensures that every Artifact appears in the correct hierarchy in Knowledge Graph and appears in user search appropriately

Overview

Navigate to the Knowledge Graph tab to view the hierarchy available of the Artifacts in your system. The Knowledge Graph represents the hierarchy of the Artifacts available in the system for your Tenant and Sub Tenant. Tenant and Sub Tenant are created when Tenant is provisioned. The entities are marked in Amber in the graph.

All the entities under Sub Tenant are called Nodes. The Nodes in the Knowledge graph are categorized as below:

Domain Node: Domain nodes represent the top-level classification of a product, service, or policy. These are directly related to the Sub-Tenant node and are the Parent nodes to one or more child Topic nodes in the Hierarchy branch. The hierarchy forms a parent-child relationship where each descendant node provides more details for the classification of the Topic. All Topics are represented in blue in the graph.

In the below example, Finance is the Domain.

Topic Node: Topic nodes represent classifications of Artifacts and are arranged under Domain nodes.  Topics are in a parent-child relationship with each other and Artifacts nodes.  Topic nodes are either categorical or tangible.  Categorical nodes do not have any Artifacts attached to them. Tangible nodes normally have one or more Artifacts attached to them.  Tangible nodes are also referred to as Object Topics which is something an Artifact is about.

In the below example, ‘Payments’ is a Topic.

Object Topic: It represents the last node in a Hierarchy branch and is the primary topic of an Artifact. Object topics are usually the products or services provided and supported by the organization, for which Artifacts or Knowledge is managed in the system. The Object topic can have multiple Artifacts or QnAs as child nodes. All Topics are represented in blue in the graph.

In the below example, Credits is Object Topic

Artifacts: Artifacts are the last nodes of the Knowledge Graph. These can be Articles or QnAs. Articles are the documents that have a single purpose. An FAQ Artifact (QnA) is a summary artifact representing a collection of questions and answers over multiple topics/subjects. Questions and answers automatically inherit the topic of the FAQ Artifact Once the Artifact goes through the curation process and Ontology is generated, the Artifact starts appearing in the Knowledge Graph. Artifacts are represented in black in the graph.

Example: In the below example, Credit Cards represent Artifacts.

  • Parent Topics and their child relationships are originated from the Ontology generation process. Additional, branches and sub-branch nodes are added by curators for adding Artifacts.

  • Object Topics are not provided Out-of-Box. These are manually created by Curators or Admins.

  • When an Artifact is curated, object topics are suggested by the curation process.

    • If the Object topic identified for the Artifact already exists in the graph, it is automatically related to the topic.

    • If a new Object topic is identified, the Artifact is related to the selected Domain Node and the QnA is related to the Artifact as a child node. Such an Artifact cannot be published until it is placed under a topic node. This ensures the artifact is assigned to an appropriate topic.

Features on Knowledge Graph

As a Curator, you can perform the below actions on the Knowledge Graph:

Default Domain

The default domain for a tenant is used whenever an artifact is created without a domain. Such artifacts are linked to the default domain automatically. The mapping can be changed after review. This ensures the artifact is always created under a specific domain and sync does not fail in case the domain is not mentioned or available. By default, a domain is automatically added at tenant provisioning (indicated by the green tick).

To update default domain, do the following:

  • Select the new domain.

  • Click on the “Mark as default Domain“ option.

  • On the confirmation pop up, click on Yes

  • The default domain is updated. (indicated by the green tick)

Traverse the Knowledge Graph

You can browse through the Knowledge Graph to view the Topics and Artifacts available in your tenant. To do so:

  • Select the Parent Node.

  • Click on the Expand/Collapse Node button. You may also double-click on the node to expand the node.

  • The Knowledge graph is refreshed to display additional nodes at the next level. You can continue expanding other topics in the graph to view related topics and Artifacts underneath.

  • At each node, you can view the count of child topics and Artifacts in the hierarchy.

Search on a Node

You may search for a Topic, QnA, or an Artifact in the Knowledge graph using a Phrase or Artifact status.

To perform a search, follow the below steps:

  • Select Search Criteria. You may search for a Topic, QnA, or an Artifact.

  • Add a term or phrase. This is not a mandatory criteria

  • Select Artifact state. This refers to if the Artifact’s status is available in the system. The filter is not available when searching for Topics

  • Once required filters are added, press Enter.

The knowledge graph is refreshed to represent the hierarchy of the searched node.

Add a New Domain

The out-of-the-box Domain list is configured when the Luma Knowledge tenant is provisioned. To add new domains to the list, follow the below steps:

  • Select the Sub Tenant Node.

  • Click on the Create Domain button.

  • On the New Domain window, add a new Domain Name and Description.

  • Click on Create.

A new domain in the hierarchy tree is now created. The hierarchy path is highlighted to display the parent-child relationship in the graph. You can hover over the domain to view the description. The domain is now available to add new Artifacts.

Add a New Branch

The curation process identifies the Topic to which the Artifact is related to. If the topic is not available in the Root Parent topic, selected while creating an Artifact, you may add the topic to the hierarchy tree and create a new branch. To add a new topic, follow the below steps:

  • Select the Parent Node. This is the node to which the new topic should be added.

  • Click on the Create topic button.

  • On the New Topic window, add a new Topic Name and Description.

  • Click on Create.

A new branch in the hierarchy tree is now created. The hierarchy path is highlighted to display the parent-child relationship in the graph. You can hover over the Topic to view the Topic description.

Points to Remember:

  • Duplicate topic nodes with the same name can be created under different levels and parent topics. However, the duplicate topics cannot be created under the same parent Node.

  • A topic node cannot be created under an Artifact node.

View an Artifact

All Artifacts and QnAs in Knowledge Graph are represented in black. You can preview Artifact details from the graph. Follow the below steps to view an Artifact:

  • Navigate through the graph and select the required Artifact or QnA.

  • Click on View Detail or double-click on the Artifact to view details.

  • A preview window appears on the screen with Artifact details. The screen provides a quick view of Summary, Q&A pairs, Metadata, and Artifact source. The information is read-only.

  • Click on the View Full Artifact details link to view the Artifact details. You will be redirected to the Knowledge store → Artifact details page.

For a QnA Artifact, the View Full Artifact details link redirects you to the selected QnA pair on the Parent Artifact’s details page. Here you can view the QnA pair and related Ontology.

Relate to a New Topic

As a curator, you can update the Artifact-Topic relationship in the following scenarios:

  1. Existing Artifact or QnA is related to an incorrect topic in the graph.

  2. An Artifact in the draft state cannot be published due to a missing Topic (metadata).

In any of the above cases, follow the below steps to relate an Artifact or QnA to another topic:

  • Navigate through the graph and select the required Artifact/QnA.

  • Click on Relate to Topic option.

  • On Relate to the topic window, select the new topic, and click on Relate. Verify the complete hierarchy path as similar topics can be available in one or more branches.

     

  • Once the Topic is related, the selected Artifact will be linked to the new topic and the graph will be refreshed to indicate the new relationship.

Edit a Node

A topic node in Knowledge Graph is important for the identification of artifacts. It is used to find appropriate Artifacts for a Search query and disambiguate in the case of Guided conversation. It is essential that Topic node details are correct and relevant to ensure the new Artifacts are associated with the correct Topic and appear in suitable searches.

As a curator, you can manage and update Domain and Topic node details in the Knowledge Graph. To do so, follow the below steps:

  • Select the required node in the graph.

  • Click on the Edit Node option.

  • On the Edit Node pop-up, you can update the Topic Name and Description as required.

  • Click Save.

Delete a Relationship

When an Artifact is curated, Luma Knowledge automatically identifies the Topic and adds the Artifact as its child node. In case, the identified topic is incorrect, the relationship in the graph can be updated by the curator.

To delete a relationship link between a topic and an Artifact/QnA, follow the below steps:

  • Navigate through the graph and locate the required Artifact/QnA.

  • Select the relationship link.

  • A delete button appears next to the relationship link. Click on the delete button.

The relationship link will be removed and the graph will be refreshed to represent the updated hierarchy.

Delete an Artifact

As a curator, you can delete a retired Artifact or QnA from the graph. Deleting the Artifact permanently removes the Artifact and related QnAs from all Luma Knowledge repositories. Follow the below steps:

  • On the Knowledge graph, select the required Artifact or QnA.

  • Click on the Delete Node button.

  • On the delete confirmation, select Delete.

  • The selected Artifact and related QnAs will be permanently deleted from the database.

Delete a Topic Node

As a curator, you can delete a Topic from the graph if it does not have a child node or Artifact linked to it.

  • Select the required node in the graph

  • Click on Delete Node.

If the Topic does not have a linked child Topic, Artifact, or QnA, it will be removed from the graph. In case a child relation is available, an error message appears, “Cannot delete Topic as it has Artifacts as children“.