mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-26 01:01:58 +00:00
54 lines
2.6 KiB
HTML
54 lines
2.6 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>Handbook Troggle Architecture</title>
|
|
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
|
|
</head>
|
|
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
|
|
<h2 id="tophead">CUCC Expedition Handbook</h2>
|
|
<h1>Troggle Architecture</h1>
|
|
|
|
<h3>Troggle data architecture</h3>
|
|
<p>
|
|
The core of troggle is the data architecture: the set of tables into which all the cave survey and expo data is poured and stored. These tables are what enables us to produce a large number of different but consistent reports and views.
|
|
|
|
<figure>
|
|
<a href="../i/troggle-tables.jpg">
|
|
<img src="../i/troggle-tables-small.jpg" /></a>
|
|
<figurecaption>
|
|
</figure>
|
|
|
|
<h3>Architecture description</h3>
|
|
<p>Read the proposal: "<a href="/expofiles/documents/troggle/troggle_paper.pdf" download>Troggle: a novel system for cave exploration information management</a>", by Aaron Curtis</em>. But remember that this paper is an over-ambitious proposal. Only the core data management features have been built. We have none of the person management features and only two forms in use: for entering cave and cave entrance data.
|
|
<p>
|
|
ALSO there have been tables added to the core representation which are not anticipated in that document of this diagram, e.g. Scannedimage, Survexdirectory, Survexscansfolder, Survexscansingle, Tunnelfile, TunnelfileSurvexscansfolders, Survey. See <a href="datamodel.html">Troggle data model</a> python code (3 April 2020).
|
|
|
|
<h3>Troggle parsers and input files</h3>
|
|
[describe which files they read and which tables they write to. Also say what error messages are likely on import and what to do about them.]
|
|
<ul>logbooks
|
|
<li>surveyscans
|
|
<li>survex files (caves)
|
|
<li>folk (people)
|
|
<li>QMs
|
|
<li>subcaves
|
|
<li>entrances
|
|
<li>drawings (tunnel)
|
|
|
|
</ul>
|
|
|
|
|
|
<h3>Files generated by troggle</h3>
|
|
<p>There are only two places where this happens. This is where online forms are used to create cave entrance records and cave records. These are created in the database but also exported as files so that when troggle is rebuilt and data reimported the new cave data is there.
|
|
|
|
<h3>Helpful tools and scripts</h3>
|
|
[ALSO talk about useful tools, such as those which interrogate MySQL or sqlite databases directly so that one can see the internals chnage as data is imported]
|
|
|
|
<hr />
|
|
Go on to: <a href="trognotes.html">Troggle uncategorised notes to be edited</a><br />
|
|
See: <a href="datamodel.html">Troggle data model</a> in python code <br />
|
|
Return to: <a href="trogintro.html">Troggle intro</a><br />
|
|
<hr />
|
|
</body>
|
|
</html>
|