[feature request] Suggestions when changing the name

[monnypython]

I've now switched to descriptive short clear names for documents instead of the automatically generated file names of the scanner. In order to get a certain structure when naming the same documents such as "Invoice Telekom 2022-07" you have to know roughly how this type of document was named a few weeks ago. For this it would be very usefull if you would get word suggestions for other filenames when entering the "name".

e.g.:

"Search" (Name)	Suggestions
"Telekom"
	Telekom Auftrag 2019
	Rechnung Telekom 2022-07
	Rechnung Telekom 2022-06
	etc.

[eikek]

I was thinking that if you use a pattern to create the name, maybe we could use this in the first place? There is some issue about this related to the filenames, I think. But imho this can be done to any "name", item and files/attachments.

The idea is that you can create some pattern and docspell would automatically generate the name from the other attributes of the item (this then only works for the name attribute). This could then avoid any manual intervention, though the search would be easier to do and requires no configuration…. wdyt - would this be also good/better/worse for your case?

[monnypython]

I found the ticket where the same thing is discussed (https://github.com/eikek/docspell/issues/543#issuecomment-755929663) (sorry :| ) Yes, that would be a very good (better) possibility!

You think that's possible? That would be great.

---

Some thoughts on this:

• if a fully automatic, global naming exists:

  • definable placeholders if not all required metadata have been filled out (and maybe a message or "alert sticker" like if not all defined data are available

• collective/user settings for renaming:

  • fully automatic (see point 1)
  • rename if confirmed

[eikek]

I think it's possible, but it has some subtleties to it. The item name is also send to the fulltext search index. That means it must be kept up to date when the user changes metadata. This is a bit annoying 😄 And the patterns currently used in the webui would be obsolete then I guess. It requires a ui change there as well.

I like the idea to apply it only once it has been confirmed.

It think it should be possible to display a warning underneath the name field if the provided pattern uses empty metadata blocks. But the pattern could also support conditionals-like structures so you could display alternatives in case a metadata is not defined.

The pattern would be defined for the whole collective, because of the fullltext index dependency. If this were to be extended to filenames - this "limitation" doesn't apply, but I guess one would want to refer to the item name