*Deprecated* This material is for historical purposes only See https://wiki.duraspace.org/display/VIVODOC/All+Documentation for current documentation
*Deprecated* See https://wiki.duraspace.org/display/VIVODOC/All+Documentation for current documentation
There are three elements in the linkage between a User Account and a Profile page:
externalAuthId
runtime.properties (deploy.properties in 1.5 or earlier)
specifies the URI
of the matching propertyURI
whose value matches the externalAuthId
. (The property value is either a String or an untyped literal.)In more detail:
externalAuthId
is optional.externalAuthId
:<http://vivo.mydomain.edu/individual/u8041>
a <http://vitro.mannlib.cornell.edu/ns/vitro/authorization#UserAccount> ;
<http://vitro.mannlib.cornell.edu/ns/vitro/authorization#emailAddress>
"jeb228@cornell.edu"^^xsd:string ;
<http://vitro.mannlib.cornell.edu/ns/vitro/authorization#externalAuthId>
"jeb228"^^xsd:string ;
vivo.all.log
file in Tomcat logs. Each time VIVO starts up, the first entry written to the log contains all of the properties from runtime.properties
. It helps to inspect this if you might possibly be reading the wrong runtime.properties file.At Cornell, ours looks like this:
selfEditing.idMatchingProperty = http://vivo.cornell.edu/ns/hr/0.9/hr.owl#netId
For example, the Individual object that forms the basis for my profile page contains a statement like this:
<http://vivo.cornell.edu/individual/JamesBlake> <http://vivo.cornell.edu/ns/hr/0.9/hr.owl#netId> "jeb228" .