LogoLogo
  • 👋Welcome to Groclake
  • ⏩Jump right in
  • 🗣️Introduction to Groclake
  • 🧠High level Concepts
    • Agent Discovery
    • Agent Registry
    • Agent Communication
      • Agent Text Transfer Protocol - ATTP
    • Agent Security
      • Agent Private Cloud - APC
      • Authentication & Encryption
      • Zero Trust Policy
  • 💽Installation & Guide
  • 🏗️Groclake Use Cases
  • 📰Groclake Records
  • Example Codes
  • GrocAgent
    • What is GrocAgent?
    • Example Chat Agent
    • Reflections in GrocAgent
      • Workflow of Reflection Handler
  • Lakes
    • 💾Data & Model Management
      • Datalake
        • Create Datalake
        • Retrieve Document
        • Upload Documents
        • Datalake Connections
          • Snowflake integration
      • Vectorlake
        • Creating vector
        • Generating Vector
        • Pushing Vector
        • Retrieve Document
        • Searching Vector
      • Modellake
        • Create Modellake
        • Language Translation
        • Conversation AI
        • Text to Speech
        • Chat Completion
      • Knowledgelake
        • Create Knowledge Base
        • Push Documents from a URL
        • Push Documents from Local Storage
        • Searching for Information
    • ⚒️Tool Management & Gateway
      • Toollake
        • Tools
        • Salesforce CRM Integration
        • Slack Communication Module
        • New Relic Integration
        • Google Calendar Integration
          • Check Slot Availability
          • Get Available Slots
          • Delete Event
          • Create new event
          • Create new calendar event
    • 🤖Agent Management & Deployment
      • Agentlake
        • Register your agent
        • Fetch agent details & categories
        • Create Agent Private Cloud (APC)
        • Assign Agent Private Cloud (APC) to an Agent
      • Promptlake
        • Setting Connection & Initializing
        • Storing a Prompt
        • Fetching a Prompt
        • Example API Calls
      • Memorylake
        • Context Component Examples
        • Value Structure
        • Setup & Guide
        • Storing & Retrieving Memory
        • Wildcard Search
        • Updating Memory Quality
    • 🗃️Index Stores
      • Cataloglake
        • Create catalog
        • Generate Product Data
        • Fetch Catalog Data
        • Push Product Data
        • Optimize Data Retrieval with Catalog Caching
        • Search for Products
        • Filter Product Search
        • Update Product Data
        • Recommend Products Based on Product Name
        • Update Inventory in Catalog
        • Fetch Inventory Details from Catalog
        • Fetch Product Price
        • Update Product Price in Catalog
        • Cache Image in Catalog
        • Sync Your Catalog with external ecomm platforms
        • Deleting items
        • Address Parsing and Intent Extraction
        • Creating Mapper
        • Convert Mapper's Metadata
        • Fetching Mapper
        • Updating Mapper
        • Example use case of Cataloglake
      • Joblake
        • Joblake Mapping
        • Creating a Joblake
      • Resumelake
        • Resumelake Mapping
        • Creating a Resumelake
Powered by GitBook
On this page
  • Examples of GrocLake Record Use Cases#
  • Summary#

Groclake Records

PreviousGroclake Use CasesNextExample Codes

Last updated 5 months ago

A GrocLake Record is a structured collection of attributes representing various pieces of data stored in GrocLake. Each attribute consists of a name and a corresponding value, making it easy to organize, search, and display information effectively.

We have provided a comprehensive list of catalog attributes categorized for various retail categories. For each attribute, an associated Enum example are there to guide. You can access these attributes by following the respective file links provided.

For a more detailed view of each attributes, refer to the full list in the .

Here’s an example of a GrocLake record containing different attribute types:

{
  "product_name": "Fresh Organic Apples",
  "description": "Crisp and sweet organic apples, perfect for snacking or baking.",
  "image": "https://yourdomain.com/images/apples.jpg",
  "price": 4.99,
  "inventory": 150,
  "categories": ["Fruits", "Organic"],
  "on_sale": true
}

In GrocLake, a record should include only the necessary information to facilitate searching, filtering, ranking, and displaying results. Avoid including irrelevant data that doesn’t enhance the user experience or search efficiency.

