Smarter Smart Collection Exclusions

Smart collections often use exclusion rules to keep a list broad while leaving out a small set of marked records. Previously, an event with no value for an attribute could be left out of a "not equal to" or "not in" rule, even when the editor meant "show everything that is not marked this way." Basker now treats missing values as a natural match for those exclusions, so lists based on hide flags, categories, and similar attributes return the expected set.

Better defaults for hide flags

For common editorial flags, an unset value usually means "not hidden" or "not in this excluded group." Smart collections now follow that reading by default, so an event does not need an explicit false value just to appear in a list. This keeps exclusion-based collections useful on large catalogues where most records should stay unmarked.

Strict matching when needed

Editors can still require the attribute to be present when that distinction matters. A new control appears for custom-attribute exclusion rules, letting you choose between the natural broad match and a stricter match that only includes records carrying the attribute. That gives you precision when you need it without making the common case harder.