Configure case-sensitivity in sorting

[damnsamn]

Hey guys - we’ve encountered an issue with our site where sorting a collection by its name field via the REST API (GET /api/posts?limit=0&sort=name) is returning alphabetical sorting in unexpected ways, seeming to sort Capitals-first, where AZ precedes Aa, and Z precedes a.

Below are two screenshots where this is an issue:

1. NSO Group sorted above Narus - we’d expect it to be sorted alphabetically under Nodus Information Technology
2. Stylised names that start with lowercase such as iFLYTEK are sorted to the absolute bottom of the list, underneath all items written as proper nouns

It would be great if there were a way to configure payload’s sorting algorithm to sort in a way that is case-insensitive, or at least sorting alphabetical->casing rather than casing->alphabetical.

[hugoburguete]

I know this is half a year old but did you find an answer in the end? I am facing the same issue and it would be nice if we could have a case insensitive sort

[damnsamn]

No, we ended up just moving the sorting logic to the front-end. Maybe if you were to move this discussion into an actual issue it might receive some stronger attention?

[damnsamn]

I tested a few approaches and I think the ideal one until we figure out this feature for the core APIs would be to make an admin-hidden field such as sortValue that you can use for sorting, using a beforeChange hook you can populate it with the title lowercased with toLowerCase()

This was the response from one of the payload team members in a private slack channel though - this is probably a good interim solution

[hugoburguete]

Thanks.

Luckily I can make sure that when my collection value is saved, I am able to capitalize the name, so that will be my workaround. It would be good if we could create a custom sort (that doesn't involve adding a dummy field).