Web Client: Offline working location dropdown not sorted

Bug #1724019 reported by Terran McCanna
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.4
Fix Released
Undecided
Unassigned

Bug Description

The working location dropdown list of shortnames isn't sorted alphabetically at the system level or by branch within each system grouping. Being in a system with 54 going on 55 systems, that makes it extremely difficult to navigate.

Joan Kranich (jkranich)
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Joan Kranich (jkranich) wrote :

Evergreen 3.0.6

We find the working location dropdown list is not sorted in some sections and also some locations are missing from the list. We have over 300 org units.

Revision history for this message
Terran McCanna (tmccanna) wrote :

Still not sorted alphabetically in 3.1.

Changed in evergreen:
importance: Undecided → Medium
tags: added: sorting
Andrea Neiman (aneiman)
tags: removed: standalone
Mike Risher (mrisher)
Changed in evergreen:
assignee: nobody → Mike Risher (mrisher)
Revision history for this message
Mike Risher (mrisher) wrote :
Changed in evergreen:
assignee: Mike Risher (mrisher) → nobody
tags: added: pullrequest
Revision history for this message
Dawn Dale (ddale) wrote :

I have tested this code and consent to signing off on it with my name, Dawn Dale and my email address, <email address hidden>.

Revision history for this message
Terran McCanna (tmccanna) wrote :

Although it does alphabetize now, it has lost the hierarchy - see attached screenshot where you can see, for example, that CONS is down in the middle. Removing the pullrequest.

Revision history for this message
Terran McCanna (tmccanna) wrote :
tags: removed: pullrequest
Revision history for this message
Mike Risher (mrisher) wrote :

This was done intentionally because my understanding is that was what was being requested. Could you help me understand the desired behavior?

Revision history for this message
Terran McCanna (tmccanna) wrote :

It should have the same hierarchy that the org units have - consortium level first, systems alphabetical under that, branches alphabetical within their systems.

The way it is done on the "Register a New Workstation" screen is good (hierarchy.jpg).

The way it is done on the patron edit screen is even better because it also grays out the consortium and system levels and only allows branches to be selected (hierarchy2.jpg).

Revision history for this message
Terran McCanna (tmccanna) wrote :
Revision history for this message
Terran McCanna (tmccanna) wrote :

Here is what it currently looks like in production - the hierarchy is there, but the systems aren't in order and the branches within each system aren't in order, so it's difficult to find the one you are looking for.

Revision history for this message
Kyle Huckins (khuckins) wrote :

Noting with relation to hierarchy2 - the Angular Org Selector doesn't currently support graying out of consortium/system-level orgs, but the functionality to do so will be present with bug 1863168

Changed in evergreen:
milestone: none → 3.5-alpha
Revision history for this message
Mike Risher (mrisher) wrote :

I re-did this work to preserve the org hierarchy when alphabetizing. Here's the branch:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrisher/lp1724019-offline-location-dropdown-orgs

tags: added: pullrequest
Revision history for this message
Terran McCanna (tmccanna) wrote :
tags: added: signedoff
Michele Morgan (mmorgan)
Changed in evergreen:
milestone: 3.5-beta → 3.5.0
Changed in evergreen:
milestone: 3.5.0 → 3.5.1
Revision history for this message
Jane Sandberg (sandbergja) wrote :

Thanks, Mike. The patch works for me. However, I don't think we should have two separate sorting methods depending on whether or not the org selector is in the offline client or not. I haven't tried it yet, but it seems like we could make a few changes to egEnv's (or maybe the lovefield service's) logic to use the existing sort_aou for offline calls as well. https://github.com/evergreen-library-system/Evergreen/blob/7c3cdbbd140865e07d08952422c82605ac8c5676/Open-ILS/web/js/ui/default/staff/services/env.js#L183

That way, the org selector could just make the assumption that it is getting correctly sorted data.

Thoughts?

Revision history for this message
Mike Risher (mrisher) wrote :

Thanks for pointing out that sort_aou function, Jane. I agree we don't want to repeat code if we can help it. With some help, I changed the approach so that it's now using that function. Branch here:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mrisher/lp1724019-offline-org-alphabetize

tags: removed: signedoff
Changed in evergreen:
milestone: 3.5.1 → 3.5.2
Revision history for this message
Bill Erickson (berick) wrote :

Issue and fix confirmed, now with shared sort. Merged to 3.4 and up. Thanks, all.

Changed in evergreen:
assignee: nobody → Bill Erickson (berick)
Bill Erickson (berick)
Changed in evergreen:
assignee: Bill Erickson (berick) → nobody
status: Confirmed → Fix Committed
tags: added: signedoff
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.