[GH-ISSUE #180] New action to reprocess documents #144

Closed
opened 2026-02-25 21:31:18 +03:00 by kerem · 3 comments
Owner

Originally created by @dani on GitHub (Oct 18, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/180

Originally assigned to: @ciur on GitHub.

Right now, documents are only processed on initial import, and automates only applies when the document is imported in the Inbox. This is by design and is fine.

But it would be useful to reprocess existing documents (OCR + Automates). Eg, maybe I uploaded it with the wrong OCR lang set. Or I just added a bunch of new automates and I'd like them to be applied to existing docs instead of setting new tags manually.

Originally created by @dani on GitHub (Oct 18, 2020). Original GitHub issue: https://github.com/ciur/papermerge/issues/180 Originally assigned to: @ciur on GitHub. Right now, documents are only processed on initial import, and automates only applies when the document is imported in the Inbox. This is by design and is fine. But it would be useful to reprocess existing documents (OCR + Automates). Eg, maybe I uploaded it with the wrong OCR lang set. Or I just added a bunch of new automates and I'd like them to be applied to existing docs instead of setting new tags manually.
kerem 2026-02-25 21:31:18 +03:00
Author
Owner

@ciur commented on GitHub (Oct 18, 2020):

@dani, thank you for opening this issue. It makes total sense to have a "restart OCR/Automate". I will take care of it.

<!-- gh-comment-id:711294965 --> @ciur commented on GitHub (Oct 18, 2020): @dani, thank you for opening this issue. It makes total sense to have a "restart OCR/Automate". I will take care of it.
Author
Owner

@amo13 commented on GitHub (Nov 13, 2020):

duplicate of #88

<!-- gh-comment-id:727077295 --> @amo13 commented on GitHub (Nov 13, 2020): duplicate of #88
Author
Owner

@ciur commented on GitHub (Jan 21, 2021):

The automation part (re-run of automation) is implemented as part of Papermerge 2.0 and will be available in couple of weeks.

The document re-processing (the OCR part) is little trickier with introduction of document versioning:
on document re-processing should new version be added or should new document with different language overwrite/reset all existing document versions ?
I close this issue as the most stringent problem (re-run of automations) was solved.

<!-- gh-comment-id:764579137 --> @ciur commented on GitHub (Jan 21, 2021): The automation part (re-run of automation) is implemented as part of Papermerge 2.0 and will be available in couple of weeks. The document re-processing (the OCR part) is little trickier with introduction of document versioning: on document re-processing should new version be added or should new document with different language overwrite/reset all existing document versions ? I close this issue as the most stringent problem (re-run of automations) was solved.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/papermerge#144
No description provided.