Custom metadata paths result in extra 'metadata' subfolder

[cnstarz 19]

In Library > Advanced, when you specify a custom metadata path, it actually throws the metadata into a new subfolder of that custom path called 'metadata'.  For example:  If I specify `/mnt/media/emby_metadata` as the custom path, it'll create subfolder `/mnt/media/emby_metadata/metadata` and throw all the metadata into that instead.

I don't think this is expected behavior.  The old value was `/config/metadata`, and that directory contained all the metadata folders:

user@server:/config/metadata# ls -al
total 968
drwxr-xr-x    14 emby media   4096 Mar  8 20:06 .
drwxr-xr-x    12 emby media   4096 Mar  8 14:25 ..
drwxr-xr-x   258 emby media  20480 Feb 24 13:33 collections
drwxr-xr-x     2 emby media   4096 Mar  8 14:45 gamegenres
drwxr-xr-x    42 emby media   4096 Mar  3 04:06 genres
drwxr-xr-x   258 emby media   4096 Jan 29  2021 library
drwxr-xr-x   188 emby media  12288 Feb 13  2023 livetv
drwxr-xr-x   129 emby media  20480 Feb  4 23:13 musicalbums
drwxr-xr-x    36 emby media   4096 Feb 19 13:42 musicartists
drwxr-xr-x     2 emby media   4096 Mar  8 14:45 musicgenres
drwxr-xr-x 17496 emby media 888832 Mar  9 01:30 people
drwxr-xr-x   116 emby media   4096 Jan  9 22:15 studios
drwxr-xr-x     6 emby media   4096 Feb 12  2023 tags
drwxr-xr-x     3 emby media   4096 Jan 29  2021 views

 

I copied the contents of that metadata folder to a mounted share, and I updated the path to `/mnt/media/emby_metadata`:

user@server:/config/metadata# ls -aln /mnt/media/emby_metadata
total 0
drwxrwxrwx  1     997  1025    208 Mar  9 08:30 .
drwxrwxrwx+ 1     997  1025     16 Mar  9 08:53 ..
drwxrwxrwx  1     997  1025  12768 Feb 24 07:33 collections
drwxrwxrwx  1     997  1025      0 Mar  8 08:45 gamegenres
drwxrwxrwx  1     997  1025    622 Mar  2 22:06 genres
drwxrwxrwx  1     997  1025   1024 Jan 29  2021 library
drwxrwxrwx  1     997  1025  11904 Feb 13  2023 livetv
drwxrwxrwx  1     997  1025  18348 Feb  4 17:13 musicalbums
drwxrwxrwx  1     997  1025   4454 Feb 19 07:42 musicartists
drwxrwxrwx  1     997  1025      0 Mar  8 08:45 musicgenres
drwxrwxrwx  1     997  1025 863398 Mar  8 19:30 people
drwxrwxrwx  1     997  1025   3204 Jan  9 16:15 studios
drwxrwxrwx  1     997  1025     50 Feb 12  2023 tags
drwxrwxrwx  1     997  1025     12 Jan 29  2021 views

 

However, after I saved it and initiated a Metadata Folder Scan, it created a subdirectory called `metadata` and placed new metadata into that folder:

user@server:/config/metadata# ls -aln /mnt/media/emby_metadata
total 0
drwxrwxrwx  1     997  1025    208 Mar  9 08:30 .
drwxrwxrwx+ 1     997  1025     16 Mar  9 08:53 ..
drwxrwxrwx  1     997  1025  12768 Feb 24 07:33 collections
drwxrwxrwx  1     997  1025      0 Mar  8 08:45 gamegenres
drwxrwxrwx  1     997  1025    622 Mar  2 22:06 genres
drwxrwxrwx  1     997  1025   1024 Jan 29  2021 library
drwxrwxrwx  1     997  1025  11904 Feb 13  2023 livetv
drwxr-xr-x  1     997  1025     14 Mar  9 08:50 metadata                           <------- NEW SUBFOLDER
drwxrwxrwx  1     997  1025  18348 Feb  4 17:13 musicalbums
drwxrwxrwx  1     997  1025   4454 Feb 19 07:42 musicartists
drwxrwxrwx  1     997  1025      0 Mar  8 08:45 musicgenres
drwxrwxrwx  1     997  1025 863398 Mar  8 19:30 people
drwxrwxrwx  1     997  1025   3204 Jan  9 16:15 studios
drwxrwxrwx  1     997  1025     50 Feb 12  2023 tags
drwxrwxrwx  1     997  1025     12 Jan 29  2021 views


user@server:/config/metadata# ls -aln /mnt/media/emby_metadata/metadata           <------- NEW SUBFOLDER
total 0
drwxr-xr-x 1 1024  100  14 Mar  9 08:50 .
drwxrwxrwx 1  997 1025 208 Mar  9 08:50 ..
drwxr-xr-x 1 1024  100   8 Mar  9 08:50 library


user@server:/config/metadata# ls -aln /mnt/media/emby_metadata/metadata/library    <------- NEW SUBFOLDER
total 0
drwxr-xr-x 1 1024 100  8 Mar  9 08:50 .
drwxr-xr-x 1 1024 100 14 Mar  9 08:50 ..
drwxr-xr-x 1 1024 100 64 Mar  9 08:50 32
drwxr-xr-x 1 1024 100 64 Mar  9 08:50 b1

 

This forced me to move everything from the `emby_metadata` folder into the `emby_metadata/metadata` folder.  Basically, this prevents users from naming their metadata folder to whatever they want and creates an inefficient (almost redundant) directory structure.

Edited March 9 by cnstarz

[Happy2Play 8296]

1 hour ago, cnstarz said:

In Library > Advanced, when you specify a custom metadata path, it actually throws the metadata into a new subfolder of that custom path called 'metadata'.  For example:  If I specify `/mnt/media/emby_metadata` as the custom path, it'll create subfolder `/mnt/media/emby_metadata/metadata` and throw all the metadata into that instead.

I don't think this is expected behavior.  The old value was `/config/metadata`, and that directory contained all the metadata folders:

It actually is as Emby will add the additional folder because user were applying custom paths to say metadata and trancoding-temp to the same custom path (Emby-stuff) and now transcoding clean-up nukes metadata do to no separation.

So forced subfolder was the solution.

[cnstarz 19]

23 minutes ago, Happy2Play said:

It actually is as Emby will add the additional folder because user were applying custom paths to say metadata and trancoding-temp to the same custom path (Emby-stuff) and now transcoding clean-up nukes metadata do to no separation.

So forced subfolder was the solution.

Huh, fair enough. I guess my suggestion would be to add that clarifying information underneath the field. "Note: This path will contain a subfolder called 'metadata' which will hold all metadata files and folders."