-
|
I noticed that a document I dropped into paperless containing the word "Rentenversicherungsnummer" would not match the word "Rentenversicherung". For it do actually match, I have to add the full word to the match strings. The reason I ask is that in some cases one might not guess all possible word ending which should still trigger the same match. Maybe I did not foresee this, or the word was broken somewhere else. For it to match correctly, I then would need to add |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Ok, so I think I can answer my own question now. As a somewhat "uncomfortable" matching pattern I overlooked regular expressions. This is what I have to use in that case. So I guess it's good that it's possible, but my conclusion from this is that a checkbox "allow substrings" next to "case insensitive" would be great. Using regular expressions might be too much for people who are afraid of anything that looks just roughly like programming code. |
Beta Was this translation helpful? Give feedback.
Ok, so I think I can answer my own question now. As a somewhat "uncomfortable" matching pattern I overlooked regular expressions. This is what I have to use in that case.
Therefore, for matching
*arbeitsunfähig*, I can use the regular expressionarbeitsunfähigand set it to case insensitive.If I need to match any of multiple subwords, I can separate the subword candidates by
|instead of spaces:sub1|sub2|sub3So I guess it's good that it's possible, but my conclusion from this is that a checkbox "allow substrings" next to "case insensitive" would be great. Using regular expressions might be too much for people who are afraid of anything that looks just roughly like programming code.