API to update Patch Panel port names

[sfeldmann-uwh]

I'm wondering how difficult it would be to add to the API some functionality that matches clicking on the dropdown for the patch panel patch port header and selecting custom. I can add patch panels via the API, but would like to follow that up with another call to set the jack IDs. In my case the pattern would be ([1st jack num];1) There are several fields throughout with similar functionality, so this could potentially cover many of them, color, media etc.

[wilpig]

not overly difficult we just haven't done much in the api with the port stuff. it's primarily just a chore for someone to sit down and convert the class over to the api paths. It isn't overly complicated and we'd welcome a pull for it

[alex001x]

Hi Wilpig,
can you tell me which class file is concerned and an example code, I think I will do the work on API

[wilpig]

All of the port connections are handled by https://github.com/opendcim/openDCIM/blob/master/classes/DevicePorts.class.php some of the other functions are handled by https://github.com/opendcim/openDCIM/blob/master/scripts/ajax_portnames.php and sections in the devices.php itself like https://github.com/opendcim/openDCIM/blob/master/devices.php#L101 https://github.com/opendcim/openDCIM/blob/master/devices.php#L164

[sfeldmann-uwh]

My dev group has done this build on our instance. I have talked to them about releasing it back to the project but haven’t gotten to that yet. I also have a request with them to help automate some notes onto the patch panel ports. If you would like to take a look at what we have to verify functionality in your environment I can share it. On Apr 22, 2024, at 7:09 AM, Wilbur Longwisch ***@***.***> wrote:  You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> WARNING: This email appears to have originated outside of the UW Health email system. DO NOT CLICK on links or attachments unless you recognize the sender and know the content is safe. All of the port connections are handled by https://github.com/opendcim/openDCIM/blob/master/classes/DevicePorts.class.php some of the other functions are handled by https://github.com/opendcim/openDCIM/blob/master/scripts/ajax_portnames.php and sections in the devices.php itself like https://github.com/opendcim/openDCIM/blob/master/devices.php#L101 https://github.com/opendcim/openDCIM/blob/master/devices.php#L164 — Reply to this email directly, view it on GitHub<#1485 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AN2VA6GLDFY6TACC7E2E3ETY6T4WPAVCNFSM6AAAAABALNMMIWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCOBYGA2DE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[alex001x]

yes, thks

[sfeldmann-uwh]

This has been uploaded here: #1535 Scott Feldmann Infrastructure Principal UW Health - Information Services ***@***.*** From: Alexandre ***@***.***> Sent: Monday, April 22, 2024 3:56 PM To: opendcim/openDCIM ***@***.***> Cc: Feldmann, Scott M ***@***.***>; Author ***@***.***> Subject: Re: [opendcim/openDCIM] API to update Patch Panel port names (Discussion #1485) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> WARNING: This email appears to have originated outside of the UW Health email system. DO NOT CLICK on links or attachments unless you recognize the sender and know the content is safe. yes, thks - Reply to this email directly, view it on GitHub<#1485 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AN2VA6EPDJDEGULFUVIERTTY6V2MHAVCNFSM6AAAAABALNMMIWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCOJTGYZTG>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>