Open totti4ever opened 4 years ago
Okay, I figured out a bit..
{tags[Bills]}
{tags[0]}
even if tag A has the id 0 system-wide.
I was wondering what this is the use case for, specially when one cannot change the order and has no influence (?!) on the automatically assigned tagsWhat I would derive as change propositions from this is
none
is used. This would help if one doesn't know how many tags documents have assigned to not have none
in the name quite often. Maybe one could use {correspondent|unknown}
?.\
as default, to not add any subdirectory if tag resolves to none
I played a bit around and came to a solution which works for me so far. I am using a custom dockerfile:
FROM pitkley/paperless
RUN \
sed -i -e "s/slugify(None)/'\.'/" /usr/src/paperless/src/documents/models.py && \
sed -i -e "s/slugify(self\.created)/slugify(self\.created)\[:10\]/" /usr/src/paperless/src/documents/models.py
This solves 4.
and 2.
& 3.
, the latter one for tags only though.
Hey guys and maybe @BastianPoe,
I love the new feature with templating the naming convention of the files, thanks @BastianPoe !!
Though, I was wondering how exactly to use the
{tags[KEY/INDEX]}
feature. I tried to use{tags[2]}
and also{tags[Bills]}
, because I do have a tag called Bills-Water for example and hoped this somehow would work. But in both cases the result isnone
:-/