Proper alphanumerical sorting on tag browser

[culytera]

Hello! I made a template function to group word counts by certain thresholds and used it for a custom column where the results are shown on the tag browser, but they're not being sorted properly on the tag browser. It seems to only see the first digit on 5000, 10000, etc. The custom columns are already sorted by text. Same case for tags with numbers though I'm not sure if that's the intended behavior.

This is the template function with the template name getWordCountGroup.

program:
	getWordCount = field('#ao3_words');
	wordCount = re(getWordCount, '[,]', '');
	first_non_empty(
		cmp(wordCount, 5001,  'Less than 5000', '', ''),
		cmp(wordCount, 10001, 'Less than 10000', '', ''),
		cmp(wordCount, 20001, 'Less than 20000', '', ''),
		cmp(wordCount, 40001, 'Less than 40000', '', ''),
		cmp(wordCount, 80001, 'Less than 80000', '', ''),
		'Over 80000'
);

[kovidgoyal]

I doubt the tag browser sorting recognizes numbers inside text fields when sorting. It would be a significant performance hit.

[culytera]

One workaround I can do is adding a space before 5000 so it gets placed at the top of the list.

[ownedbycats]

Originally Posted by kovidgoyal

I doubt the tag browser sorting recognizes numbers inside text fields when sorting. It would be a significant performance hit.

Oddly enough, my purchase cost column does.



Template:

Spoiler:

program:
	switch_if(
		$$#purchasecost == 'none', '',
		$$#purchasecost ==# '00.00', '$0.00',
		$$#purchasecost <=# '00.99', '$0.01 - $0.99',
		$$#purchasecost <=# '04.99', '$1.00 - $4.99',
		$$#purchasecost <=# '10.00', '$5.00 - $9.99',
		$$#purchasecost <=# '15.00', '$10.00 - $14.99',
		$$#purchasecost <=# '15.00', '$10.00 - $14.99',
		$$#purchasecost <=# '20.00', '$15.00 - $19.99',
		$$#purchasecost <=# '30.00', '$20.00 - $29.99',
		'$30.00 and up' 
	)

[theducks]

Originally Posted by ownedbycats

Oddly enough, my purchase cost column does.

Attachment 199742

Template:

Spoiler:

program:
	switch_if(
		$$#purchasecost == 'none', '',
		$$#purchasecost ==# '00.00', '$0.00',
		$$#purchasecost <=# '00.99', '$0.01 - $0.99',
		$$#purchasecost <=# '04.99', '$1.00 - $4.99',
		$$#purchasecost <=# '10.00', '$5.00 - $9.99',
		$$#purchasecost <=# '15.00', '$10.00 - $14.99',
		$$#purchasecost <=# '15.00', '$10.00 - $14.99',
		$$#purchasecost <=# '20.00', '$15.00 - $19.99',
		$$#purchasecost <=# '30.00', '$20.00 - $29.99',
		'$30.00 and up' 
	)

Because that is a Numeric field and the other is Alpha-numeric. the sort/alignment is natively different, which is why we pad series index in templates

[ownedbycats]

Originally Posted by theducks

Because that is a Numeric field and the other is Alpha-numeric. the sort/alignment is natively different, which is why we pad series index in templates

It's a composite column, sorted by text.

[theducks]

Originally Posted by ownedbycats

It's a composite column, sorted by text.

That is an Alpha-numeric sort (most characters on a keyboard)
Numeric has 2 general modes: Integer and Floating Point
Integer has no exponent or decimal, although it can be signed -32,767

[culytera]

I still don't understand the difference between mine and ownedbycats'. I've even changed the template to use switchif(). Same result for either composite column type.

The word count column the template is taking values from is an Integer type with the format {:,d}

Spoiler:

program:
	switch_if(
		$$#ao3_words <=# '5000',  '0 - 5000',
		$$#ao3_words <=# '10000', '5001 - 10000',
		$$#ao3_words <=# '20000', '10001 - 20000',
		$$#ao3_words <=# '40000', '20001 - 40000',
		$$#ao3_words <=# '80000', '40001 - 80000',
		'80000+' 
	)

[chaley]

Is this option checked in Preferences / Behavior?

[culytera]

Originally Posted by chaley

Is this option checked in Preferences / Behavior?

It wasn't, didn't even notice that was off. That fixed my issues. It doesn't properly sort the ones that started with a number as mentioned on the option, but I don't mind. I can just use the other style anyway for the composite column. Thanks!

[ownedbycats]

I actually looked for a setting like that... but in tweaks. Thanks for clearing up the mystery!