Create a Guru Unstructured Data Lake Object (UDLO)

Create an unstructured data lake object (UDLO) in Data 360 to ingest your organization’s content from Guru into Data 360.

See the Unstructured Data File Formats and Connectors for a list of supported file formats.

User Permissions Needed
To create a connection:	System Admin profile or Data Cloud Architect permission set

Before you begin:

Make sure that you’ve set up a Guru connection and you know its name.
Verify you have a list of tags you want to use to filter your Guru cards.
Verify you have a list of Guru collections and folders that you want to ingest.

From App Launcher, select Data Cloud.
Select Data Lake Objects and then select New.
Select the From External Files tile, and select Next.
From the New Data Lake Object screen, choose the Guru connector tile and select Next.
From the Connection Details dropdown, choose the Guru connection you previously created.
In the Guru Collections and Folders Section, in the Included Collections field, enter the list of Collection IDs you created earlier as a comma-separated list. Without filtering applied, all knowledge base articles from all specified collections are ingested. If you leave the field blank, all cards in all collections are ingested.
In the Guru Collections and Folders section, in the Included Folders field, enter the list of folders you collected earlier. Specify each folder as a comma-separated list in the following format: collection/folder. If you don’t apply filters, all knowledge base articles from all specified folders are ingested. If you leave the field blank, all cards in all folders are ingested.
- If the folder isn’t in the specified collection, but the collection name is valid, the entire collection is ingested.
- If an invalid collection is listed, no content is ingested.
- If the folder and collection are valid, only the contents in the folder are ingested.
Note
If you want to include only verified Guru cards, check the Ingest only verified cards checkbox. If you leave the checkbox unchecked, unverified cards are ingested.
In the Apply Filters section, you can apply filters to limit ingestion to the articles you want. There are several filters available. If you leave any filter field blank, all applicable items are ingested. When you apply more than one filter (even more than one filter of the same type), each filter removes or includes content from the number of files that are ingested. If you apply filters and no content is ingested, your filters are probably too restrictive. If you see content you didn’t intend to ingest, your filters are probably too broad.

Apply any or all of the following filters:
- Included Tags: Provide a comma-separated list of tags. Any card tagged with the provided tag is included. If multiple tags are listed, any cards tagged with any included tag is ingested. This field is case-sensitive. If you misspell a tag, it is ignored.
- Excluded Tags: Provide a comma-separated list of tags. Any card tagged with the provided tag is excluded. If multiple tags are listed, all cards tagged any excluded tag is excluded. This field is case-sensitive. If you misspell a tag, it is ignored.
- Creation Date: Select one date from the calendar widget. Any card created on or after the provided date is ingested.
- Last Update Date: Select one date from the calendar widget. Any card updated on or after the provided date is ingested.
In the Guru Card Access Levels to Include section, select the radio button to restrict the ingestion of Guru cards to: Default is Both.
- Only Public cards
- Non-public (teammates and restricted) cards
- Both public and non-public (teammates and restricted) cards
Click Next. The connector runs by default every two hours. You can monitor sync status in Data Stream status.
Add an Object Name and an Object API Name for the UDLO. See Data Lake Object Naming Standards. Make sure that the object API name is unique, and the field autopopulates based on the object name.
In the Unstructured Data Model Object Mapping section, select New.
From the Data Space Dropdown, leave the selection as Default.
For the UDMO mapping, enter an Object Name and an Object API Name. See Data Lake Object Naming Standards. Make sure that the object API name is unique. The field autopopulates based on the object name.
Select the checkbox to enable Content Harmonization for the UDLO. Leave it deselected to enable content harmonization later.

If you enable content harmonization now, AI Enrichments (Summary and Q&A) are disabled by default. To enable AI Enrichments, create a Harmonization Configuration and enable Einstein.
Note

When you enable content harmonization, you enable collection of Content Viewer engagement data.
Note
Select Next.
In the Search Index Configuration section, leave the checkbox selected to Enable Semantic Search with System Defaults. The system default settings automatically select text fields and apply a chunking strategy for each field. Deselect the checkbox to create a search index configuration later.
Leave the remaining fields as-is to use the default settings, or rename and change the Search Configuration details and objects to make changes.
Save your work.

The data stream ingests cards from Guru into a UDLO and maps them to a UDMO. From this UDMO, a search index is created which can now be used to ground AI-generated responses.

If you have any connection or ingestion issues look at the Troubleshooting information.

Create a Guru Unstructured Data Lake Object (UDLO)

See Also