#Unconfigured Collections Vs Unmanaged Collections (understanding logs)

1 messages · Page 1 of 1 (latest)

verbal niche
#

Greetings! Apologies for what I imagine is a pretty basic question. I found some answers searching the discord but still having a bit of trouble wrapping my head around it/confirming what I am seeing in my logs.

Running Kometa I see in my logs:

834 Unmanaged Collections - to be expected I've let Plex control collection creation so no surprises here.
910 Unconfigured Collections - this I see the same list of Plex created collections as well as my Kometa created collections.

I guess my confusion comes in as why are my Kometa collections being listed under Unconfigured? I see that to be managed all it takes for a collection to contain the Kometa Tag but I would have though since I'm controlling those Kometa collections with differnt .yml files they would not be listed as unconfigured?

Happy to provide any examples from logs/add any clarifying details I may have missed. Thanks a lot for any asstiance in wrapping my head around this. Thanks!

long marshBOT
#

Welcome @verbal niche!

Someone from <@&938443185347244033> will assist when they're available.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

#

You can press the "Close Post" button above or type /close at any time to close this post.

raven nymph
#

Managed = Kometa created this collection
Configured = This collection is referenced in the currently active config

#

Given this config:

libraries:
  Movies:
    collection_files:
      - file: config/imdb-things.yml
      - file: config/trakt-things.yml

The collections produced by those files show up as both "Managed" and "Configured".

If you do this:

libraries:
  Movies:
    collection_files:
      - file: config/imdb-things.yml
      # - file: config/trakt-things.yml

They are all still Managed, but the trakt-sourced collections are "Unconfigured".

#

Collections where it's not known at the start of the run whether they are goign to be touched will show up as "unconfigured" since at that moment Kometa doesn't know if they will be part of the run or not.

#

For example, running this:

libraries:
  Movies:
    collection_files:
    - default: imdb
    - default: trakt

after all these collections have been created produces:

|============================= Unmanaged Collections in Movies Library
|
| Created in Plex
|
| 1 Unmanaged Collection
|
|============================ Unconfigured Collections in Movies Library
|
| IMDb Lowest Rated
| IMDb Popular
| IMDb Top 250
| Trakt Collected
| Trakt Popular
| Trakt Recommended
| Trakt Trending
| Trakt Watched
| Created in Plex
|
| 9 Unconfigured Collections

Since at that moment Kometa doesn't know if those are going to be for sure part of the run.

verbal niche
#

Ah gotcha, that makes sense. Thanks so much for the detailed explanation really appreciate it!