More > JRiver Media Center 27 for Windows

Change a View to sort on Composer Surname

<< < (4/4)

glynor:
I was assuming leezer was asking for something automatic, in field containing a mixture of English-style and Japanese/Korean-style names. Hence, how?

DJLegba:

--- Quote from: glynor on November 24, 2020, 07:03:33 pm ---I was assuming leezer was asking for something automatic, in field containing a mixture of English-style and Japanese/Korean-style names. Hence, how?

--- End quote ---

The easiest and best way is to edit the composer tag. A little more work, but it's always right.

leezer3:

--- Quote from: zybex on November 24, 2020, 04:01:15 pm ---Well... you could create a sort column that sorts similar/reversed names together. You can then use it directly to Sort a view, or to fix the files with similar/reversed values so that they contain the actual same value.

Something like this - it sorts the names+surnames alphabetically, so that "Carmen Miranda" sorts the same as "Miranda Carmen":

--- Code: ---listsort(listclean(replace([composer],/ ,;),3))
--- End code ---

You can improve it to cleanup "dirtier" names so that it handles names with commas, parenthesis, articles, etc:

--- Code: ---listsort(listclean(replace(RemoveCharacters(clean([composer],2),/(/)/,.-),/ ,;),3))
--- End code ---

These split the names into words and then sorts the words alphabetically - "Wolfgang Amadeus Mozart" becomes "Amadeus;Mozart;Wolfgang". This is perhaps more useful to group related files together to then fix their tagging, since the actual order we get is not exactly by name or surname.

--- End quote ---

Now that's actually genius, splitting into the component parts for browsing- Never thought of that.
Works very well for spotting translation errors / spelling differences too :)

Not quite automatic yet, but I'll think about that a bit more.

AndrewFG:
Hi glynor,

I am finally getting round to implementing the solution you proposed in this thread. I got side-tracked on other things, so sorry for the delay, but nevertheless many thanks for your detailed and knowledgeable advice.

Basically it all seems to work as you suggest. However it turns out that [Composer] is indeed a list-type field as you suspected in the post below, so it does indeed need further work.


--- Quote from: glynor on November 23, 2020, 11:00:24 pm ---I left out: I can't remember if [Composer] is a list-type field, like [Artist] and [Actors]. But if so, and you need to handle that, this is possible too with a few modifications to the Expression in [Composer (Sort)]. Swap() does properly handle list-type data, so it is primarily adding the data type to the expression, but there might be other things to consider.

--- End quote ---

You say "Swap() does properly handle list-type data, so it is primarily adding the data type to the expression" but I am not sure what you mean by "adding the data type". Could you please explain that further.

---

EDIT: after playing around a bit, I figured out the solution to the "data type" question. The correct expression for the Composer Surname (aka Composer Sort) Field Expression is:


--- Code: ---If([Composer Surname Override],[Composer],Swap([Composer]))&datatype=[list]

--- End code ---

glynor:
Sorry I was so delayed. This is my busy season at work (basically the whole summer) and I'm also in the process of completely rebuilding my network and servers because my firewall machine (which is literally an AMD Athlon64 X2 that has been running nearly constantly since it was brand-new) is finally starting to show its age and needs to be replaced.

My daughter and I are assembling my fancy new rack today. A four poster, with doors, replacing my old 2-poster AV-style shallow rack.

I think you got it?

Navigation

[0] Message Index

[*] Previous page

Go to full version