Bug 14005 - Fix wording of previousIssuesDefaultSortOrder and todaysIssuesDefaultSortOrder
Summary: Fix wording of previousIssuesDefaultSortOrder and todaysIssuesDefaultSortOrder
Status: In Discussion
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low trivial (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-16 14:36 UTC by Kyle M Hall
Modified: 2016-05-05 19:26 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: String patch
Bot Control: ---
When did the bot last check this:
Who signed the patch off:
Text to go in the release notes:


Attachments
Bug 14005 - Fix working of previousIssuesDefaultSortOrder and todaysIssuesDefaultSortOrder (1.93 KB, patch)
2015-04-16 14:37 UTC, Kyle M Hall
Details | Diff | Splinter Review
Bug 14005 - Fix wording of previousIssuesDefaultSortOrder and todaysIssuesDefaultSortOrder (1.93 KB, patch)
2015-04-16 14:38 UTC, Kyle M Hall
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2015-04-16 14:36:01 UTC
It appears that many librarians find the language for the default sort order system preferences ambiguous and confusing.
Comment 1 Kyle M Hall 2015-04-16 14:37:43 UTC Comment hidden (obsolete)
Comment 2 Kyle M Hall 2015-04-16 14:38:21 UTC
Created attachment 37963 [details] [review]
Bug 14005 - Fix wording of previousIssuesDefaultSortOrder and todaysIssuesDefaultSortOrder

It appears that many librarians find the language for the default sort
order system preferences ambiguous and confusing.

Test Plan:
1) Apply this patch
2) View the system preferences previousIssuesDefaultSortOrder and todaysIssuesDefaultSortOrder
3) Verify the new language is sensible and describes each sort order correctly
Comment 3 Andreas Hedström Mace 2015-04-16 20:00:10 UTC
Unfortunately I think that the new language used is more confusing. Especially previousIssuesDefaultSortOrder. For me "due most recently" and "due earliest" is pretty much the same thing. Also todaysIssuesDefaultSortOrder's second option states to sort from "first item checked out today to latest checked item out" due date. Shouldn't it read "...latest checked out item"?
Comment 4 Liz Rea 2015-10-06 01:57:57 UTC
I am pretty sure that the  todaysIssuesDefaultSortOrder preference is actually reversed in meaning. 

Latest to earliest (according to the preference)
Today's checkouts
10/06/2015 14:29	
10/06/2015 14:30	
10/06/2015 14:36	
10/06/2015 14:39	

Earliest to latest
10/06/2015 14:39	
10/06/2015 14:36	
10/06/2015 14:30	
10/06/2015 14:29

This doesn't seem right to me?
Comment 5 Kyle M Hall 2015-10-06 11:36:33 UTC
(In reply to Liz Rea from comment #4)
> I am pretty sure that the  todaysIssuesDefaultSortOrder preference is
> actually reversed in meaning. 
> 
> Latest to earliest (according to the preference)
> Today's checkouts
> 10/06/2015 14:29	
> 10/06/2015 14:30	
> 10/06/2015 14:36	
> 10/06/2015 14:39	
> 
> Earliest to latest
> 10/06/2015 14:39	
> 10/06/2015 14:36	
> 10/06/2015 14:30	
> 10/06/2015 14:29
> 
> This doesn't seem right to me?

It's the ambiguity of the terms. It's like looking at that image that's either a face or a lamp!

I suggested with do with "Most recently issued to least recently issued" and "Least recently issued to most recently issued". What do you think?