Bug #5599

Changing sort order on Authority records has no effect

Added by Dan Gillean about 7 years ago. Updated about 7 years ago.

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

0%

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

Description

1) Navigate to Browse > Authority records
2) Change sort order from Most recent to Alphabetic

Resulting error
Sort order is not changed

Expected result
Page reloads with Authority records in Alphabetic order

Related issues

Related to Access to Memory (AtoM) - Bug #5643: Something wonky with sort order of "most recent" Verified 09/21/2013
Related to Access to Memory (AtoM) - Feature #5173: Improve default ElasticSearch alphabetic sort to better r... Verified 06/03/2013

History

#1 Updated by Dan Gillean about 7 years ago

Additional notes

1) Create new authority record, define type as "Person"
2) Navigate to Browse > Authority records. Ensure that sort is by "Most recent"

Resulting error
New authority record does not appear on first (or last) page of results. In fact, without a dedicated search bar for authority records, I couldn't find my new record anywhere in the Browse page, as there are over a thousand pages.

Expected result
The newest authority record is shown as the first result when browsing authority records and sorting by "Most recent"

Also we really need that dedicated search bar back.

#2 Updated by José Raddaoui Marín about 7 years ago

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

#3 Updated by José Raddaoui Marín about 7 years ago

Hi Dan,

This should be fixed now. But we still have the same limitations that we have in the alphabetic sort for information objects (#5173).

Maybe we can close both and create a new one to tweak/improve how ElasticSearch alphabetic order works, and add it to the 2.1 target.

Regards.

#4 Updated by Dan Gillean about 7 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