This documentation relates to an old version of VIVO, version 1.10.x. Looking for another version? See all documentation.
Permits external applications to add or remove specific triples from the VIVO data model. These changes use the standard data channels in VIVO, so the search index will be updated as appropriate, and the reasoner will add or remove inferences as needed.
By default, the SPARQL Update API is disabled in VIVO, for security reasons. See Enabling the API.
Previous implementations of the Harvester and similar tools have written directly to the VIVO triple-store, bypassing the usual data channels in VIVO. After ingesting, it was necessary to rebuild the search index, and to run the reasoner to add or remove inferences. Since the search index and the reasoner were not aware of the exact changes, the entire data model was re-indexed and re-inferenced.
When the Harvester and other tools have been modified to use the SPARQL Update API, VIVO will ensure that the search index and inferences are kept in synchronization with the data.
Other ingest tools
This API permits ingest tools such as Karma to programmatically insert data into VIVO without requiring knowledge of VIVOs internal data structures.
VIVO "face" applications
Linked Open Data requests have permitted people to write Drupal applications (for example) that display data from VIVO. This API will permit such applications to accept user edits, and apply them back to VIVO.
The API supports only HTTP POST calls. GET, HEAD, and other methods are not supported, and will return a response code of
405 Method Not Allowed.
|the email address of a VIVO adminstrator account
|the password of the VIVO administrator account
|A SPARQL Update request
The syntax for a SPARQL Update request is described on the World Wide Web Consortium site at http://www.w3.org/TR/2013/REC-sparql11-update-20130321/
The API requires that you specify a GRAPH in your SPARQL update request. Insertions or deletions to the default graph are not supported.
|SPARQL Update was successful.
400 Bad Request
|HTTP request did not include an
|The SPARQL Update request did not specify a GRAPH.
|The SPARQL Update request was syntactically incorrect.
|HTTP request did not include an
|HTTP request did not include a
|The combination of
password is not valid.
|The selected VIVO account is not authorized to use the SPARQL Update API.
405 Method Not Allowed
|Incorrect HTTP method; only POST is accepted.
500 Internal Server Error
|VIVO could not execute the request; internal code threw an exception.
These examples use the UNIX
curl command to insert and delete data using the API.
This example inserts a single RDF statement into the data model.
This example removes the previous statement, and inserts a replacement.
This example removes the modified statement.
For large files one can also use the SPARQL LOAD command.
For this, you have to first create the RDF file with the triples that you want to add, and make the file accessible at a URL. In the example below, the RDF file containing the triples is called
data.rdf, and is available in the root directory of the web server at
Like the previous commands, this one references a data file, in this case called
import.sparql. That file contains the
LOAD command which references the actual data.
Increase the default Tomcat
By default, Tomcat sets the default maximum of a POST request to 2 megabytes. If you want to increase this to be able to POST larger sets of triples to VIVO, you can use the
maxPostSize attribute in
server.xml. The example below would increase the maximum to 10 MB. See the Tomcat documentation for more details.
Enabling the API
Before enabling the SPARQL update handler, you should secure the URL
api/sparqlUpdate with HTTPS. Otherwise, email/password combinations will be sent across the network without encryption. Methods for securing the URL will depend on your site's configuration.
By default, the SPARQL Update handler is enabled for only the root user in VIVO. To enable it for other user groups, you can either:
- uncomment the line references "UseSparqUpdateAPI" in [vitro]/rdf/auth/everytime/permission_config.n3 or
- create an RDF file in the
[vitro]/rdf/auth/everytimedirectory that will authorize your site administrators to use the API. Below is an example of such a file, using N3 syntax.