#Collections Help
1 messages · Page 1 of 1 (latest)
Welcome @lofty thicket!
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.
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Can you please provide the full log showing the error[s] in context?
This kind of logic won't work
When you use a smart filter, the items don't actually "belong" to the collection, it's just a filter of your entire library to show you things that match the criteria.
So when you are saying in your Comedies collection, "show me items which are not in the Rom Coms collection", there are technically 0 items in that collection because it is a Smart Filter collection.
The way around this is to label your items when they meet the criteria and use that label as your .not criteria:
collections:
Musicals:
item_label: Musicals
# your builder criteria here
Rom Coms:
item_label: RomComs
smart_filter:
all:
genre:
- comedy
- romance
label.not:
- Musicals
Comedies:
item_label: Comedies
smart_filter:
all:
genre: comedy
label.not:
- Musicals
- RomComs
Or you convert it to a Dumb collection, but that means it won't update until you run Kometa again.
Also worth noting that those genres are case-sensitive, so comedy vs Comedy and romance vs Romance
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Ah! I see. This makes a lot of sense. Thanks for the help!