Menu

#887 Sorting overwrites "Default sort criteria" preference

open
nobody
core (92)
5
2013-12-30
2010-05-31
Anonymous
No

Sorting the database using the main interface overwrites the default sorting criteria specified in the preferences. This behavior is frustrating when quickly sorting columns for an overview of the database.

The pre-2.6 behavior of JabRef was definitely much better since it was possible to specify a custom database sort & save order (not just author/editor/year) that is independent of the current sort status of the main interface.

I hope the pre-2.6 behavior is restored in one of the next releases of JabRef.

Discussion

  • Morten Omholt Alver

    One man's bug is another man's feature :) Many applications will remember sorting order, more similarly to the way JabRef 2.6 works. Perhaps this can be made configurable in the next version.

     
  • Olaf Lenz

    Olaf Lenz - 2013-08-06

    I think the main trouble is that there is no way to specify the save order anymore, except to sort by author name or by the current sort order that changes when you click on a column. Before 2.7, I was using the "Default sort criteria" to specify the order of the entries in the file - independent of the current sort order. Now this is not possible anymore.
    As it is used currently, the term "Default" is actually a misnomer, it is merely the current sort order.

    Also, if this sort order is stored in the preferences, this means that the sort order is stored per session, and not per BibTeX file, which would probably make more sense.

    So I think to solve this issue perfectly, one should have two distinct sort orders, the "saving order", and the "current order". And maybe also an "export order". It is my holidays soon, maybe I find some time to put some work into this.

     
  • Olaf Lenz

    Olaf Lenz - 2013-12-30

    I have just created a "merge request" https://sourceforge.net/p/jabref/code/merge-requests/4/

    My modifications add the possibility to specify the sort order of the entries when saving or exporting, independent of the table sort order. This should fix the bug.

     

Log in to post a comment.

MongoDB Logo MongoDB