Create Artifact using Knowledge Templates
Luma Knowledge allows the Curator to create Artifacts using organization-specific Knowledge Templates. These are the documents that may not follow generic Question-Answer format and have predefined templates such as System guides, ‘How to’ documents, RCA documents, etc. You can import these documents in Luma Knowledge and create Artifacts to make the information easily accessible to end-user on different integrated platforms.
The difference between Create Artifact’s Document and Documents with Template options is QnA generation. Artifact creation with Knowledge Template by-passes QnA generation. This means Luma Knowledge does not generate QnA pairs for these Artifacts and the information in the file is available in Artifact details.
Using Knowledge Templates
A Curator / Administrator can use Knowledge Templates to create artifacts manually or by importing documents. You can import one or more documents and create Artifacts with the information available in the files. The document is validated based on the Knowledge template to ensure that the information required to create the Artifact is available. Upon successful validation, Knowledge Artifact is created in Luma Knowledge.
For more information on creating artifacts manually using Knowledge Templates, refer to Create Artifact using Templates | Using-Regular-Template.
Organization-specific custom templates can also be configured in Luma Knowledge to create Artifacts manually. Currently, this is a backend process. You may contact the Serviceaide support team for more information.
Upload documents
Follow the below steps to Import a document and create an Artifact using a Knowledge Template:
On the Create Artifact page, navigate to Import Documents.
Select Documents With Template as Source.
Click on Choose File(s) and browse to the required file. You may add multiple files or upload a zip file to import multiple files. You may also drag and drop the required files.
Select Template to Map. The selected template is used to validate and map the information in the uploaded document(s) to the template fields for Artifact and Ontology generation.
Select a domain from the Domain list. This represents the area, department, region, or field the Artifact belongs to. The Domains available in the list are available out-of-the-box. To update the list, refer to Adding a new domain on Knowledge Graph.
Click on Import Documents.
The selected documents are now queued for Artifact creation. Luma Knowledge validates the document based on the selected Knowledge template and creates Artifact. The new Artifact(s) is linked to the selected template. Artifact details are extracted from the document. The information available in the various sections (text and media content) is mapped to the template fields.
The Artifact state is determined based on your tenant's Artifact Publishing Mode configuration and the identified ontology. Refer to Tenant Configurations for more information.
Click on Check Progress to view the Import status, where you can view details on the Documents imported and artifacts created.
Points to Remember:
It is important to select the correct Knowledge Template. Your document must follow the structure of the Knowledge Template selected. If the uploaded document’s structure does not follow the selected template, artifact creation fails.
Your document section names or headings should be the same as the Template Fields or respective Aliases. Luma Knowledge identifies the section headings as the template fields.
You can upload .docx, .pdf, and .xlsx files to create Artifact with Templates. To upload multiple files, you selected the file one by one or upload a zip file.
Artifact Ontology is automatically generated from the text available in Template fields that are marked as Summary and with Ontology Type as ‘Main’ or ‘Suggested’.
If your document contains sections with Metadata and Topic Hierarchy, the Metadata Extraction script associated with the selected template will extract the information and add the metadata to the Artifact.
If Open AI is enabled for your Tenant, Metadata, Key phrases and Summary are automatically generated. Refer to Integrating Advanced Language Models for more details on Open AI features.
To ignore the Topic automatically generated from the text in the document, set Tenant configuration Skip Topic Generation to Yes. This ensures only the Topic hierarchy provided in the document is used to associate with the Artifact in Knowledge Graph.
If none of the fields in the Knowledge template is marked as Artifact Summary and Automatical Summarization is not enabled for your tenant, Luma Knowledge identifies the content in the first heading of the document as the artifact summary automatically. For correct ontology generation, ensure that the document begins with the summary of the Knowledge Artifact.
Bulk Artifact Upload
In addition to creating artifacts one at a time, Curators or Administrators can create multiple artifacts with a single file upload. Luma Knowledge supports Bulk Artifact upload using Knowledge Templates and an excel file.
To upload multiple artifacts, follow the below steps:
Build Excel file for upload
Select the Knowledge Template for your artifacts. Note that all the artifacts are created based on the select Knowledge Template.
Based on the Knowledge Template, build your excel sheet. Each field in the template should be available as a column in the sheet.
Now add each artifact as a row in the sheet. The Import process creates an Artifact for each row in the sheet.
Upload file
Once the file is ready, you can upload the document and create the artifacts. To do so,
Navigate to Create Artifact → Import Documents.
Select Documents With Template as Source.
Click on Choose File(s) and browse to the required file.
Select Template to Map. The selected template is used to validate and map the text to the template fields for Artifact and Ontology generation.
Select a domain from the Domain list.
Click on Import Documents.
Luma Knowledge reads and creates artifacts for each row in the sheet. You can view the artifact creation status in the Import status.
Â