litvinovg/vivo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Cleaned markup, added styles, and aria roles for Refresh Content pages

Browse source
This commit is contained in:
manolobevia 2011-11-14 19:51:31 +00:00
parent dd411fe7dc
commit 49bf2dea0a
1 changed files with 12 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

24
productMods/templates/freemarker/visualization/tools.ftl
View file

@ -7,20 +7,20 @@
<a href="${refreshCacheURL}">Refresh Cached Models for Visualization</a>
<h5>Why</h5>
Large-scale visualizations like the Temporal Graph or the Map of Science involve calculating total counts of publications or
<h3>Why</h3>
<p>Large-scale visualizations like the Temporal Graph or the Map of Science involve calculating total counts of publications or
of grants for some entity. Since this means checking also through of its all sub-entities, the underlying queries can be both
memory-intensive and time-consuming. For a faster user experience, we wish to save the results of these queries for later re-use.
memory-intensive and time-consuming. For a faster user experience, we wish to save the results of these queries for later re-use.</p>
<h5>What</h5>
To this end we have devised a caching solution which will retain information about the hierarchy of organizations-namely,
which publications are attributed to which organizations-by storing the RDF model. <br />
We're currently caching these models in memory. The cache is built (only once) on the first user request after a server restart.
<h3>What</h3>
<p>To this end we have devised a caching solution which will retain information about the hierarchy of organizations-namely,
which publications are attributed to which organizations-by storing the RDF model.</p>
<p>We're currently caching these models in memory. The cache is built (only once) on the first user request after a server restart.
Because of this, the same model will be served until the next restart. This means that the data in these models may become stale
depending upon when it was last created. This works well enough for now. In future releases we will improve this solution so that
models are stored on disk and periodically updated.
models are stored on disk and periodically updated.</p>
<h5>How</h5>
The models are refreshed each time the server restarts. Since this is not generally practical on production instances,
administrators can instead use the “refresh cache” link above to do this without a restart.
<br />
<h3>How</h3>
<p>The models are refreshed each time the server restarts. Since this is not generally practical on production instances,
administrators can instead use the "refresh cache" link above to do this without a restart.</p>