While talking in the weekly meeting about hengsin proposed to use usage statistics for the sort list. We agreed that both approaches are useful for different purposes and should be implemented. Because of limited time we decided to close like it is (shortlist from an extra column "isShortList" in the given table) and to open a new issue for the usage statics based shortlist.
I believe we could use parts of the infrastructure of IDEMPIERE-90.
We need a way to save usage statistics. IMO we need a new table for that. And I would propose a formula that allows for "aging" so that an entry that I used very often last year will leave the list faster if I use it much lesser this year - even if the total usage number is still very high.
I think it should be configurable how many items are in the usage statistics shortlist. We need a numeric column for this in the column definition or in the field definition (or in the table definition of the references table). Personally I prefer this setting in the field definition. This allows to switch the shortlist on or off depending on the operational purpose. On the other hand this may lead to many fields not using the shortlist because of bad configuration. This speaks for the setting in the column definition.
We could switch this functionality off by setting it to "0" items.
Over-aged issue. Set as a Potential-Idea.