app.analyses
Business Definition Reference
For details on triggering analyses, exploration workflows, and user personas, refer to the Analyses Business Definition.
The app.analyses table tracks goals, status settings, parameters, and saved Jupyter/interactive notebook structures for AI-driven and manual analytical reports.
Schema Field Definition
| Field Name | Type | Description |
|---|---|---|
id | UUID (Primary Key) | Unique identifier generated via uuid.uuid4. |
title | VARCHAR(255) (Required) | The title or name of the analysis report. |
description | TEXT (Optional) | Broad description of the analysis goal. |
status | VARCHAR(50) (Default: pending) | Execution states: pending, running, completed, failed. |
result | TEXT (Optional) | Final text summaries or markdown responses generated by the agent. |
analysis_metadata | JSON (Optional) | Holds parameters, configs, or file links related to the run. |
notebook | JSON (Optional) | Stores the cell layouts and outputs (conforming to the .ipynb spec). |
created_at | TIMESTAMP | Analysis creation timestamp. |
updated_at | TIMESTAMP | Analysis update timestamp. |
owner | UUID (Foreign Key) | References the app.user_groups.id owning the analysis. |
created_by | UUID (Foreign Key) | References the app.users.id who generated the analysis. |
updated_by | UUID (Foreign Key) | References the app.users.id who updated the analysis. |
owner_id | UUID (Optional) | Polymorphic owner ID link. |
owner_type | VARCHAR(50) (Optional) | Polymorphic owner type (user or group). |
Cell-Based Notebook Architecture
The notebook column stores JSON-serialized notebooks. This allows Ravioli's interactive cells to preserve execution order, code contents, visual structures, and outputs, facilitating subsequent re-execution or visualization updates.