DataSource
Data Collection Pipeline
Section titled “Data Collection Pipeline”Data sources are collected through the following nine pipelines. Each pipeline includes both schema editing (selecting which columns to collect) and data management (viewing collected data).
| Pipeline | Name | Description |
|---|---|---|
odbc |
Database Connection | Connects to a database to collect data. |
usr_db |
User‑Defined DB | Reads tables/views (usr schema) in DataStudio’s User‑Defined tab with Zio.entity() using SELECT. Unlike ODBC, there is no connection information—it reads only within usr (even if you write FROM teacher, it refers to usr.teacher). It rejects other schemas by name. Example: SELECT * FROM teacher WHERE updated_at >= '@getDate()' — reserve words are enclosed in quotes (without quoting, the date is interpreted as subtraction). When running for the first time, include a LIMIT or date condition—the amount read is determined by the SELECT. Duplicates are filtered out using the primary key of the collection schema, just like other pipelines. |
mcp |
MCP Client | Connects to an MCP server to retrieve data. |
email_accounts |
Email Accounts | Stores email account information for collection. |
direct_cable |
Port Capture | Used when a cable is directly connected to the server’s LAN port. |
crawl_targets |
Crawling Sites | Visits websites with URLs and collects data via crawling. |
google_sheets |
Google Spreadsheets | Collects from Google Sheets, an online cloud‑based Excel file. |
email_emlfile |
EML File | Reads locally stored .eml files. |
restapi |
RESTful | Collects data through REST‑style endpoints. |
$TableName.FieldName
Section titled “$TableName.FieldName”These are variable names collected from the data source. They are used to apply retrieved data to a template. The name must start with $ and end with the variable name; parentheses are not allowed.
| Category | Syntax | Example |
|---|---|---|
| Basic syntax | $TableName.FieldName | $apis.model |
| Filtering | $TableName.FieldName?condition=value | $customers.domain?gubun=소비자 |
| And / Or conditions | {$TableName.FieldName?condition1=value&condition2=value1,value2} | {$customers.domain?gubun=소비자&grade=A,B} |
| Upper limit | $TableName.FieldName?limit=100 | If omitted, only 200 items are loaded. Truncation is logged on the server |
The outer braces { } may be omitted. Even if there are multiple conditions, $TableName.FieldName?condition1=value&condition2=value remains unchanged. However, when referencing within a prompt using {{ }}, never overlap them — writing {{{$…}}} will leave the outer braces as literal characters.
#OntologyNodeName.FieldName
Section titled “#OntologyNodeName.FieldName”This is the label of an ontology node. It is used to apply data retrieved from the ontology into a template. It must start with # and end with a variable name. Parentheses are not used.
| Category | Syntax | Example |
|---|---|---|
| Basic syntax | #NodeName.FieldName | #Sender.title |
| Filtering | #NodeName.FieldName?condition=value | #Customers.domain?gubun=소비자 |
| And / Or conditions | {#NodeName.FieldName?condition1=value&condition2=value1,value2} | {#Customers.domain?gubun=소비자&grade=A,B} |
| Upper limit | #NodeName.FieldName?limit=100 | If omitted, 200 items are loaded at most. Truncation is logged on the server |
The outer braces { } may be omitted. Even if there are multiple conditions, you can write #NodeName.FieldName?condition1=value&condition2=value. However, when calling within a prompt using {{ }}, do not overlap them — writing {{{#…}}} will leave the outer braces as literal characters.
Appendix 1. How to Obtain a Google Spreadsheet Service Account Key
Section titled “Appendix 1. How to Obtain a Google Spreadsheet Service Account Key”The google_sheets pipeline reads sheets using a Google service account. The key only needs to be registered once per instance; before registration the collection ends with an empty result and the server log contains [Google Auth Error] 'google_service_account_json' field is empty or missing.
- Go to Google Cloud Console and select a project (create one if none exists).
- In APIs & Services → Library, enable
Google Sheets APIandGoogle Drive APIrespectively. - In APIs & Services → Credentials → Create credentials → Service account. Enter a name and finish (you can leave the role blank).
- Open the created service account, go to Keys → Add Key → Create new key → JSON. A file starting with
{"type": "service_account", …}will download. This file is equivalent to a password—do not place it in a shared folder. - In Zio open Basic Code →
system_configstable, and paste the entire contents of the JSON file into thegoogle_service_account_jsonfield. - Share the spreadsheet (or its containing folder) with the service account email. The email is the
client_emailvalue in the JSON (…@….iam.gserviceaccount.com). Since only read access is needed, Viewer permission suffices.
You can use the same service account across multiple instances. If you forget to share the sheet with that email, even a correct key will result in “file not found.”
(주)지오유 · 경기 용인시 처인구 유림로154번길(유방동 673-2) 20-13
CEO 신달수·Business no. 142-81-36612·E-commerce no. 용인처인-0118호·Privacy officer 신달수·Email shindalsoo@gmail.com·Tel 1833-3623·Fax 02-6918-4006