# About Metadata

For better understanding of the parameters from the Advanced category let’s consider the time series shown in the picture below:

<figure><img src="/files/XaJL7ZE9uRbCB62yggu0" alt=""><figcaption></figcaption></figure>

Note that for all time series specified data source and store are the same, but types of addresses and comments are different.

**Case when default store parameters are used.** After data source value changes request *SELECT \* FROM "timeseries"."autogen"."tssamples" GROUP BY "tsid" ORDER BY DESC LIMIT 1* will return the following result:

| **time**            | **tsid**                     | **s** | **v** |
| ------------------- | ---------------------------- | ----- | ----- |
| 2019-09-25 23:12:41 | MySeries.Series1             | 0     | 25.00 |
| 2019-09-25 23:12:41 | MyCustomID                   | 0     | 25.00 |
| 2019-09-25 23:12:41 | 22ePXYjPQ0GM/3iyM+Dii12+3n4= | 0     | 25.00 |

**Case when Add Time Series Comment to Tag parameter is True.** After data source value changes the same request will return the following result:

| **time**            | **tsid**                     | **tsc**    | **s** | **v** |
| ------------------- | ---------------------------- | ---------- | ----- | ----- |
| 2019-09-25 23:57:16 | MySeries.Series1             | S1 Comment | 0     | 99.00 |
| 2019-09-25 23:57:16 | MyCustomID                   | S3 Comment | 0     | 99.00 |
| 2019-09-25 23:57:16 | 22ePXYjPQ0GM/3iyM+Dii12+3n4= | S2 Comment | 0     | 99.00 |

Thus *tsc* tag will be added to the record metadata for each time series and it will contain time series comment.

**Case when Add Time Series Path to Tag parameter is True*****.*** After data source value changes the same request will return the following result:

| **time**            | **tsid**                     | **tsp**          | **s** | **v**  |
| ------------------- | ---------------------------- | ---------------- | ----- | ------ |
| 2019-09-26 00:09:58 | MySeries.Series1             | MySeries.Series1 | 0     | 117.00 |
| 2019-09-26 00:09:58 | MyCustomID                   | MySeries.Series3 | 0     | 117.00 |
| 2019-09-26 00:09:58 | 22ePXYjPQ0GM/3iyM+Dii12+3n4= | MySeries.Series2 | 0     | 117.00 |

Thus *tsp* tag will be added to the record metadata for each time series and it will contain path to the series.

**Case when Add Server UID to Tag parameter is True.** After data source value changes the same request will return the following result:

| **time**            | **tsid**                     | **su**                   | **s** | **v** |
| ------------------- | ---------------------------- | ------------------------ | ----- | ----- |
| 2019-09-26 00:09:58 | MySeries.Series1             | CeSqAF5sGUqMJqdilungXg== | 0     | 33.00 |
| 2019-09-26 00:09:58 | MyCustomID                   | CeSqAF5sGUqMJqdilungXg== | 0     | 33.00 |
| 2019-09-26 00:09:58 | 22ePXYjPQ0GM/3iyM+Dii12+3n4= | CeSqAF5sGUqMJqdilungXg== | 0     | 33.00 |

Thus *su* tag will be added to the record metadata for each time series and it will contain unique server identifier in the format of Base64.

You can use different combinations of flags from the Advanced category in order to define several meta-tags.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.monokot.io/time-series-and-stores/influxdb-connectivity-store/about-metadata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.