Metadata templates (new files) not applied on forced rescan

[ubacher]

If I do a forced rescan of a file (or reload metadata) the metadata template specified under NEW does not get re-applied.
(If I put it under UPDATED it does get reloaded i.e.applied.)  Screenshot shows setup.

Should it not get applied?



[attachment deleted by admin]

[Mario]

The "new" is only applied to files not yet in the database.

[ubacher]

So if I need to fix up a Metadata template and reapply it to existing files I need to fill the Updated field, rescan, then restore the original setting.

Is there a reason why it could not reapply the template on a forced rescan?

[Mario]

You can automatically apply metadata templates to new files (files not yet in the database) and files which are updated.

A forced rescan is a rarely used operation. It's basically a last resort, when another application has changed a file without updating the time stamp, or in the rare case when you want to change the thumbnail size later). I don't see a use case for applying a "new" metadata template in this case. And surely not every user would like that, which means I would to have another set of options. I don't think so.

When you force rescan some files, why don't you used run the Metadata Template from the commands menu afterwards?