case insensitive sorts throughout

Summary

All the alphabetical sorts (in drop downs, indices, exports, and reports) should be in natural alphabetical order (aka case insensitive alphabetical order)

Why?

It's the human way of doing things

Details

The 'natural' and computer-based alphabetizing are not the same --- so there are a bunch of surnames that would be out of order, for example -- (the ones beginning with de or van for example ). As well, if someone enters a new item in lowercase, it would be out of order in various dropdowns

Survey and repair all the sorts.

Please keep an eye out for sorts that are still in order-added order -- call those out, but we're pretty sure they should be natural alpha as well.

Consider adding shared helpers (if it makes sense).

Note: This will require communication to the users if any exports are involved.

Criteria for completion

• all sorts are in human alphabetical order
• Tests to support
• May need some light work on the user guide to point out the new orders

Note:

Double-check we don't already have exactly this one.

Start by surveying the dropdowns, indices, exports, and reports named in the issue, and check whether an identical issue already exists. Identify sorts that are case-sensitive or order-added, then review the existing test coverage before making changes. Done means all applicable sorts have tests, exports and the user guide reflect any changed ordering, and remaining order-added cases are documented.