mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 03:55:58 +03:00
[GH-ISSUE #178] Aumotation based upon Filename #140
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#140
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @grover31 on GitHub (Oct 17, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/178
Originally assigned to: @ciur on GitHub.
My Scanner allows filename prefixes based on shortcut scanning profiles ("Cheque_", "Receipt_" etc), Allowing filename matching (rather than content matching) for Automations would allow these shortcuts to be used for reliable folder-selection.
@l4rm4nd commented on GitHub (Dec 5, 2020):
+1
@patrk commented on GitHub (Dec 17, 2020):
+1
@h3rbst commented on GitHub (May 22, 2021):
+1
@koehntopp commented on GitHub (May 22, 2021):
+100
I would actually like an option to skip the OCR altogether.
@ciur commented on GitHub (May 22, 2021):
Based on popular demand 😄 I will implement this feature as part of 2.1 release.
But you'll need some patients as 2.1.0 will be released around December 2021.
@koehntopp, what is the advantage of skipping OCR ?
@koehntopp commented on GitHub (May 25, 2021):
The advantage is that in my case PDFs already come in OCRd elsewhere ;)