The Catalogs View provides administrators with a centralized interface to group and manage related resources such as Large Language Models (LLMs), Data Sources, and Tools. By organizing these resources into catalogs, administrators can efficiently manage access control and simplify the assignment of resources to user groups.

​
Catalogs Overview

  1. Purpose:
    • Catalogs group similar resources (LLMs, Data Sources, or Tools) for streamlined management.
    • Access to these resources is controlled by assigning catalogs to specific teams.
  2. Use Cases:
    • Simplify resource management by categorizing related LLMs, Data Sources, or Tools into a single catalog.
    • Apply consistent access control policies by assigning catalogs to teams.
    • Manage large quantities of resources efficiently in a growing environment.

​
Catalogs View Layout

  1. Columns:
    • Name:
      • The name of the catalog (e.g., Main Catalogue).
    • Resources:
      • Lists the resources included in the catalog:
        • For LLMs: Displays the LLMs included (e.g., Anthropic, OpenAI GPT-4).
        • For Data Sources: Shows vector or relational data sources.
        • For Tools: Lists available tools (e.g., APIs, web scrapers).
    • Actions:
      • A dropdown menu to perform actions such as editing or deleting the catalog.
  2. Add Catalog Button:
    • Located at the top-right of the view, this green button (+ ADD CATALOG) opens a form to create a new catalog.
  3. Pagination Control:
    • Adjust the number of catalogs displayed per page using the dropdown at the bottom-left.

​
Cross-Resource Applicability

This view applies to the following catalog types:
  1. LLM Catalogs:
    • Group and manage collections of LLMs, enabling administrators to easily control access to models based on their functionality or vendor.
  2. Data Source Catalogs:
    • Organize vector or structured data sources into catalogs for efficient assignment and governance.
  3. Tool Catalogs:
    • Categorize tools (e.g., APIs, search utilities) into logical groups to streamline their use in chat rooms or applications.

​
Benefits

  1. Centralized Management:
    • Simplifies resource organization and reduces redundancy.
  2. Efficient Governance:
    • Allows for consistent application of access control policies across groups.
  3. Scalability:
    • Handles large numbers of resources effectively as organizational needs evolve.
  4. Flexible Integration:
    • Ensures that related resources are grouped for seamless assignment to teams or chat rooms.
This generalized view supports catalog management for all resource types, providing a uniform approach to simplify administration while maintaining security and organizational efficiency.