Structuring GrocLake Records#

When building GrocLake records, keep the structure simple, yet meaningful. Focus on the attributes that help with searching and displaying relevant results. For example, while adding product data, include information that assists with search relevance (e.g., product names, descriptions, categories) and exclude redundant details.

Key steps for structuring records:

  1. Extract valuable data: Identify the critical attributes needed for search and display.

  2. Rework data: Remove unnecessary information, standardize formats, and add metadata.

  3. Enhance discoverability: Compute or include additional data (e.g., synonyms or tags) to improve search results.


Examples of GrocLake Record Use Cases#

Product Search#

If you’re creating a grocery store search engine, you can structure records like this to help users find the products they’re looking for:

{
  "product_name": "Whole Wheat Bread",
  "description": "Freshly baked whole wheat bread, made with natural ingredients.",
  "categories": ["Bakery", "Whole Grains"],
  "price": 2.99,
  "on_sale": false,
  "image": "https://yourdomain.com/images/wholewheatbread.jpg",
  "inventory": 120
}

This record contains attributes like product_name, categories, and price, which are essential for search and display.


Attributes for Searching#

Searchable attributes in GrocLake should contain the terms users are most likely to search for, such as product names, descriptions, or categories. For example:

  • product_name: Helps users find specific products, such as "Banana."

  • categories: Allows users to search by product types, such as "Fruits" or "Vegetables."

  • description: Provides additional context for users searching with broader terms.


Example#

If a user searches for “Fresh apples”, GrocLake will look for matches in the product_name and description attributes:

{
  "product_name": "Fresh Organic Apples",
  "description": "Crisp and sweet organic apples, perfect for snacking or baking.",
  "categories": ["Fruits", "Organic"],
  "price": 4.99,
  "inventory": 150
}

This ensures search results are relevant and easy to understand.


Attributes for Displaying#

Attributes like product_name, description, price, and image are used to display search results in a user-friendly way. These attributes help provide the essential information users need at a glance.

Example:

{
  "product_name": "Bananas",
  "description": "Fresh ripe bananas, perfect for a healthy snack or smoothie.",
  "price": 1.29,
  "image": "https://yourdomain.com/images/bananas.jpg",
  "inventory": 200
}

This record ensures users see the name, price, and image of the product in search results.


Attributes for Filtering#

To help users refine their search, use attributes like:

  • Boolean: on_sale (true/false) to show discounted items.

  • Numeric: price for filtering based on cost.

  • Lists: categories for filtering by product type.

Example of a filterable record:

{
  "product_name": "Organic Milk",
  "categories": ["Dairy", "Organic"],
  "price": 3.49,
  "on_sale": true,
  "inventory": 50
}

This record enables users to filter for organic dairy products or items on sale.


Attributes for Custom Ranking#

Custom ranking attributes improve the relevance of search results by considering business metrics like popularity, stock levels, or sales.

Example:

{
  "product_name": "Strawberries",
  "categories": ["Fruits"],
  "price": 5.99,
  "likes": 1024,
  "sales": 200,
  "inventory": 80
}

You can use the sales and likes attributes to rank popular items higher in search results.


Simplified Records for Efficiency#

When creating records for GrocLake, ensure simplicity and relevance by avoiding unnecessary complexity.

For instance, instead of this:

{
  "product_name": "Almond Butter",
  "description": "Smooth and creamy almond butter made from roasted almonds.",
  "details": {
    "nutritional_info": {
      "calories": 190,
      "fat": 16g,
      "protein": 7g
    },
    "brand": "Nature's Best",
    "origin": "USA"
  },
  "inventory": 50,
  "price": 9.99,
  "categories": ["Snacks", "Healthy"]
}

Use this:

{
  "product_name": "Almond Butter",
  "description": "Smooth and creamy almond butter made from roasted almonds.",
  "price": 9.99,
  "categories": ["Snacks", "Healthy"],
  "inventory": 50
}

Simplifying records enhances performance and reduces noise while still meeting search and display needs.


Summary#

With GrocLake, structuring records effectively is critical to building powerful, intuitive search and recommendation systems. By including only the most valuable attributes, GrocLake ensures a fast, accurate, and user-friendly experience for any grocery or retail platform.

📰
spreadsheet