Advice on Paperless storage path
Advice on Paperless storage path
I'm starting to go all in on PaperlessNGX after discovering it recently in this community. At first, I started testing and exploring, but I realize that this will satisfy my needs for record-keeping. The one thing I have to figure out is the storage path. Today, Paperless will store everything in a single folder. That's fine, as long as Paperless exists. However, should I ever want to move away from it or it stops getting developed, I'm stuck with a massive directory of PDFs.
I was thinking instead of organizing like so:
media/YYYY/Doc_Type/Correspondent/Title
I would want to do this for existing documents in the system, as well as any new ones I create.
What is the best way of accomplishing this?
Also, is this the best way of sorting these documents? Any other ideas I should consider?
I set up
/--.pdfto start with. I find that for my yearly document amount, there is no value in adding more than one level of hierarchy. File browser search tools are easier than more hierarchy for the last bit.I think I will switch my default path to be
<correspondent>/filename.pdf(with filename as above). I think organizing by correspondent will give a more meaningful sorting for "manual" access than sorting by year.For files which are strongly tied to a date, as documents in Paperless pretty much always are, I like to have a
YYYY-MM-DD(ISO-8601) format date as the first element. This gives a nice chronological sorting.2I use {correspondent}/{created_year}/{created_year}.{created_month}.{created_day} - {title} as my default storage path to achieve exactly that since I mount a CIFS volume I use on my Windows clients as well into paperless-ngx, this makes it easy to also access the PDF’s via any client and not just the paperless-ngx web UI.
1Thanks, everyone.
I ended up going with {correspondent}/{created_year}/{created_year}.{created_month}.{created_day} - {title}
For those who Google, if you have already loaded in documents and would like to make the corresponding changes to follow the above structure, you'll have to run this:
sudo docker exec -it Paperless-NGX document_renamer
For the record, this worked with Container Manager within a Synology NAS.
1