Alert system
Four alert badges appear at the top of the dashboard. Each badge turns active (with a count) when the condition is met:| Alert | Condition | Why it matters |
|---|---|---|
| Unassigned tasks | Tasks with no assignedTo value | Work with no owner is at risk of being dropped |
| Stalled tasks | Tasks that have not changed status in a configured period | Indicates a blocked dependency or forgotten work item |
| Overdue tasks | Tasks whose deadline is in the past and are not completed | Direct risk to delivery timelines |
| High-priority tasks | Open tasks with priority = high | Surface the most critical work at a glance |
Dashboard widgets
Overall progress
A large percentage figure showing how many of the project’s total tasks are in Completado status. Updates immediately when a task is moved to completed.
Task summary
Two counters: total tasks in the project and total completed tasks. Gives you an absolute count to complement the percentage.
Traceability count
The total number of traceability records (datasets + experiments + decisions) logged across all phases. A low count relative to project size may indicate incomplete documentation.
At-risk count
The number of tasks currently flagged by any alert condition (overdue, stalled, unassigned, or high-priority). Helps you prioritize your next action.
CRISP-DM pipeline semaphore
One progress bar per phase, showing completion percentage. Color coding: green (all tasks done), amber (in progress), red (no progress or blocked). Read left-to-right to spot where the project is stuck.
Status distribution
A pie chart (recharts) showing the proportion of all tasks in each of the five statuses. Useful for spotting bottlenecks — for example, a large En Revisión slice means reviews are queuing up.
Collaborator workload
A bar chart with one bar per team member, split into completed (solid) and in progress (lighter) segments. Identifies overloaded individuals and team members with capacity.
Traceability by phase
For each CRISP-DM phase, three stacked counts: datasets, experiments, and decisions. Phases with zero traceability records are highlighted so you know where documentation is missing.
Upcoming deadlines
A list of tasks whose deadline falls within the next 7 days. Sorted by date ascending. Each item shows the task name, phase, assignee, and exact deadline.
Top experiments
The three experiments with the highest numeric result value, pulled from the traceability log. Useful for a quick summary of modeling performance at a glance.
Interpreting the pipeline semaphore
The pipeline semaphore is the fastest health check for a CRISP-DM project:- All phases green — the project is on track or complete.
- Early phases amber, later phases red — the project is progressing normally; downstream phases haven’t started yet.
- Middle phases red while later phases have activity — work is happening out of order, which may indicate scope or planning issues.
- Any phase at 0% with a deadline approaching — action required immediately.
Generating a PDF report
The Reporte button is located in the project navigation bar, alongside the Dashboard toggle and team management buttons.Click Reporte
Click the Reporte button. Babel begins compiling the report data from the server, which includes tasks, datasets, experiments, decisions, and stalled tasks.
Wait for generation
The PDF is generated client-side using
jspdf and html2canvas. Generation typically takes a few seconds depending on the size of the project. Do not navigate away during this process.What the report contains
The exported PDF includes:- Project summary — name, client, description, and manager
- Task list — all tasks with status, phase, assignee, priority, and deadline
- Stalled tasks — tasks identified as stalled, highlighted for attention
- Datasets — all dataset records, grouped by phase
- Experiments — all experiment records with parameters and results, grouped by phase
- Decisions — all decision records with justifications, grouped by phase
The report reflects the state of the project at the moment you click Reporte. It is a static snapshot — changes made after export are not reflected in the downloaded file.