Lexi is both a data catalog and a search platform. Universal Data Representation (UDR) documents are automatically generated as objects are processed by View, and emitted to Lexi. Lexi's internal data layout is closely related to the UDR document structure, enabling both simple and advanced search cases along any number of dimensions including key terms, content-types, date ranges, schema filters, and more.

Lexi has two primary resource types: collections and sourcedocuments.

Collections are logical groupings of source documents within a tenant, similar to a bucket for object storage. Though collections can be defined and used for practically any purpose, they are typically used for documents that are correlated through a common subject matter.

Source documents are the UDR layout of a data asset. Source documents are stored in collections and can be managed in a manner similar to how objects are managed in buckets. Further, source documents can be identified by perform searches against collections.

JavaScript SDK Setup

Install SDK from npm

npm install view-sdk

Initialize Configuration Sdk

import { ViewLexiSdk } from "view-sdk";

const api = new ViewLexiSdk(
  "00000000-0000-0000-0000-000000000000", //tenant Id
  "default", //access token
  "http://localhost:8000/" //endpoint
);

Python setup

Install SDK from pip

pip install view-sdk

Initialize Configuration Sdk

import view_sdk
from view_sdk import lexi

sdk = view_sdk.configure( access_key="default",base_url="localhost", tenant_guid= "00000000-0000-0000-0000-000000000000")

C# setup

Install SDK from NuGet

dotnet add package View.Sdk

Initialize Lexi Sdk

using View.Sdk;
using View.Sdk.Lexi;

public static class Example {
    public static async Task Main(string[] args)
    {
        Guid _TenantGuid = Guid.Parse("00000000-0000-0000-0000-000000000000");
        string _AccessKey = "default";
        string _Endpoint = "http://localhost:8000/";
        ViewLexiSdk sdk = new ViewLexiSdk(_TenantGuid, _AccessKey, _Endpoint);      
    }
}