VIVO-281 Make extended linked data a configurable option.

This commit is contained in:
j2blake 2013-09-12 16:46:50 -04:00
parent ffc968b1ca
commit 331869b526

View file

@ -50,6 +50,7 @@
<li><a href="#homePage">Home Page Re-design</a></li> <li><a href="#homePage">Home Page Re-design</a></li>
<li><a href="#rdffiles">Auto-loaded RDF files move to the Home directory</a></li> <li><a href="#rdffiles">Auto-loaded RDF files move to the Home directory</a></li>
<li><a href="#language">Support for additional languages</a></li> <li><a href="#language">Support for additional languages</a></li>
<li><a href="#extended_lod">More compact responses to Linked data requests</a></li>
<li><a href="#BOGUS">ANYTHING ELSE?</a></li> <li><a href="#BOGUS">ANYTHING ELSE?</a></li>
</ol> </ol>
</li> </li>
@ -335,8 +336,9 @@ rdf/tbox/filegraph/tbox/vivo-foaf-1.5.owl
rdf/tbox/filegraph/tbox/vivo-pws-1.5.owl rdf/tbox/filegraph/tbox/vivo-pws-1.5.owl
rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre> rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
<p> <p>
If you are using a three-tier build process, you will need to add a single line If you are using a three-tier build process, you will need to add two lines
to the build script so the RDF files will be merged properly across the tiers. So this: to the build script to accomodate the RDF files, and the language support (see below)
So this:
<pre>&lt;patternset id="appbase.patterns"&gt; <pre>&lt;patternset id="appbase.patterns"&gt;
&lt;include name="src/**/*" /&gt; &lt;include name="src/**/*" /&gt;
&lt;include name="lib/**/*" /&gt; &lt;include name="lib/**/*" /&gt;
@ -353,6 +355,7 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
&lt;include name="src/**/*" /&gt; &lt;include name="src/**/*" /&gt;
&lt;include name="lib/**/*" /&gt; &lt;include name="lib/**/*" /&gt;
&lt;include name="rdf/**/*" /&gt; &lt;include name="rdf/**/*" /&gt;
&lt;include name="languages/**/*" /&gt;
&lt;include name="test/**/*" /&gt; &lt;include name="test/**/*" /&gt;
&lt;include name="themes/**/*" /&gt; &lt;include name="themes/**/*" /&gt;
&lt;include name="config/*.properties" /&gt; &lt;include name="config/*.properties" /&gt;
@ -387,6 +390,47 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
Add a new language to VIVO</a>. Add a new language to VIVO</a>.
</p> </p>
<h4 id="extended_lod">More compact responses to Linked data requests</h4>
<p>
In VIVO 1.6, the response to requests for linked data is changed, to be smaller and faster.
</p>
<p>
When responding to a request for linked data about an individual, VIVO 1.6 returns:
<ul>
<li>Data properties of the individual</li>
<li>Object relationships to and from the individual</li>
<li>The RDF types and RDFS labels for any object that directly relates to the individual</li>
</ul>
This data is filtered by the usual VIVO privacy policies,
so properties such as salary or employee ID number may not be revealed
unless the requester has been properly authenticated.
</p>
<p>
VIVO releases prior to VIVO 1.6 returned a more complex set of statements,
referred to as "extended linked data":
<ul>
<li>Data properties of the individual</li>
<li>Object relationships from the individual</li>
<li>All properties of the context nodes (positions, roles, etc.) that are associated with the individual.</li>
<li>Labels of objects that are joined to the individual through context nodes.</li>
<li>Full details of time intervals that are attached to context nodes: start, end, precision.</li>
</ul>
As above, this data was filtered by the VIVO privacy policies.
Although these additional items were included,
extended linked data was based only on relationships from the individual.
Relationships to the individual were not included.
</p>
<p>
Extended linked data was costly to produce, in terms of resources,
because it required a recursive search of the data model.
Extended linked data typically contained 50% more information than its non-extended equivalent,
and took more than 10 times as long to produce.
</p>
<p>
VIVO release 1.6 can be configured to produce extended linked data like previous releases.
However, extended linked data will not be supported in future releases.
</p>
<h4 id="BOGUS">ANYTHING ELSE?</h4> <h4 id="BOGUS">ANYTHING ELSE?</h4>
<p> <p>
</p> </p>
@ -614,7 +658,7 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
</tr> </tr>
<tr class="odd_row blue"> <tr class="odd_row blue">
<td> <td>
developer.defeatI18nCache = true developer.defeatI18nCache
</td> </td>
<td> <td>
false false
@ -632,7 +676,7 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
</tr> </tr>
<tr class="odd_row blue"> <tr class="odd_row blue">
<td> <td>
developer.insertFreemarkerDelimiters = true developer.insertFreemarkerDelimiters
</td> </td>
<td> <td>
false false
@ -647,7 +691,7 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
</tr> </tr>
<tr class="odd_row blue"> <tr class="odd_row blue">
<td> <td>
homePage.geoFocusMaps = enabled homePage.geoFocusMaps
</td> </td>
<td> <td>
enabled enabled
@ -667,13 +711,35 @@ rdf/tbox/filegraph/tbox/vivo-skos-1.5.owl</pre>
</tr> </tr>
<tr class="odd_row blue"> <tr class="odd_row blue">
<td> <td>
MultiViews.profilePageTypes=disabled MultiViews.profilePageTypes
</td> </td>
<td> <td>
disabled disabled
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">
Setting this property causes VIVO 1.6 to produce extended responses to requests
for linked data. This provides compatibility with earlier releases.
The default is <code>false</code>.
<br/>
Extended linked data is costly, in terms of server resource. Typically, extended
linke data contains 50% more information than its non-extended equivalent, and
takes 10 times as long to produce.
<br/>
<b>Extended linked data will not be supported in future releases of VIVO.</b>
</td>
</tr>
<tr class="odd_row blue">
<td>
serveExtendedLinkedData
</td>
<td>
true
</td>
</tr>
</tbody> </tbody>
</table> </table>