...
When 2 URIs are declared to be the same in VIVO, all the statements about both will be displayed for either (e.g., Israel and Israel). Improvements are needed, however:
...
- add the switch to configuration
Jira server DuraSpace JIRA key VIVO-110
- offer it as a standard predicate to add values for
Jira server DuraSpace JIRA key VIVO-111
- modify the interface to allow adding those statements and to display the statements
- there is no way via the current UI to add or remove owl:sameAs assertions – they have to be added as tiny RDF files via the add/remove RDF command
...
- This becomes more complicated when the 2nd or higher URI is not in the local VIVO
- Colorado has a use case to assert sameAs relationships between people's profiles in their university-wide VIVO and the separate implementation at the Laboratory for Atmospheric and Space Physics, where additional information about research projects, equipment, and facilities will be stored behind a firewall. They would like to pull data from the CU VIVO into the LASP VIVO dynamically, and pull any publicly visible data from LASP VIVO to supplement the CU VIVO content about a person.
- Colorado also has a need to pull data from the Harvard Profiles system used by the University of Colorado Medical School in Denver to the CU VIVO without replicating more than is necessary. This is a similar use case to the connections needed between VIVO on the Cornell Ithaca campus and the Weill Cornell VIVO.
Improvements are needed, however:
For 1.6
It may be a first step to
...
simply show a link to the equivalent URI, with some form of "see also" label
A constrained approach could disable sameAs reasoning in our simple reasoner, which will start filling in for one URI everything that is inferred about the other
add the switch to configuration
Jira server DuraSpace JIRA key VIVO-110
offer it as a standard predicate to add values for, modifying the interface to allow adding and removing those statements and to display the statements
Jira server DuraSpace JIRA key VIVO-111
More general support for sameAs
- It will adversely affect performance to require VIVO to detect that two or more URIs for an individual have been declared to be sameAs each other and then retrieve and blend all the data for each URI for rendering on a single page
- This becomes more complicated when the 2nd or higher URI is not in the local VIVO
- sameAs in the object position
- when another VIVO individual is linked to one or the other of these Israels, the application is not yet smart enough to show only one object property statement to one instance of the Israel, and it looks to users like a duplicate of both the country and the relationship
- sameAs in the object position
- when another VIVO individual is linked to one or the other of these Israels, the application is not yet smart enough to show only one object property statement to one instance of Israel, and it looks to users like a duplicate of both the country and the relationship
- Colorado has a use case to assert sameAs relationships between people's profiles in their university-wide VIVO and the separate implementation at the Laboratory for Atmospheric and Space Physics, where additional information about research projects, equipment, and facilities will be stored behind a firewall. They would like to pull data from the CU VIVO into the LASP VIVO dynamically, and pull any publicly visible data from LASP VIVO to supplement the CU VIVO content about a person.
- Colorado also has a need to pull data from the Harvard Profiles system used by the University of Colorado Medical School in Denver to the CU VIVO without replicating more than is necessary. This is a similar use case to the connections needed between VIVO on the Cornell Ithaca campus and the Weill Cornell VIVO.
| 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
- 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.
- 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 without having to set up SSL certificates
- It would help the user experience if it's possible to bundle together an Would you want a bundled atomic change set for (at least all those changes for one graph together), so could control additions and retractions better than when piecemealwould not show up piecemeal
- Note that since inferences are done is a separate thread there may still be some lag
| Anchor | ||||
|---|---|---|---|---|
|
...