{% extends "base.html" %} {% block content %} {% if jobs_completed %}
 Just finished running:  See Data Issues report
 
{% endif %} {% if error %}
{{ error }}
{% endif %}

This control panel is being redeveloped

Do not attempt to use any of these functions as they are in active development.

  1. Importing things in the wrong order will screw-up the database links and break things.
  2. The export of logbooks in a standard HTML-like format is very much not working.

Today (Jan. 2022) we use the databaseReset program 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.

Before you even think about doing database imports, you should understand the implications on everyone else. See the Troggle documentation.

As soon as you can cope, you should read the source code for databaseReset to see what it does, as the details are not documented anywhere else yet. But at least the code is quite well commented.

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 Data Issues page.

{% comment %}
{% csrf_token %}

Wipe:

Wipe entire database and recreate tables:
{% endcomment %}

Import (on top of existing data):

To get a fully-functioning system, all these imports must be done and in this order.

{% csrf_token %}
Import from master files
all caves
all people
all surveys scans
all logbooks
QMs (from old csv files)
all drawings files
all survex data (10 minutes)

 

Export to a different format:

This creates 'newlogbook.html' in the years/<year>/ folder
Export and Download
{% csrf_token %}

Download a logbook file which is dynamically generated by Troggle.

Expedition year:

Output style:

{% endblock %}