Sortable search result for 4.0 (by relevance, by date, etc.)

[eaquigley]

---

Author Name: Philip Durbin (@pdurbin)
Original Redmine Issue: 3482, https://redmine.hmdc.harvard.edu/issues/3482
Original Date: 2014-02-03
Original Assignee: Kevin Condon

---

Need an option for a user to be able to sort results by Global ID, Title, Production Date, Relevance. Currently supported in 3.6, needs to be in 4.0.

For 4.0, sortable by:
Title
Release Date
Relevance

*Need to confirm Global ID and make sure there aren't others (EQ 3/11/14)

"Ability to order results by type, alphabetical, or by release/published date in results table." -- https://trello.com/c/jmry3BJR/28-browse-dataverses

Per Mike, we plan to put a "Sort" button to the right of pagination widget. See http://labs.adsabs.harvard.edu/adsabs/search/?q=* for what the Sort button might look like.

[eaquigley]

---

Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-03-13T17:10:00Z

---

As of commit 2c01126 I'm done with an initial implementation of sorting search results with Solr. The front end design was inspired by http://ux.stackexchange.com/questions/23169/showing-asc-desc-icons-intuitively/23272#23272 where you can see on the button which sort you are on. Unfortunately, "Sort by" is on the wrong side in Firefox (but not Chrome). Mike will fix this and do some other clean up so I'm passing this ticket to him.

Goal:
!https://redmine.hmdc.harvard.edu/attachments/download/719/goal.png!

Actual:
!https://redmine.hmdc.harvard.edu/attachments/download/720/actual.png!

I should note that we want to sort by "Release Date" but that concept doesn't exist in the system yet. I just added a ticket for this so we can have that go through QA separately: #3701.

[eaquigley]

---

Original Redmine Comment
Author Name: Mike Heppler (@mheppler)
Original Date: 2014-03-13T17:43:28Z

---

Cleaned up the layout of the sort button on the search include. Added a render to the relevance option, so it's hidden on browse, but it isn't working. Passing to Phil to fix.

[eaquigley]

---

Original Redmine Comment
Author Name: Mike Heppler (@mheppler)
Original Date: 2014-03-13T17:47:27Z

---

Sorry. Fixed that. Phil should probably still have this ticket for release date, or maybe that gets it's own ticket for when that feature is ready...?

[eaquigley]

---

Original Redmine Comment
Author Name: Philip Durbin (@pdurbin)
Original Date: 2014-03-13T19:43:08Z

---

"Kangaroos" was being sorted before "2Legit2Quit" in an A-Z sort, which made no sense. I fixed this with a change to the Solr schema.xml in commit 6248b03.

The API and the GUI should show the same results. Here's the "before" and "after" from the API:

Before:

murphy:dataverse_temp pdurbin$ curl -s 'http://localhost:8080/api/search?q=*&fq=subtree_ss:"/sortingishard"&sort=name_sort&order=asc' | jq '.itemsJson[] | {name_sort}'
{
  "name_sort": "1ForTheMoney"
}
{
  "name_sort": "Kangaroos"
}
{
  "name_sort": "2Legit2Quit"
}
{
  "name_sort": "Lemmings"
}

After:

murphy:dataverse_temp pdurbin$ curl -s 'http://localhost:8080/api/search?q=*&fq=subtree_ss:"/sortingishard"&sort=name_sort&order=asc' | jq '.itemsJson[] | {name_sort}'
{
  "name_sort": "1ForTheMoney"
}
{
  "name_sort": "2Legit2Quit"
}
{
  "name_sort": "Kangaroos"
}
{
  "name_sort": "Lemmings"
}

Passing to QA. After dropping the new schema.xml into place you'll need to "index all".

I think sort is ready but please note that sorting by "release date" will be handled in a future ticket: #3701

I know the test search rules ticket is separate (#3695) but I'll go ahead and paste the latest rules as of this writing:

/**
 * These are our decided-upon search/browse rules, the way we expect
 * users to search/browse and how we want the app behave:
 *
 * 1. When a user is browsing (i.e. hasn't entered a search term) we
 * only show dataverses and datasets. Files are hidden. See
 * https://redmine.hmdc.harvard.edu/issues/3573
 *
 * 2. A search is always brand new. Don't keep around old facets that
 * were selected. Show page 1 of results. Make the results bookmarkable:
 * https://redmine.hmdc.harvard.edu/issues/3664
 *
 * 3. When you add or remove a facet, you should always go to page 1 of
 * search results. Search terms should be preserved. Sorting should be
 * preserved.
 *
 * 4. After search terms have been entered and facets have been
 * selected, we expect users to (optionally) page through search results
 * and as they do so we will preserve the state of their search terms,
 * their facet selections, and their sorting.
 *
 * 5. Someday the default sort order for browse mode will be by "release
 * date" (newest first) but that functionality is not yet available in
 * the system ( see https://redmine.hmdc.harvard.edu/issues/3628 and
 * https://redmine.hmdc.harvard.edu/issues/3629 ) so for now the default
 * sort order for browse mode will by alphabetical (sort by name,
 * ascending). The default sort order for search mode will be by
 * relevance. (We only offer ascending ordering for relevance since
 * descending order is unlikely to be useful.) When you sort, facet
 * selections and what page you are on should be preserved.
 *
 */

[eaquigley]

---

Original Redmine Comment
Author Name: Kevin Condon (@kcondon)
Original Date: 2014-04-02T18:12:52Z

---

Tested on 4/2

Basic alpha sort works, release date does something but it is not finalized and there is a separate ticket. It does not yet seem honor newest/oldest in either datasets or dataverses, either by create or release so I am leaving that alone until that ticket comes to QA

Closing ticket, basic feature is in place, needs completing.