← BOLDR MAXCONTENT HISTORY

Update to BOLDR MAX

Snapshot Oct 31, 2026 · 01:24 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save BOLDR MAX and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Turn a pasted or uploaded table (CSV, spreadsheet excerpt, spec sheet) into a BOLDR form with all of its rows and measurements in one call.",
  "included_files": [],
  "name": "import-table",
  "skill_md_contents": "---\nname: import-table\ndescription: Turn a pasted or uploaded table (CSV, spreadsheet excerpt, spec sheet) into a BOLDR form with all of its rows and measurements in one call.\n---\n\n# Import a table into BOLDR\n\nUse this when the user provides tabular data — a CSV, a pasted table, a cut\nlist, a spec sheet — and wants it in BOLDR.\n\n1. Confirm the destination: which project and job (create them with\n   `create_project` / `create_job` if the user asks for new ones).\n2. Map the table's headers to column types: lengths → `measurement`,\n   angles → `angle`, categories with a fixed set of values → `singleSelect`\n   (collect the options), yes/no → `boolean`, free text → `text`, counts →\n   `number`. Show the user the mapping before writing if anything is\n   ambiguous.\n3. Call `import_table` once: `columns` from the headers, `rows` with cells\n   keyed by column NAME. Measurement cells take the values as written —\n   numbers are read in `unit`, strings like `3' 4-1/2\"` parse as-is, and\n   `{value, label}` attaches a label to the created measurement.\n4. More than 50 rows? `import_table` the first 50, then batch the rest with\n   `create_groups` using the column ids the first call returned (cells are\n   keyed by column ID there, not name).\n5. Hand back the section name and row count, and offer a follow-up: lock a\n   measurement column's display unit with `set_column_unit_lock`, or set\n   tolerances so out-of-spec rows surface in reports.\n\nNever create rows one call at a time with `create_group` +\n`create_measurement` when the data is already tabular — the bulk tools are\natomic and far cheaper on the organization's request quota.\n"
}

SHA-256 of public snapshot: da37dc81af1d5a24a6224d5b48280f3e31a66265b8d1338c04efdc80301b3b62