RE: [EXTERNAL] Re: PeeringDB Hackathon - looking for feature requests

["Knopps, Brian" <Brian.Knopps () charter com>]

I agree that this would be an interesting feature as it is something we commonly do over here using two or more 
queries. 

-B 

-----Original Message-----
From: NANOG <nanog-bounces+brian.knopps=charter.com () nanog org> On Behalf Of Alarig Le Lay
Sent: Thursday, August 12, 2021 3:10 PM
To: nanog () nanog org
Subject: [EXTERNAL] Re: PeeringDB Hackathon - looking for feature requests

CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking 
links, or following guidance.

On Thu 12 Aug 2021 15:27:48 GMT, Steve McManus wrote:
> PeeringDB is looking at participating at an upcoming NANOG Hackathon.
> One of the ideas for a theme is to improve the API. Specifically by 
> adding API calls for common use cases that people need to handle 
> outside of the API. Typically, by dumping the entire database to SQL 
> For example - given two IXes, which networks are present at both? We'd 
> like to make a list of such useful queries such that people don't have 
> to dump the database just to run them. A stretch goal would be to 
> expose into the website instead of requiring API calls.
>
> This issue has some more detail, including a few existing ideas:
> https://github.com/peeringdb/peeringdb/issues/1020
>
> Comments there or in email to me would be super helpful. As always, if 
> there are other feature requests for PeeringDB, feel free to create an 
> issue in github ( 
> https://github.com/peeringdb/peeringdb/issues/new/choose ) or in 
> email, even if they're not strictly Hackathon ideas. They are always 
> appreciated!
>
> Thanks! 
>
> -Steve
> PeeringDB Product Committee chair

A nice feature could be, while logged in, to highlight the IXPs shared with the ASN currently displayed.

--
Alarig
E-MAIL CONFIDENTIALITY NOTICE: 
The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain 
confidential and/or legally privileged information. If you are not the intended recipient of this message or if this 
message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this 
message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, 
distribution, copying, or storage of this message or any attachment is strictly prohibited.