ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Knowledge Base: Organize data by project
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
All knowledge base endpoints currently use a single bucket, making it difficult to perform a clean data flush for NGOs, resulting in offboarding issues.
Describe the solution you'd like
- Organize data into per-project-ID folders within the same bucket (following the audio setup).
- Implement a migration script for existing documents and a legacy fallback option in the code (check top level, then project level).
- Conduct testing on staging first.
- Defer the bring-your-own-bucket/credentials aspect until TAP.
Priority
- P2, September in-person ops/infra sprint.
Original issue
Context
For knowledge base enpoints, everything currently lands in a single bucket. If an NGO uses the product for two years and then requests a full data flush, that's very hard to honour cleanly — an offboarding liability.
Fix
- Same bucket, per-project-ID folders (audio already does this; documents may not).
- Provide a migration script for existing documents and a legacy fallback in code (check top level, then project level).
- Test on staging first.
- The bring-your-own-bucket/credentials half of this is deferred until TAP.
Priority
- P2, September in-person ops/infra sprint.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the knowledge base endpoints and comparing their storage layout with the existing audio setup. Define the migration script and legacy lookup behavior, then test the migration and fallback on staging; the work is done when documents use per-project-ID folders while existing top-level documents remain accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100