Feature/paperless-ngx connector

[cbrown350]

Description

This adds code for a Paperless-ngx connector: https://docs.paperless-ngx.com

How Has This Been Tested?

This includes the standard mock testing similar to other connectors. Additionally, it has been manually tested extensively. Anyone can easily test it using a clean Docker Paperless-ngx image by running the included script at backend\tests\daily\connectors\paperless_ngx\run_manual_test_paperless_server.sh. This script sets up a server and then provides credentials you can use to create a connector in a local Onyx instance.

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

#159
#776
#3107

onyx-dot-app/documentation#196

[vercel]

@cbrown350 is attempting to deploy a commit to the Danswer Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

PR Summary

This PR adds a new Paperless-ngx connector implementation with comprehensive testing and documentation. Here are the key points:

• Implements LoadConnector, PollConnector, and SlimConnector interfaces with proper date filtering, tag/user filtering, and error handling in /backend/onyx/connectors/paperless_ngx/connector.py

• Includes a robust testing setup with both unit tests and a convenient Docker-based manual testing script (run_manual_test_paperless_server.sh) for local validation

• Adds proper UI configuration in web/src/lib/connectors/connectors.tsx with fields for tag filtering, username filtering, and no-owner document inclusion

• Bug in date field validation - the code raises an exception when ui_date_field matches a valid field instead of setting it, and lacks proper handling of master vs local date fields

• Missing error handling for API response validation in _parse_document() - should add checks for required fields and data type validation

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{12 file(s) reviewed, 10 comment(s)
Edit PR Review Bot Settings | Greptile}

[cbrown350]

Hello @yuhongsun96, do you know if there's still interest in this connector?

[github-actions]

This PR is stale because it has been open 75 days with no activity. Remove stale label or comment or this will be closed in 15 days.

[github-actions]

This PR was closed because it has been stalled for 90 days with no activity.