graph-explorer
graph-explorer copied to clipboard
aws
React-based web application that enables users to visualize both property graph and RDF data and explore connections between data without having to write graph queries.
## Description I have tried to simply deploy this project locally to test it quickly on publicly available SPARQL endpoints, but the current documentation only explain in details how to...
The initial setup for anyone trying to run Graph Explorer locally is a bit cumbersome. With better documentation and examples it should be easier to accomplish and have a higher...
The local Docker setup documentation in the readme can be confusing for new users. ## Ideas - Add example for a typical local setup - Add documentation for Docker arguments...
The proxy server currently defaults to port 80 for local development uses. Since port 80 is disabled on many OS environments for security reasons we should use a different default....
There are many reasons why a user may want to reconfigure the port that the Graph Explorer proxy server uses. We should document what that process is in the [development...
The root `Readme.md` file has a lot of information in it. It can be a bit overwhelming for a new user who is unfamiliar with a lot of the concepts...
Investigate all SPARQL queries and optimize when possible. ## Related - Parent #358 - Addresses #240 - Addresses #184 - Addresses #263 - Addresses #747 - Potential solution #400
## Description For large public sparql endpoints such as [uniprot](https://sparq.uniprot.org/) statistics gathering takes a long time. UniProt and other endpoints provide detailed statistics with VoID, which might be useful to...
We can trace many reliability and performance issues to sub-optimal database queries. Here, we attempt to tackle some of the most impactful database queries in the app. ## Plan The...
## Description A http GET request is easier to cache than a POST request. Considering the repeated nature of some of the queries this might give a big performance increase....