Skip to content

Commit 011df90

Browse files
authored
Update Mx GenAI Connector.md
added diagram for data separation through metadata
1 parent cbb01e9 commit 011df90

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

content/en/docs/marketplace/genai/mendix-cloud-genai/Mx GenAI Connector.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,9 +163,13 @@ Metadata is additional information that can be attached to data in a GenAI knowl
163163
Metadata consists of key-value pairs and serves as additional information connected to the data, though it is not part of the vectorization itself.
164164

165165
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
166-
* key: `Item Type`, value: `Ticket`
166+
* key: `Category`, value: `Ticket`
167167

168-
can be added during insertion. The model then generates its response using the specified metadata instead of solely the input text. Using metadata, even more fine-grained filtering becomes feasible. Each ticket may have associated metadata such as
168+
can be added during insertion. The model then generates its response using the specified metadata instead of solely the input text.
169+
170+
{{< figure src="/attachments/appstore/platform-supported-content/modules/genai/navigate_mxgenai/GenAIKBMetadataSeparation.png" >}}
171+
172+
Using metadata, even more fine-grained filtering becomes feasible. Each ticket may have associated metadata such as
169173

170174
* key: `Ticket Type`, value: `Bug`
171175
* key: `Status`, value: `Solved`

0 commit comments

Comments
 (0)