Individual data block links should be linked via a UID, not the name
Overrides are so powerful for managing large numbers of assets in a project, and I love their concept. But as soon as you rename an object or collection in the source asset file, any overrides associated with it break. This is because the overrides on the data block are linked by the user-facing, editable name, meaning that you're locked into the name you chose before working on overrides. Additionally, you cannot relocate the broken link like you can with external files.
The best solution would be to tackle the problem from the root, using a new system of UID links instead of name links. I don't see any downsides to this method, since they're just strings like the name links were, only much more stable.
1 Comment
Raised here: blender.community/c/rightclickselect/k795 Item #4. UUID = GUID.
Linked libraries break far too easily. Think using a UUID/GUID is a good idea, however it should be done in conjunction with names, because you need the ability to be able to replace part of an asset with a new object (which would have a new UUID/GUID). So propose link using name first, and if that fails, then by UUID/GUID.