-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move files between documents #979
Comments
In the principle of a DMS, it is better to store the documents separately, even if they are in a mail. So you can tag them individually and add further information. This is not possible if they are stored as an attachment in the item. For example, how are you going to find an invoice in a few years that you haven't tagged as such. You can then neither search for the period, the company or the like. You may have already forgotten the context of the mail;). I've got used to the following workflow: Maybe this will help you further ... |
=> yes this is mostly true
=> this is not true in case of mail import with the scan mailbox function
Your proposal is a thing to think about...but this solution is not optimal because:
One question: Why do you additionally set a tag "linked"? The custom filed is shown like a tag in the GUI... |
I use a similar approach: I have a field "Vorgang" which can mostly filled with some number that is already on the paper. Or sometimes I make something up. But I can also see the need to merge items. I'm not quite sure what you mean exactly given this title @vakilando - there is #414 and #528 - you mean the latter, right? In my case there are sometimes contracts with additional stuff that I rather have in one item. So these I would want to "merge" into one item and remove the other. For the link documents case, I seldomly needed something beyond the custom field solution. But I'm fine with adding it, because it will be optional and if one chooses to not use it, it's not in the way. But maybe we can find a solution based on custom fields … that would be least effort and I always like reusing what is there :-) |
Yes, I have that problem too. We had already discussed this on the gitter. The listing of all the phrases used in a particular user field would be very helpful. Maybe you could activate this option for certain fields in the options? I hope @eikek will find time for this at some point. Edit: Just an idea: |
Hmm not quite Sure what is better. I need one of those but merging and linking are two different things I think... |
Yes, these two are completely different. I want to add the "merge" at some point. For the linking, I'm not sure anymore whether a dedicated feature makes sense. Maybe I can add a new field type where the ui could improve suggestions/editing. |
I think this could work well. It can be made available for a specific (new) field type. So the user is then to decide when searching for existing options makes sense for a given field by selecting the field type. Fields of this type could also be rendered differently in the UI. |
That sounds very good. |
This is really great to hear!
Yes, this also is a very good idea to be realized. I'll wait impatiently but patiently for these two (for me important) features! |
Hi @vakilando - with the release of 0.26.0 and the merge feature, is this covering what you described in this issue? |
Sorry for the late reply... |
No worries! Thanks for the feedback and the improvement idea. This could be its own issue - hm, maybe the name of the item can be added to the notes; not sure. I'll create one and close this one then. |
Once again: very great piece of software, thank you very much!
I've just upgraded from v0.23 to v0.25.1 and from postgresql 11.7 to 13.3 - flawlessly...
What I'm still missing very much:
Move or maybe also copy (as link) files between documents!
A use case:
When you automatically upload mails (Scan Mailbox) you may get more than one document (imported mails with attachments) for the same "event" (order, confirmation, bill).
To be able to move the relevant files to one document would be grate !
Another thing...I've updated my Unraid Templates.
The text was updated successfully, but these errors were encountered: