Skip to content
This repository has been archived by the owner on Feb 28, 2022. It is now read-only.

"Folder {0} is not eligible for auto-organize because it is also part of an Emby library" #56

Open
Ferk opened this issue Jan 31, 2021 · 0 comments

Comments

@Ferk
Copy link

Ferk commented Jan 31, 2021

My library is a bit of a mess in terms of naming and distribution of videos (some have folders, some don't, names are not always optimal or consistent, etc).
So I wanted to try auto-organize with the expectation that it'd organize and standardize the names

Yet it doesn't seem to be doing that. I've found these messages in the logs:

https://github.com/jellyfin/jellyfin-plugin-autoorganize/blob/a545397ca64a23b492995a9d3e178853c767ca70/Emby.AutoOrganize/Core/MovieFolderOrganizer.cs#L74
https://github.com/jellyfin/jellyfin-plugin-autoorganize/blob/718d5c3f53bfeaee483acdd69af8899e3b1c9a07/Emby.AutoOrganize/Core/TvFolderOrganizer.cs#L74

  1. I believe this should be "Jellyfin", not "Emby" (or just "Movie library" and "TV Show library" without naming the app)

  2. It should be made more clear what exactly is this plugin meant to do and why the path given isn't eligible when it's part of the library. At least something about how the directory is used could be part of the description of the field that asks for the path.

My expectation was that it would organize files within the folder, without moving/copying them out of the folder. But if the purpose of this plugin is to copy/move files FROM places that are NOT in the library TO the library, then which library folder is the destination? you can define multiple directories as sources for each Jellyfin library, does it just use the first one? Or does it not copy the files at all and directly adds them to the database somehow, even if not in the library? Either way, this should be explained somewhere.

However, if what the message is trying to say is that the folder will not be watched by the plugin because it's already watched by Jellyfin and the auto-organization will happen later at some other point after regular library scan... then I'd suggest more clear wording, like Folder {0} is part of a library, auto-organize will process it after scan or something along those lines. But it's hard to tell if that's what's going on since, at least in my case, the auto-organizing doesn't seem to happen at all.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

1 participant