search

BHoM / RDF_Prototypes

Research project of the Cluster of Excellence "Integrative Computational Design and Construction for Architecture" (IntCDC) https://www.intcdc.uni-stuttgart.de/ **Project Name**: Knowledge Representation for Multi-Disciplinary Co-Design of Buildings. https://www.intcdc.uni-stuttgart.de/research/research-projects/rp-20/
GNU Lesser General Public License v3.0
9 stars 4 forks source link

GraphDB_Adapter: Push to a non local host #108

Closed DiellzaElshani closed 9 months ago

DiellzaElshani commented 1 year ago

Text edited by @alelom for several structure/content reasons. @DiellzaElshani Please remember to add the Project name in the title as a first thing, followed by a semicolon, when it is applicable (in this case: GraphDB_Adapter:).

We need to add a new adapter to GraphDB liking to a remote host (not local host).

@alelom comments:

  • we do not want to add a new adapter; the existing one already writes to http servers; the server being local or remote should not make a difference to it.
  • The GraphDB adapter already takes an input being the address of the server (default: localhost)
  • the adapter simply uses REST API calls to do its work.
  • It's just a matter of ensuring the REST API calls are correct. We need to create proper unit tests to ensure that this use case is covered.

I currently got access and admin rights to this service "https://kg.informatik.uni-stuttgart.de/" but I can not upload data to it using our components (because our components just call a local host). I tried adding the correct URI and repo name, however that didn't work.

The old adapter can stay, as it is useful for local/internal exploration of the graph; however we need one that we can communicate with others. I made a draft of the new components, including new input items such as username, etc. image

@polnischfrosch could you please check this issue before Wednesday, and we discuss it together with @alelom on Wednesday?

@alelom comment: @DiellzaElshani please do not include communication logistics in GitHub issues, this is a space for code discussions only

Here is the script of the new components draft, (they are empty, I just wanted to illustrate what is needed).

@alelom comment: where is the script?

We probably will create the repo directly in GraphDB, from GH we just need to access that repo.

@alelom comment: I concorporated the below text from the additional message posted by @DiellzaElshani below. Because no-one had commented on the issue already, and because the message expands on the information required for the description of the issue, please edit the issue text adding the information in it, rather than commenting. Comments are for starting a conversation. The text below describes a key defining aspect of the feature (what needs to be delivered), not just additional information, and as such it should stay in the body.

The goal is to have one repo created in graphDB, and from grasshopper we can send, update, delete only our stream of data. Not the whole repo:

Here is an example: image

Daniel can also assist if you have any questions.

@alelom comment: please tag the GitHub users in the assignees rather than mentioning them in the body as a dialogue. In this case, @polnischfrosch and @danielhz can be added as assignees, with @polnischfrosch delivering and @danielhz (and me) reviewing the subsequent PR/assisting the delivery.

DiellzaElshani commented 1 year ago

The goal is to have one repo created in graphDB, and from grasshopper we can send, update, delete only our stream of data. Not the whole repo:

Here is an example: image