mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #34] How I would like to use papermerge as a paperless user #27
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#27
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 @Tooa on GitHub (Jul 11, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/34
Hi 👋,
this is a reply to your paperless issue ticket showcasing papermerge. I would like to give you some feedback on the project from the perspective of a paperless user. Further, I would like to describe my current paperless setup and how I would love to use papermerge in the future (tested version v1.2.3)
Feel free to ask questions if something is unclear.
Usage
How I use Paperless (docker installation)
20200711Z - correspondent - titleand choose WebDav target in the app to upload it to my NASPost-consumptionscript of paperless, I send a notification via Telegram to my phoneThings that trouble me with this workflow
import to documentsthe document's metadata is merged with my existing structure. Then, I wouldn't have to delete the wrong tags and correspondents.How I would like to use Papermerge (docker installation)
20200711Z - correspondent - titleand choose WebDav target in the app to upload it to my NASFeature Requests
Blocker
Following a few things that do not work out for me and therefore block me from migrating to papermerge as a paperless user:
./import:/opt/papermerge/import/with the worker, I have no permissions to copy files in the created host mountimportWould need in the future
Improvements
KeyError at /paste-pages/Nice to have
@ciur commented on GitHub (Jul 11, 2020):
wow, I am very impressed ! Thank you very much for detailed feedback! Let me go over it carefully and later I'll be back with a detailed reply.
@ciur commented on GitHub (Jul 11, 2020):
first question: what is correspondent? I saw it in paperless source code/documentation but was unable to figure it; out what does it stands for ? (obviously I know dictionary description of the word, but what does it mean in paperless/papermerge context ? )
@Tooa commented on GitHub (Jul 11, 2020):
No problem, you are welcome.
Correspondent refers to the sender of the document. Let's say you receive a bill from your insurance called "TK - Technikerkrankenkasse" then
correspondentrefers to that name. Tagging the documents with the correspondent allows me to quickly filter all correspondence between me and that specific insurance.@totti4ever commented on GitHub (Jul 24, 2020):
I can second the workflow and feature request plus blocker to like 95%, also being a paperless user. Would love to give papermerge a try (and I love the idea to have an folder view additionally!), but right now, it is nothing which would help me.
Will check back regularly as you seem to be ambitious on this project :-) !
@ciur commented on GitHub (Jul 25, 2020):
@totti4ever thank you for your feedback!
Backup/Restore feature was implemented. See #23.
Tags management is planned for version 1.5.0
@Pyromane commented on GitHub (Aug 3, 2020):
Date and time "Tags" are automatically recognized and assigned at paperless, which is a great relief.
Using keywords, self-defined tags can be automatically assigned to the documents when they are recognized.
@ciur commented on GitHub (Aug 3, 2020):
tag feature is top priority for 1.5 release. I absolutely agree that tags is a must for any decent document management.
This part:
In Papermerge is called Automates.
It is already there. It can 'recognize' documents and move them to destination folder.
As bonus automates can extract metadata from recognized document. But that is a more advanced topic.
Anyway, when tags feature will be ready, user will be able to configure automates so that recognized document will be assigned 'automatically' preconfigured tags.
Sounds, cool, eh ? 🚀
@Pyromane commented on GitHub (Aug 3, 2020):
Sounds great! Thanks for the detailed answer!
(I assumed the status of your last video)