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

VIVO-719 Improve the user interface

Browse source
This commit is contained in:
Jim Blake 2014-06-09 15:14:16 -04:00
parent be11b190bc
commit ae6a2a7251
5 changed files with 53 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

65
webapp/web/templates/freemarker/body/datatools/datatools-dumpRestore.ftl
View file

@ -1,38 +1,38 @@
<#-- $This file is distributed under the terms of the license in /doc/license.txt$ -->
<h2>Dump/Restore knowledge base</h2>
<style media="screen" type="text/css">
p.explain {
font-style: italic;
margin-left: 5em;
}
table.choices td {
padding-left: 2em;
padding-right: 2em;
}
</style>
<h3>Before you start:</h3>
<ul>
<li>
<b>Content models</b> hold the data that VIVO contains and operates on.
This includes the ABox and the TBox, instances and ontologies, assertions and inferences.
</li>
<li>
<b>Configuration models</b> hold the data that controls VIVO,
including display options, privacy restrictions, and user accounts.
</li>
<li>
Dumping the content models make take several minutes, and may produce large files.
For example, dumping a fully populated VIVO instance may take 20 minutes and produce a file of 3 gigabytes.
</li>
<li>
The restore process is additive: it will not delete existing triples.
However, duplicate triples will not be stored.
</li>
<li>
After restoring, the search index should be re-built.
The data will probably not require re-inferencing,
since the dump includes both assertions and inferences.
</li>
</ul>
<h2>Dump or Restore the knowledge base</h2>
<p class="explain">
<b>Content models</b> hold the data that VIVO contains and operates on.
This includes the ABox and the TBox, instances and ontologies, assertions and inferences.
</p>
<p class="explain">
<b>Configuration models</b> hold the data that controls VIVO,
including display options, privacy restrictions, and user accounts.
</p>
<hr>
<h3>Dump</h3>
<p class="explain">
Dumping the content models make take several minutes, and may produce large files.
For example, dumping a fully populated VIVO instance may take 20 minutes and produce a file of 3 gigabytes.
</p>
<form action="${selectUrl}" method="get">
<table>
<table class="choices">
<tr>
<td>Select models</td>
<td>Select format</td>
@ -63,6 +63,17 @@
<h3>Restore</h3>
<p class="explain">
The restore process is additive: it will not delete existing triples.
</p>
<p class="explain">
Choosing to purge large models can result in an OutOfMemory error.
It is better to start with a small or empty knowledge base.
</p>
<p class="explain">
After restoring, it is not necessary to rebuild the search index, or re-inference the data.
</p>
<#if tripleCount?? >
<section class="restore-feedback">
<p>Loaded ${tripleCount} triples</p>
@ -70,7 +81,7 @@
</#if>
<form action="${restoreUrl}" enctype="multipart/form-data" method="post">
<table>
<table class="choices">
<tr>
<td>Select models</td>
<td>Select a file to restore from</td>