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

AllegroGraph request chain breaks with existing Goo code #101

Closed
mdorf opened this issue Apr 2, 2020 · 1 comment
Closed

AllegroGraph request chain breaks with existing Goo code #101

mdorf opened this issue Apr 2, 2020 · 1 comment

Comments

@mdorf
Copy link
Member

mdorf commented Apr 2, 2020

Out-of-the-box, the GOO implementation of request chain does not work properly with AllegroGraph.

@mdorf
Copy link
Member Author

mdorf commented Apr 2, 2020

The format of the request differs between 4store (4s) and AllegroGraph (AG):

4s - the body of the message contained a hash of two values:

{ 
  graph: "http://data.bioontology.org/ontologies/MAPPING_TEST1/submissions/11",
  data: "the actual graph data in turtle format"
}

AG - the graph name passed as a (query) parameter called "context” and body of the POST had to contain solely the actual graph data (no individual parameters):

http://server:port/repositories/bioportal/statements?context=%22http%3A%2F%2Fdata.bioontology.org%2Fontologies%2FMAPPING_TEST1%2Fsubmissions%2F11%22

Solution:

  1. Added the type of backend as a configurable parameter.
  2. Modified the append_triples_no_bnodes method to allow connections to both 4store and AllegroGraph. AllegroGraph supposedly uses the "standard" request format.

@mdorf mdorf closed this as completed Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant