Project

Represents a data analysis project involving internal stakeholders with high influence. Data models such as StandardSalaryRecord, StandardHealthRecord, StandardFinancialTransaction, StandardGeographicData, and StandardBudgetRecord are used within projects to structure relevant data. The project entity is linked to physical tables like FileUpload, Query, Insight, and ProcessingJob, which manage project files, executed queries, insights, and background tasks respectively. Each Project's data is stored in a dedicated DuckDB file (e.g., project_4.duckdb) managed by DuckDBService. Each Project's semantic data is stored in a dedicated Qdrant collection used by QdrantService. User interacts with Project data via the API, querying and managing project-specific information. Project physical table contains multiple FileUpload physical tables representing uploaded files associated with the project. PostgreSQL database stores project metadata like org_id and created_by user. Query data entity references the Project entity by project_id.