mammoth-cli 2.2.16__tar.gz → 2.2.17__tar.gz

{mammoth_cli-2.2.16 → mammoth_cli-2.2.17}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mammoth-cli
-Version: 2.2.16
+Version: 2.2.17
 Summary: Command-line interface for the Mammoth Analytics platform
 Project-URL: homepage, https://mammoth.io
 Project-URL: repository, https://github.com/EdgeMetric/mammothsdk

{mammoth_cli-2.2.16 → mammoth_cli-2.2.17}/mammoth_cli/__init__.py

@@ -6,7 +6,7 @@ not implement a second HTTP client and does not call private SDK members.
 
 from __future__ import annotations
 
-__version__ = "2.2.16"
+__version__ = "2.2.17"
 
 # The versioned machine output envelope contract.
 SCHEMA_VERSION = 1

{mammoth_cli-2.2.16 → mammoth_cli-2.2.17}/mammoth_cli/bundled_skill/mammoth-cli/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mammoth-cli
-version: 2.0.75
+version: 2.2.16
 description: "Use Mammoth Analytics from a terminal: install or authenticate the CLI, discover its live command contract, and safely manage projects, data, views, pipelines (join, merge, pivot, filter, clean), dashboards, exports, and handoffs."
 ---
 

{mammoth_cli-2.2.16 → mammoth_cli-2.2.17}/mammoth_cli/bundled_skill/mammoth-cli/references/operations.md

@@ -36,7 +36,10 @@ credentials because they call the live API. To find a dataset by name, run
 `dataset list --input '{"name": "NAME"}'` inside one project: a
 case-insensitive substring match over every page, returned as short rows
 (id, name, rows, cols) with `matched`. Do not page `dataset list` by hand;
-`limit` is at most 100.
+`limit` is at most 100. To find the dataset that holds given columns, pass
+`dataset find --input '{"columns": ["Order ID", "Region"]}'` (the name is then
+optional). A `browse` search hit carries `dataset_id` or `view_id`: use those,
+never the tree `id`.
 
 ```bash
 mammoth capability find "transform"
@@ -116,11 +119,45 @@ mammoth workflow create "Revenue report"
 mammoth workflow get WORKFLOW_ID
 ```
 
+`WORKFLOW_ID` is the workflow's record id (URL id `w12` is record 12). An
+unnamed workflow (long base64 URL id) has no record: list the workflows and
+root datasets with `workflow graph`, then name it with `workflow create
+NAME --input '{"seed_datasource_id": ROOT_DATASET_ID}'`, which returns its
+record id. `workflow cleanup` deletes the project's orphaned skeleton
+("ghost") workflows (destructive; needs `--yes`).
+
+To only *suggest* a workflow's shape for the user to review, use `workflow
+canvas WORKFLOW_ID --input '{"canvas_state": {"proposed_changes": [...]}}'`.
+Nothing is built until the user presses Save on the Workflows canvas; tell
+them the changes are waiting there. Changes are `add_view`, `rename_view`,
+`trash_view`, `rename_dataset`, `trash_dataset`, `send_to_new_dataset`,
+`send_to_dataset`, `join` and `export` (fields per op: `schema get
+workflow.canvas`). A later change in the same call can point at an earlier
+one: give the earlier change a `ref`, then use `view_ref`, `dataset_ref` or
+`target_dataset_ref` instead of an id. It cannot add filters, calculations or
+other tasks; if the request needs those, build it with `view` commands.
+
 Draft mode is server-side batching for view pipeline edits. Enter, inspect
 status, submit, and verify pipeline state; discard only with the required
 confirmation. A draft submit result is not proof that every intended task was
 applied.
 
+## Reading data and history without changing the pipeline
+
+- A trend, distribution or top-values answer: `view data explore VIEW_ID
+  COLUMN` (read-only; `level` sets the date bucket). `{"cumulative": true}`
+  adds a running total per bucket, whatever `sort` or `limit` shows. Figures
+  from `explore` and `view data aggregate` are rounded for display (2
+  decimals; 4 below 1); `view data compare` keeps full precision.
+- "Who changed X": `activity list` (a change list of time, user, action and a
+  `path` naming the dataset and view). Filter with `resource_id` in the log's
+  typed form, `dataview_<id>` or `datasource_<id>` (a bare number matches
+  nothing and is refused), plus `start_time`, `end_time`, `user_ids`; page
+  with `limit` and `offset`.
+- `view export dataset` that returns `status: pending` was accepted and is
+  still being written. Do not export again (that makes a second dataset); run
+  its `next` command (`dataset find NAME`) to get the new dataset id.
+
 ## Response shapes
 
 Response shapes are not uniform; never reuse one `jq` path across commands.

{mammoth_cli-2.2.16 → mammoth_cli-2.2.17}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mammoth-cli"
-version = "2.2.16"
+version = "2.2.17"
 description = "Command-line interface for the Mammoth Analytics platform"
 authors = [{name = "Mammoth Analytics", email = "support@mammoth.io"}]
 readme = "README.md"