nextcloud / nextcloud/context_chat_backend
[feat]: fetch files metadata along with the data when the actual indexing happens so it's not stale
Open
Nobody has claimed this yet.
enhancement
priority: normal
- Dominant language
- Python
- Stars
- 27
- Forks
- 24
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 6
Description
this does not apply to the content providers since the updated metadata is already present in the db when the providers add data, it's de-duplicated based on ids on re-addition.
thanks @miaulalala
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 at context_chat_backend/chain/ingest/injest.py around lines 386-388 and trace the indexing path for non-content-provider data. Confirm how file metadata is currently obtained and ensure the metadata used during indexing is fetched freshly, while preserving the existing provider behavior; done means indexed metadata is no longer stale.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100