expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2026-05-01 12:30:02 +01:00
Code Issues Packages Projects Releases Wiki Activity

django documentaiton updates

Browse Source
This commit is contained in:
Philip Sargent
2021-03-30 01:42:41 +01:00
parent fa81616797
commit ecaaec7927
7 changed files with 41 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
handbook/troggle/trogarch.html
+12 -2
View File
@@ -10,9 +10,19 @@
<h1>Troggle Architecture</h1>
<style>figure {font-weight: bold; font-size: small; font-family: sans-serif;font-variant-caps: small-caps;}</style>
<h2>Troggle overall architecture</h2>
<p>Troggle is made up of three large chunks:
<ul>
<li>The <strong>website pages</strong>: the handbook, instructions, indexes, reference material, walking guides,
logbook typescripts, reports to funding agencies, copies of expo reports in magazines, instruction guides for how to run an expo, accounting protocols for subsidising transport, rope maintenance standards: over 900 pages in all. What you are reading now is part of this.<br><br>
<li>The <strong>file archive</strong>: the photo galleries, the copies of PDF reports, the scans of original survey notebooks, GPS tracks, maps, aerial photos, scanned images of our handwritten expo logbooks. There are 40 GB of files.<br><br>
<li>The <strong>troggle-generated reports</strong>: the tables of survey trips for each cave, the lists of scanned surveys for each survey trip, who was on what trip, calendar lists of logbook entries corrleated with recorded survey trips, who surveyed what caves, what source material was used to create the final cave survey images, who went on which expeditions (and who didn't go caving). There are over 2,000 webpages generated using over 6,000 lines of bespoke python code from over 90 different urls.
</ul>
<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.
The core of the troggle software 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.
<div style="display: flex">
<div style="flex: 50%">
<figure>
@@ -29,7 +39,7 @@ The core of troggle is the data architecture: the set of tables into which all t
</figure>
</div></div>
<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 (15 May 2020) and click on the Class Diagram below on the right.
Also there have been tables added to the core representation which are not included in this old diagram, e.g. Scannedimage, Survexdirectory, Survexscansfolder, Survexscansingle, Tunnelfile, TunnelfileSurvexscansfolders, Survey. See <a href="datamodel.html">Troggle data model</a> python code (15 May 2020) and click on the Class Diagram below on the right.
<div class="onright">
<figure>
<a href="../l/trogclass-1.html"><img src="../t/trogclass-1.jpg"></a>