How vivekyadav796/doc-mind works
DocMind appears to be a Spring backend for document ingestion and retrieval-augmented chat. The tree identifies API controllers, ingestion/parsing and metadata services, a RAG service, and a metadata repository. No README or source excerpts were provided, so internal call wiring and external AI or vector-store integrations cannot be verified; the graph shows only the API boundary and repository/store relationship implied by their names.
Main entry points: DocumentMetadataRepo.java Metadata Repository · DocumentController.java Document API · ChatController.java Chat API
Components 9
API
- Document API
backend/src/main/java/com/example/docmind/backend/controller/DocumentController.java - Chat API
backend/src/main/java/com/example/docmind/backend/controller/ChatController.java
Document Processing
- Document Ingestion
backend/src/main/java/com/example/docmind/backend/service/DocumentIngestionService.java - Document Parser
backend/src/main/java/com/example/docmind/backend/service/DocumentParserService.java - Metadata Service
backend/src/main/java/com/example/docmind/backend/service/DocumentMetadataService.java
Retrieval and Chat
- RAG Service
backend/src/main/java/com/example/docmind/backend/service/RagService.java
Metadata Persistence
- Metadata Repository
backend/src/main/java/com/example/docmind/backend/repository/DocumentMetadataRepo.java - Metadata Store
Other components
- Client
Connections 3
- Client → Document API: uploads documents
- Client → Chat API: sends chat requests
- Metadata Repository → Metadata Store: reads and writes