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

NIHVIVO-2930 minor layout changes to visualization tools page

Browse source
This commit is contained in:
tworrall 2012-06-29 16:52:52 +00:00
parent a60f78004c
commit 056b17d77a
2 changed files with 20 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
productMods/css/visualization/visualization.css
View file

@ -79,4 +79,13 @@ span.incomplete-data-holder,
}
.infoIcon {
padding-right:30px;
}
}
/* ---------------------------*/
/* Visualization Tools -------*/
/* ---------------------------*/
section.visualizationTools h3, p {
margin-left:20px;
}
section.visualizationTools p {
margin-left:20px;
}

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

@ -6,21 +6,24 @@
<h2>Visualization Tools</h2>
<a href="${refreshCacheURL}">Refresh Cached Models for Visualization</a>
<h3>Why</h3>
<section class="visualizationTools">
<h3>Why is it needed?</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
of grants for some entity. Since this also means checking through all of its 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.</p>
<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>
<h3>What's involved in the caching process?</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.</p>
<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>
</section>
${stylesheets.add('<link rel="stylesheet" href="${urls.base}/css/visualization/visualization.css" />')}