Relational Operators for Smart Collection Search

Rathinosk

I am trying to build a Smart Collection for a show using the duration of the episode, but I don't see anything in the documentation in regards to relational operators such as < (less than), > (greater than), <= (less than or equal), and >= (greater than or equal).

Assuming I would like to include all episodes of a particular show, but only episodes 30 minutes or less, I would assume to use syntax similar to:

type:episode AND title:"particular show" AND minutes<=30

Or maybe:

type:episode AND title:"particular show" AND minutes:<=30

I can currently search using "minutes:30", but the search only returns episodes of roughly 30 minutes.

Maybe this is a feature request... :-)

wallawallawa

You can try:

type:episode AND title:"particular show" AND minutes:[* TO 30]

or substitute the minimum time length you want for the '*'; e.g., [18 TO 30]

Rathinosk

Using "minutes:[* TO 30]" seems to work perfectly for my purpose - Thank You!

This "TO" operator certainly gives me something else to play with for building smarter channels.

Was this documented somewhere that I missed?
Are there any other operators like this?

wallawallawa

Glad that worked for you. ErsatzTV uses Lucene for querying/searching, and some of the search syntax is covered in the ErsatzTV documentation. You can also look at other sites that have examples of Lucene syntax, that's what I did when I couldn't find what I wanted in my media items for creating collections. Below is a link to just one such site.

https://lucene.apache.org/core/2_9_4/queryparsersyntax.html

Not sure when he could have time to do so, but the ErsatzTV documentation would benefit by being updated (search/query syntax, FFMPEG, other 'technical' items settings fully explained, etc.).

Rathinosk

Ah, that syntax looked familiar but I hadn't made the connection. I have too many different search syntaxes rattling around in my brain. Thanks again!

I agree that expanding the documentation in this regard would be helpful, but TBH, I made it this far with the documentation that's currently in place. A simple mention of Lucene would have filled the gap there though.

I think that a lot of the FFMPEG stuff would be mitigated by including a solid set of well-tested basic configuration profiles - something that would work for the typical user out of the box. I honestly don't remember what it came with because I still use four primary profiles that I created months ago.