Favorite with season or original airdate keyword?

[bialio]

I frequently find myself wanting to record a show's latest season (usually start something on Netflix, realize I like it, and start recording it).

It'd be nice if I could create a favorite that used a 'Season 4 or later' condition along with matching the title or keyword or whatever.

Is that possible? I don't know how the favorite manager code in the scheduler works....

[Fuzzy]

It's not 'entirely' possible. The lucene engine that handles the keyword search has a select set of information for the shows to match against. As far as I can tell, the fields that are present are:
id; title; desc; ep; year; rated; peeps; categories; ers; bonuses

So season and episode are not really available. the year property is I think only populated normally for movies.

Now, I'm not sure this can't be added - adding more fields to the search should not be difficult, but it would increase the memory for print of the index, as well as slow down the index and searching tasks. Even then, I'm not sure if the keyword query would support a 'Season>3' type test. I know nothing about lucene queries.

[nyplayer]

I did something similar with Matlock a while back just wanted the last few seasons. I had to use the EP as a keyword.

[bialio]

Thanks! that's tricky.

[Narflex]

Beyond that...you'd need to modify Agent.java to add a field for season and then add it into the UI as well so you can set it. This won't have any performance impacts though...so nothing to worry about there.

[Fuzzy]

Originally Posted by Narflex

Beyond that...you'd need to modify Agent.java to add a field for season and then add it into the UI as well so you can set it. This won't have any performance impacts though...so nothing to worry about there.

Something I couldn't tell in my first code exploration of this... Do agents use the lucene search? Would it be possible to do more advanced filters in a keyword search my specifying an actual lucene query?

[Narflex]

Originally Posted by Fuzzy

Something I couldn't tell in my first code exploration of this... Do agents use the lucene search? Would it be possible to do more advanced filters in a keyword search my specifying an actual lucene query?

Agents can use the Lucene search feature...however, for compatibility with how it worked before we added Lucene, there is the flag use_legacy_keyword_favorites which defaults to true. If you set that to false, then it'll use Lucene for keyword favorites only; but then it won't support regex in search patterns and also won't search every field like it would without Lucene.

The normal process is just walking over the entire Airing table and matching those against the Agent's criteria. Even for the Lucene search, it would first search using the keyword and then apply the same matching after that to limit even further (for things like channel restrictions).

[Fuzzy]

Originally Posted by Narflex

Agents can use the Lucene search feature...however, for compatibility with how it worked before we added Lucene, there is the flag use_legacy_keyword_favorites which defaults to true. If you set that to false, then it'll use Lucene for keyword favorites only; but then it won't support regex in search patterns and also won't search every field like it would without Lucene.

The normal process is just walking over the entire Airing table and matching those against the Agent's criteria. Even for the Lucene search, it would first search using the keyword and then apply the same matching after that to limit even further (for things like channel restrictions).

Okay, that was what was confusing me in the code I think. I saw all the lucene code in there, and saw the legacy switch - I just made an assumption that the legacy mode would be optional, and that the 'new' way would be the norm (though honestly, if I'd looked closer, that would have been clear).

So i wonder, if the most versatile option to improve on the agent's flexibility, while allowing the old regex 'keyword' search, would be to add either a 'query' search, or maybe even a prefix that could be added in a keyword search that flagged it as a more advanced 'lucene' search (thereby making it compatible with older UI's). might be a relatively simple change in the agent code then to check not just the legacy switch, but also the first few bytes of the keyword, and if it matches, it will process the keyword NOT as regex, but as a lucene query. Combined with adding a few more fields to the lucene index, this would provide all the flexibility the op is asking for and more.

[bialio]

Can you put a full REGEX in the Keyword field? I see the * and ? are called out, but if the other operators are available that'd be sweet....

[Fuzzy]

Yeah, pretty sure it does a regex match to some string generated from the airing - I'm not entirely sure the full format of the string though. I'm pretty sure it starts with the ID though, which is why a very common use of the keyword on a regular title favorite is EP\d+ to only match to airings with full episodic metadata with them (since those without the actual episode info will be SH* ID's).

[bialio]

SO - I modified a keyword favorite with some basic REGEX and it works. So with a little work you can accomplish this 'season x or later' - just have to find the EP number.

btl.