View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003249 | Composr | catalogues | public | 2017-04-25 01:18 | 2017-04-26 00:01 |
Reporter | Adam Edington | Assigned To | Chris Graham | ||
Severity | Feature-request | ||||
Status | closed | Resolution | no change required | ||
Product Version | |||||
Fixed in Version | |||||
Summary | 0003249: Sort by name (ascending) | ||||
Description | Shouldn't this be like:- Sentinel Judge Raziel | ||||
Tags | No tags attached. | ||||
Time estimation (hours) | |||||
Sponsorship open | |||||
related to | 0003252 | non-assigned | The terms 'ascending' and 'descending' are not user-friendly |
|
|
|
Ascending means A-Z. I wonder if you are either saying "Judge" should be skipped because it's a title. If so, that's too specific, we're not going to know the word Judge specifically. Or you may be thinking it should know they are in a "Forename Surname" format and it should sort by Surname. However there's no system for this, and you could just use separate fields. |
|
I always believed ascending meant bottom to top (so like Z-A) and descending meant top to bottom (A-Z). Maybe it's different in code. |
|
Haha, I see what you mean (ascending a mountain), but no you're mistaken here. http://www.mathsteacher.com.au/year7/ch02_power/06_asc/asc.htm I'll add a new issue, given that it's confusing. I doubt it'll get handled anytime soon though. |
|
I was thinking alphabetically not numerically, but yeah I suck at maths so thanks for the lesson. |
|
It's using the term in the same way (i.e. lowerer end toward upper end), regardless of data type. |
|
Wouldn't different terms lead to the same issue (ie, up and down) if the order is still the opposite of what you would expect from alphabetic sorting? Maybe standard catalogues should use alphabetic ordering and I assume the numeric stuff is for the ecommerce ones so maybe sort that numerically by default. I think changing the terms wouldn't solve the issue, but then again I don't understand it fully from a coding point of view. |
|
Read how I specified the other issue. I didn't say "up" or "down". |
|
No I was saying up and down as an example of different terms for ascending and descending. Changing the terms doesn't solve the confusing if the ordering is the same. Anyhow, it's not the biggest issue in the world so I shall let you get on with the more important stuff :) |
|
Yeah, my issue talks about changing it to natural language like 'alphabetical'. So we wouldn't be switched out ascending/descending to some other terms, we'd be introducing per-data-type terms that read much more naturally. |
|
Ahh okay, yes that does make sense. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-04-25 01:18 | Adam Edington | New Issue | |
2017-04-25 01:18 | Adam Edington | File Added: ascending.png | |
2017-04-25 11:20 | Chris Graham | Note Added: 0005021 | |
2017-04-25 11:20 | Chris Graham | Status | non-assigned => closed |
2017-04-25 11:20 | Chris Graham | Assigned To | => Chris Graham |
2017-04-25 11:20 | Chris Graham | Resolution | open => no change required |
2017-04-25 23:22 | Adam Edington | Note Added: 0005022 | |
2017-04-25 23:24 | Chris Graham | Note Added: 0005023 | |
2017-04-25 23:26 | Chris Graham | Relationship added | related to 0003252 |
2017-04-25 23:29 | Adam Edington | Note Added: 0005024 | |
2017-04-25 23:30 | Chris Graham | Note Added: 0005025 | |
2017-04-25 23:40 | Adam Edington | Note Added: 0005026 | |
2017-04-25 23:43 | Chris Graham | Note Added: 0005027 | |
2017-04-25 23:52 | Adam Edington | Note Added: 0005028 | |
2017-04-25 23:56 | Chris Graham | Note Added: 0005029 | |
2017-04-26 00:01 | Adam Edington | Note Added: 0005030 |