Merge pull request #785 from isaacsando/master

update advanced_usage.rst to remove wording regarding filename parsing
This commit is contained in:
Jonas Winkler 2021-03-16 17:28:29 +01:00 committed by GitHub
commit b6428aa85f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -10,14 +10,13 @@ easier.
Matching tags, correspondents and document types Matching tags, correspondents and document types
################################################ ################################################
After the consumer has tried to figure out what it could from the file name, Paperless will compare the matching algorithms defined by every tag and
it starts looking at the content of the document itself. It will compare the correspondent already set in your database to see if they apply to the text in
matching algorithms defined by every tag and correspondent already set in your a document. In other words, if you defined a tag called ``Home Utility``
database to see if they apply to the text in that document. In other words, that had a ``match`` property of ``bc hydro`` and a ``matching_algorithm`` of
if you defined a tag called ``Home Utility`` that had a ``match`` property of ``literal``, Paperless will automatically tag your newly-consumed document with
``bc hydro`` and a ``matching_algorithm`` of ``literal``, Paperless will your ``Home Utility`` tag so long as the text ``bc hydro`` appears in the body
automatically tag your newly-consumed document with your ``Home Utility`` tag of the document somewhere.
so long as the text ``bc hydro`` appears in the body of the document somewhere.
The matching logic is quite powerful, and supports searching the text of your The matching logic is quite powerful, and supports searching the text of your
document with different algorithms, and as such, some experimentation may be document with different algorithms, and as such, some experimentation may be