Comment 7 for bug 1857351

In general, as long as the name (and org unit when relevant) are at the top, I don't have a strong preference for the rest of the fields. But, here are some suggestions:

Carousel Editor
1. Owner
2. Name
3. Carousel Type
4. Age Limit
5. Maximum Items
6. Item Libraries
7. Shelving Locations
8. Is Active
9. Carousel ID
10. Bucket
11. Last Refresh Time

Address Alerts
1. Owner
2. Alert Message
3. Street (1)
4. Street (2)
3. City
4. Postal Code
5. County
6. Country
7. Billing Address
8. Mailing Address
9. Match All Fields
10. Active
11. Address Alert ID

Holds Policies
This one has so many fields, I think it would be helpful to put the Description field first and then to break it up visually into natural groups of fields related to related to a) item, b) user, c) holds (or something along those lines).

Shelving Locations Editor
1. Owning Org Unit
2. Name
3. Is OPAC visible?
4. Can Circulate?
5. Is Holdable?
6. Hold Capture Requires Verification
7. Checkin Alert
8. Is Deleted?
9. Label Prefix
10. Label Suffix
11. URL
12. Location ID

For the question of having the column order match the fields, I think it's a good idea in general. There may be cases where some of the top fields on the form aren't particularly useful in the summary-type view of a grid so wouldn't default to visible - for instance, if a form has a name followed by a description, the name might be first in the grid but the description might not default to visible.