Hi Jeff, so name is in the CR, then I suggest we switch to using it from there and deprecate acs_objects.get_name for as many object types as possible.
(I'm tempted to suggesting adding a verbose description field to cr_items - but I'll do that later 😃)
There's one way to make acs_objects.name a lot lighter btw: hardcode the most frequently values. That's *very* easy and non-breaking.
One point as to why adding a central name field is pretty straight-forward and not that worrysome: It's a change that is visible even to a rather naive user. People complain quickly if "object xyz doesn't have a name".
