Every OSS inventory project I know of spends a disproportionate amount of time (and hence money) on working out what to name objects. To use a cliché, every project re-invents the wheel. The naming choice is limitless, and is often a battle, or even a war, between a unique system identifier local to the inventory tool, a user friendly name, a name encoded with short codes for 10 attributes, a name understood by upstream and downstream systems, network names, or sometimes preservation of lots of legacy names that are engraved on the souls of users. The human condition seems to love encoding as much information into the name as possible.
Come on vendors – please provide a best practice, well reasoned, naming standard out of the box so we never have to think about this again. Then I can sleep at night.
Who can recommend an efficient way to tackle this on their project?