User Interface
137 entities found
Project Dashboard UI
The Project Dashboard UI displays the project goal to the user. Dashboard file.ai_summary display renders data stored in the FileUpload record ai_summary column for users to see file summaries. The Frontend provides user interfaces including the Dashboard for displaying file info, AI summaries, and progress status.
project goal
DataLens Agent (Opus) developed the project goal field design proposal. The project goal concept is represented by the scope field in the data model although renamed in UI. The project goal is used to inform the file summary prompt replacing the previous hardcoded budget analysis description. The Project Dashboard UI displays the project goal to the user.
project overview
projects > :id
The page projects > :id > agent is part of the projects > :id page. The page projects > :id > analyze is part of the projects > :id page. The page projects > :id > workflow is part of the projects > :id page. The page projects > :id is part of the projects page. project details page is implemented as a SvelteKit page. projects > :id page is built using the SvelteKit framework. projects > :id page is part of the DataLens system. The projects > :id page is part of the DataLens project.
projects > :id > agent
projects > :id > agent page is built using the SvelteKit framework. projects > :id > agent page is part of the DataLens system. The projects > :id > agent page is part of the DataLens project.
projects > :id > analyze
projects > :id > analyze page is built using the SvelteKit framework. projects > :id > analyze page is part of the DataLens system. The projects > :id > analyze page is implemented as a SvelteKit page. The projects > :id > analyze page is part of the DataLens project.
projects > :id > workflow
The page projects > :id > workflow is part of the projects > :id page. project workflow page is implemented as a SvelteKit page. projects > :id > workflow page is built using the SvelteKit framework. projects > :id > workflow page is part of the DataLens system. The projects > :id > workflow page is part of the DataLens project.
Projects List Page
The Frontend UI Translation use case includes a language selector on the Projects page. The page projects > :id is part of the projects page. The page projects > new is part of the projects page. The Frontend contains a projects list page
q2-sql-capture.png
Screenshot capturing SQL queries or data during quarter 2 analysis.
RAGAgent
The plan includes RAGAgent to query unstructured text and synthesize answers with vLLM. RAG Agent uses Qdrant for semantic vector search of documents RAG Agent uses Ollama embeddings via nomic-embed-text for document retrieval RAG Agent generates answers using the qwen3-coder-next LLM via Ollama RAGAgent corresponds to the rag agent implementation RAGAgent corresponds to the rag agent implementation RAG Agent uses Qdrant for semantic vector search of documents RAG Agent uses Ollama embeddings via nomic-embed-text for document retrieval RAG Agent generates answers using the qwen3-coder-next LLM via Ollama RAGAgent corresponds to the rag agent implementation RAGAgent corresponds to the rag agent implementation RAG Agent uses Qdrant for semantic vector search of documents RAG Agent uses Ollama embeddings via nomic-embed-text for document retrieval RAG Agent generates answers using the qwen3-coder-next LLM via Ollama RAGAgent corresponds to the rag agent implementation RAGAgent corresponds to the rag agent implementation The RAGAgent is part of Document RAG to perform retrieval and answer synthesis. RAG Agent integrates with Qdrant for vector storage and semantic search. RAG Agent uses Ollama to generate embeddings and answers based on semantic search results. RAG Agent employs the nomic-embed-text embedding model for creating document embeddings. RAG Agent realizes the Natural Language Querying capability by semantic search and answer generation over documents. Lightweight Implementation uses RAG Agent for document question answering without heavy dependencies. RAGAgent optionally searches unstructured text in the data analysis process. RAGAgent uses LlamaIndex to chunk PDFs and generate embeddings. RAGAgent stores embeddings in the Qdrant vector database for retrieval.
regenerate_summaries.py
Relationship Matrix
UI listing tables and shared columns, with visual indicators of confirmed and suggested joins for user verification.
requeue_missing_summaries.py
results-findings-panel.png
Visual of the findings panel UI, showing detected insights.
results-full-page.png
Full-page screenshot of analysis results display.
results-q1-simple-budget.png
Visualization of Q1 budget analysis results.
results-q2-comparison.png
Comparison graph for Q2 data analysis.
results-q3-metrics.png
Metrics visualization for Q3 results.
RESULTS_VISUALIZATION_TEST_REPORT.md
Test report for visualization components, verifying functionality and performance.
Row-Level Security
Vanna 2.0 enforces row-level security by filtering queries based on user permissions. Vanna 2.0 enforces row-level security by filtering queries per user permissions. Vanna 2.0 enforces row-level security filtering queries per user permissions
Schema Relationship Explorer
Schema Relationship Explorer is an instance or feature of the User Schema Relationship Mapper used for data visualization. The Schema consolidation mechanism is planned to be presented via the Schema relationship explorer UI for better transparency and customization.
Semantic Search Panel
Semantic search sidebar
Semantic search sidebar uses the Qdrant collection for retrieving relevant document chunks based on vector embeddings. DataLens includes a Semantic Search Sidebar displaying matching documents alongside results
shadcn-svelte
The Frontend uses shadcn-svelte UI components. The Frontend uses shadcn-svelte as a third-party component. The npm dev dependency shadcn-svelte depends on svelte in the frontend project dependencies.
shadcn-ui
The DataLens platform backend incorporates shadcn-ui as part of its user interface skills. The DataLens platform backend includes the shadcn-ui skill. The Frontend uses shadcn-svelte components The DataLens platform backend integrates the shadcn-ui skill.
SOUL.md
SOUL.md contains the core configuration and design decisions for the DataLens platform; included in the project repository. Agent configuration includes the SOUL.md file. Phase 2 research outputs include SOUL.md in the research documents.
Split-Pane Catalog
Step Builder for Custom Consolidations
Interactive UI allowing users to define, adjust, and test schema consolidation strategies for targeted queries.
Step Builder UI Component
Storage directory
The DataLens Platform stores project data and files in the storage directory at /home/ops/datalens-platform/storage/.