some columns are not sortable in the web staff client
Bug #1437104 reported by
Sally Fortin
This bug affects 27 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Many columns are not sortable in the web client. The patron search screen has some sortable columns, but there are other, unsortable ones that people may want to sort by (e.g. patron id, home library). The item status, checkin, and holds screens have no sorting. One area of particular interest is sorting columns in the holds pull list.
description: | updated |
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Stephen (smoss-e) |
Changed in evergreen: | |
milestone: | none → 2.next |
tags: | added: webstaffprodcirc |
Changed in evergreen: | |
assignee: | Stephen (smoss-e) → nobody |
Changed in evergreen: | |
importance: | Undecided → Medium |
Changed in evergreen: | |
assignee: | nobody → Cesar V (cesardv) |
Changed in evergreen: | |
assignee: | Cesar V (cesardv) → nobody |
tags: | added: webstaffcolumns |
tags: | removed: webstaffclient |
tags: |
added: sorting removed: webstaffprodcirc |
Changed in evergreen: | |
status: | Confirmed → Won't Fix |
milestone: | 3.next → none |
To post a comment you must log in.
Regarding the holds pull list, a while back I started a branch to have the browser client start using the IDL-based holds pull list. With this, the holds pull list will be (server-side) sortable. I don't have set plans to dust this off at the moment, but want to list it as a possible solution.
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ browser- staff-pull- list-from- idl
Other interfaces, which are not PCRUD based, like patron search, are a little more complicated. They API that delivers the data to the grid may or may not offer sorting. In the case of patron search, it offers partial sorting (which is why some columns don't let you sort). Each such grid and its backing API will have to be addressed individually to provide server-side sorting on every column. Doing this globally is a big task, so it's probably best to start on the interfaces that need it the most.
We just have to avoid situations where clicking a column forces the grid to retrieve every row so it can be sorted locally, which the XUL client has to do in some interfaces. This is how we get pages that freeze.