Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow INSERT instruction #87

Open
StephaneBranly opened this issue Nov 27, 2024 · 3 comments
Open

Allow INSERT instruction #87

StephaneBranly opened this issue Nov 27, 2024 · 3 comments

Comments

@StephaneBranly
Copy link

Would be nice to have the possibility to insert data using a notebook.

@BenjaminHofstetter
Copy link
Collaborator

BenjaminHofstetter commented Dec 3, 2024

@StephaneBranly this is necessary. Can you help me shape this feature?

What triple store do you use? Do you have a separate SPARQL endpoint for inserts (updates)?

@BenjaminHofstetter
Copy link
Collaborator

BenjaminHofstetter commented Dec 3, 2024

Some thoughts on this feature:

  • Some stores have different update endpoints.
  • We can define a “Server Connection” with two endpoints: one for reads and one for writes. The notebook can detect writes and choose the endpoint accordingly.
  • Should we bind a Cell to an Endpoint, like “use this connection for this cell”? This isn’t portable because different users may have different connection names. But we can check the URL.
  • SPARQL on Turtle files: I need to verify that the Writes operations work with Oxigraph. I don’t think it’s a significant concern. However, I’m curious about when we should write the changes back to the Turtle file.

@StephaneBranly
Copy link
Author

@StephaneBranly this is necessary. Can you help me shape this feature?

What triple store do you use? Do you have a separate SPARQL endpoint for inserts (updates)?

We are using an Apache Jena instance. There are 2 different endpoints (by default), one for reads and an other for writes.

Some thoughts on this feature:

* Some stores have different update endpoints.

* We can define a “Server Connection” with two endpoints: one for reads and one for writes. The notebook can detect writes and choose the endpoint accordingly.

* Should we bind a Cell to an Endpoint, like “use this connection for this cell”? This isn’t portable because different users may have different connection names. But we can check the URL.

* SPARQL on Turtle files: I need to verify that the Writes operations work with Oxigraph. I don’t think it’s a significant concern. However, I’m curious about when we should write the changes back to the Turtle file.

I also suggest to save in the notebook the used endpoints (without credientials) as a config. This should simplify the third point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants