...
this feature still needs further clarification, requirements analysis or design work so will not be included in VIVO v1.6
we don't see any way to do this for 1.6
...
| Anchor | ||||
|---|---|---|---|---|
|
Jira server DuraSpace JIRA key VIVO-101 - Implementing a web service interface (with authentication) to the VIVO RDF API, to allow the Harvester and other tools to add/remove data from VIVO and trigger appropriate search indexing and recomputing of inferences.
- This would also enable round-trip editing of VIVO content from Drupal or another tool external to VIVO via the SPARQL update capability of the RDF api
- Authentication will be involved
- Could manage in our own authentication and authorization system and tell Apache that the servlet requires an HTTPS connection
- This approach would allow testing in a known environment without having to set up SSL certificates
- It would help the user experience if it's possible to bundle together an atomic change set (at least all those changes for one graph), so additions and retractions would not show up piecemeal
- Note that since inferences are done is a separate thread there may still be some lag
- Put and delete of data via LOD requests – this has been suggested but we're not sure a specification even exists for an LOD "put" request – please add references here if you're aware of discussion or documentation.
| Anchor | ||||
|---|---|---|---|---|
|
Jira server DuraSpace JIRA key VIVO-23
...