Skip to content

Feature request: Natural sorting for product attributes #1158

Closed

Description

@stefanmuellerdo

Feature Request: Natural Sorting for Product Attributes

Summary:
Implement natural sorting for product attributes in Smartstore to ensure a more intuitive and user-friendly automatic standard sorting order for alphanumeric strings. without having to set up the sort order manually in the attribute details.

https://en.wikipedia.org/wiki/Natural_sort_order

autosorted

Description:
Currently, product attributes in Smartstore are sorted using standard lexicographical order.

This can lead to unintuitive sorting results, especially when dealing with strings containing numbers.

For instance, the current sorting might order "1", "11", "2", which is not ideal for user experience.

Natural sorting would arrange these values as "1", "2", "11", reflecting a more logical numerical progression.

Benefits:

  • Improved user experience: Users will find it easier to navigate and find items with correctly ordered attributes.
  • Enhanced data presentation: More intuitive sorting will make product listings and attribute filtering more readable and logical.
  • Competitive advantage: This feature can be highlighted as a user-centric enhancement, setting Smartstore apart from competitors.

Natural Sorting is standard in modern OS, like MacOS file lists. https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemDetails/FileSystemDetails.html

Has been reported by a store operator & ERP partner.

Activity

  1. added this to the 5.2.0 milestone on Aug 7, 2024
  2. stefanmuellerdo commented on Aug 8, 2024

    @stefanmuellerdo
    Author

    thanks !!!

  3. changed the title [-]Feature Request: Natural Sorting for Product Attributes[/-] [+]Feature request: Natural sorting for product attributes[/+] on Aug 8, 2024
  4. mgesing commented on Aug 19, 2024

    @mgesing
    Contributor

    Some notes. NATURAL_SORT_KEY is not supported by T-SQL. Only to be used in certain cases for materialized data. Should be avoided on database side for performance reasons. Link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions