-
Notifications
You must be signed in to change notification settings - Fork 352
Suggest tags when editing a document #264
Comments
Suggesting tags that have not been added by the user implies using an external source or some kind of pre-existing lexicon (to be declined for each document language), I'm not sure that the components used here contain such things (@jonaswinkler will be able to tell us). This subject inspires me another suggestion: sometimes we forget to tag documents with a tag that might have been appropriate. |
I'm no talking about unknown tags; I'm talking about tags assigned to other documents (but not the one currently being edited). In fact, your second paragraph comes close to what I mean, but from the tag-perspective. |
First of all, "Auto" tags work roughly like this:
Providing tag suggestions is certainly possible, however:
This is only possible for tags / correspondents / types for which a matching algorithm has been set. This is also a rather expensive operation, since I have to run the matching algorithms on all documents to discover document suggestions. I like the idea, but I'll have to think about how to properly integrate that. |
This is exactly the issue I'm trying to solve: I imported all my documents into paperless, and am now trying to make sense of them by tagging some. It would help a lot if I could tag a number of documents, then have the system suggest other documents that might be similar. Indeed, those documents were already consumed, so they won't be auto-tagged. Do I understand that any document not tagged with a certain auto-tag, is actually anti-tagged? Maybe a middle ground might be a solution: yes, no, undecided. |
As far as the "Auto" matching algorithm is concerned: Anything in your inbox (marked with inbox tags) is regarded as undecided. Apart from that, you understand correctly that anything not tagged with a particular "Auto" matching tag is "anti-tagged". I think that should be enough and works in most use cases without requiring the user to know all the details about how the system works internally. For that reason, I don't want to add a third state to tags.
Hm. You could try using the retagger. Define some tags with manual matching algorithms and see what the I'll think about some way for tag suggestions, but this will def. take a while. |
Thank you. I will see from my side what is possible. An external classification system through the api (if that exists) might be a nice workaround. |
In order not to consume resources unnecessarily, I wouldn't be bothered if the action to suggest missing tags (or missing documents) was done on demand, with a progress bar to keep me waiting. |
In terms of required cpu time, this is actually a very simple operation. |
@jovandeginste How does this look? Clicking would add the tag / type / correspondent to the form and hide the suggestions. |
This is awesome! |
That would be great, if it actually works ? 😄 Can I test it? (AKA do you have a docker image ready?) |
This will simply run the matching algorithms again on the current document and suggest any missing tag or alternative correspondent / type. @jovandeginste The 'dev' version on the Hub has this feature. (I'm really happy about the CI/CD pipeline) |
I rebuilt my container from the latest dev image, and see suggestions on occasion. Also on correspondent. Nice! I'll try a bit more, but I'm happy so far! |
This is great, bravo! |
Would it be possible to suggest appropriate tags when editing a document?
I know I can add and create new tags, but those are all the tags known. It might be nice to have some kind of ranking for "appropriate tags". I'm not sure how the document classification system now works under the hood, but since there are "auto" tags available, I think this should be possible?
Something like "Tags used for similar documents: <tag1> <tag2>"
(Click tags to add them to this document)
The text was updated successfully, but these errors were encountered: