Similar:
https://glpi.userecho.com/en/communities/1/topics/1786-it-would-be-useful-to-manage-physical-connections-in-racks-server-rooms-those-that-nicely-in

https://glpi.userecho.com/en/communities/1/topics/1786-it-would-be-useful-to-manage-physical-connections-in-racks-server-rooms-those-that-nicely-in

https://glpi.userecho.com/en/communities/1/topics/940-passive-painel-to-rack

https://glpi.userecho.com/en/communities/1/topics/541-add-patch-panel-in-network-assets

Good idea, only additionally should cover IP and MAC all network addresses (computers, network devices, printers ...)

You have this in: .../front/fieldunicity.php

Home > Setup > Fields Uniqueness

Currently, adding other assets or new fields is one of the basic functionalities in systems of this type.

In addition, there is a problem because other plugins do not use the added fields, but only those in GLPI core - if it were in the core - plugin developers would take into account additional assets and fields by default.

Look on ProcessMaker plugin.

https://glpi.userecho.com/en/communities/1/topics/85-add-workflow-engine

in Cli:

https://glpi.userecho.com/en/communities/1/topics/2058-console-ldapsync-add-parameter-basedn-to-synchronize-users

Look here:
https://glpi.userecho.com/communities/1/topics/1786-it-would-be-useful-to-manage-physical-connections-in-racks-server-rooms-those-that-nicely-in

here is very good (best) image:
https://hub.docker.com/r/turgon37/glpi/

or 0.93.version
https://hub.docker.com/r/wolvverine/glpi/