Learn@UW - Sorting Classlist by Last (or First) Name May Not Use the Other to Resolve Ties

When sorting names in the Classlist by last names, it would seem that if there are duplicates of a last name, then the first name field should be used as a 'secondary' key to resolve ties. Likewise, when sorting by first name, the last name field should be used to resolve ties.

When sorting names in the Classlist by last names, it would seem that if there are duplicates of a last name, then the first name field should be used as a 'secondary' key to resolve ties. Likewise, when sorting by first name, the last name field should be used to resolve ties.

This is the case if the last names are sorted in ascending order (A-Z) but not descending order (Z-A): first names for a common last name are sorted in ascending order. Likewise, this is also the case if the first names are sorted in ascending order (A-Z) but not descending order (Z-A): last names for a common last name are sorted in ascending order.

This is a known issue.




Keywords:brightspace learn@uw learnuw d2l desire2learn known issue Classlist sort name tie ascending descending order   Doc ID:4426
Owner:Joan W.Group:Learn@UW Utility
Created:2006-01-24 19:00 CDTUpdated:2016-05-24 14:31 CDT
Sites:DoIT Help Desk, DoIT Tech Store, Learn@UW Madison, Learn@UW Utility
Feedback:  0   1