arc53/DocsGPT

Feature: Add graph retriever

Open

#1,015 opened on Jun 27, 2024

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Python (1,359 forks)batch import
applicationbackendhelp wantedpython

Repository metrics

Stars
 (13,691 stars)
PR merge metrics
 (Avg merge 6d 11h) (39 merged PRs in 30d)

Description

I think we can make upload / training process more advanced, maybe let users choose some "advanced" options on upload in the UI.

This way we can for example prepare data for graph + vector database. And when user creates a query it will automatically figure out where which retriever type needs to be used for that source. So I guess its a two part issue:

  • Edit structure of source docs in general (clean up a bit, and add retriever type field)

  • Add new graph retriever, add graph ingest, add UI to choose ingestion method maybe

Contributor guide

Research direction
Investigate the existing source document structure and ingestion pipeline. Design the graph retriever based on a graph database (e.g., Neo4j). Add UI components for choosing ingestion method.
Tech stack
python
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65