@mastra/mcp-docs-server 0.13.37 → 0.13.38

package/.docs/raw/rag/vector-databases.mdx

@@ -1,80 +1,80 @@
 ---
-title: "Storing Embeddings in A Vector Database | Mastra Docs"
+title: "Storing Embeddings in A Vector Database | RAG | Mastra Docs"
 description: Guide on vector storage options in Mastra, including embedded and dedicated vector databases for similarity search.
 ---
 
-import { Tabs } from "nextra/components";
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
 
-## Storing Embeddings in A Vector Database
+# Storing Embeddings in A Vector Database
 
 After generating embeddings, you need to store them in a database that supports vector similarity search. Mastra provides a consistent interface for storing and querying embeddings across various vector databases.
 
 ## Supported Databases
 
-{/*
-LLM CONTEXT: This Tabs component showcases different vector database implementations supported by Mastra.
-Each tab demonstrates the setup and configuration for a specific vector database provider.
-The tabs show consistent API patterns across different databases, helping users understand how to switch between providers.
-Each tab includes import statements, initialization code, and basic operations (createIndex, upsert) for that specific database.
-The providers include Pg Vector, Pinecone, Qdrant, Chroma, Astra, LibSQL, Upstash, Cloudflare, MongoDB, OpenSearch, Couchbase and S3 Vectors.
-*/}
-
-<Tabs items={['MongoDB', 'Pg Vector', 'Pinecone', 'Qdrant', 'Chroma', 'Astra', 'LibSQL', 'Upstash', 'Cloudflare', 'OpenSearch', 'Couchbase', 'LanceDB', 'S3 Vectors']}>
-  <Tabs.Tab>
-    ```ts filename="vector-store.ts" showLineNumbers copy
-    import { MongoDBVector } from '@mastra/mongodb'
-
-    const store = new MongoDBVector({
-      uri: process.env.MONGODB_URI,
-      dbName: process.env.MONGODB_DATABASE
-    })
-    await store.createIndex({
-      indexName: "myCollection",
-      dimension: 1536,
-    });
-    await store.upsert({
-      indexName: "myCollection",
-      vectors: embeddings,
-      metadata: chunks.map(chunk => ({ text: chunk.text })),
-    });
-
-    ```
-    ### Using MongoDB Atlas Vector search
-
-    For detailed setup instructions and best practices, see the [official MongoDB Atlas Vector Search documentation](https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-search-overview/?utm_campaign=devrel&utm_source=third-party-content&utm_medium=cta&utm_content=mastra-docs). 
-  </Tabs.Tab>
-
-  <Tabs.Tab>
-  ```ts filename="vector-store.ts" showLineNumbers copy
-  import { PgVector } from '@mastra/pg';
-
-  const store = new PgVector({ connectionString: process.env.POSTGRES_CONNECTION_STRING })
-
-  await store.createIndex({
-    indexName: "myCollection",
-    dimension: 1536,
-  });
-
-  await store.upsert({
-    indexName: "myCollection",
-    vectors: embeddings,
-    metadata: chunks.map(chunk => ({ text: chunk.text })),
-  });
+<Tabs>
+  <TabItem value="mongodb" label="MongoDB">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { MongoDBVector } from "@mastra/mongodb";
+
+const store = new MongoDBVector({
+  uri: process.env.MONGODB_URI,
+  dbName: process.env.MONGODB_DATABASE,
+});
+await store.createIndex({
+  indexName: "myCollection",
+  dimension: 1536,
+});
+await store.upsert({
+  indexName: "myCollection",
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
+```
+
+### Using MongoDB Atlas Vector search
+
+For detailed setup instructions and best practices, see the [official MongoDB Atlas Vector Search documentation](https://www.mongodb.com/docs/atlas/atlas-vector-search/vector-search-overview/?utm_campaign=devrel&utm_source=third-party-content&utm_medium=cta&utm_content=mastra-docs).
+
+  </TabItem>
+
+  <TabItem value="pg-vector" label="PgVector">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { PgVector } from "@mastra/pg";
+
+const store = new PgVector({
+  connectionString: process.env.POSTGRES_CONNECTION_STRING,
+});
+
+await store.createIndex({
+  indexName: "myCollection",
+  dimension: 1536,
+});
+
+await store.upsert({
+  indexName: "myCollection",
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
 ```
 
 ### Using PostgreSQL with pgvector
 
 PostgreSQL with the pgvector extension is a good solution for teams already using PostgreSQL who want to minimize infrastructure complexity.
 For detailed setup instructions and best practices, see the [official pgvector repository](https://github.com/pgvector/pgvector).
-</Tabs.Tab>
 
-<Tabs.Tab>
-```ts filename="vector-store.ts" showLineNumbers copy
-import { PineconeVector } from '@mastra/pinecone'
+  </TabItem>
+
+  <TabItem value="pinecone" label="Pinecone">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { PineconeVector } from "@mastra/pinecone";
 
 const store = new PineconeVector({
   apiKey: process.env.PINECONE_API_KEY,
-})
+});
 await store.createIndex({
   indexName: "myCollection",
   dimension: 1536,
@@ -82,37 +82,40 @@ await store.createIndex({
 await store.upsert({
   indexName: "myCollection",
   vectors: embeddings,
-  metadata: chunks.map(chunk => ({ text: chunk.text })),
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
 });
 ```
-</Tabs.Tab>
 
-<Tabs.Tab>
-  ```ts filename="vector-store.ts" showLineNumbers copy
-  import { QdrantVector } from '@mastra/qdrant'
+  </TabItem>
 
-  const store = new QdrantVector({
-    url: process.env.QDRANT_URL,
-    apiKey: process.env.QDRANT_API_KEY
-  })
+  <TabItem value="qdrant" label="Qdrant">
 
-  await store.createIndex({
-    indexName: "myCollection",
-    dimension: 1536,
-  });
+```ts title="vector-store.ts" showLineNumbers copy
+import { QdrantVector } from "@mastra/qdrant";
 
-  await store.upsert({
-    indexName: "myCollection",
-    vectors: embeddings,
-    metadata: chunks.map(chunk => ({ text: chunk.text })),
-  });
+const store = new QdrantVector({
+  url: process.env.QDRANT_URL,
+  apiKey: process.env.QDRANT_API_KEY,
+});
 
+await store.createIndex({
+  indexName: "myCollection",
+  dimension: 1536,
+});
+
+await store.upsert({
+  indexName: "myCollection",
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
 ```
-</Tabs.Tab>
 
-<Tabs.Tab>
-```ts filename="vector-store.ts" showLineNumbers copy
-import { ChromaVector } from '@mastra/chroma'
+  </TabItem>
+
+  <TabItem value="chroma" label="Chroma">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { ChromaVector } from "@mastra/chroma";
 
 // Running Chroma locally
 // const store = new ChromaVector()
@@ -121,8 +124,8 @@ import { ChromaVector } from '@mastra/chroma'
 const store = new ChromaVector({
   apiKey: process.env.CHROMA_API_KEY,
   tenant: process.env.CHROMA_TENANT,
-  database: process.env.CHROMA_DATABASE
-})
+  database: process.env.CHROMA_DATABASE,
+});
 
 await store.createIndex({
   indexName: "myCollection",
@@ -132,44 +135,46 @@ await store.createIndex({
 await store.upsert({
   indexName: "myCollection",
   vectors: embeddings,
-  metadata: chunks.map(chunk => ({ text: chunk.text })),
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
 });
 ```
-</Tabs.Tab>
 
-<Tabs.Tab>
-  ```ts filename="vector-store.ts" showLineNumbers copy
-  import { AstraVector } from '@mastra/astra'
+  </TabItem>
 
-  const store = new AstraVector({
-    token: process.env.ASTRA_DB_TOKEN,
-    endpoint: process.env.ASTRA_DB_ENDPOINT,
-    keyspace: process.env.ASTRA_DB_KEYSPACE
-  })
+  <TabItem value="astra" label="Astra">
 
-  await store.createIndex({
-    indexName: "myCollection",
-    dimension: 1536,
-  });
+```ts title="vector-store.ts" showLineNumbers copy
+import { AstraVector } from "@mastra/astra";
 
-  await store.upsert({
-    indexName: "myCollection",
-    vectors: embeddings,
-    metadata: chunks.map(chunk => ({ text: chunk.text })),
-  });
+const store = new AstraVector({
+  token: process.env.ASTRA_DB_TOKEN,
+  endpoint: process.env.ASTRA_DB_ENDPOINT,
+  keyspace: process.env.ASTRA_DB_KEYSPACE,
+});
+
+await store.createIndex({
+  indexName: "myCollection",
+  dimension: 1536,
+});
 
+await store.upsert({
+  indexName: "myCollection",
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
 ```
-</Tabs.Tab>
 
+  </TabItem>
 
-<Tabs.Tab>
-```ts filename="vector-store.ts" showLineNumbers copy
+  <TabItem value="libsql" label="LibSQL">
+
+```ts title="vector-store.ts" showLineNumbers copy
 import { LibSQLVector } from "@mastra/core/vector/libsql";
 
 const store = new LibSQLVector({
   connectionUrl: process.env.DATABASE_URL,
-  authToken: process.env.DATABASE_AUTH_TOKEN // Optional: for Turso cloud databases
-})
+  authToken: process.env.DATABASE_AUTH_TOKEN, // Optional: for Turso cloud databases
+});
 
 await store.createIndex({
   indexName: "myCollection",
@@ -179,39 +184,43 @@ await store.createIndex({
 await store.upsert({
   indexName: "myCollection",
   vectors: embeddings,
-  metadata: chunks.map(chunk => ({ text: chunk.text })),
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
 });
 ```
-</Tabs.Tab>
-
-<Tabs.Tab>
-  ```ts filename="vector-store.ts" showLineNumbers copy
-  import { UpstashVector } from '@mastra/upstash'
-
-  // In upstash they refer to the store as an index
-  const store = new UpstashVector({
-    url: process.env.UPSTASH_URL,
-    token: process.env.UPSTASH_TOKEN
-  })
-
-  // There is no store.createIndex call here, Upstash creates indexes (known as namespaces in Upstash) automatically
-  // when you upsert if that namespace does not exist yet.
-  await store.upsert({
-    indexName: "myCollection", // the namespace name in Upstash
-    vectors: embeddings,
-    metadata: chunks.map(chunk => ({ text: chunk.text })),
-  });
+
+  </TabItem>
+
+  <TabItem value="upstash" label="Upstash">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { UpstashVector } from "@mastra/upstash";
+
+// In upstash they refer to the store as an index
+const store = new UpstashVector({
+  url: process.env.UPSTASH_URL,
+  token: process.env.UPSTASH_TOKEN,
+});
+
+// There is no store.createIndex call here, Upstash creates indexes (known as namespaces in Upstash) automatically
+// when you upsert if that namespace does not exist yet.
+await store.upsert({
+  indexName: "myCollection", // the namespace name in Upstash
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
 ```
-</Tabs.Tab>
 
-<Tabs.Tab>
-```ts filename="vector-store.ts" showLineNumbers copy
-import { CloudflareVector } from '@mastra/vectorize'
+  </TabItem>
+
+  <TabItem value="cloudflare" label="Cloudflare">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { CloudflareVector } from "@mastra/vectorize";
 
 const store = new CloudflareVector({
   accountId: process.env.CF_ACCOUNT_ID,
-  apiToken: process.env.CF_API_TOKEN
-})
+  apiToken: process.env.CF_API_TOKEN,
+});
 await store.createIndex({
   indexName: "myCollection",
   dimension: 1536,
@@ -219,17 +228,18 @@ await store.createIndex({
 await store.upsert({
   indexName: "myCollection",
   vectors: embeddings,
-  metadata: chunks.map(chunk => ({ text: chunk.text })),
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
 });
 ```
 
-</Tabs.Tab>
+  </TabItem>
+
+  <TabItem value="opensearch" label="OpenSearch">
 
-<Tabs.Tab>
-```ts filename="vector-store.ts" showLineNumbers copy
-import { OpenSearchVector } from '@mastra/opensearch'
+```ts title="vector-store.ts" showLineNumbers copy
+import { OpenSearchVector } from "@mastra/opensearch";
 
-const store = new OpenSearchVector({ url: process.env.OPENSEARCH_URL })
+const store = new OpenSearchVector({ url: process.env.OPENSEARCH_URL });
 
 await store.createIndex({
   indexName: "my-collection",
@@ -239,60 +249,65 @@ await store.createIndex({
 await store.upsert({
   indexName: "my-collection",
   vectors: embeddings,
-  metadata: chunks.map(chunk => ({ text: chunk.text })),
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
+```
+
+  </TabItem>
+  <TabItem value="couchbase" label="Couchbase">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { CouchbaseVector } from "@mastra/couchbase";
+
+const store = new CouchbaseVector({
+  connectionString: process.env.COUCHBASE_CONNECTION_STRING,
+  username: process.env.COUCHBASE_USERNAME,
+  password: process.env.COUCHBASE_PASSWORD,
+  bucketName: process.env.COUCHBASE_BUCKET,
+  scopeName: process.env.COUCHBASE_SCOPE,
+  collectionName: process.env.COUCHBASE_COLLECTION,
+});
+await store.createIndex({
+  indexName: "myCollection",
+  dimension: 1536,
+});
+await store.upsert({
+  indexName: "myCollection",
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
 });
 ```
 
-</Tabs.Tab>
-<Tabs.Tab>
-  ```ts filename="vector-store.ts" showLineNumbers copy
-  import { CouchbaseVector } from '@mastra/couchbase'
-
-  const store = new CouchbaseVector({
-    connectionString: process.env.COUCHBASE_CONNECTION_STRING,
-    username: process.env.COUCHBASE_USERNAME,
-    password: process.env.COUCHBASE_PASSWORD,
-    bucketName: process.env.COUCHBASE_BUCKET,
-    scopeName: process.env.COUCHBASE_SCOPE,
-    collectionName: process.env.COUCHBASE_COLLECTION,
-  })
-  await store.createIndex({
-    indexName: "myCollection",
-    dimension: 1536,
-  });
-  await store.upsert({
-    indexName: "myCollection",
-    vectors: embeddings,
-    metadata: chunks.map(chunk => ({ text: chunk.text })),
-  });
-  ```
-</Tabs.Tab>
-<Tabs.Tab>
-  ```ts filename="vector-store.ts" showLineNumbers copy
-  import { LanceVectorStore } from '@mastra/lance'
-
-  const store = await LanceVectorStore.create('/path/to/db')
-  
-  await store.createIndex({
-    tableName: "myVectors",
-    indexName: "myCollection",
-    dimension: 1536,
-  });
-  
-  await store.upsert({
-    tableName: "myVectors",
-    vectors: embeddings,
-    metadata: chunks.map(chunk => ({ text: chunk.text })),
-  });
-  ```
-
-  ### Using LanceDB
-  
-  LanceDB is an embedded vector database built on the Lance columnar format, suitable for local development or cloud deployment.
-  For detailed setup instructions and best practices, see the [official LanceDB documentation](https://lancedb.github.io/lancedb/).
-</Tabs.Tab>
-<Tabs.Tab>
-```ts filename="vector-store.ts" showLineNumbers copy
+  </TabItem>
+  <TabItem value="lancedb" label="Lance">
+
+```ts title="vector-store.ts" showLineNumbers copy
+import { LanceVectorStore } from "@mastra/lance";
+
+const store = await LanceVectorStore.create("/path/to/db");
+
+await store.createIndex({
+  tableName: "myVectors",
+  indexName: "myCollection",
+  dimension: 1536,
+});
+
+await store.upsert({
+  tableName: "myVectors",
+  vectors: embeddings,
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
+});
+```
+
+### Using LanceDB
+
+LanceDB is an embedded vector database built on the Lance columnar format, suitable for local development or cloud deployment.
+For detailed setup instructions and best practices, see the [official LanceDB documentation](https://lancedb.github.io/lancedb/).
+
+  </TabItem>
+  <TabItem value="s3vectors" label="S3 Vectors">
+
+```ts title="vector-store.ts" showLineNumbers copy
 import { S3Vectors } from "@mastra/s3vectors";
 
 const store = new S3Vectors({
@@ -310,10 +325,11 @@ await store.createIndex({
 await store.upsert({
   indexName: "my-index",
   vectors: embeddings,
-  metadata: chunks.map(chunk => ({ text: chunk.text })),
+  metadata: chunks.map((chunk) => ({ text: chunk.text })),
 });
 ```
-</Tabs.Tab>
+
+  </TabItem>
 
 </Tabs>
 
@@ -325,7 +341,7 @@ Once initialized, all vector stores share the same interface for creating indexe
 
 Before storing embeddings, you need to create an index with the appropriate dimension size for your embedding model:
 
-```ts filename="store-embeddings.ts" showLineNumbers copy
+```ts title="store-embeddings.ts" showLineNumbers copy
 // Create an index with dimension 1536 (for text-embedding-3-small)
 await store.createIndex({
   indexName: "myCollection",
@@ -345,15 +361,8 @@ The dimension size must match the output dimension of your chosen embedding mode
 
 Each vector database enforces specific naming conventions for indexes and collections to ensure compatibility and prevent conflicts.
 
-{/*
-LLM CONTEXT: This Tabs component displays naming convention rules for different vector databases.
-Each tab explains the specific naming requirements and restrictions for that database provider.
-This helps users understand the constraints and avoid naming conflicts when creating indexes or collections.
-The tabs provide examples of valid and invalid names to clarify the rules for each database.
-*/}
-
-<Tabs items={['MongoDB', 'Pg Vector', 'Pinecone', 'Qdrant', 'Chroma', 'Astra', 'LibSQL', 'Upstash', 'Cloudflare', 'OpenSearch', 'S3 Vectors']}>
-  <Tabs.Tab>
+<Tabs>
+  <TabItem value="mongodb" label="MongoDB">
     Collection (index) names must:
     - Start with a letter or underscore
     - Be up to 120 bytes long
@@ -362,15 +371,15 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Example: `my_collection.123` is valid
     - Example: `my-index` is not valid (contains hyphen)
     - Example: `My$Collection` is not valid (contains `$`)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="pgVector" label="PgVector">
     Index names must:
     - Start with a letter or underscore
     - Contain only letters, numbers, and underscores
     - Example: `my_index_123` is valid
     - Example: `my-index` is not valid (contains hyphen)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="pinecone" label="Pinecone">
     Index names must:
     - Use only lowercase letters, numbers, and dashes
     - Not contain dots (used for DNS routing)
@@ -378,8 +387,8 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Have a combined length (with project ID) under 52 characters
       - Example: `my-index-123` is valid
       - Example: `my.index` is not valid (contains dot)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="qdrant" label="Qdrant">
     Collection names must:
     - Be 1-255 characters long
     - Not contain any of these special characters:
@@ -388,8 +397,8 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
       - Unit separator (`\u{1F}`)
     - Example: `my_collection_123` is valid
     - Example: `my/collection` is not valid (contains slash)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="chroma" label="Chroma">
     Collection names must:
     - Be 3-63 characters long
     - Start and end with a letter or number
@@ -398,23 +407,23 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Not be a valid IPv4 address
     - Example: `my-collection-123` is valid
     - Example: `my..collection` is not valid (consecutive periods)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="astra" label="Astra">
     Collection names must:
     - Not be empty
     - Be 48 characters or less
     - Contain only letters, numbers, and underscores
     - Example: `my_collection_123` is valid
     - Example: `my-collection` is not valid (contains hyphen)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="libsql" label="LibSQL">
     Index names must:
     - Start with a letter or underscore
     - Contain only letters, numbers, and underscores
     - Example: `my_index_123` is valid
     - Example: `my-index` is not valid (contains hyphen)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="upstash" label="Upstash">
     Namespace names must:
     - Be 2-100 characters long
     - Contain only:
@@ -424,8 +433,8 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Can be case-sensitive
     - Example: `MyNamespace123` is valid
     - Example: `_namespace` is not valid (starts with underscore)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="cloudflare" label="Cloudflare">
     Index names must:
     - Start with a letter
     - Be shorter than 32 characters
@@ -433,8 +442,8 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Use dashes instead of spaces
     - Example: `my-index-123` is valid
     - Example: `My_Index` is not valid (uppercase and underscore)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="opensearch" label="OpenSearch">
     Index names must:
     - Use only lowercase letters
     - Not begin with underscores or hyphens
@@ -443,8 +452,8 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Example: `my-index-123` is valid
     - Example: `My_Index` is not valid (contains uppercase letters)
     - Example: `_myindex` is not valid (begins with underscore)
-  </Tabs.Tab>
-  <Tabs.Tab>
+  </TabItem>
+  <TabItem value="s3vectors" label="S3 Vectors">
     Index names must:
     - Be unique within the same vector bucket
     - Be 3–63 characters long
@@ -455,14 +464,14 @@ The tabs provide examples of valid and invalid names to clarify the rules for ea
     - Example: `-myindex` is not valid (begins with hyphen)
     - Example: `myindex-` is not valid (ends with hyphen)
     - Example: `MyIndex` is not valid (contains uppercase letters)
-  </Tabs.Tab>
+  </TabItem>
 </Tabs>
 
 ### Upserting Embeddings
 
 After creating an index, you can store embeddings along with their basic metadata:
 
-```ts filename="store-embeddings.ts" showLineNumbers copy
+```ts title="store-embeddings.ts" showLineNumbers copy
 // Store embeddings with their corresponding metadata
 await store.upsert({
   indexName: "myCollection", // index name
@@ -481,7 +490,7 @@ The upsert operation:
 - Creates new vectors if they don't exist
 - Automatically handles batching for large datasets
 
-For complete examples of upserting embeddings in different vector stores, see the [Upsert Embeddings](../../examples/rag/upsert/upsert-embeddings.mdx) guide.
+For complete examples of upserting embeddings in different vector stores, see the [Upsert Embeddings](/examples/rag/upsert/upsert-embeddings) guide.
 
 ## Adding Metadata