#Metadata File Failed To Load

1 messages · Page 1 of 1 (latest)

steep echo
#

Hey guys!

This is a new one for me. I'm not sure if I've missed some new attributes to the config file. The error I'm seeing is:

[2024-01-23 08:00:23,097] [meta.py:758]               [INFO]     |====================================================================================================|
[2024-01-23 08:00:23,097] [meta.py:758]               [INFO]     |                           Loading Metadata File File: config/movies.yml                            |
[2024-01-23 08:00:23,097] [meta.py:758]               [INFO]     |====================================================================================================|
[2024-01-23 08:00:23,097] [meta.py:759]               [INFO]     |                                                                                                    |
[2024-01-23 08:00:23,106] [meta.py:158]               [DEBUG]    | File Loaded From: /config/movies.yml                                                               |
[2024-01-23 08:00:23,106] [library.py:166]            [ERROR]    | YAML Error: metadata attribute is required                                                         |
[2024-01-23 08:00:23,106] [library.py:167]            [INFO]     | Metadata File Failed To Load  

And this is the actual config it's trying to build:

collections:

  Trending Movies:
    trakt_trending: 50
    tmdb_trending_weekly: 50
    summary: Trending Movies.
    sort_title: '++_002'
    visible_library: true
    visible_home: true
    visible_shared: true
    smart_label: added.desc
    filters:
      release.after: 2023-01-01
    sync_mode: sync
    schedule: daily
    collection_mode: hide

I've tried searching for an answer in the wiki, but I struggle to find anything that makes sense for me. Help and avenues are highly appreciated! Thanks!

hot mortarBOT
#

YAML Error: metadata attribute is required

The attributes metadata_path and overlay_path are now legacy, and will likely produce an error metadata attribute is required when running PMM.

We have new attributes: collection_files, overlay_files and metadata_files

Whilst this error can be ignored, we strongly advise you to move over to the new attributes, which can be done following this guidance:

:one: If your YAML file creates collections or is a PMM Defaults Collection File then it belongs under collection_files.

:two: If your YAML file creates overlays or is a PMM Defaults Overlay File then it belongs under overlay_files

:three: If your YAML file edits item metadata then it belongs under metadata_files

:four: If your file creates collections AND edits item metadata, then it should go in both collection_files and metadata_files

If you are unsure on the above, the majority of metadata_path files will now fall under collection_files, and all overlay_path files will now fall under overlay_files.

Below is an example of the new attributes in use:

libraries:
  Movies:
    collection_files:
      - pmm: imdb
    overlay_files:
      - pmm: resolution
    metadata_files:
      - file: config/metadata.yml
playlist_files:
  - pmm: playlists

https://metamanager.wiki/en/latest/config/files/#example

trim ploverBOT
#

Welcome @steep echo!

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

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

#

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

golden venture
#

@steep echo see above

steep echo
# golden venture <@602451403868340236> see above

I've read that information on the wiki page as well, but it's still unclear to me which category my config should fall under. Since it's a config that builds a collection, logically it seems like it would belong under "collection_files". However, my main config includes assets with a poster associated with the collection. Does this mean it should also be categorized under "metadata_files"? I don't understand this part:

      - pmm: imdb```

That section doesn't seem to fit into my configuration at all. Could you please provide some guidance?
warm bay
#

metadata_files is used for files doing things like this:

metadata:
  Godzilla (1954):
    match:
      title: Godzilla
      year: 1954
    content_rating: R
  Godzilla (1998):
    match:
      title: Godzilla
      year: 1998
    sort_title: Godzilla 03
    content_rating: PG-13
lean sonnet
#

notice the keyword metadata:

#

hence metadata_files:

#

if that had said collection: or dynamic_collection: then it would have been collection_files:

steep echo
# lean sonnet if that had said `collection:` or `dynamic_collection:` then it would have been ...

Ok so from the example below, what should I put as value in collection_files? This is what I’m struggling to understand.

collections:

  Trending Movies:
    trakt_trending: 50
    tmdb_trending_weekly: 50
    summary: Trending Movies.
    sort_title: '++_002'
    visible_library: true
    visible_home: true
    visible_shared: true
    smart_label: added.desc
    filters:
      release.after: 2023-01-01
    sync_mode: sync
    schedule: daily
    collection_files: xxxxx
lean sonnet
#

This yml is not what you put in config.yml. This is yml that you would place in a file called whatever_you_want.yml

#

Then in config.yml, under the "heading" called collection_files: you would have an entry below it that references /oath/to/whatever_you_want.yml

#

Examples there

steep echo
golden venture
#

Matadata_path should really become collection_files

steep echo
steep echo
golden venture
#

that is what we explained earlier in the post

trim ploverBOT
#

Hello @steep echo, a user has suggested that this thread has been resolved and can be closed.

Please confirm that you are happy to close this thread by typing /close or by pressing the Close Post button which is pinned to this thread.

steep echo