You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2019. It is now read-only.
Putting the title into the filename (<filename>_<uid>_<primaryNumber>.>secondaryNumber>.<fileExtension>) offers the ability to make the document files itself human readable. This would be maybe a good idea if the storage is taken elsewhere without the software or on datacrash within the database.
But in doing this, the file must be renamed every time the user changes the title of a document. But from the expected use-case, this should be not often, if any.
The text was updated successfully, but these errors were encountered:
It would be more useful to use the original filename which was transmitted on upload.
As example: If a user uploads a file invoice_foobar_24.02.19.pdf, we are using this as permanent name in the background. The user is just seeing the title which he set, which is the filename as default.
So the title can be changed at any time, the original filename not. This is why we should use the filename instead of the title.
Was my first thought too. But then i saw, that many PDFs i have in my download-directory are named "invoice.pdf" or other "unmeaningful" names, so the filename "invoice1.pdf" or "unnamed.png" are not very nice to use :/
But can decide on that later :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Putting the title into the filename (
<filename>_<uid>_<primaryNumber>.>secondaryNumber>.<fileExtension>
) offers the ability to make the document files itself human readable. This would be maybe a good idea if the storage is taken elsewhere without the software or on datacrash within the database.But in doing this, the file must be renamed every time the user changes the title of a document. But from the expected use-case, this should be not often, if any.
The text was updated successfully, but these errors were encountered: