FILENAME_SCRIPT as alternative to PAPERLESS_FILENAME_FORMAT [Feature Request] #7009
Replies: 2 comments
-
|
This discussion has been automatically closed due to lack of community support. Please see our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
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. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description
When building a file/pathname for archive documents ther is a configuration parameter PAPERLESS_FILENAME_FORMAT in general also on document type level. I want to be able to modify the resulting path and filename using a custom script taht gets all variables already defined for PAPERLESS_FILENAME_FORMAT but to be able to parse those and build an custom path/filename.
My use case is, that my file structure depends sometimes on tags that are added to the document but I do not want to have all Tags {tag_list} represented in the resulting name.
So if I can specify a custom script that has access to all filename placehoders I can parse them and return my custom name...
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions