open-webui/oikb

Fork 0

mirror of https://github.com/open-webui/oikb.git synced 2026-11-05 01:27:25 +00:00

[GH-ISSUE #42] PaperlessNGX connector #25

New issue

Open

opened 2026-10-18 21:13:35 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-18 21:13:35 +00:00

Owner

Originally created by @Alfabeta01 on GitHub (Jun 8, 2026).
Original GitHub issue: https://github.com/open-webui/oikb/issues/42

This project is very interesting.
As many people use document management with PaperlessNGX I highly appreciate a API connection to PaperlessNGX via OIKB as the logic there seems convenient to me.
With that it would be pretty simple to inject documents based on simple timings.
I hope it can be picked up.

Originally created by @Alfabeta01 on GitHub (Jun 8, 2026). Original GitHub issue: https://github.com/open-webui/oikb/issues/42 This project is very interesting. As many people use document management with PaperlessNGX I highly appreciate a API connection to PaperlessNGX via OIKB as the logic there seems convenient to me. With that it would be pretty simple to inject documents based on simple timings. I hope it can be picked up.

bsakaguchi commented

2026-10-18 21:13:35 +00:00

Author

Owner

@Micsi commented on GitHub (Jul 30, 2026):

I am thinking on this as well and might come up with an PR. Do you have any wishes/ideas on how tags or other information from paperlessNGX could be transferred to OIKB? I am thinking on syncing filtered by tags or storage paths but am interesed in other ideas.

Would you want to import the original PDF as well or just the Text-Layer?

@Micsi commented on GitHub (Jul 30, 2026): I am thinking on this as well and might come up with an PR. Do you have any wishes/ideas on how tags or other information from paperlessNGX could be transferred to OIKB? I am thinking on syncing filtered by tags or storage paths but am interesed in other ideas. Would you want to import the original PDF as well or just the Text-Layer?

bsakaguchi commented

2026-10-18 21:13:36 +00:00

Author

Owner

@philus88 commented on GitHub (Aug 16, 2026):

Hi @Micsi, are you already actively working on the Paperless connector?

We have implemented and tested an external Paperless → Markdown → oikb bridge and are considering contributing a native PaperlessConnector to oikb. We would be happy to coordinate the source syntax, filters and output format with you to avoid duplicating work.

For transparency: our existing bridge was developed with substantial AI assistance, and the proposed upstream connector would also be AI-assisted. We would still review and take responsibility for the complete contribution, provide focused automated tests, and validate it against real Paperless-ngx and Open WebUI instances before submitting the PR.

If you have already started, we can contribute our architecture findings and test cases. Otherwise, we could prepare a clean connector implementation under oikb’s MIT license.

@philus88 commented on GitHub (Aug 16, 2026): Hi @Micsi, are you already actively working on the Paperless connector? We have implemented and tested an external Paperless → Markdown → oikb bridge and are considering contributing a native `PaperlessConnector` to oikb. We would be happy to coordinate the source syntax, filters and output format with you to avoid duplicating work. For transparency: our existing bridge was developed with substantial AI assistance, and the proposed upstream connector would also be AI-assisted. We would still review and take responsibility for the complete contribution, provide focused automated tests, and validate it against real Paperless-ngx and Open WebUI instances before submitting the PR. If you have already started, we can contribute our architecture findings and test cases. Otherwise, we could prepare a clean connector implementation under oikb’s MIT license.

bsakaguchi commented

2026-10-18 21:13:36 +00:00

Author

Owner

@Micsi commented on GitHub (Aug 17, 2026):

Hi @philus88,

I did not yet start working on the connector. Our paperless archive would be pretty big, so I would have to take that into account, caching uploaded docs and such. My work identified some areas in oikb, that should be improved for the connector.

I am very interested to see your achievements!

@Micsi commented on GitHub (Aug 17, 2026): Hi @philus88, I did not yet start working on the connector. Our paperless archive would be pretty big, so I would have to take that into account, caching uploaded docs and such. My work identified some areas in oikb, that should be improved for the connector. I am very interested to see your achievements!

bsakaguchi commented

2026-10-18 21:13:36 +00:00

Author

Owner

@philus88 commented on GitHub (Sep 5, 2026):

Small update from my side (@Micsi ):

After looking at the native AI/RAG capabilities now available in Paperless-ngx, I won't continue working on the oikb Paperless connector for now.

For our use case, we will keep the RAG functionality in Paperless itself and access Paperless through its API, potentially via MCP.

So please don't wait for a PR from my side. Thanks again for the discussion!

Paperless AI documentation:
https://docs.paperless-ngx.com/advanced_usage/#ai-features

@philus88 commented on GitHub (Sep 5, 2026): Small update from my side (@Micsi ): After looking at the native AI/RAG capabilities now available in Paperless-ngx, I won't continue working on the oikb Paperless connector for now. For our use case, we will keep the RAG functionality in Paperless itself and access Paperless through its API, potentially via MCP. So please don't wait for a PR from my side. Thanks again for the discussion! Paperless AI documentation: https://docs.paperless-ngx.com/advanced_usage/#ai-features

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

open-webui/oikb#25

No description provided.

Rows
Columns