2
0
mirror of https://expo.survex.com/repositories/troggle/.git synced 2024-11-25 00:31:55 +00:00
troggle/templates/controlPanel.html
2021-12-30 00:55:42 +00:00

145 lines
4.7 KiB
HTML

{% extends "base.html" %}
{% block content %}
{% if jobs_completed %}
<div class="noticeBox">
&nbsp;Just finished running:
<ul>
{% for job in jobs_completed %}
<li>{{ job }}</li>
{% endfor %}
</ul>
&nbsp;See <a href="/dataissues">Data Issues</a> report
<br>&nbsp;
</div>
{% endif %}
{% if error %}
<div class="noticeBox">
{{ error }}
</div>
{% endif %}
<h3>This control panel is being redeveloped</h3>
<p>Do not attempt to use any of these functions as they are in active development.
<ol>
<li>Importing things in the wrong order will screw-up the database links and break things.
<li>The export of logbooks in a standard HTML-like format is very much not working.
</ol>
<p>Today (Jan. 2022) we use the <a href="/handbook/troggle/trogimport.html">databaseReset program</a> to import from the master files. This is run on the server itself only by nerds who remotely log in to the server using ssh.
<p>Before you even think about doing database imports, you should understand the implications on everyone else. See <a href="/handbook/troggle/trogindex.html">the Troggle documentation</a>.
<p>As soon as you can cope, you should read the source code for
<a href="http://expo.survex.com/repositories/troggle/.git/tree/databaseReset.py">databaseReset</a> to see what it does, as the details are not documented anywhere else yet. But at least the code is quite well commented.
<p>There is currently no feedback here when an import failure occurs - even a catastrophic one. You can see the list of parsing errors on the most recent imports on the <a href="/dataissues">Data Issues</a> page.
<font style="color: silver">
<div style="column-count: 2; ">
{% comment %}
<form name="reset" method="post" action="">
{% csrf_token %}
<h3>Wipe:</h3>
<table>
<tr>
<td>Wipe entire database and recreate tables: </td>
<td><input type="checkbox" name="reload_db" /></td>
<td>
<input type="submit" id="Import" value="I really want to delete all information in troggle, and accept all responsibility.">
</td>
</tr>
</table>
</form>
{% endcomment %}
<h3>Import (on top of existing data):</h3>
<p>To get a fully-functioning system, all these imports must be done and in this order.
<form name="import" method="post" action="">
{% csrf_token %}
<table>
<tr>
<th colspan="2">Import from master files</th>
</tr>
<tr>
<td>all caves </td>
<td><input type="checkbox" name="import_caves"/></td>
</tr>
<tr>
<td>all people </td>
<td><input type="checkbox" name="import_people"/></td>
</tr>
<tr>
<td>all surveys scans </td>
<td><input type="checkbox" name="import_surveyscans"/></td>
</tr>
<tr>
<td>all logbooks</td>
<td><input type="checkbox" name="import_logbooks"/></td>
</tr>
<tr>
<td>QMs (from old csv files)</td>
<td><input type="checkbox" name="import_QMs" /></td>
</tr>
<tr>
<td>all drawings files</td>
<td><input type="checkbox" name="import_drawingsfiles" /></td>
</tr>
<tr>
<td>all survex data (10 minutes)</td>
<td><input type="checkbox" name="import_survex" /></td>
</tr>
</table>
<p>
<input type="submit" id="Import" value="Import">
</p>
</form>
<p>&nbsp;
<h3>Export to a different format:</h3>
<p>This creates 'newlogbook.html' in the years/&lt;year&gt;/ folder
<table>
<tr>
<th>Export and Download</th>
</tr>
<tr>
<td>
<form name="export" method="POST" action={% url "exportlogbook" %}>
{% csrf_token %}
<p>Download a logbook file which is dynamically generated by Troggle.</p>
<p>
Expedition year:
<select name="year">
{% for expedition in expeditions %}
<option value="{{expedition}}"> {{expedition}} </option>
{% endfor %}
</select>
</p>
<p>
Output style:
<select name="extension">
<option value="html2005">.html file - 2005 style</option>
<option value="html2022">.html file - 2022 style</option>
</select>
</p>
<p>
<input name="download_logbook" type="submit" value="Download logbook" />
</p>
</form>
</td>
</tr>
</table>
</form>
</div>
</font>
{% endblock %}