GSoC'25 idea: IYP Browser

[dpgiakatos]

The Internet Yellow Pages (IYP) is a knowledge database that aggregates information about various Internet resources, such as ASNs, IP prefixes, and domain names. Currently, we utilize the Neo4J browser to query the graph, which returns results in four formats: an interactive graph, a table, a raw table, and a JSON object.

To enhance user experience, especially for those unfamiliar with Cypher, we have developed an LLM model and will provide an API to simplify the querying process. Our goal is to integrate this API with the Neo4J browser, allowing users to input either a Cypher query or a natural language description of the results they wish to obtain from the database.

The Neo4J browser will continue to return the default four output formats, and we will also include an explanation generated by our LLM, resulting in a total of five output formats. Since modifying the Neo4J browser would require maintaining a forked codebase and keeping up with updates from the original repository, we aim to create a new browser that connects directly to IYP, eliminating the need for users to input credentials and URLs as required by the Neo4J browser.

Expected Results:

• Design a user-friendly, maintainable browser that connects to both the Neo4J DB API and our LLM API (frontend only, no backend)
• Implement a graph visualizer similar to that of the Neo4J browser
• Implement a data table viewer similar to that of the Neo4J browser
• Allow users to input either a Cypher query or a natural language description
• Provide the LLM-generated explanation text (from our LLM API) alongside the graph visualizer and/or data table viewer

[amaydixit11]

This is an excellent initiative to make querying Neo4J databases more accessible, especially for users unfamiliar with Cypher. Integrating natural language processing into the browser will undoubtedly enhance the user experience and broaden the audience for this tool.

As someone experienced with Neo4J and frontend technologies like React and D3.js, I’d like to contribute to this project by offering suggestions for frontend design and implementation. A few suggestions/ideas for implementation,

• Frontend Design: Using a framework like Next.js for the browser interface can facilitate easy integration with APIs and efficient rendering of dynamic components.
• Graph Visualizer: Libraries like D3.js or Cytoscape.js can replicate and enhance the Neo4J browser's graph view. Features like node filtering, highlighting, and relationship exploration could improve usability. Additionally using Cytoscape.js with the cola layout can help handle large network graphs well and while also supporting custom styling/interactions
• Table Viewer: A library like AG Grid or React Table can handle large datasets efficiently and provide sorting, filtering, and pagination features.
• Natural language query interface: Add query templates/examples to help users understand capabilities, Show real-time previews of the Cypher translation when possible, Include an option to edit the generated Cypher before execution

Moreover, a cypher query builder GUI can also be implemented in the same without much difficulty,

If the team is open to contributions, I’d be happy to prototype a component (e.g., the graph visualizer or the LLM integration) or assist in designing the frontend architecture.

I’m excited about the potential of this tool to simplify interactions with Neo4J and would love to contribute to making it a success. Let me know how I can best support this initiative!

[dpgiakatos]

Hello,

Thank you for your suggestion, but it requires too much effort. I believe it would be better to stick to the initially planned features. Additionally, it is preferable for us to use the technologies that we are currently utilizing within the IHR organization. Therefore, VueJS and the Quasar framework would be more suitable for this project.

Regarding the graph framework, I would like to use the following library:
https://github.com/yWorks/yfiles-jupyter-graphs-for-neo4j
However, it does not have a free license if we want to use it for an HTML app.

Thank you for considering this in your GSoC proposal.

[srinitha709]

@dpgiakatos This is a fantastic idea, and I’m truly excited about the direction you’re taking with the IYP browser! simplifying the querying process while leveraging existing technologies like VueJS and Quasar framework is an excellent approach. Below is my proposed plan:

Leverage VueJS and Quasar:
Build a responsive, maintainable user interface using VueJS and Quasar's component library.
Interactive Graph Visualization:
Incorporate a visualization tool (e.g., Cytoscape.js) for features like zoom, node interactions, and tooltips.
Dynamic Data Table and Natural Language Querying:
Create a dynamic table with Quasar components, including sorting, filtering, and export functionalities.
Integrate the LLM API to convert natural language inputs into Cypher queries.
Display LLM-generated explanations alongside the results.

I’m confident this approach will deliver a robust, user-friendly solution that meets the project’s objectives. I’d love to contribute and collaborate further to ensure its success. Please let me know the next steps.

[dpgiakatos]

Hello,

Regarding the table or LLM explanation view, displaying the contents is quite straightforward. However, the graph rendering presents more challenges. Here are some questions that may help you as you create your proposal (the same comment also for @amaydixit11):

• What format does the Neo4j response of a query take?
• How can we visualize the Neo4j response using a graph (if the response returns a graph)?
• If the returned graph is too large, what can we do in this case, as the visualization may not be feasible?
• Are there any open-source solutions that can create a graph similar to Neo4j?
• Is it possible to use parts of the Neo4j browser, since it is an open-source project, and reuse them in our project?
• We also want to ensure that the graph we create matches the one generated by the Neo4j browser.

With that in mind, it would be beneficial to start thinking about the graph feature and its implementation before submitting your proposal. We can provide feedback on this prior to your submission.

Thank you.

[GoonsD]

Hello @dpgiakatos, This is really an exciting project, it will ease the use of IYP especially for those not familiar with cypher queries. Over the past few days, I’ve taken time to research how IYP functions as a knowledge database and have explored its integration with Neo4J. I’ve also run the existing project locally, reviewed the codebase, and gained a good understanding of its current architecture and features.

The proposed integration of an LLM API to simplify querying is a great step forward. It's great to use VueJS and the Quasar framework, as they align with the technologies currently used within IHR. However, I’d like to seek some clarity and share a few thoughts:

1. Graph Framework: The yFiles library seems like a robust choice, but its licensing restrictions for HTML applications might be a limitation. Would it be worth considering open-source alternatives?
2. LLM Integration: Are there any particular challenges you foresee in embedding LLM-generated explanations into the new browser’s interface? It would be helpful to understand any potential performance or usability concerns.
3. Authentication Simplification: Since the new browser will remove the need for users to input credentials or URLs, what would be the recommended approach for securely managing API access to the Neo4J DB and LLM?

I look forward to hearing your thoughts and suggestions. Please let me know if there are specific areas where I can focus my efforts to align with the project’s goals.

[dpgiakatos]

Hello,

Thank you for your questions. I answered them below:

1. Yes, we are considering other open-source alternatives, as we do not want to reinvent the wheel. One option we have is to refer to the Neo4j browser and use parts of its code related to graph visualization, since it is an open-source project. However, it may take some time to understand its codebase. If you know of any other alternatives, please feel free to share them.
2. We are currently running our LLM in-house for testing. We already have an API running and are testing its performance. We expect to have a better overview in the next months. We will provide endpoints for this part, and performance is not a concern for this project, as it is a frontend-only project that displays data from endpoints.
3. All the endpoints we provide do not require authentication. Anyone can use them for free without needing to log in. We have taken all necessary actions to ensure that every endpoint we expose is secure.

As I mentioned earlier, I believe the most challenging aspect of this project is the graph visualization. With that in mind, it would be beneficial to start thinking about the graph feature and its implementation before submitting your proposal. We can provide feedback on this prior to your submission.

Thank you.