[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C2K0N7WYCVCZ1XY7R4NPYP":3,"skill-same:01M7C2K0N7WYCVCZ1XY7R4NPYP":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7C2K0N7WYCVCZ1XY7R4NPYP","marketplace",null,"Use when something has to appear or be labelled in the Denodo 9.5 Data Marketplace — the separate server behind \u002Fdenodo-data-catalog that is driven by REST, not VQL. Covers a marketplace tag, a category tree, assigning either to the views a consumer browses, importing VDP tags into the marketplace, synchronising the marketplace catalog with Virtual DataPort, and registering an external element (asset extension) — a dashboard, ETL job, data contract, notebook or AI agent from another tool — so it shows up in the 360 graph beside the views it uses. Also for \"tag it in the marketplace\", \"put this data product in a category\", \"show our BI dashboards in the catalog\", \"why does the marketplace not see this view\". Not for VDP tags (CREATE TAG, ALTER TAG) — those are \u002Fdenodo:catalog.","kirivandubai\u002Fdenodo_wipe_coading_skills","kirivandubai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221521416?v=4","01M7C2HC9KETA166XKR09YMKZQ","01M7C2HCAJ787NNYKMCG12S3DY",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarketplace\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketplace\ndescription: Use when something has to appear or be labelled in the Denodo 9.5 Data Marketplace — the separate server behind \u002Fdenodo-data-catalog that is driven by REST, not VQL. Covers a marketplace tag, a category tree, assigning either to the views a consumer browses, importing VDP tags into the marketplace, synchronising the marketplace catalog with Virtual DataPort, and registering an external element (asset extension) — a dashboard, ETL job, data contract, notebook or AI agent from another tool — so it shows up in the 360 graph beside the views it uses. Also for \"tag it in the marketplace\", \"put this data product in a category\", \"show our BI dashboards in the catalog\", \"why does the marketplace not see this view\". Not for VDP tags (CREATE TAG, ALTER TAG) — those are \u002Fdenodo:catalog.\n---\n\n# Marketplace tags, categories and external elements\n\nThree objects that live in the **Data Marketplace**, not in Virtual DataPort: the\nmarketplace **tag**, the **category**, and the **external element** that represents an asset\nfrom another tool. The channel is REST — `scripts\u002Fdenodo api` — and the server is the one\nin `marketplace_url`, not the VDP port.\n\nA \"tag\" alone does not say which object the human means. A **VDP tag** is `CREATE TAG` in\nVirtual DataPort and belongs to `\u002Fdenodo:catalog`; a **marketplace tag** is\n`POST \u002Fpublic\u002Fapi\u002Ftags` here. They are different objects on different servers, and a request\nsent to the wrong one succeeds — on the wrong side. When the request does not say, ask — or\nlook at where the object has to be visible: a consumer who only browses the marketplace means\na marketplace tag.\nViews themselves are `\u002Fdenodo:views` and `\u002Fdenodo:datasources`; applying anything is\n`\u002Fdenodo:execute`; the safety rule and the working loop are `\u002Fdenodo:vql`.\n\n## Two rules that govern everything below\n\n**1. Names are not keys.** Every object here is addressed by a numeric `id` that the server\nassigns and that differs between installations. A template cannot contain one. There is no\n`CREATE OR REPLACE`: idempotence is a *sequence* — look the name up, then `POST` if it is\nmissing or `PUT` if it is there. Two calls, every time, and the lookup is not optional.\n\n**2. Nothing can be attached to a view the marketplace has not synchronised.** The\nmarketplace keeps its own copy of the VDP catalog. A view that exists in VDP but is not in\nthat copy has no id, and `view-details` says so:\n`{\"id\": null, \"inLocal\": false, \"inVDP\": true}` — *verified: 9.5.1 (live, 2026-09-10)*.\nSynchronise first (see the template), then assign.\n\n**But that answer has two causes, and they look identical.** A view queried against the\n*wrong* `serverId` returns exactly the same body — `id: null`, `inLocal: false`, and\n`inVDP: true` even from a server that never saw the database — and nothing in the response\nnames the server it means — *verified: 9.5.1 (live, 2026-09-10)*. So before concluding\n\"needs synchronising\", repeat the `view-details` call against the other registered servers:\nif one of them answers `inLocal: true`, you had the wrong id and nothing needs\nsynchronising. Getting this backwards means changing a shared catalog to fix a query\nparameter. `VIEWS\u002Fchanges` does not shortcut the round: a server that never carried the\ndatabase lists its views under `serverElements` too, as views it would import —\n*verified: 9.5.1 (live, 2026-10-01)*. The server list does not say which server carries a\ndatabase; under a wrong id everything is created happily and only the import fails, naming a\nview that \"does not exist\".\n\n## Name the server: `serverId`\n\nThe marketplace can have several VDP servers registered, and tags, views and external tool\nservers are **per server** — the same call against two ids returns two different catalogs.\nWith more than one registered, omitting the server is an error whose text names something\nelse entirely:\n\n| Call without a server named | Answer |\n|---|---|\n| `\u002Fpublic\u002Fapi\u002Ftags`, `\u002Fpublic\u002Fapi\u002Fviews\u002F…` | `500 {\"code\":\"GENERIC\",\"message\":\"Session Expired.\"}` |\n| `\u002Fpublic\u002Fapi\u002Fexternal-tool-servers` | `403`, empty body |\n| `\u002Fpublic\u002Fapi\u002Fcategory-management\u002F…` | works — categories are not server-scoped |\n\n*verified: 9.5.1 (live, 2026-09-10).* Read the ids once:\n\n```bash\n# verified: 9.5.1 (live, 2026-10-07)\napi get --env dev \u002Fpublic\u002Fapi\u002Fconfiguration\u002Fservers\n# → [{\"id\":\u003CserverId>,\"name\":\"\u003CVDP server as registered>\",\"url\":\"\u002F\u002F\u003Cvdp-host>:9999\u002Fadmin\"}, …]\n```\n\n**The id belongs in the profile, as `marketplace_server_id` — a human puts it there, not\nyou — and the tool adds it to every call by itself.** That is why no template below names a\nserver: the profile is the single place the environment is described, so the same template\nworks against any marketplace. One registered server needs no id at all.\n\n`--param serverId=\u003Cid>` overrides the profile for one call, and the transport then leaves\nthat call alone. Reach for it only when you genuinely mean a different server than the\nprofile's — asking each registered server which one holds a view, rule 2, is the case\nthat needs it. Putting it on ordinary calls silently pins the environment into a command.\n\n## Templates\n\n### Tag, with an assignment\n\n```bash\n# verified: 9.5.1 (live, 2026-09-10)\n\n# 1. does it exist? — the lookup that replaces CREATE OR REPLACE\napi get --env dev \u002Fpublic\u002Fapi\u002Ftag-management\u002Ftags \\\n    --param offset=0 --param limit=50 --param nameFilter=pii\n# → {\"count\":1,\"elements\":[{\"id\":\u003Canother tag's id>,\"name\":\"pii_legacy\", …}]}   ← NOT your tag\n\n# 2a. missing → create it\napi post --env dev \u002Fpublic\u002Fapi\u002Ftags \\\n    --json '{\"name\":\"pii\",\"description\":\"Personal data, GDPR scope\",\"descriptionType\":\"TEXT\"}'\n# → {\"id\":\u003Ctag_id>,\"name\":\"pii\",\"vdpTag\":false, …}\n\n# 2b. present → update it, id and all four fields in the body\napi put --env dev \u002Fpublic\u002Fapi\u002Ftags \\\n    --json '{\"id\":\u003Ctag_id>,\"name\":\"pii\",\"description\":\"Personal data, GDPR scope\",\"descriptionType\":\"TEXT\"}'\n\n# 3. hang it on views, by marketplace view id\napi post --env dev \u002Fpublic\u002Fapi\u002Ftags\u002F\u003Ctag_id>\u002Fviews --json '[\u003Cview_id>]'\n# → []   ← empty list IS the success\n```\n\n- **`nameFilter` is a case-insensitive *substring* match, so the lookup needs a second step:\n  compare `name` yourself, exactly.** `nameFilter=pii` also returns a tag called `pii_legacy`,\n  and `nameFilter=finance` one called `Finance` — *verified: 9.5.1 (live, 2026-09-10)*. Taking the first element and calling it yours is how a script ends up\n  `PUT`-ing over somebody else's tag. A namesake differing only in case is a collision, not a\n  match: creating the second one is `409`, so that case is a question for the human, not\n  something to resolve automatically.\n- **The two base paths are the API's own, not a slip in this template:** the paged lookup is\n  `\u002Fpublic\u002Fapi\u002Ftag-management\u002Ftags`, while create, update and the per-tag reads are\n  `\u002Fpublic\u002Fapi\u002Ftags\u002F…`. Do not \"correct\" one to match the other.\n- `name`, `description` and `descriptionType` are all mandatory on create; missing ones are\n  `400 VALIDATE_FIELD`. `descriptionType` is `TEXT` or `RICH_TEXT` (the latter renders HTML).\n- A duplicate name is `409` with an **empty body** — no message to read. That is why step 1\n  exists.\n- **`POST \u002Ftags\u002F{id}\u002Fviews` adds; `POST \u002Fviews\u002F{id}\u002Ftags` replaces** the view's whole tag\n  set. Use the first unless you mean to wipe what other people put there.\n- The response is the list of ids that were **not** assigned. `[]` is success; `[\u003Cview_id>]`\n  means \"already assigned\" **or** \"no such view\" — the two are indistinguishable, both come\n  back `200` — *verified: 9.5.1 (live, 2026-09-10)*. Read the assignment back.\n- **Anything that runs twice must read before it writes:** check\n  `GET \u002Fpublic\u002Fapi\u002Ftags\u002F{id}\u002Felements` and skip the `POST` for a view already listed, so\n  `[\u003Cview_id>]` always means something is wrong; `PUT` a found tag only when a field differs.\n- Assigning to an external element instead of a view is\n  `POST \u002Fpublic\u002Fapi\u002Ftags\u002F{id}\u002Fexternal-elements` with the same body shape, and it answers\n  with an **empty body**, not a list.\n\n### Category tree\n\n```bash\n# verified: 9.5.1 (live, 2026-09-10)\napi post --env dev \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories \\\n    --json '{\"name\":\"Consumer marts\",\"description\":\"What analysts read\",\"descriptionType\":\"TEXT\"}'\n# → {\"id\":\u003Ccategory_id>,\"parentId\":null, …}\n\napi post --env dev \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories \\\n    --json '{\"name\":\"Retail\",\"description\":\"Retail marts\",\"descriptionType\":\"TEXT\",\"parentId\":\u003Ccategory_id>}'\n\napi post --env dev \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F\u003Ccategory_id>\u002Fviews \\\n    --json '[\u003Cview_id>]'\n# → []\n```\n\nSame lookup-first rule (`GET …\u002Fcategories\u002Ftree`), same empty-list-is-success rule. Two\ndifferences from tags, both *verified: 9.5.1 (live, 2026-09-10)*:\n\n- **Deleting a parent deletes its children.** No warning, no mention of them in the\n  response, and the assignments go with them. Read the tree before you offer a delete.\n- **A repeated `DELETE` answers `200`**, where a repeated tag delete answers `500`. Do not\n  read a status to decide whether something existed.\n\n### Synchronising the marketplace catalog with VDP\n\nNeeded before any assignment to a view, and before an external element can name one. Look\nat the radius first — the whole point of `changes` is that it costs nothing:\n\n```bash\n# verified: 9.5.1 (live, 2026-10-07)\napi get --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FDATABASES\u002Fchanges\napi get --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FVIEWS\u002Fchanges\n# → {\"serverElements\":[…new…], \"modifiedElements\":[…], \"localElements\":[…gone from VDP…]}\n\napi post --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FDATABASES\u002Fsynchronize \\\n    --json '{\"proceedWithConflicts\":\"SERVER_WITH_LOCAL_CHANGES\"}'\napi post --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FVIEWS\u002Fsynchronize \\\n    --json '{\"proceedWithConflicts\":\"SERVER_WITH_LOCAL_CHANGES\"}'\n# → {\"inserted\":[…],\"modified\":[…],\"removed\":[…]}\n```\n\n- **Both steps.** A new database registers with the first call and its views still have no\n  ids; only `VIEWS\u002Fsynchronize` gives them ids — *verified: 9.5.1 (live, 2026-09-10)*.\n- `proceedWithConflicts` decides what happens to descriptions that differ:\n  `SERVER_WITH_LOCAL_CHANGES` takes VDP's but keeps edits made in the marketplace,\n  `LOCAL` keeps the marketplace's, `SERVER` overwrites them. **Use the first**; `SERVER`\n  is the one that quietly destroys other people's work.\n- `localElements` in `changes` is the list of things that will be **removed** from the\n  marketplace because VDP no longer has them, whatever the conflict mode. **A view renamed in\n  VDP is in that list under its old name** — the next section.\n- A `modifiedElements` entry with `reason: \"DESCRIPTION,FIELD_DESCRIPTION\"` is usually an\n  element whose descriptions were edited in the marketplace: it is listed on every reading,\n  and `SERVER_WITH_LOCAL_CHANGES` keeps those edits — *verified: 9.5.1 (live, 2026-10-01)*.\n  Such an entry loses nothing in the call — say so when you show the human the radius.\n- **The radius is a reading, not a promise, and there is no scope.** `changes` describes the\n  moment you asked; anything created between then and the call comes along too, and the call\n  cannot be narrowed to one database — it synchronises the whole server. On a shared server\n  that means other people's new views land in the catalog with yours. Re-read the response:\n  `inserted` says what actually happened.\n- The user running it needs `METADATA` on the whole VDP catalog. Under a narrower account\n  the marketplace treats what it cannot see as deleted and **removes it** —\n  *unverified: 9.5 documentation only* (Synchronize with Virtual DataPort).\n- **Who sends it.** You, when the same call with `--plan`, right before it, says `needs_yes:\n  false`: it reads both `changes` — both, even when only `VIEWS\u002Fsynchronize` is needed — and\n  finds only what this session created (`radius.own`): every `serverElements` entry a database\n  or view of yours, every `localElements` entry the element of a view of yours — your own view\n  renamed, with the pair matched in the call, included; with\n  `SERVER_WITH_LOCAL_CHANGES`, on a profile that is not production; `modifiedElements` do not\n  change it. Then read `removed` and `inserted` against that radius, and both `changes` again:\n  once a database is gone from VDP, its elements left the catalog with `removed` empty in both\n  responses — *verified: 9.5.1 (live, 2026-10-06)* — so only the second reading shows what went.\n  Tell the human at once about anything you did not expect. One entry in `radius.not_own` —\n  another team's new database, an orphan you did not make — and the body goes in a file, with\n  what waiting risks; the human sends it or says yes (`\u002Fdenodo:vql`). The one other exception\n  is the first import on a tool server you created in this session (the external element, step\n  4). Neither applies on production; nothing else about a `synchronize` is exempt.\n\n| Rationalization | Reality |\n|---|---|\n| \"Nothing gets removed — the rest of the radius only adds\" | Clean is not the test; whose is. Another team's new database or view under `serverElements` lands in the catalog everybody browses before its owner chose to publish it. |\n| \"The pair is matched, so the rename costs nothing\" | A view that existed before this session is someone's: the rename and its matched `synchronize` wait for one yes, shown together. |\n\n### A view in the marketplace is renamed, recreated or moved\n\nWhat people add in the marketplace belongs to the view's **element**, found by database and\nview name, and a synchronisation sees a renamed view as one element removed with all of it and\nanother imported empty. So: `view-details` on the view **before** the change, saved to a file;\nthe pair matched in the same `synchronize` call (`matchedElements`); a `DROP` and `CREATE` under\nthe same name in one run; a move to another database cannot be matched at all. The template,\nwho sends the matched call, and the move: `references\u002Frenames.md`.\n\n### External element — a dashboard, job or contract from another tool\n\nThere is no `POST \u002Fexternal-elements`. An external element is *imported*: the marketplace\nreads an interface view in VDP and creates, updates and deletes elements to match it. So the\nchain runs VQL and REST alternately, and the whole block below carries one verification mark.\n\n```bash\n# verified: 9.5.1 (live, 2026-09-10) — the chain as a whole\n\n# 0. the views this element will link to must already be in the marketplace catalog\n#    (previous template) — otherwise step 4 fails and nothing is created\n# 0b. the element type the VQL half names ('DASHBOARD') must be listed; missing →\n#     POST \u002Fpublic\u002Fapi\u002Fexternal-elements-types, body in references\u002Fexternal-elements.md\n\n# 1. provider type: the tool the metadata comes from. Multipart, but the icon is optional\napi post --env dev \u002Fpublic\u002Fapi\u002Fexternal-providers-types \\\n    --part 'request=json:{\"name\":\"ACME_BI\",\"visualName\":\"Acme BI\"}'\n# → 201 {\"externalProviderTypeId\":\u003Cprovider_type_id>,\"iconImage\":null, …}\n#   with a logo:  --part 'icon=@.\u002Facme.svg'\n#   the next call answers 200, this one 201 — check 2xx, never a particular code\n#   — verified: 9.5.1 (live, 2026-09-12)\n\n# 2. the server that will read the contract. The interface view need not exist yet\napi post --env dev \u002Fpublic\u002Fapi\u002Fexternal-tool-servers \\\n    --json '{\"type\":\"CUSTOM\",\"name\":\"acme_bi_server\",\"description\":\"Acme BI dashboards\",\n             \"externalProviderTypeId\":\u003Cprovider_type_id>,\n             \"databaseName\":\"sales_analytics\",\"viewName\":\"i_acme_bi_elements\"}'\n# → {\"id\":\u003Ctool_server_id>, …}\n\n# 3. ask the marketplace for the contract it expects. NOT a file to apply as it stands:\n#    the two CREATE TYPE come back usable verbatim, the interface view comes back\n#    without SET IMPLEMENTATION and without FOLDER — you write the implementation\napi get --env dev \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002F\u003Ctool_server_id>\u002Fvql-metadata\n# → a JSON string: CONNECT DATABASE …; two CREATE TYPE; CREATE INTERFACE VIEW (columns only)\n\n# 4. import\napi post --env dev \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002Fsynchronize \\\n    --json '{\"externalToolServerIds\":[\u003Ctool_server_id>]}'\n# → externalElementsAdded \u002F Updated \u002F Deleted, per server\n```\n\n**Step 4 is a `synchronize`, and the safety rule of `\u002Fdenodo:vql` says stop and ask before\none — but the first import on a server you have just created cannot delete anything.** The\ncall deletes elements *absent from the snapshot*, and a server created in this same session\nhas imported none. So: your own new server, first import — go, and say in the summary what\nwas imported. **From the second import on, the confirmation is back**, because the interface\nview is the whole picture and a row that stopped being selected is an element that gets\nremoved with its tags and categories. Read the current set first and show the human what is\nabout to disappear — the server's own elements are\n`POST \u002Fpublic\u002Fapi\u002Fsearch\u002Fexternal-elements\u002Fmetadata` with `externalToolServerIds: [\u003Cid>]`\nand the nine other mandatory fields — *verified: 9.5.1 (live, 2026-09-12)*.\nThere is no `GET …\u002Fexternal-tool-servers\u002F{id}\u002Fexternal-elements`: that path is `404`.\nNone of this changes the tool: the call is stamped\n`destructive: replace` either way, and on a `production` profile it is refused without\n`--allow-destructive`, which only a human may add.\n\n**Look each type up before creating it — they are different objects.** The element type, what\nthe asset *is*, is listed by `GET \u002Fpublic\u002Fapi\u002Fexternal-elements-types`, which returns the name as\n`externalElementTypeName` (sent as `name`) and has no `description`; the provider type, the tool\nit *comes from*, by `GET \u002Fpublic\u002Fapi\u002Fexternal-providers-types`. **That listing embeds every icon\nas base64 and can be large** — read it into a file and project\n`{externalProviderTypeId, name, visualName}` rather than letting it into the conversation —\n*verified: 9.5.1 (live, 2026-09-10)*. Tableau and Power BI are the documented native tools: the\n`REPORT` element type, the `TABLEAU` and `POWERBI` providers. Every other type a marketplace\nlists (`DASHBOARD`, `ETL_JOB`, an `…_PROVIDER`) is a custom type, created on that installation,\nand another marketplace may lack it — the template's `DASHBOARD` included (step 0b). A new type\nis a marketplace-wide object that everyone then sees. Step 1 of the chain above is skipped only\nwhen a listed provider type really is the asset's tool.\n\nThe VQL half — the implementation behind the contract from step 3. **Its names are outside\nthe naming convention of `\u002Fdenodo:vql` on purpose:** the interface view's name is part of\nthe contract you gave the tool server, and the three views under it are its implementation,\nnot integration-layer or business-entity objects. Keep them together in one folder and named\nafter the tool, as below; do not rename them to `iv_…` to match the table.\n\n```sql\n-- verified: 9.5.1 (live, 2026-10-07)\nCONNECT DATABASE sales_analytics;\n\n-- the two types come from vql-metadata verbatim. The names are part of the contract\nCREATE OR REPLACE TYPE external_element_association_type AS REGISTER OF (\n    associated_element_id:text, external_tool_server_name:text,\n    associated_element_type:text, direction:text, role:text);\nCREATE OR REPLACE TYPE external_element_association_array_type AS ARRAY OF external_element_association_type;\n\nCREATE OR REPLACE VIEW acme_bi_metadata FOLDER = '\u002F02 - integration'\n    AS SELECT 'ACME-DASH-01'                       AS id,\n              'Revenue cockpit'                    AS name,\n              'Weekly revenue by region'           AS description,\n              'DASHBOARD'                          AS external_element_type,\n              'https:\u002F\u002Facme.example\u002Fd\u002Frevenue'     AS url,\n              CAST('timestamp', '2026-01-19 09:00:00') AS created_at,\n              CAST('timestamp', '2026-09-06 07:45:00') AS updated_at\n       FROM DUAL();\n\nCREATE OR REPLACE VIEW acme_bi_associations FOLDER = '\u002F02 - integration'\n    AS SELECT 'ACME-DASH-01'                        AS owner_id,\n              'sales_analytics.household_income'    AS associated_element_id,\n              CAST('text', NULL)                    AS external_tool_server_name,\n              'VIEW'                                AS associated_element_type,\n              'OUT'                                 AS direction,\n              'consumes'                            AS role\n       FROM DUAL();\n\nCREATE OR REPLACE VIEW acme_bi_elements FOLDER = '\u002F02 - integration'\n    AS SELECT m.id AS id, m.name AS name, m.description AS description,\n              m.external_element_type AS external_element_type, m.url AS url,\n              m.created_at AS created_at, m.updated_at AS updated_at,\n              CAST('external_element_association_array_type',\n                   NEST(a.associated_element_id, a.external_tool_server_name,\n                        a.associated_element_type, a.direction, a.role)) AS associations\n       FROM acme_bi_metadata m INNER JOIN acme_bi_associations a ON m.id = a.owner_id\n       GROUP BY m.id, m.name, m.description, m.external_element_type, m.url,\n                m.created_at, m.updated_at;\n\nCREATE OR REPLACE INTERFACE VIEW i_acme_bi_elements (\n        id:text, name:text, description:text, external_element_type:text, url:text,\n        created_at:timestamp, updated_at:timestamp,\n        associations:external_element_association_array_type\n    )\n    SET IMPLEMENTATION acme_bi_elements\n    FOLDER = '\u002F02 - integration';\n```\n\nFour things here are load-bearing, each *verified: 9.5.1 (live, 2026-09-10)*:\n\n- **`external_element_association_array_type` is the name the marketplace checks**, literally.\n  Rename it and synchronisation refuses the whole server:\n  `400 INVALID_EXTERNAL_ELEMENT_INTERFACE_VIEW … expected type external_element_association_array_type`.\n- **`external_element_type` must equal an element type's `name`**, character for character\n  (read back as `externalElementTypeName`, above).\n- **`INNER JOIN`, not `LEFT OUTER JOIN`.** A left join over an element with no associations\n  makes `NEST` produce one all-null record, and the import rejects the element:\n  `400 … Required field 'associated_element_id' is null … association index 0`. As written\n  above — every element has an association — the inner join is the whole story; only if some\n  element has none, add the `UNION ALL` branch with a NULL array in\n  `references\u002Fexternal-elements.md`.\n- `CREATE OR REPLACE INTERFACE VIEW … SET IMPLEMENTATION` in one statement, so the file\n  re-applies. `ALTER INTERFACE VIEW` does the same thing but is a change to an existing\n  object and needs a human's yes (`\u002Fdenodo:vql`).\n\n`SELECT * FROM i_acme_bi_elements` before step 4: an interface view accepts an implementation\nthat does not match it, and only the `SELECT` shows it (`\u002Fdenodo:views`).\n\n## What you need before filling a template\n\n| Slot | Where it comes from |\n|---|---|\n| Which \"tag\" | marketplace or VDP (top of this skill); ask when the request does not say |\n| `serverId` | `marketplace_server_id` in the profile, set by a human (Name the server); never in a call unless you mean another server |\n| Tag or category name, description | the human. Both are shown to consumers browsing the marketplace, so they read as labels, not as identifiers |\n| A new category's parent | `GET …\u002Fcategories\u002Ftree` first; a *domain* the human names is a category of this tree, usually a root one. A live marketplace's tree is a taxonomy somebody designed — hang the new category inside the branch it belongs to. A **new top-level** category is a question for the human, not a default: it adds an axis to what everybody browsing sees. (`GET …\u002Fcategories\u002F{id}\u002Fpotential-parent` is for moving an existing one) |\n| Every numeric id | never a template, never memory: a `GET` in this session. Ids differ per installation and per server |\n| View ids to assign to | `GET \u002Fpublic\u002Fapi\u002Fview-details?databaseName=…&viewName=…`; `id:null`: rule 2, the other servers first, then synchronise. Save the answer to a file and read `id`, `inLocal` and `inVDP` out of it with a script — it carries the view's whole field list and its connection URIs, and truncating it instead is how the three fields get missed |\n| Whether the catalog may be synchronised | the call's `--plan` (`needs_yes`), see **Who sends it** |\n| Whether a view about to be renamed, recreated or moved is in the marketplace | `view-details` on it **before** the change — `id` not null and `inLocal: true`. The answer is also what to keep: it is the only copy of the element's metadata |\n| Which removed element is which new one | you renamed it, or the human says so. The same database and the same columns are a hint, not proof |\n| For an external element: the type | `GET \u002Fpublic\u002Fapi\u002Fexternal-elements-types` — list it; create one if none fits |\n| For an external element: id, name, url, timestamps | the source tool. `updated_at` is what drives updates — an element whose `updated_at` does not move is never refreshed |\n| Which views the element links to | the human, plus their exact `database.view` — an association naming a view the marketplace does not know fails the whole import |\n| Direction and role | `IN`\u002F`OUT` plus free text (`consumes`, `feeds`, `validates`). The documentation calls `direction` the data-flow direction and the 360 graph draws its arrow by it, without saying from whose side; Denodo's own sample marks every association `OUT`, a dashboard that *reads* a view included, and what `IN` changes is *unverified*. Follow the marketplace's existing elements, say which you chose, and look at the arrow after the first import. The role is the label on the edge of the 360 graph |\n\nDo not ask about property groups, endorsements, requests or personalisation — they are\nmarketplace features with their own screens, not part of creating these objects.\n\n## Reference\n\n- `references\u002Ftags.md` — the full tag surface, taking a tag off one view, importing VDP tags\n  and why that call is the most destructive one here, webservice targets, `delete-multiple`.\n- `references\u002Fcategories.md` — the tree endpoints, moving a category, taking a view out of one,\n  assignment from the view's side, what cascades.\n- `references\u002Fexternal-elements.md` — the element and provider type surface, the association\n  record in detail, element-to-element associations, what synchronisation adds, updates and\n  deletes, and how to read `\u002Fdetails`.\n- `references\u002Frenames.md` — a view renamed, recreated or moved: the template, the move, what to\n  re-apply.\n\nThe server is also its own reference: `GET \u002Fv3\u002Fapi-docs` on the marketplace returns the whole\nOpenAPI document, which settles any path or body this skill does not\ncover.\n\n## Verify\n\nA `200` here means less than usual: assignments report failure inside a `200` body, and the\nimport reports what it did rather than whether it worked. Read the object back, from the\nother side where there is one. Every read-back below — *verified: 9.5.1 (live, 2026-10-05)*; the external element's\n`\u002Fdetails`, *verified: 9.5.1 (live, 2026-09-10)*.\n\n| Question | Read-back |\n|---|---|\n| Did the tag\u002Fcategory land | `GET \u002Fpublic\u002Fapi\u002Ftags\u002F{id}` · `GET \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F{id}` |\n| Is the assignment real, from the tag's side | `GET \u002Fpublic\u002Fapi\u002Ftags\u002F{id}\u002Felements` → `{\"views\":[…],\"webservices\":[…]}` |\n| … from the category's side | `GET \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F{id}\u002Fviews` with `offset` and `limit` |\n| … from the view's side | `GET \u002Fpublic\u002Fapi\u002Fviews\u002F{viewId}\u002Ftags` · `GET \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fviews\u002F{viewId}\u002Fcategories` |\n| Is the view in the catalog at all | `GET \u002Fpublic\u002Fapi\u002Fview-details?databaseName=…&viewName=…` → `id`, `inLocal`, `inVDP` |\n| Did a renamed view keep its element | `view-details` on the new name → the `id` the old name had, with its tags, categories and endorsements |\n| What a synchronisation would change | `GET \u002Fpublic\u002Fapi\u002Felement-management\u002F{DATABASES\\|VIEWS}\u002Fchanges` — **before**, not after |\n| Did the import create what you meant | the `synchronize` response names each element: `externalElementsAdded\u002FUpdated\u002FDeleted` with `originalExternalElementId` |\n| Did the element import (read as you) | `GET \u002Fpublic\u002Fapi\u002Fexternal-elements\u002F{id}\u002Fdetails` — type, server, url, and its lineage. A consumer sees the element only with the Visualize permission of its element type, `METADATA` on every view it links to and `CONNECT` on their databases; a report over data outside Denodo also needs *Visualize external data*. A new type adds its own Visualize column, which an administrator grants to roles (External element, in the Permissions tab of the marketplace's Server Set-Up): tell the human what a new type still needs |\n| **Does the view show the element** | `GET \u002Fpublic\u002Fapi\u002Fviews\u002Ftree\u002Fexternal-elements\u002Flineage?databaseName=…&viewName=…` — the question a human actually asked (\"what consumes this?\"), answered from the other end. The view node must resolve to `databaseName`\u002F`viewName`, not stay a bare string |\n| Is it really gone | `GET` it: `404` is the answer you want. The tool reports that as `ok:false` and exit `1`, so a verification script must treat `404` as success here rather than stopping — *verified: 9.5.1 (live, 2026-09-10)* |\n| Which VDP tags are imported | `GET \u002Fpublic\u002Fapi\u002Ftags\u002Fvdp\u002Flocal` (`references\u002Ftags.md`) |\n\n## Common mistakes\n\n| You did | Server says | Fix |\n|---|---|---|\n| read `id: null` from `view-details` as \"not synchronised\" | `200`, and the same body a wrong `serverId` produces | ask the other servers first; only then synchronise |\n| `GET …\u002Fcategories\u002F{id}\u002Fviews` without paging | `400 MISSING_REQUEST_PARAMETER` | `--param offset=0 --param limit=50` |\n| `POST \u002Ftags` with a name that exists | `409`, empty body | look up by name first, then `PUT` |\n| take the first element `nameFilter` returned | `200`, the wrong tag | the filter matches substrings and ignores case — compare `name` exactly |\n| read an assignment's `200` as success | `200` and `[\u003Cview_id>]` | not assigned: already there or not synchronised — read `tags\u002F{id}\u002Felements`; synchronise, then re-assign |\n| `POST \u002Fviews\u002F{id}\u002Ftags` to add one tag | `200` | that endpoint **replaces** the view's tags; use `\u002Ftags\u002F{id}\u002Fviews` |\n| `DELETE` a parent category | `200` | its children went too — read `…\u002Fcategories\u002Ftree` before offering it |\n| `DELETE` the same tag twice | `500 GENERIC \"Incorrect number of deleted tuples\"` | it was already gone; categories answer `200` and servers `404` for the same thing |\n| `synchronize` a tool server before the associated view is in the catalog | `400 INVALID_VDP_EXTERNAL_ELEMENT_METADATA \"The view '…' does not exist\"` | the view **does** exist in VDP: either the marketplace copy is missing — synchronise the catalog — or the tool server was created under the wrong `serverId` (rule 2): ask the other servers first |\n| rename the association array type | `400 INVALID_EXTERNAL_ELEMENT_INTERFACE_VIEW … expected type external_element_association_array_type` | keep the contract's names |\n| `LEFT OUTER JOIN` for elements without associations | `400 … Required field 'associated_element_id' is null` | `INNER JOIN` plus a `UNION ALL` branch with a NULL array |\n| drop an element from a non-empty snapshot | `200`, and the element is **deleted** with its tags and categories | that is the contract: the interface view is the full picture, not a delta |\n| empty the snapshot entirely to clear elements | `200`, nothing deleted | an empty result is treated as \"no data\", not \"delete everything\" — *verified: 9.5.1 (live, 2026-09-10)* |\n| `DELETE` an external tool server to tidy up | `200` | every element it imported disappeared with it, tags and categories included |\n| rename a view in VDP, then synchronise without `matchedElements` | `200`, old name under `removed`, new under `inserted` | the element went with every tag, category, description and endorsement on it; the new one is empty. Match the pair in the same call — and if it already ran, only a `view-details` saved before the rename can say what to re-apply |\n| `\"type\":\"View\"` (or any `type`) in a matched pair | `400 \"Invalid input JSON\"` | the pair is `localElement` and `serverElement`, nothing else |\n| match a view moved to another database | `200`, the pair in neither `inserted` nor `removed` | ignored, not applied: nothing happened. Re-apply from the saved `view-details` after a plain synchronisation |\n| `POST \u002Fproperty-management\u002Fviews\u002F{id}\u002Fgroups` to add one group | `200` | it **replaces** the view's groups, and the values of the ones left out are gone |\n\nDestructive here is decided by method and path, not by the word in it:\n\n| Call | What is lost |\n|---|---|\n| `DELETE \u002Fpublic\u002Fapi\u002Ftags\u002F{id}`, `\u002Ftags\u002Fdelete-multiple` | the tag and every assignment of it |\n| `DELETE \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F{id}` | the category **and all its children** |\n| `DELETE \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002F{id}` | the server and **every element it imported** |\n| `DELETE` of an assignment, a tag or a category off a view | that assignment (`references\u002Ftags.md`) |\n| `POST \u002Fpublic\u002Fapi\u002Ftags\u002Fvdp\u002Fsynchronize` | every imported VDP tag missing from the list you send — a complete list still replaces a set the human has not seen |\n| `POST \u002Fpublic\u002Fapi\u002Felement-management\u002F{all,DATABASES,VIEWS,…}\u002Fsynchronize` | what VDP no longer has (`localElements`), in any mode — a renamed view's element unless the pair is matched; `\"SERVER\"` also overwrites marketplace edits |\n| `POST \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002Fsynchronize` | every element the interface view no longer selects, with its tags and categories |\n| `POST \u002Fpublic\u002Fapi\u002Fviews\u002F{id}\u002Ftags`, `\u002Fpublic\u002Fapi\u002Fcategory-management\u002Fviews\u002F{id}\u002Fcategories`, `\u002Fpublic\u002Fapi\u002Fproperty-management\u002Fviews\u002F{id}\u002Fgroups` | the view's previous set — they replace, not add; a property group left out takes its values |\n\nAll of them wait for the human's yes to the calls you show (`\u002Fdenodo:vql`) — the request that\nasked for them is not that yes, and with nobody to answer the body goes in a file and your\nmessage — except the two in **Who sends it**.\n","# Marketplace tags, categories and external elements\n\nThree objects that live in the **Data Marketplace**, not in Virtual DataPort: the\nmarketplace **tag**, the **category**, and the **external element** that represents an asset\nfrom another tool. The channel is REST — `scripts\u002Fdenodo api` — and the server is the one\nin `marketplace_url`, not the VDP port.\n\nA \"tag\" alone does not say which object the human means. A **VDP tag** is `CREATE TAG` in\nVirtual DataPort and belongs to `\u002Fdenodo:catalog`; a **marketplace tag** is\n`POST \u002Fpublic\u002Fapi\u002Ftags` here. They are different objects on different servers, and a request\nsent to the wrong one succeeds — on the wrong side. When the request does not say, ask — or\nlook at where the object has to be visible: a consumer who only browses the marketplace means\na marketplace tag.\nViews themselves are `\u002Fdenodo:views` and `\u002Fdenodo:datasources`; applying anything is\n`\u002Fdenodo:execute`; the safety rule and the working loop are `\u002Fdenodo:vql`.\n\n## Two rules that govern everything below\n\n**1. Names are not keys.** Every object here is addressed by a numeric `id` that the server\nassigns and that differs between installations. A template cannot contain one. There is no\n`CREATE OR REPLACE`: idempotence is a *sequence* — look the name up, then `POST` if it is\nmissing or `PUT` if it is there. Two calls, every time, and the lookup is not optional.\n\n**2. Nothing can be attached to a view the marketplace has not synchronised.** The\nmarketplace keeps its own copy of the VDP catalog. A view that exists in VDP but is not in\nthat copy has no id, and `view-details` says so:\n`{\"id\": null, \"inLocal\": false, \"inVDP\": true}` — *verified: 9.5.1 (live, 2026-09-10)*.\nSynchronise first (see the template), then assign.\n\n**But that answer has two causes, and they look identical.** A view queried against the\n*wrong* `serverId` returns exactly the same body — `id: null`, `inLocal: false`, and\n`inVDP: true` even from a server that never saw the database — and nothing in the response\nnames the server it means — *verified: 9.5.1 (live, 2026-09-10)*. So before concluding\n\"needs synchronising\", repeat the `view-details` call against the other registered servers:\nif one of them answers `inLocal: true`, you had the wrong id and nothing needs\nsynchronising. Getting this backwards means changing a shared catalog to fix a query\nparameter. `VIEWS\u002Fchanges` does not shortcut the round: a server that never carried the\ndatabase lists its views under `serverElements` too, as views it would import —\n*verified: 9.5.1 (live, 2026-10-01)*. The server list does not say which server carries a\ndatabase; under a wrong id everything is created happily and only the import fails, naming a\nview that \"does not exist\".\n\n## Name the server: `serverId`\n\nThe marketplace can have several VDP servers registered, and tags, views and external tool\nservers are **per server** — the same call against two ids returns two different catalogs.\nWith more than one registered, omitting the server is an error whose text names something\nelse entirely:\n\n| Call without a server named | Answer |\n|---|---|\n| `\u002Fpublic\u002Fapi\u002Ftags`, `\u002Fpublic\u002Fapi\u002Fviews\u002F…` | `500 {\"code\":\"GENERIC\",\"message\":\"Session Expired.\"}` |\n| `\u002Fpublic\u002Fapi\u002Fexternal-tool-servers` | `403`, empty body |\n| `\u002Fpublic\u002Fapi\u002Fcategory-management\u002F…` | works — categories are not server-scoped |\n\n*verified: 9.5.1 (live, 2026-09-10).* Read the ids once:\n\n```bash\n# verified: 9.5.1 (live, 2026-10-07)\napi get --env dev \u002Fpublic\u002Fapi\u002Fconfiguration\u002Fservers\n# → [{\"id\":\u003CserverId>,\"name\":\"\u003CVDP server as registered>\",\"url\":\"\u002F\u002F\u003Cvdp-host>:9999\u002Fadmin\"}, …]\n```\n\n**The id belongs in the profile, as `marketplace_server_id` — a human puts it there, not\nyou — and the tool adds it to every call by itself.** That is why no template below names a\nserver: the profile is the single place the environment is described, so the same template\nworks against any marketplace. One registered server needs no id at all.\n\n`--param serverId=\u003Cid>` overrides the profile for one call, and the transport then leaves\nthat call alone. Reach for it only when you genuinely mean a different server than the\nprofile's — asking each registered server which one holds a view, rule 2, is the case\nthat needs it. Putting it on ordinary calls silently pins the environment into a command.\n\n## Templates\n\n### Tag, with an assignment\n\n```bash\n# verified: 9.5.1 (live, 2026-09-10)\n\n# 1. does it exist? — the lookup that replaces CREATE OR REPLACE\napi get --env dev \u002Fpublic\u002Fapi\u002Ftag-management\u002Ftags \\\n    --param offset=0 --param limit=50 --param nameFilter=pii\n# → {\"count\":1,\"elements\":[{\"id\":\u003Canother tag's id>,\"name\":\"pii_legacy\", …}]}   ← NOT your tag\n\n# 2a. missing → create it\napi post --env dev \u002Fpublic\u002Fapi\u002Ftags \\\n    --json '{\"name\":\"pii\",\"description\":\"Personal data, GDPR scope\",\"descriptionType\":\"TEXT\"}'\n# → {\"id\":\u003Ctag_id>,\"name\":\"pii\",\"vdpTag\":false, …}\n\n# 2b. present → update it, id and all four fields in the body\napi put --env dev \u002Fpublic\u002Fapi\u002Ftags \\\n    --json '{\"id\":\u003Ctag_id>,\"name\":\"pii\",\"description\":\"Personal data, GDPR scope\",\"descriptionType\":\"TEXT\"}'\n\n# 3. hang it on views, by marketplace view id\napi post --env dev \u002Fpublic\u002Fapi\u002Ftags\u002F\u003Ctag_id>\u002Fviews --json '[\u003Cview_id>]'\n# → []   ← empty list IS the success\n```\n\n- **`nameFilter` is a case-insensitive *substring* match, so the lookup needs a second step:\n  compare `name` yourself, exactly.** `nameFilter=pii` also returns a tag called `pii_legacy`,\n  and `nameFilter=finance` one called `Finance` — *verified: 9.5.1 (live, 2026-09-10)*. Taking the first element and calling it yours is how a script ends up\n  `PUT`-ing over somebody else's tag. A namesake differing only in case is a collision, not a\n  match: creating the second one is `409`, so that case is a question for the human, not\n  something to resolve automatically.\n- **The two base paths are the API's own, not a slip in this template:** the paged lookup is\n  `\u002Fpublic\u002Fapi\u002Ftag-management\u002Ftags`, while create, update and the per-tag reads are\n  `\u002Fpublic\u002Fapi\u002Ftags\u002F…`. Do not \"correct\" one to match the other.\n- `name`, `description` and `descriptionType` are all mandatory on create; missing ones are\n  `400 VALIDATE_FIELD`. `descriptionType` is `TEXT` or `RICH_TEXT` (the latter renders HTML).\n- A duplicate name is `409` with an **empty body** — no message to read. That is why step 1\n  exists.\n- **`POST \u002Ftags\u002F{id}\u002Fviews` adds; `POST \u002Fviews\u002F{id}\u002Ftags` replaces** the view's whole tag\n  set. Use the first unless you mean to wipe what other people put there.\n- The response is the list of ids that were **not** assigned. `[]` is success; `[\u003Cview_id>]`\n  means \"already assigned\" **or** \"no such view\" — the two are indistinguishable, both come\n  back `200` — *verified: 9.5.1 (live, 2026-09-10)*. Read the assignment back.\n- **Anything that runs twice must read before it writes:** check\n  `GET \u002Fpublic\u002Fapi\u002Ftags\u002F{id}\u002Felements` and skip the `POST` for a view already listed, so\n  `[\u003Cview_id>]` always means something is wrong; `PUT` a found tag only when a field differs.\n- Assigning to an external element instead of a view is\n  `POST \u002Fpublic\u002Fapi\u002Ftags\u002F{id}\u002Fexternal-elements` with the same body shape, and it answers\n  with an **empty body**, not a list.\n\n### Category tree\n\n```bash\n# verified: 9.5.1 (live, 2026-09-10)\napi post --env dev \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories \\\n    --json '{\"name\":\"Consumer marts\",\"description\":\"What analysts read\",\"descriptionType\":\"TEXT\"}'\n# → {\"id\":\u003Ccategory_id>,\"parentId\":null, …}\n\napi post --env dev \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories \\\n    --json '{\"name\":\"Retail\",\"description\":\"Retail marts\",\"descriptionType\":\"TEXT\",\"parentId\":\u003Ccategory_id>}'\n\napi post --env dev \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F\u003Ccategory_id>\u002Fviews \\\n    --json '[\u003Cview_id>]'\n# → []\n```\n\nSame lookup-first rule (`GET …\u002Fcategories\u002Ftree`), same empty-list-is-success rule. Two\ndifferences from tags, both *verified: 9.5.1 (live, 2026-09-10)*:\n\n- **Deleting a parent deletes its children.** No warning, no mention of them in the\n  response, and the assignments go with them. Read the tree before you offer a delete.\n- **A repeated `DELETE` answers `200`**, where a repeated tag delete answers `500`. Do not\n  read a status to decide whether something existed.\n\n### Synchronising the marketplace catalog with VDP\n\nNeeded before any assignment to a view, and before an external element can name one. Look\nat the radius first — the whole point of `changes` is that it costs nothing:\n\n```bash\n# verified: 9.5.1 (live, 2026-10-07)\napi get --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FDATABASES\u002Fchanges\napi get --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FVIEWS\u002Fchanges\n# → {\"serverElements\":[…new…], \"modifiedElements\":[…], \"localElements\":[…gone from VDP…]}\n\napi post --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FDATABASES\u002Fsynchronize \\\n    --json '{\"proceedWithConflicts\":\"SERVER_WITH_LOCAL_CHANGES\"}'\napi post --env dev \u002Fpublic\u002Fapi\u002Felement-management\u002FVIEWS\u002Fsynchronize \\\n    --json '{\"proceedWithConflicts\":\"SERVER_WITH_LOCAL_CHANGES\"}'\n# → {\"inserted\":[…],\"modified\":[…],\"removed\":[…]}\n```\n\n- **Both steps.** A new database registers with the first call and its views still have no\n  ids; only `VIEWS\u002Fsynchronize` gives them ids — *verified: 9.5.1 (live, 2026-09-10)*.\n- `proceedWithConflicts` decides what happens to descriptions that differ:\n  `SERVER_WITH_LOCAL_CHANGES` takes VDP's but keeps edits made in the marketplace,\n  `LOCAL` keeps the marketplace's, `SERVER` overwrites them. **Use the first**; `SERVER`\n  is the one that quietly destroys other people's work.\n- `localElements` in `changes` is the list of things that will be **removed** from the\n  marketplace because VDP no longer has them, whatever the conflict mode. **A view renamed in\n  VDP is in that list under its old name** — the next section.\n- A `modifiedElements` entry with `reason: \"DESCRIPTION,FIELD_DESCRIPTION\"` is usually an\n  element whose descriptions were edited in the marketplace: it is listed on every reading,\n  and `SERVER_WITH_LOCAL_CHANGES` keeps those edits — *verified: 9.5.1 (live, 2026-10-01)*.\n  Such an entry loses nothing in the call — say so when you show the human the radius.\n- **The radius is a reading, not a promise, and there is no scope.** `changes` describes the\n  moment you asked; anything created between then and the call comes along too, and the call\n  cannot be narrowed to one database — it synchronises the whole server. On a shared server\n  that means other people's new views land in the catalog with yours. Re-read the response:\n  `inserted` says what actually happened.\n- The user running it needs `METADATA` on the whole VDP catalog. Under a narrower account\n  the marketplace treats what it cannot see as deleted and **removes it** —\n  *unverified: 9.5 documentation only* (Synchronize with Virtual DataPort).\n- **Who sends it.** You, when the same call with `--plan`, right before it, says `needs_yes:\n  false`: it reads both `changes` — both, even when only `VIEWS\u002Fsynchronize` is needed — and\n  finds only what this session created (`radius.own`): every `serverElements` entry a database\n  or view of yours, every `localElements` entry the element of a view of yours — your own view\n  renamed, with the pair matched in the call, included; with\n  `SERVER_WITH_LOCAL_CHANGES`, on a profile that is not production; `modifiedElements` do not\n  change it. Then read `removed` and `inserted` against that radius, and both `changes` again:\n  once a database is gone from VDP, its elements left the catalog with `removed` empty in both\n  responses — *verified: 9.5.1 (live, 2026-10-06)* — so only the second reading shows what went.\n  Tell the human at once about anything you did not expect. One entry in `radius.not_own` —\n  another team's new database, an orphan you did not make — and the body goes in a file, with\n  what waiting risks; the human sends it or says yes (`\u002Fdenodo:vql`). The one other exception\n  is the first import on a tool server you created in this session (the external element, step\n  4). Neither applies on production; nothing else about a `synchronize` is exempt.\n\n| Rationalization | Reality |\n|---|---|\n| \"Nothing gets removed — the rest of the radius only adds\" | Clean is not the test; whose is. Another team's new database or view under `serverElements` lands in the catalog everybody browses before its owner chose to publish it. |\n| \"The pair is matched, so the rename costs nothing\" | A view that existed before this session is someone's: the rename and its matched `synchronize` wait for one yes, shown together. |\n\n### A view in the marketplace is renamed, recreated or moved\n\nWhat people add in the marketplace belongs to the view's **element**, found by database and\nview name, and a synchronisation sees a renamed view as one element removed with all of it and\nanother imported empty. So: `view-details` on the view **before** the change, saved to a file;\nthe pair matched in the same `synchronize` call (`matchedElements`); a `DROP` and `CREATE` under\nthe same name in one run; a move to another database cannot be matched at all. The template,\nwho sends the matched call, and the move: `references\u002Frenames.md`.\n\n### External element — a dashboard, job or contract from another tool\n\nThere is no `POST \u002Fexternal-elements`. An external element is *imported*: the marketplace\nreads an interface view in VDP and creates, updates and deletes elements to match it. So the\nchain runs VQL and REST alternately, and the whole block below carries one verification mark.\n\n```bash\n# verified: 9.5.1 (live, 2026-09-10) — the chain as a whole\n\n# 0. the views this element will link to must already be in the marketplace catalog\n#    (previous template) — otherwise step 4 fails and nothing is created\n# 0b. the element type the VQL half names ('DASHBOARD') must be listed; missing →\n#     POST \u002Fpublic\u002Fapi\u002Fexternal-elements-types, body in references\u002Fexternal-elements.md\n\n# 1. provider type: the tool the metadata comes from. Multipart, but the icon is optional\napi post --env dev \u002Fpublic\u002Fapi\u002Fexternal-providers-types \\\n    --part 'request=json:{\"name\":\"ACME_BI\",\"visualName\":\"Acme BI\"}'\n# → 201 {\"externalProviderTypeId\":\u003Cprovider_type_id>,\"iconImage\":null, …}\n#   with a logo:  --part 'icon=@.\u002Facme.svg'\n#   the next call answers 200, this one 201 — check 2xx, never a particular code\n#   — verified: 9.5.1 (live, 2026-09-12)\n\n# 2. the server that will read the contract. The interface view need not exist yet\napi post --env dev \u002Fpublic\u002Fapi\u002Fexternal-tool-servers \\\n    --json '{\"type\":\"CUSTOM\",\"name\":\"acme_bi_server\",\"description\":\"Acme BI dashboards\",\n             \"externalProviderTypeId\":\u003Cprovider_type_id>,\n             \"databaseName\":\"sales_analytics\",\"viewName\":\"i_acme_bi_elements\"}'\n# → {\"id\":\u003Ctool_server_id>, …}\n\n# 3. ask the marketplace for the contract it expects. NOT a file to apply as it stands:\n#    the two CREATE TYPE come back usable verbatim, the interface view comes back\n#    without SET IMPLEMENTATION and without FOLDER — you write the implementation\napi get --env dev \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002F\u003Ctool_server_id>\u002Fvql-metadata\n# → a JSON string: CONNECT DATABASE …; two CREATE TYPE; CREATE INTERFACE VIEW (columns only)\n\n# 4. import\napi post --env dev \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002Fsynchronize \\\n    --json '{\"externalToolServerIds\":[\u003Ctool_server_id>]}'\n# → externalElementsAdded \u002F Updated \u002F Deleted, per server\n```\n\n**Step 4 is a `synchronize`, and the safety rule of `\u002Fdenodo:vql` says stop and ask before\none — but the first import on a server you have just created cannot delete anything.** The\ncall deletes elements *absent from the snapshot*, and a server created in this same session\nhas imported none. So: your own new server, first import — go, and say in the summary what\nwas imported. **From the second import on, the confirmation is back**, because the interface\nview is the whole picture and a row that stopped being selected is an element that gets\nremoved with its tags and categories. Read the current set first and show the human what is\nabout to disappear — the server's own elements are\n`POST \u002Fpublic\u002Fapi\u002Fsearch\u002Fexternal-elements\u002Fmetadata` with `externalToolServerIds: [\u003Cid>]`\nand the nine other mandatory fields — *verified: 9.5.1 (live, 2026-09-12)*.\nThere is no `GET …\u002Fexternal-tool-servers\u002F{id}\u002Fexternal-elements`: that path is `404`.\nNone of this changes the tool: the call is stamped\n`destructive: replace` either way, and on a `production` profile it is refused without\n`--allow-destructive`, which only a human may add.\n\n**Look each type up before creating it — they are different objects.** The element type, what\nthe asset *is*, is listed by `GET \u002Fpublic\u002Fapi\u002Fexternal-elements-types`, which returns the name as\n`externalElementTypeName` (sent as `name`) and has no `description`; the provider type, the tool\nit *comes from*, by `GET \u002Fpublic\u002Fapi\u002Fexternal-providers-types`. **That listing embeds every icon\nas base64 and can be large** — read it into a file and project\n`{externalProviderTypeId, name, visualName}` rather than letting it into the conversation —\n*verified: 9.5.1 (live, 2026-09-10)*. Tableau and Power BI are the documented native tools: the\n`REPORT` element type, the `TABLEAU` and `POWERBI` providers. Every other type a marketplace\nlists (`DASHBOARD`, `ETL_JOB`, an `…_PROVIDER`) is a custom type, created on that installation,\nand another marketplace may lack it — the template's `DASHBOARD` included (step 0b). A new type\nis a marketplace-wide object that everyone then sees. Step 1 of the chain above is skipped only\nwhen a listed provider type really is the asset's tool.\n\nThe VQL half — the implementation behind the contract from step 3. **Its names are outside\nthe naming convention of `\u002Fdenodo:vql` on purpose:** the interface view's name is part of\nthe contract you gave the tool server, and the three views under it are its implementation,\nnot integration-layer or business-entity objects. Keep them together in one folder and named\nafter the tool, as below; do not rename them to `iv_…` to match the table.\n\n```sql\n-- verified: 9.5.1 (live, 2026-10-07)\nCONNECT DATABASE sales_analytics;\n\n-- the two types come from vql-metadata verbatim. The names are part of the contract\nCREATE OR REPLACE TYPE external_element_association_type AS REGISTER OF (\n    associated_element_id:text, external_tool_server_name:text,\n    associated_element_type:text, direction:text, role:text);\nCREATE OR REPLACE TYPE external_element_association_array_type AS ARRAY OF external_element_association_type;\n\nCREATE OR REPLACE VIEW acme_bi_metadata FOLDER = '\u002F02 - integration'\n    AS SELECT 'ACME-DASH-01'                       AS id,\n              'Revenue cockpit'                    AS name,\n              'Weekly revenue by region'           AS description,\n              'DASHBOARD'                          AS external_element_type,\n              'https:\u002F\u002Facme.example\u002Fd\u002Frevenue'     AS url,\n              CAST('timestamp', '2026-01-19 09:00:00') AS created_at,\n              CAST('timestamp', '2026-09-06 07:45:00') AS updated_at\n       FROM DUAL();\n\nCREATE OR REPLACE VIEW acme_bi_associations FOLDER = '\u002F02 - integration'\n    AS SELECT 'ACME-DASH-01'                        AS owner_id,\n              'sales_analytics.household_income'    AS associated_element_id,\n              CAST('text', NULL)                    AS external_tool_server_name,\n              'VIEW'                                AS associated_element_type,\n              'OUT'                                 AS direction,\n              'consumes'                            AS role\n       FROM DUAL();\n\nCREATE OR REPLACE VIEW acme_bi_elements FOLDER = '\u002F02 - integration'\n    AS SELECT m.id AS id, m.name AS name, m.description AS description,\n              m.external_element_type AS external_element_type, m.url AS url,\n              m.created_at AS created_at, m.updated_at AS updated_at,\n              CAST('external_element_association_array_type',\n                   NEST(a.associated_element_id, a.external_tool_server_name,\n                        a.associated_element_type, a.direction, a.role)) AS associations\n       FROM acme_bi_metadata m INNER JOIN acme_bi_associations a ON m.id = a.owner_id\n       GROUP BY m.id, m.name, m.description, m.external_element_type, m.url,\n                m.created_at, m.updated_at;\n\nCREATE OR REPLACE INTERFACE VIEW i_acme_bi_elements (\n        id:text, name:text, description:text, external_element_type:text, url:text,\n        created_at:timestamp, updated_at:timestamp,\n        associations:external_element_association_array_type\n    )\n    SET IMPLEMENTATION acme_bi_elements\n    FOLDER = '\u002F02 - integration';\n```\n\nFour things here are load-bearing, each *verified: 9.5.1 (live, 2026-09-10)*:\n\n- **`external_element_association_array_type` is the name the marketplace checks**, literally.\n  Rename it and synchronisation refuses the whole server:\n  `400 INVALID_EXTERNAL_ELEMENT_INTERFACE_VIEW … expected type external_element_association_array_type`.\n- **`external_element_type` must equal an element type's `name`**, character for character\n  (read back as `externalElementTypeName`, above).\n- **`INNER JOIN`, not `LEFT OUTER JOIN`.** A left join over an element with no associations\n  makes `NEST` produce one all-null record, and the import rejects the element:\n  `400 … Required field 'associated_element_id' is null … association index 0`. As written\n  above — every element has an association — the inner join is the whole story; only if some\n  element has none, add the `UNION ALL` branch with a NULL array in\n  `references\u002Fexternal-elements.md`.\n- `CREATE OR REPLACE INTERFACE VIEW … SET IMPLEMENTATION` in one statement, so the file\n  re-applies. `ALTER INTERFACE VIEW` does the same thing but is a change to an existing\n  object and needs a human's yes (`\u002Fdenodo:vql`).\n\n`SELECT * FROM i_acme_bi_elements` before step 4: an interface view accepts an implementation\nthat does not match it, and only the `SELECT` shows it (`\u002Fdenodo:views`).\n\n## What you need before filling a template\n\n| Slot | Where it comes from |\n|---|---|\n| Which \"tag\" | marketplace or VDP (top of this skill); ask when the request does not say |\n| `serverId` | `marketplace_server_id` in the profile, set by a human (Name the server); never in a call unless you mean another server |\n| Tag or category name, description | the human. Both are shown to consumers browsing the marketplace, so they read as labels, not as identifiers |\n| A new category's parent | `GET …\u002Fcategories\u002Ftree` first; a *domain* the human names is a category of this tree, usually a root one. A live marketplace's tree is a taxonomy somebody designed — hang the new category inside the branch it belongs to. A **new top-level** category is a question for the human, not a default: it adds an axis to what everybody browsing sees. (`GET …\u002Fcategories\u002F{id}\u002Fpotential-parent` is for moving an existing one) |\n| Every numeric id | never a template, never memory: a `GET` in this session. Ids differ per installation and per server |\n| View ids to assign to | `GET \u002Fpublic\u002Fapi\u002Fview-details?databaseName=…&viewName=…`; `id:null`: rule 2, the other servers first, then synchronise. Save the answer to a file and read `id`, `inLocal` and `inVDP` out of it with a script — it carries the view's whole field list and its connection URIs, and truncating it instead is how the three fields get missed |\n| Whether the catalog may be synchronised | the call's `--plan` (`needs_yes`), see **Who sends it** |\n| Whether a view about to be renamed, recreated or moved is in the marketplace | `view-details` on it **before** the change — `id` not null and `inLocal: true`. The answer is also what to keep: it is the only copy of the element's metadata |\n| Which removed element is which new one | you renamed it, or the human says so. The same database and the same columns are a hint, not proof |\n| For an external element: the type | `GET \u002Fpublic\u002Fapi\u002Fexternal-elements-types` — list it; create one if none fits |\n| For an external element: id, name, url, timestamps | the source tool. `updated_at` is what drives updates — an element whose `updated_at` does not move is never refreshed |\n| Which views the element links to | the human, plus their exact `database.view` — an association naming a view the marketplace does not know fails the whole import |\n| Direction and role | `IN`\u002F`OUT` plus free text (`consumes`, `feeds`, `validates`). The documentation calls `direction` the data-flow direction and the 360 graph draws its arrow by it, without saying from whose side; Denodo's own sample marks every association `OUT`, a dashboard that *reads* a view included, and what `IN` changes is *unverified*. Follow the marketplace's existing elements, say which you chose, and look at the arrow after the first import. The role is the label on the edge of the 360 graph |\n\nDo not ask about property groups, endorsements, requests or personalisation — they are\nmarketplace features with their own screens, not part of creating these objects.\n\n## Reference\n\n- `references\u002Ftags.md` — the full tag surface, taking a tag off one view, importing VDP tags\n  and why that call is the most destructive one here, webservice targets, `delete-multiple`.\n- `references\u002Fcategories.md` — the tree endpoints, moving a category, taking a view out of one,\n  assignment from the view's side, what cascades.\n- `references\u002Fexternal-elements.md` — the element and provider type surface, the association\n  record in detail, element-to-element associations, what synchronisation adds, updates and\n  deletes, and how to read `\u002Fdetails`.\n- `references\u002Frenames.md` — a view renamed, recreated or moved: the template, the move, what to\n  re-apply.\n\nThe server is also its own reference: `GET \u002Fv3\u002Fapi-docs` on the marketplace returns the whole\nOpenAPI document, which settles any path or body this skill does not\ncover.\n\n## Verify\n\nA `200` here means less than usual: assignments report failure inside a `200` body, and the\nimport reports what it did rather than whether it worked. Read the object back, from the\nother side where there is one. Every read-back below — *verified: 9.5.1 (live, 2026-10-05)*; the external element's\n`\u002Fdetails`, *verified: 9.5.1 (live, 2026-09-10)*.\n\n| Question | Read-back |\n|---|---|\n| Did the tag\u002Fcategory land | `GET \u002Fpublic\u002Fapi\u002Ftags\u002F{id}` · `GET \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F{id}` |\n| Is the assignment real, from the tag's side | `GET \u002Fpublic\u002Fapi\u002Ftags\u002F{id}\u002Felements` → `{\"views\":[…],\"webservices\":[…]}` |\n| … from the category's side | `GET \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F{id}\u002Fviews` with `offset` and `limit` |\n| … from the view's side | `GET \u002Fpublic\u002Fapi\u002Fviews\u002F{viewId}\u002Ftags` · `GET \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fviews\u002F{viewId}\u002Fcategories` |\n| Is the view in the catalog at all | `GET \u002Fpublic\u002Fapi\u002Fview-details?databaseName=…&viewName=…` → `id`, `inLocal`, `inVDP` |\n| Did a renamed view keep its element | `view-details` on the new name → the `id` the old name had, with its tags, categories and endorsements |\n| What a synchronisation would change | `GET \u002Fpublic\u002Fapi\u002Felement-management\u002F{DATABASES\\|VIEWS}\u002Fchanges` — **before**, not after |\n| Did the import create what you meant | the `synchronize` response names each element: `externalElementsAdded\u002FUpdated\u002FDeleted` with `originalExternalElementId` |\n| Did the element import (read as you) | `GET \u002Fpublic\u002Fapi\u002Fexternal-elements\u002F{id}\u002Fdetails` — type, server, url, and its lineage. A consumer sees the element only with the Visualize permission of its element type, `METADATA` on every view it links to and `CONNECT` on their databases; a report over data outside Denodo also needs *Visualize external data*. A new type adds its own Visualize column, which an administrator grants to roles (External element, in the Permissions tab of the marketplace's Server Set-Up): tell the human what a new type still needs |\n| **Does the view show the element** | `GET \u002Fpublic\u002Fapi\u002Fviews\u002Ftree\u002Fexternal-elements\u002Flineage?databaseName=…&viewName=…` — the question a human actually asked (\"what consumes this?\"), answered from the other end. The view node must resolve to `databaseName`\u002F`viewName`, not stay a bare string |\n| Is it really gone | `GET` it: `404` is the answer you want. The tool reports that as `ok:false` and exit `1`, so a verification script must treat `404` as success here rather than stopping — *verified: 9.5.1 (live, 2026-09-10)* |\n| Which VDP tags are imported | `GET \u002Fpublic\u002Fapi\u002Ftags\u002Fvdp\u002Flocal` (`references\u002Ftags.md`) |\n\n## Common mistakes\n\n| You did | Server says | Fix |\n|---|---|---|\n| read `id: null` from `view-details` as \"not synchronised\" | `200`, and the same body a wrong `serverId` produces | ask the other servers first; only then synchronise |\n| `GET …\u002Fcategories\u002F{id}\u002Fviews` without paging | `400 MISSING_REQUEST_PARAMETER` | `--param offset=0 --param limit=50` |\n| `POST \u002Ftags` with a name that exists | `409`, empty body | look up by name first, then `PUT` |\n| take the first element `nameFilter` returned | `200`, the wrong tag | the filter matches substrings and ignores case — compare `name` exactly |\n| read an assignment's `200` as success | `200` and `[\u003Cview_id>]` | not assigned: already there or not synchronised — read `tags\u002F{id}\u002Felements`; synchronise, then re-assign |\n| `POST \u002Fviews\u002F{id}\u002Ftags` to add one tag | `200` | that endpoint **replaces** the view's tags; use `\u002Ftags\u002F{id}\u002Fviews` |\n| `DELETE` a parent category | `200` | its children went too — read `…\u002Fcategories\u002Ftree` before offering it |\n| `DELETE` the same tag twice | `500 GENERIC \"Incorrect number of deleted tuples\"` | it was already gone; categories answer `200` and servers `404` for the same thing |\n| `synchronize` a tool server before the associated view is in the catalog | `400 INVALID_VDP_EXTERNAL_ELEMENT_METADATA \"The view '…' does not exist\"` | the view **does** exist in VDP: either the marketplace copy is missing — synchronise the catalog — or the tool server was created under the wrong `serverId` (rule 2): ask the other servers first |\n| rename the association array type | `400 INVALID_EXTERNAL_ELEMENT_INTERFACE_VIEW … expected type external_element_association_array_type` | keep the contract's names |\n| `LEFT OUTER JOIN` for elements without associations | `400 … Required field 'associated_element_id' is null` | `INNER JOIN` plus a `UNION ALL` branch with a NULL array |\n| drop an element from a non-empty snapshot | `200`, and the element is **deleted** with its tags and categories | that is the contract: the interface view is the full picture, not a delta |\n| empty the snapshot entirely to clear elements | `200`, nothing deleted | an empty result is treated as \"no data\", not \"delete everything\" — *verified: 9.5.1 (live, 2026-09-10)* |\n| `DELETE` an external tool server to tidy up | `200` | every element it imported disappeared with it, tags and categories included |\n| rename a view in VDP, then synchronise without `matchedElements` | `200`, old name under `removed`, new under `inserted` | the element went with every tag, category, description and endorsement on it; the new one is empty. Match the pair in the same call — and if it already ran, only a `view-details` saved before the rename can say what to re-apply |\n| `\"type\":\"View\"` (or any `type`) in a matched pair | `400 \"Invalid input JSON\"` | the pair is `localElement` and `serverElement`, nothing else |\n| match a view moved to another database | `200`, the pair in neither `inserted` nor `removed` | ignored, not applied: nothing happened. Re-apply from the saved `view-details` after a plain synchronisation |\n| `POST \u002Fproperty-management\u002Fviews\u002F{id}\u002Fgroups` to add one group | `200` | it **replaces** the view's groups, and the values of the ones left out are gone |\n\nDestructive here is decided by method and path, not by the word in it:\n\n| Call | What is lost |\n|---|---|\n| `DELETE \u002Fpublic\u002Fapi\u002Ftags\u002F{id}`, `\u002Ftags\u002Fdelete-multiple` | the tag and every assignment of it |\n| `DELETE \u002Fpublic\u002Fapi\u002Fcategory-management\u002Fcategories\u002F{id}` | the category **and all its children** |\n| `DELETE \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002F{id}` | the server and **every element it imported** |\n| `DELETE` of an assignment, a tag or a category off a view | that assignment (`references\u002Ftags.md`) |\n| `POST \u002Fpublic\u002Fapi\u002Ftags\u002Fvdp\u002Fsynchronize` | every imported VDP tag missing from the list you send — a complete list still replaces a set the human has not seen |\n| `POST \u002Fpublic\u002Fapi\u002Felement-management\u002F{all,DATABASES,VIEWS,…}\u002Fsynchronize` | what VDP no longer has (`localElements`), in any mode — a renamed view's element unless the pair is matched; `\"SERVER\"` also overwrites marketplace edits |\n| `POST \u002Fpublic\u002Fapi\u002Fexternal-tool-servers\u002Fsynchronize` | every element the interface view no longer selects, with its tags and categories |\n| `POST \u002Fpublic\u002Fapi\u002Fviews\u002F{id}\u002Ftags`, `\u002Fpublic\u002Fapi\u002Fcategory-management\u002Fviews\u002F{id}\u002Fcategories`, `\u002Fpublic\u002Fapi\u002Fproperty-management\u002Fviews\u002F{id}\u002Fgroups` | the view's previous set — they replace, not add; a property group left out takes its values |\n\nAll of them wait for the human's yes to the calls you show (`\u002Fdenodo:vql`) — the request that\nasked for them is not that yes, and with nobody to answer the body goes in a file and your\nmessage — except the two in **Who sends it**.\n",{"name":5,"description":7},"main","fd41fb386b25141c459264d10a1c49bd3b4f4c4b","skills\u002Fmarketplace","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills","https:\u002F\u002Fgithub.com\u002Fkirivandubai","2026-10-29 13:49:22",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add kirivandubai\u002Fdenodo_wipe_coading_skills --skill marketplace",{"tool":35,"command":36},"bunx","bunx skills add kirivandubai\u002Fdenodo_wipe_coading_skills --skill marketplace",{"tool":38,"command":39},"pnpm","pnpm dlx skills add kirivandubai\u002Fdenodo_wipe_coading_skills --skill marketplace","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarketplace\u002FSKILL.md",true,[43,49,53,57],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"references\u002Fcategories.md","REFERENCE","参考文档",5116,"https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarketplace\u002Freferences\u002Fcategories.md",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fexternal-elements.md",11588,"https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarketplace\u002Freferences\u002Fexternal-elements.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Frenames.md",8859,"https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarketplace\u002Freferences\u002Frenames.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ftags.md",7490,"https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fmarketplace\u002Freferences\u002Ftags.md",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7C2NGAJEKKG90BG9Q1Z2M96","vql","Use when doing anything with Denodo — creating or changing a database, folder, tag, data source, wrapper, base, derived, interface or metric view, association, cache, role or security policy, remote table or summary, a Data Marketplace object, a regression test or a Scheduler job; writing or fixing VQL, or an expression in a SELECT — text, dates, casts; deciding where an object lives and what to name it; \"where do I start\", \"build a mart\", \"connect a source\", \"vibe-code on Denodo\". Start here when the request is ambiguous or names no single object.","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fvql\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7C2N5W4203SQ2TRYT6E0VSR","views","Use when building on top of views that already exist in Denodo 9.5 — a derived view (a join, an aggregate, a mart, a filtered or parameterised view, a UNION ALL of views of one entity, FLATTEN of a JSON array into rows, NEST of rows into an array), an interface view, or an association between two views. Also before changing a view others depend on — \"what uses this view\", \"can I drop this column\", \"where does this field come from\" — for whether a mart over a database runs there or pulls every row into Denodo, for \"combine these sources into one view\", \"expose this as a data product\", and for a view created without an error that fails on SELECT or turns up INVALID. Not for sources and base views — \u002Fdenodo:datasources; databases, folders, VDP tags — \u002Fdenodo:catalog; a view's cache — \u002Fdenodo:cache; a copy stored as a table — \u002Fdenodo:materialize; a metric view — \u002Fdenodo:metrics.","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fviews\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7C2MY48XXHR87G39R0F0VTK","testing","Use when a Denodo 9.5 project needs regression tests, or its tests need running or fixing — .denodotest files that the Denodo Testing Tool runs in CI (%EXECUTION, %RESULTS[data|query|csv|exception], configuration.properties, denodo-test.sh) — \"add tests for this mart\", \"a safety net before I rewrite these views\", \"make sure the dashboards see no difference\", \"what should CI check on our data products\", \"prove the mart is right\", \"CI is red on the Denodo tests\", a test that fails on row order, on a column it did not ask for or on a value padded with spaces. Not for checking a new view once, right after creating it — \u002Fdenodo:views.","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7C2MMFX40K0WTDNW05VCQEJ","semantics","Use when the views of an existing Denodo 9.5 database have to be understood by people and by AI consumers — the Denodo MCP Server, Assisted Query in the Data Marketplace, the AI SDK. Auditing a database for views and fields without descriptions, primary keys that are missing or not unique, missing associations and the VDP tag the MCP Server shows views by; writing view, field, association and tag descriptions from the data, and primary keys. Also for \"describe \u002F document these views\", \"prepare this database for AI, MCP or Assisted Query\", \"why does the agent not see this view through MCP\", a description that says the wrong thing. Not for building or changing what a view computes — \u002Fdenodo:views; not for marketplace-only metadata (logical names, property groups, marketplace tags) — \u002Fdenodo:marketplace.","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fsemantics\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7C2M9XVTRVXYXMGTEC62EFB","security","Use when deciding who may read what in Denodo 9.5 — masking or hiding columns (PII, contact details, salaries, bank accounts) from some users or roles, letting a role see only some rows (a country, a tenant) or each person only their own, taking someone's access away (ALTER USER … REVOKE), denying a view to a group, a global security policy (CREATE GLOBAL_SECURITY_POLICY) and the VDP tags it reads, giving a user a role or giving a role access to a database or views (CREATE ROLE … GRANT EXECUTE, ALTER USER … GRANT ROLE), checking what a given user really gets back, or a user who sees data a restriction should hide (\"he still gets every row\", \"the masking stopped working\"). Not for a tag as a label without a policy (\u002Fdenodo:catalog) or for descriptions and the MCP visibility tag (\u002Fdenodo:semantics).","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7C2KYWB8B6ZC026CT3Z1MZA","scheduler","Use when something in Denodo 9.5 has to happen on a schedule, or a scheduled run misbehaves — refreshing the cache of a view every night or every hour, running REFRESH of a remote table or a procedure at a set time, exporting a view to a CSV file every week or month, running a Denodo Scheduler job now, stopping, pausing, enabling or deleting it, reading what last night's run did or why it failed, \"the cache doubles after every refresh\", \"the job fires at the wrong hour\", \"the export file is missing or has no header\". Denodo Scheduler projects, jobs, cron triggers and reports, through the REST API of the Scheduler administration tool. Not for switching a cache on or loading it once (\u002Fdenodo:cache), not for creating the remote table or summary itself (\u002Fdenodo:materialize).","https:\u002F\u002Fgithub.com\u002Fkirivandubai\u002Fdenodo_wipe_coading_skills\u002Fblob\u002Fmain\u002Fskills\u002Fscheduler\u002FSKILL.md",[],[]]