Grouping Functions: Difference between revisions
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
The [[expression language]] is largely used to evaluate one file at a time. The grammar implies that something like {{monospace|Field(Artist)}} should get the Artist value for the current file being evaluated. Grouping Functions are a special class of functions that operate on a group of files, instead of on individual files. A simple example would be a function to count the number of artists in the current group. |
The [[expression language]] is largely used to evaluate one file at a time. The grammar implies that something like {{monospace|Field(Artist)}} should get the Artist value for the current file being evaluated. Grouping Functions are a special class of functions that operate on a group of files, instead of on individual files. A simple example would be a function to count the number of artists in the current group. |
||
Grouping Functions may only be |
Grouping Functions may only be useful in relevant areas where Media Center displays groups of files (most notably in [[Categories]] and the [[Tag Action Window]]), and not to individual file listings, such as an expression column in a File Details View, where they can be used, but will not be all that useful. |
||
The [[GroupCountQuery()]] and [[GroupSummaryQuery()]] functions detailed below are special functions that work globally, returning results from the ''entire'' library, regardless of Media Type, or any other filters currently in action. This makes them especially useful for presenting information in Theater View, where typically, 1 file is represented, pertaining to given fields shared with this single file, such as number of tracks in an album, or total duration of the album this track is a part of. |
|||
=== <span id="GroupCount">GroupCount(…)</span> === |
=== <span id="GroupCount">GroupCount(…)</span> === |
||
Line 66: | Line 68: | ||
=== <span id="GroupSummaryQuery">GroupSummaryQuery(…)</span> === |
=== <span id="GroupSummaryQuery">GroupSummaryQuery(…)</span> === |
||
: Globally summarises the |
: Globally summarises the {{monospace|Field}} entries for files that share a {{monospace|Match}} with the current file. |
||
{{function description box |
{{function description box |
||
Line 81: | Line 83: | ||
{{argument table row|1|Supresses labels such as Avg or Total}} |
{{argument table row|1|Supresses labels such as Avg or Total}} |
||
}} |
}} |
||
<u>'''Notes:'''</u><br> |
|||
: * GroupSummaryQuery is special because it returns counts from the entire library, not just the currently filtered subset. |
|||
: * GroupSummaryQuery can only do what it does by using a cache of the library data. The cache is rebuilt every 60 seconds, so, when testing these, changes may not be immediately noticeable. |
|||
: * GroupSummaryQuery uses field names only, the usual square brackets should not be used. |
|||
: * Special characters are required to be escaped, otherwise, they will break the expression. For example, use Album Artist /(Auto/) not Album Artist (Auto) |
|||
| examples= |
| examples= |
Revision as of 10:34, 19 July 2020
- This article is a incomplete. It is missing detail about critical functions, or contains a number of red links. You can help the JRiver Wiki by expanding it.
- See also: Expression Language and Function Index
The expression language is largely used to evaluate one file at a time. The grammar implies that something like Field(Artist) should get the Artist value for the current file being evaluated. Grouping Functions are a special class of functions that operate on a group of files, instead of on individual files. A simple example would be a function to count the number of artists in the current group.
Grouping Functions may only be useful in relevant areas where Media Center displays groups of files (most notably in Categories and the Tag Action Window), and not to individual file listings, such as an expression column in a File Details View, where they can be used, but will not be all that useful.
The GroupCountQuery() and GroupSummaryQuery() functions detailed below are special functions that work globally, returning results from the entire library, regardless of Media Type, or any other filters currently in action. This makes them especially useful for presenting information in Theater View, where typically, 1 file is represented, pertaining to given fields shared with this single file, such as number of tracks in an album, or total duration of the album this track is a part of.
GroupCount(…)
- Counts the members of a specified group (in a category or field).
Description | GroupCount(field)
GroupCount() can be used to count the members of a group of files. |
---|---|
Examples | Example Threads: |
GroupCountQuery(…)
- Globally counts the number of different Field 2 entries for files that share Field 1 with the current file.
Description | GroupCountQuery(field 1, Field 2)
Notes:
|
---|---|
Examples | [album artist (auto), 1] (GroupCountQuery(album artist /(auto/), album) albums)
GroupCountQuery(album artist /(auto/);Camera, album)
|
GroupSummary(…)
- Summarises the members of a specified group (in a category or field).
Description | GroupSummary(field)
Smartly summarizes the members of a specified group (mode, mean, min, max, etc as is most logical for that grouping). |
---|---|
Examples | Example Threads: |
GroupSummaryQuery(…)
- Globally summarises the Field entries for files that share a Match with the current file.
Description | GroupSummaryQuery(Match, Field, Mode)
Available mode values:
Notes:
| ||||
---|---|---|---|---|---|
Examples | GroupSummaryQuery()
GroupSummaryQuery()
|