Request: Collections extras (url & cover)
-
- Posts: 107
- Joined: 12 Apr 2020, 04:02
Request: Collections extras (url & cover)
I'd love the possibility to enrich collections folders with post processing features such as the one we have on simple movies. A link to the tmdb collection page and an import on the cover would be very appreciated. Thanks for reading and keep up the great work !
Re: Request: Collections extras (url & cover)
This should be easy because the info is in the main movie lookup
e.g.
https://developers.themoviedb.org/3/mov ... ie-details
e.g.
Code: Select all
"belongs_to_collection":{"id":87096,"name":"Avatar Collection","poster_path":"/nslJVsO58Etqkk17oXMuVK4gNOF.jpg","backdrop_path":"/8nCr9W7sKus2q9PLbYsnT7iCkuT.jpg"}
-
- Posts: 107
- Joined: 12 Apr 2020, 04:02
Re: Request: Collections extras (url & cover)
Well then fingers crossed chief wizard agrees to make this happen
Re: Request: Collections extras (url & cover)
Not planned, because how does FileBot know which folders are collections folders? You know because you wrote your format. But FileBot can't know, because FileBot doesn't "understand" your format so to say, and also doesn't know what format may have been used in the first place when first organizing files sometime down the line.
Please read the FAQ and How to Request Help.
-
- Posts: 107
- Joined: 12 Apr 2020, 04:02
Re: Request: Collections extras (url & cover)
Filebot knows if a movie is part of a collection though, so movie folder -1 level is where the collection folder should be, regardless of format.
Else a naming convention, like all Collections folders need to have "Collection" in their name?
Else a naming convention, like all Collections folders need to have "Collection" in their name?
Re: Request: Collections extras (url & cover)
Yes, supporting your specific use case it easy. But we can't assume your specific use case. We can't just say "parent parent folder" is the collection folder. It might be in your case, but it's not necessarily the case for others.
e.g.
We do have the same problem with artwork, making assumptions about the folder structure, but that's because we assume {plex} to be the standard that everyone uses. There is no such standard for collections. The Plex standard doesn't specify collection folders (though it may work mostly, it's still out of spec). We don't have a special special "plex with collection folders" binding, and so we neither have a standard, nor can we make assumptions of how the majority of users use collection folders.
e.g.
Code: Select all
{collection}/{ny}/{ny}
Code: Select all
{any{collection}{ny}}/{ny}
We do have the same problem with artwork, making assumptions about the folder structure, but that's because we assume {plex} to be the standard that everyone uses. There is no such standard for collections. The Plex standard doesn't specify collection folders (though it may work mostly, it's still out of spec). We don't have a special special "plex with collection folders" binding, and so we neither have a standard, nor can we make assumptions of how the majority of users use collection folders.
Please read the FAQ and How to Request Help.
-
- Posts: 107
- Joined: 12 Apr 2020, 04:02
Re: Request: Collections extras (url & cover)
No problem thanks for the consideration.
Re: Request: Collections extras (url & cover)
myabe something like:
FYI: KODI set info
https://kodi.wiki/view/Movie_sets_artwork
Code: Select all
{
if (folder instanceof Collection) {
getCollectionInfo()
}
}
https://kodi.wiki/view/Movie_sets_artwork
Re: Request: Collections extras (url & cover)
Well, that wiki page further emphasizes that Kodi doesn't support collection folders (on the file system level) and that's why they have this magic movie sets artwork folder where Kodi can find extra local artwork in case it's needed for some special view in the Kodi interface.
It wouldn't be that hard to write a custom script for a custom use case, because that way can make all the assumptions we want, but the problem is a universal solution that works out-of-the-box for the vast majority of users and relevant use cases.
It wouldn't be that hard to write a custom script for a custom use case, because that way can make all the assumptions we want, but the problem is a universal solution that works out-of-the-box for the vast majority of users and relevant use cases.
Please read the FAQ and How to Request Help.