Versions Compared

Old Version 1

changes.mady.by.user Jim Blake

Saved on

compared with

New Version 2

changes.mady.by.user Jim Blake

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • You can confirm this value by looking in the 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 deploy.properties. It helps to inspect this if you might possibly be reading the wrong deploy.properties file.

  • At Cornell, ours looks like this:

    No Format
    
   selfEditing.idMatchingProperty = http://vivo.cornell.edu/ns/hr/0.9/hr.owl#netId

...

  • To associate a profile page with a user account, the Individual must have a data property whose URI is the one from deploy.properties, and whose value is equal to the externalAuthId of the user account.

  • For example, the Individual object that forms the basis for my profile page contains a statement like this:

    No Format
    
&lt;http<http://vivo.cornell.edu/individual/JamesBlake&gt;JamesBlake>
    &lt;http<http://vivo.cornell.edu/ns/hr/0.9/hr.owl#netId&gt;owl#netId>
    "jeb228" 
    .
  • You can confirm this by logging in as an admin, navigating to the profile page, clicking on "edit this individual" and then the button labelled "Raw Statements with this Resource as Subject"
  • In the example above, the "netId" field is set to an untyped Literal. A String Literal will work also.