Skip to content

Commit f60287a

Browse files
authored
Update navigate_mxgenai.md
added diagram for data separation through metadata
1 parent 011df90 commit f60287a

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

content/en/docs/marketplace/genai/mendix-cloud-genai/navigate_mxgenai.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,14 @@ Metadata is additional information that can be attached to data in a GenAI knowl
9595

9696
Metadata consists of key-value pairs and serves as additional information connected to the data, though it is not part of the vectorization itself.
9797

98-
For example, a GenAI Knowledge Base could be used to store historical customer support tickets. Each ticket may have associated metadata such as
98+
To come back to the previous example for collections: Instead of having two different collections, such as 'IT Setup & Equipment' and 'Historical Support tickets', there could be one named 'Company IT'. To be able to retrieve only tickets and no other information from this collection, metadata like
99+
* key: `Category`, value: `Ticket`
100+
101+
can be added during insertion. The model then generates its response using the specified metadata instead of solely the input text.
102+
103+
{{< figure src="/attachments/appstore/platform-supported-content/modules/genai/navigate_mxgenai/GenAIKBMetadataSeparation.png" >}}
104+
105+
Using metadata, even more fine-grained filtering becomes feasible. Each ticket may have associated metadata such as
99106

100107
* key: `Ticket Type`, value: `Bug`
101108
* key: `Status`, value: `Solved`

0 commit comments

Comments
 (0)