this post was submitted on 13 Nov 2023
2 points (100.0% liked)

Self-Hosted Main

504 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
2
Advice on Paperless storage path (alien.top)
submitted 1 year ago by puckpuckgo@alien.top to c/main@selfhosted.forum
3 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] puckpuckgo@alien.top 1 points 1 year ago

Thanks, 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.