Wrong archive path and naming for documents

[Maginos2210]

Hi guys,

I observed, that newly added documents are not stored in the right archive path and that they are not named correctly.

The documents are now located in the "archive" folder directly and not in the "archive/correspondent" folder.
The names of the documents are also wrong. They are named as "year-month-day-correspondent-title", but should be named "year-month-day_correspondent_title" (underscores after date and correspondent).

In paperless "Storage path" --> "Default", I set up following rule:

{correspondent}/{created_year}/{created_year}-{created_month}-{created_day}_{correspondent}_{title}

I run the docker container under unraid with the following command:

`docker run
-d
--name='paperless-ngx'
--net='proxynet'
--cpuset-cpus='1,2,3,4,5,7,8,9,10,11'
-e TZ="Europe/Berlin"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="Tilda"
-e HOST_CONTAINERNAME="paperless-ngx"
-e 'PAPERLESS_REDIS'='redis://192.168.5.3:6380'
-e 'PAPERLESS_OCR_LANGUAGE'='deu'
-e 'PAPERLESS_OCR_LANGUAGES'='deu'
-e 'PAPERLESS_FILENAME_FORMAT'='{created}-{correspondent}-{title}'
-e 'PAPERLESS_TIME_ZONE'='Europe/Berlin'
-e 'PAPERLESS_DBENGINE'='postgresql'
-e 'PAPERLESS_DBHOST'='postgresql14'
-e 'PAPERLESS_DBPORT'='5432'
-e 'PAPERLESS_DBNAME'='paperless'
-e 'PAPERLESS_DBUSER'='paperless'
-e 'PAPERLESS_DBPASS'='xxxxxx'
-e 'PAPERLESS_ADMIN_USER'='Florian'
-e 'PAPERLESS_ADMIN_PASSWORD'='xxxxx'
-e 'UMASK'='000'
-e 'PAPERLESS_IGNORE_DATES'=''
-e 'PAPERLESS_CONSUMER_POLLING'='0'
-e 'PAPERLESS_SECRET_KEY'='xxxxx'
-e 'USERMAP_UID'='99'
-e 'USERMAP_GID'='100'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:8000]'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/paperless.png'
-p '8000:8000/tcp'
-v '/mnt/nvmecache/appdata/paperless-ngx/data':'/usr/src/paperless/data':'rw'
-v '/mnt/user/home_florian/Dokumente/3_Media/':'/usr/src/paperless/media':'rw'
-v '/mnt/user/home_florian/Dokumente/1_Input/':'/usr/src/paperless/consume':'rw'
-v '/mnt/user/home_florian/Dokumente/2_Output/':'/usr/src/paperless/export':'rw' 'ghcr.io/paperless-ngx/paperless-ngx:latest'

`

Paperless is set up to pick up documents that were firstly processed by ocrmypdf-auto docker.

So far it worked without any issue. The last successful documents I added was at the 11th April, so the latest update for the docker container should not be the problem.

Can anyone help me with this? I would like to get paperless to rename the documents in the "archive" folder and store them with the correct name in the "archive/correspondent/year/" folder.

Thank you in advance.

Maginos

[shamoon]

Did you assign that storage path to the documents? Also, https://docs.paperless-ngx.com/administration/#renamer

[Maginos2210]

Yes, it's the only storage path available, so all my documents use the same storage path.

Thank you for the tip with the document_renamer. I executed this command in the console of the paperless docker container and it went through without any error, but the documents stay in the "archive" folder with the wrong name.

[Maginos2210]

Ok, I found the issue.

The storage path for each document was greyed, but not selected. After selecting the "Default" storage location, the documents were renamed and moved to the desired location.

I also changed the "Assignment algorithm" in the configuration of the storage path to "Auto" which was not selected before (the setting before was: "Any word: contains one of the following words:" and then "Name-of-Maginos". I don't remember if I set that up like this, but other documents, where my name was not in it, were assigned to the correct storage path, so yeah...) since the setup of paperless I did not change this setting. So with this, there should be no issues like this in the future.

Thank you for your help @shamoon.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. Please see our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.