Bug #5643

Something wonky with sort order of "most recent"

Added by Tim Hutchinson over 8 years ago. Updated over 8 years ago.

Status:VerifiedStart date:09/21/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:


Category:Search / Browse
Target version:Release 2.0.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:


There seems to be something wrong with the sort order on browse screens when the sort order is set to most recent.

There doesn't seem to be any correlation between this order and the order on the description updates page, and new/updated descriptions disappear into the void (though you can find them in unexpected spots when filtering to a repository with a workable number of descriptions, so they are apparently still on the list).

Here's a more systematic way to try to reproduce this.
- create a new repository, e.g. Test Repository
- create 11 descriptions, with title and repository (Test Repository), using titles like:
Test 1
Test 2
Test 3
etc. but in any case so that the order of entry is obvious
(Note: you could do fewer than 11 entries if you're able to look up the repository id from the backend, and therefore figure out the URL for the filtered description browse)
- navigate to the new repository page, then follow the link to "browse 11 holdings"
- make sure "most recent" is the sort order
- in my case, the order (top to bottom) was:
Test 1
Test 5
Test 10
Test 2
Test 6
Test 11
Test 3
Test 7
Test 8
Test 4
Test 9
- but Browse Newest Additions was correct (11 to 1)

Related issues

Related to Access to Memory (AtoM) - Bug #5599: Changing sort order on Authority records has no effect Verified 09/17/2013
Related to Access to Memory (AtoM) - Feature #5173: Improve default ElasticSearch alphabetic sort to better r... Verified 06/03/2013


#1 Updated by Tim Hutchinson over 8 years ago


I edited Test 1, and it ended up 3rd on the list.
Then I edited Test 2, and it ended up 6th on the list.
Instead of 2nd and 1st respectively, which is the case on Browse Newest Additions

#2 Updated by Dan Gillean over 8 years ago

  • Category set to Search / Browse
  • Assignee set to Jesús García Crespo
  • Target version set to Release 2.0.0

There are a couple issues that I have related to this one, which cover aspects of this behaviour already - but your testing notes are very thorough and useful, Tim, so for now I have left the duplicates in place and related. See #5173 and #5599.

#3 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from New to In progress
  • Assignee changed from Jesús García Crespo to José Raddaoui Marín

#4 Updated by José Raddaoui Marín over 8 years ago

Hi Tim,

This should be fixed now, but you'll need to rebuild the search index using:

php symfony search:populate


#5 Updated by Tim Hutchinson over 8 years ago

Thanks, José. Our developer/server admin is away for the next week so I won't have access to the new development version until after that. I trust Dan can do the QA, especially since #5599 basically reports the same symptoms.

#6 Updated by Dan Gillean over 8 years ago

  • Status changed from In progress to Verified

Any remaining issues with the sort have to do with the default alphabetic sorting in ElasticSearch - i.e., how accented letters are handled, how quotations are handled etc. Will open a new issue to consider revising ElasticSearch's defaults in another issue as this can be improved to better match user expectations for a "natural sort" order - but marking this verified, as the sort order now works.

Any record recently edited and saved will now show up at the top of the "Most recent" sort order. Users can change to alphabetic sort and back.

Also available in: Atom PDF