[Feature] Physical world interface for scanned docs - file name vs. displayed name

[cnbhl]

Do you want to request a feature or report a bug?
Feature request

First of all I really appreciate the work, you folks been doing on ONLYOFFICE. Thanks for that. I will shortly describe a used workflow, that I think could be useful for every user.

When dealing with scanned pdf files (e.g. old non digitalised documents, signed contracts, invoices ...) I scan these documents with an UUID as file name (e.g. dee0fa25-39ba-4add-9661-6574fc47793d.pdf coming form a barcode lable on document).

The benefit of doing it that way is, the physical document is uniquely identified and when I rescan the document (e.g. second signature), resp. upload it a second time, onlyoffice will notice the new version of an already existing file (the upload option "replace same filename", what is a very nice feature).

The disadvantage is, that I have non human readable filenames. If I change the filename the recognition of a new version is not working any more.

The same behaviour - documents leaving ONLYOFFICE and comming back - could be applied for digital documents. So a unique identifier placed inside the file itself would be a good idea, i think.

What is the current behavior?
It is possible to upload pdf files with UUIDs as filename and store them inside ONLYOFFICE. When I change the filename to human readable the benefit of unique identifiers vanish.

What is the expected behavior?
It would be perfect to have a phyical/digital interface using UUIDs which are used as filename to identify a document inside ONLYOFFICE. And to have a second let's call it display name stored inside the database that can be changed instead of the file name of the stored document. Maybe both names are displayed.

This way ONLYOFFICE notice the incoming files by the identifier but the user sees a human readable display name.

Attached:
Example file: doc_7c40160f-7f7f-4ca4-bb4e-376c2c00a49d.pdf

[ShockwaveNN]

Originally created here ONLYOFFICE/DocumentServer#1249

Maybe some kind system of tags for files will be enough, but it's just my idea while I read this issue
It's up to developers and designers to decide do we need it at all and in which form

[ShockwaveNN]

Oops, sorry, closed by mistake

[cnbhl]

The reason I didn't suggested a tagging system (that would as well be nice) is for that you probably create a great amount of tags if you want to name every file. And you can't see a human readable filename in UI.

E.g.:
original filename: 0af215d...pdf
tag: [Invoice] [1526595] [Company A]

the number tag 1526595 (which represents e.g. the foreign invoice number) would differ with every received invoice and would create a new tag.

Therefore I suggested a "display name" that does not change the original file name (inside UI).

E.g.:
original filename: 0af215d...pdf (small displayed or inside information; used to identify the document when coming from outside OO)
display filename: Invoice 1526595 - Company A - 15.04.2021.pdf
tag: [Invoice] [Company A]

maybe with a general preference to name downloaded files (when leaving OO) by original or displayed file name.

[HelenBelova17]

Hello @cnbhl,
Thank you for your suggestion, we will take it into consideration, issue 50270 in our private bug tracker.