Display other asset values in the Ordering and Grouping tab of the configuration and also relax the requirements set forth in AssetEntryQuery.checkOrderByCol.

• Type: Feature Request
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Asset Framework
• Labels:
  • ee-nf

ISSUE
In the AssetEntryQuery class, the order columns are set manually, hard coded, instead of being picked up from a properties file, so the checkOrderByCol method doesn't get the values sent not null values) and returns modified date as the default ordering field, resulting in their field being ignored. This design makes it very difficult to customize the ordering, and even more if you want to use advanced features such as sorting by distance (using Elasticsearch and Hits) with this AssetEntryQuery approach.
FEATURE REQUEST
Display other asset values in the Ordering and Grouping tab of the configuration and also relax the requirements set forth in AssetEntryQuery.checkOrderByCol.

Please consider also every possible Sort type, as defined in the Sort class; the GEO_DISTANCE_TYPE does not appeared used within the portal, while it should be possible to use it as defined in Sort.java, GeoDistanceSort and in the ElasticsearchIndexSearcher.