Date Scanned and Existing Media

[Netsrfr 1]

I am not certain if this should be classified as a bug or a feature request, since this seems to be unexpected behavior to me, but may very well be the intended behavior.

My libraries are configured to use the "date scanned into the library" as the behavior for the new content date. However, it appears that Emby determines whether content is new or existing based on the file path, rather than the existing metadata. I recently updated a TV show to address a filename ordering issue, i.e., Season 1 -> Season 01, Season 2 -> Season 02, etc. Since this content exists in the media library, I would not expect the date added to change

Observed Behavior:

Scan new media into the library from the filepath /TV/Show/Season 1/Episode 1.mkv on 2020/01/01 | Date added: 2020/01/01
Move media from the filepath /TV/Show/Season 1/Episode 1.mkv on 2025/01/01

[GrimReaper 4740]

11 minutes ago, Netsrfr said:

I am not certain if this should be classified as a bug or a feature request, since this seems to be unexpected behavior to me, but may very well be the intended behavior.

It is, as moving/renaming items effectively clears the item from the db and re-adds it as new. The only way to preserve Date Added is by saving NFOs next to media, whereupon existing (i.e. original) date added NFO tag will be honored. 

[Netsrfr 1]

Thank you for the quick response. I was still working on outlining the issue and providing the relevant report details, but I had inadvertently hit Ctrl+Enter while still writing up the post.