Open compgeniuses opened 6 months ago
Paperless-ng is also a lot different to storing something in folders. With folders, you have one option and that's it.
With paperless-ng, you assign the document a type (letter, contract, invoice, ...), a correspondant (who is it from) and tag it. Espacially with tags you now have numerous different options. Meaning, once you have more documents it is easier to find. Have you ever struggled to decide which folder a document belongs to or didn't have a proper one and just stuck it where it made the most sense?
Appart from this, paperless-ng will learn your setting etc, so actually storing and sorting documents will become a lot easier and more automatic.
You said you don't have many documents. You can still try it out. Over the year you will have a lot of documents and starting early is easier than later.
the whole point of paperless-ng is like having an organized filing cabinet with a secretary where Nextcloud is more like putting all of your documents in a box or nested boxes with a label and calling it good.
a good filing system, can really help in a tight spot with time constraints.
An interesting overview, in relation to NS8 https://github.com/jdoss/ppngx
Since Paperless Has Advanced Tagging, naming and OCR functionalities, we make use of its Super powers, to integrate with NExtcloud, since Most USers would mostly likely be using Nextcloud alot more.
Integrate Nextcloud with PAperless Ngx.
Possibility, include input and output folder as external FTP storage in NExtcloud Another possibility would be to include a local path. This also requires the Nextcloud addon for external storage. You can then mount a local path as Nextcloud folder
USecase1: In the Nextcloud container I mount the consume path from Paperless and specify it in Nextcloud as input folder The same goes for the output folder of course
in the default configuration, the filenames in the output folder are not necessarily meaningful. But this could also be solved: https://docs.paperless-ngx.com/advanced_usage/#file_name_handling Probably By Defining: PAPERLESS_FILENAME_FORMAT={created_year}/{correspondent}/{title}
Video Discussion here: https://www.youtube.com/watch?v=DQIbbwHPAqo Notes for Video Here: https://apfelcast.com/paperless-ngx-nextcloud-scanner-automatischer-workflow/
So BAsically, A folde rin NExtcloud for Input/ that sends fils to paperless for OCR and a Folder in NExtcloud for Output, that gets OCR documents from Paperless.
We can Implemnt File automated Taggin in NExtcloud, as well as File action on tags.
So that, if we tag a File OCR, the FIle is Copied into the Input folder of PAperless, Gets OCR into PAperless, and once the file comes back inot NExtcloud in th eOutput Folder, the Automation Copies the file back into an Editable Nextcloud Folder.
this is because we can not edit the files in any of the paperless folder.
This Discussion is a Point of Reference for the Same: https://community.nethserver.org/t/posibility-of-an-internal-module-to-module-connection-link/22664/1
additional implementations. https://eightify.app/summary/technology-and-software/efficient-paperless-ngx-integration-in-nextcloud-andres-hardware