Items are incorrectly sorting when using the Sort By Publication date feature
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.7 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.8 |
Won't Fix
|
Medium
|
Unassigned | ||
2.9 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
When using "Sort by Publication Date" in the advanced search menu, items that have a date1 value of "||||" rather than an actual date are being sorted to the top of the list when sorting by newest first. At the very least, these should be moved to the back of the sort list since they do not have an actual date. It looks like if spaces are used instead, it does put it at the end but may still move to the front when sorting by oldest items first.
I believe Items without a proper pub date should be tacked on to the very end of a sort list. Whether it's newest first or oldest first, I would expect no-dates to either not show up, or show after all the items with dates have been sorted.
I've tested this in 2.7.
Steve
Changed in evergreen: | |
milestone: | none → 2.9-alpha |
Changed in evergreen: | |
milestone: | 2.9-alpha → 2.9-beta |
Changed in evergreen: | |
milestone: | 2.9-beta → 2.9.0 |
Changed in evergreen: | |
milestone: | 2.9.0 → 2.9.1 |
Changed in evergreen: | |
milestone: | 2.9.1 → 2.next |
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
assignee: | nobody → Jennifer Pringle (jpringle-u) |
Changed in evergreen: | |
milestone: | 2.next → 2.10-beta |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
This comes from a lack of stock configuration for normalizing the pubdate sorter. We also don't install the normalizers for date1 and date2, which is also addressed herein. The latter will help before, after, between, and during searches.
From the commit message:
We supply a normalizer function for making sure date-ish values are
always numeric (several, in fact) but we don't enable them by default
for appropriate fields. This does that.
Additionally, we allow NULL sorters so that the reingest of a "broken"
record will get fixed.
We avoid the need for a reingest to cover the sorter issue by removing
non-numeric pubdate sorters.
Branch coords: http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ miker/lp1470957 -allow- null-FF- sorter- via-normalizati on
Test plan
--------------
Sort a result containing date1 values that equal "||||" by date descending, and the "bad" values will be at the top. Apply patch and they'll be at the bottom as they should be.
No release notes, as this is a bug fix for pubdate sorting.