Rigging Guide now includes Slack chat stuff

handbook/computing/todo.html

@@ -141,6 +141,10 @@ If a heading is in italics, then there are hidden items.
 
 <h3>Troggle</h3>
 <dl>
+    <dt><!--2020-07-27 psargent--> QM links in cave descriptions ALL BROKEN
+        <dd><!--2020-07-24 psargent-->There are HREF links to individual QMs in the cave description in e.g. 204 
+<a href="1623/204/swings.html">Swings and Roundabouts</a> such as  "At the bottom there is a climb down over boulders <a href="1623/204/qm.html#C2001-204-45">[C2001-204-45 C]</a>." where the troggle URL fails completely.
+
     <dt>Better import error messages 
         <dd><!--2020-04-20 psargent-->REPORT 'folder not recognised' errors into error log inside database -> "DataIssue" register
     <dt><!-- 2020-04-11 psargent -->Troggle parser/viewer 

handbook/logbooks.html

@@ -41,30 +41,21 @@ and
 and then the 
 <a href="survey/index.htm">Survey Handbook</a>
 
-<h3>Interim rigging guide</h3>
+<h3>Initial rigging guide</h3>
-<p>The logbook is the place where we record the rigging of caves as we discover them.
+<p>The logbook is the place where we record the rigging of caves as we discover them. You will manually copy the notes you made underground into the logbook.
-<p>When a cave is derigged, 
+<p>Writing up this and the final rigging guide is an important part of the Expo cave exploration process and is documented in <a href="survey/newrig.html">a specific "rigging" section</a>  the survey handbook.
-a good way of getting the rope lengths for your rigging guide is to 
+
-leave the knots in ropes removed  so they can
-be <b>measured</b>, but these days our caves are a bit deep 
-and complicated for this to be feasible. 
-Although a good survey and details of the belays
-can be used to estimate the length of rope needed, this is no substitute for
-measuring how much rope it actually took to rig.</p>
 
 <h3>The online logbook file</h3>
 
 <p>If you are at basecamp, then it is an excellent idea to 
 <b>type the text of your logbook trip report</b> instead of writing it by hand - see <a href="#type">below</a>. But still do lots of drawings in the paper logbook.
 
-
 <p>The contents of both the topcamp logbook and the basecamp logbook are typed into the same  
 "logbook.html" file for future use in tracking down leads and surveys. The drawings are scanned and stored in the same place, and hand-edited
 into the logbook.html file after expo finished. The typed notes are uploaded into the expo server database and 
 correlated with survey data done on the same day or by the same people.
 
-
-
 <p>Recent logbooks:
 <ul>
 <li><a href="../years/2018/logbook.html">2018</a>
@@ -75,6 +66,9 @@ which is then synchronised the version control system.
 <p>The result is a webpage reporting who did what and what was done by whom on expo, 
 e.g. see <a href="http://expo.survex.com/expedition/2018">the 2018 expo report</a>.
 
+<h3 =id="type">Typing your trip report - in the UK Caving Blog</h3>
+<p>In recent years we have seen an admirable increase in the number of people writing up their trips and experiences on social media and in particular on the UK Caving blog, see <a href="https://ukcaving.com/board/index.php?topic=25249.0">2019 Blog</a>. But please, please also make a handwritten entry in the logbook saying you have done this so that the text and pictures can be transcribed later. It is too easy to lose these: in 2018 there were two blogs in operation and most people didn't know that.
+
 <h3 =id="type">Typing just your trip report (at the <i>Expo Laptop</i>)</h3>
 <p>As handwriting can be very bad, please try to type the text, print it and stick it in the logbook, adding any sketches by hand. 
 This will save someone (probably you) deciphering your handwriting and typing it up later.
@@ -144,7 +138,7 @@ idea to type up <i>just your trip(s)</i> in a separate file, e.g. "logbook-mynew
 &lt;div class="timeug"&gt;T/U 10 mins&lt;/div&gt;</pre></code>
 <p>Note:  the ID's must be unique, so are generated from 't' plus the trip date plus a,b,c etc. 
 when there is more than one trip on a day.</p>
-<p>Note: <var><span style="color:red">T/U</span></var> stands for "Time Underground" in hours (6 minutes would be "0.1 hours").
+<p>Note: <var><span style="color:red">T/U</span></var> stands for "Time Underground" in minutes and/or hours. (We do not parse or collate this information so the format and units don't matter.)
 <p>Note: the <var><span style="color:red">&lt;hr /&gt;</span></var> is significant and used in parsing, it is not just prettiness.
 
 <p>Note this special format <var>"<span style="color:red">Top Camp - </span>"</var> in the triptitle line:
@@ -152,7 +146,7 @@ when there is more than one trip on a day.</p>
 It denotes the <var>cave</var> or <var>area</var> the trip or activity happened in. It is a word or two separated from the rest of the triptitle with "<var> - </var>" (space-dash-space). Usual values
 for this are "Plateau", "Base camp", "264", "Balkon", "Tunnocks", "Travel" etc.
 
-<p>Note this special format <var>"<span style="color:red">&lt;u&gt;Jenny Black&lt;/u&gt;</span>"</var> in the trippeople line:
+<p>Note this special format <var>"<span style="color:red">&lt;u&gt;Jenny Black&lt;/u&gt;</span>"</var> in the trip-people line:
 <code><pre>&lt;div class="trippeople"&gt;<span style="color:red">&lt;u&gt;Jenny Black&lt;/u&gt;</span>, Olly Betts&lt;/div&gt;
 </pre></code>
 It is necessary that one (and only one) of the people on the trip is set in <span style="color:red">&lt;u&gt;&lt;/u&gt;</span> underline format. This is interpreted to mean that this is the author of the logbook entry. If there is no author set, then this is an error and the entry is ignored.

handbook/rig/rigit.html

@@ -42,7 +42,9 @@ ways similar to Austria. </p>
 guides are drawn for any new rigging or rerigging each year so that we can add rigging
 guides to the online cave descriptions. 
 <p>This write-up should be done by the person who did the rigging at the first available moment: usually this will be in the top-camp logbook. 
-<p>See the <a href="../survey/newrig.html">making a rigging guide</a> part of the survey preparation process for where and when to do the initial and the final rigging guides for a new cave you have discovered.
+<p>See the <a href="../survey/newrig.html">New Rigging Guide</a> part of the survey preparation process for where and when to do the initial and the final rigging guides for a new cave you have discovered. 
+
+Instructions for the first, immediate rigging guide are in the <a href="../logbooks.html">Logbook write-up</a> part of the survey handbook.
 
 <p>It's also essential for future years to
 record any gear left <span lang="la">in situ</span>, so that we can keep the <a

handbook/survey/newrig.html

@@ -38,33 +38,65 @@ This page outlines step 5 of the survey production process. Each step is documen
 <p>
 
 <h3>Interim rigging guide</h3>
-The logbook is the place where we record the rigging of caves as we discover them. For a particularly fine example of rigging guides in a logbook see <a href="../../years/2015/logbook.html">the 2005 logbook</a>.
+The logbook is the place where we record the rigging of caves as soon as possible after we discover them. For a particularly fine example of rigging guides in a logbook, scroll through <a href="../../years/2015/logbook.html">the 2005 logbook</a>. 
-<p>
+<p><strong>SAFETY:</strong> Sketched rigging guides are most intensively used during the few days after the pitch is first rigged, and this is also the time when accidents are most likely, so this is an occasion where hours count. <em>Sketch the rigging in the logbook as soon as possible</em> and make sure a copy is at both base camp and top camp.
+<p>When a cave is derigged, 
+a good way of getting the rope lengths for your rigging guide is to 
+leave the knots in ropes removed  so they can
+be <b>measured</b>, but these days our caves are a bit deep 
+and complicated for this to be feasible. 
+Although a good survey and details of the belays
+can be used to estimate the length of rope needed, this is no substitute for
+measuring how much rope it actually took to rig. So please do this during the initial exploration and write it down in your survey notes.</p>
 
-When a cave is derigged, a good way of getting the rope lengths for your rigging guide is to leave the knots in ropes removed so they can be measured, but these days our caves are a bit deep and complicated for this to be feasible. Although a good survey and details of the belays can be used to estimate the length of rope needed, this is no substitute for measuring how much rope it actually took to rig.
+<h3>Preparation of rigging notes</h3>
-
-
-<h3>Final rigging guide</h3>
-
-<p>Complementing the passage description in vertical bits is a <b>Rigging
-Guide</b>. This is usually easiest to do as a sketch, but include notes to
-ensure that all bolts can be found again and any deviations and natural belays recognised.
 <p>
 You will already have an "Interim rigging guide" in the logbook entries of the trips, and also sketches on waterproof paper 
 which were made underground which were stored in the survey wallet and scanned to produce "notes-XXX.jpg" files in the online survey wallet for your trip. For small caves the logbook entry may be all you need.
-<p>Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the online survey wallets. The next step can take some time so get the rigging data in order now.
+<p>Collect together your notes for the rigging guide now, including all the pitch lengths. It is a good idea to copy these notes now and put them in the plastic survey wallet or to photograph them and put the files in the <a href="newwallet.html">online survey wallets</a>. The next step of doing the survey can take some time so get the rigging data in order now so that it doesn't get forgotten.
-<p>You will enter the final rigging guide as part of the 
+
+<h3>Final rigging guide</h3>
+
+<p>A <b>Rigging Guide</b> of the vertical sections is published with the cave survey and the cave passage descriptions in the cave guide after surveying is complete.
+
+This is usually easiest to do as a sketch, but must include notes to
+ensure that all bolts can be found again and any deviations and natural belays recognised for re-rigging in future.
+
+<p>You will enter the final rigging guide sketch as a scanned drawing within the 
     cave description when you edit the HTML pages for the online cave documentation. 
     This is done using the "New Cave" online form.
-<p>You should also produce a separate rigging guide document which will live in 
+
-    expofiles/rigging_topos/ e.g. see 
-    <a href="/expofiles/rigging_topos/264/entrance_topo_2016.pdf">expofiles/rigging_topos/264/entrance_topo_2016.pdf</a>
-    but also <a href="/expofiles/rigging_topos/264/entrance_topo2_2016.jpeg">/expofiles/rigging_topos/264/entrance_topo2_2016.jpeg</a>
 <p>Your initial rigging guide might be needed with some urgency during expo while exploration continues, so this is the place to put it.</p>
 </p>
 
 <p>See also the part of the <a href="../rig/rigit.html">bolting & rigging handbook</a> which discusses writing up your rigging attempts.
 
+<h3>Filing and Finding rigging guides</h3>
+<p>There are three different activities for rigging topos: 
+<ul>
+<li>drawing them up (either scanning or re-drawing scrappy images out of logbooks), 
+<li>making them findable/appear in cave descriptions,
+<li>(optionally) making prettier versions for important caves which have complex rigging. 
+</ul>
+<p>The simple and nicest-looking way to make them findable is to add them to the HTML inline in cave descriptions. For a finished example see the rigging topo for the "<a href="/1623/204/swings.html">Merry Go Round</a>" pitches in the Swings and Roundabouts area in 204.
+
+<a href="caveentry.html">Creating a new cave in the online system</a> is how you create the inline HTML. It is the next step in this Survey Handbook sequence of pages. <br><em>[To Do - improve documentatiton for how to add in image files in cave descriptions]</em>
+
+<p>You should produce a separate rigging guide file for each connected set of pitches which will live in<br> 
+    <var>expofiles/rigging_topos/</var> e.g. see <br>
+    <a href="/expofiles/rigging_topos/264/entrance_topo_2016.pdf">expofiles/rigging_topos/264/entrance_topo_2016.pdf</a><br>
+    but also (to demonstrate that something is always better than nothing):<br>
+    <a href="/expofiles/rigging_topos/264/entrance_topo2_2016.jpeg">expofiles/rigging_topos/264/entrance_topo2_2016.jpeg</a>
+    
+<p>The format is important. Please <em>don't</em> use PDF: if you are scanning a hand-drawn sketch then JPEG is best for our purposes as it is compact and we reuse it easily elsewhere in the system. 
+<p>If you are using a drawing package then produce the file in SVG format.  
+<a href="https://www.theregister.com/2020/04/14/16_years_inkscape_v1/">Inkscape</a> is what most cavers use as it's free and stable. This will make it possible to edit and update your topo in future.
+
+<p>Discussions on Expo Slack after the 2019 expo resulting in us consolidating rigging topo files into <var>expofiles/rigging_topos/</var> when previously they had had a number of different homes. So if you remember putting them somewhere else int he past, don't do that now. Put them in <var>expofiles/rigging_topos/</var>.
+
+<p>[ We could dream up some fancy scheme for indexing the rigging for every pitch in the system and add that  
+into troggle but frankly we don't think it's worth the effort.]
+
 <hr />
 <p>Back to the previous page in this sequence <a href="drawup.htm">Drawing up your survey</a>.
 <br />Now go the the next page in this sequence <a href="caveentry.html">Creating a new cave in the online system</a>.

handbook/troggle/trogindex.html

@@ -10,15 +10,15 @@
 <h1>Handbook Troggle - Index</h1>
 
 <p>The number of different webpages describing troggle, configuring the server troggle runs on, maintaining the underlying Django system, current documentation, future design issues and historical decisions is all getting a bit voluminous. So we need a complete index:
-<p>
+<p><img  border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
-<a href="trogintro.html">Troggle Introduction</a> - what it is<br>
+<a href="trogintro.html">Troggle - Introduction</a> - what it is<br>
 <a href="trogusers.html">Troggle - the users</a> - Who needs to know What and When<br>
 <a href="trogdocm.html">Troggle - Fixing things</a> - users' manuals for data import<br>
-<a href="trogimport.html">Troggle Data Import</a> - reset and import data<br>
+<a href="trogimport.html">Troggle - Data Import</a> - reset and import data<br>
-<a href="trogmanual.html">Troggle Maintenance</a> - list of maintenance tasks<br>
+<a href="trogmanual.html">Troggle - Maintenance</a> - list of maintenance tasks<br>
-<a href="trogarch.html">Troggle Architecture</a> - diagrams, files, structure<br>
+<a href="trogarch.html">Troggle - Architecture</a> - diagrams, files, structure<br>
-<a href="datamodel.html">Troggle Data Model</a> - syntax-coloured list of Classes, instance variables and foregin keys<br>
+<a href="datamodel.html">Troggle - Data Model</a> - syntax-coloured list of classes, instance variables and foreign keys<br>
-<a href="trogdesign.html">Troggle Design Decisions for the Future</a> - open issues being worked on<br>
+<a href="trogdesign.html">Troggle - Design Decisions for the Future</a> - open issues being worked on:<br>
 <ul>
 <li><a href="trogsimpler.html">Troggle - a kinder simpler troggle?</a> - Radost's proposals (critiqued)<br>
 <li><a href="trogspeculate.html">Troggle Architecture Speculations</a> - as in April 2020<br>
@@ -27,7 +27,7 @@
 <li><a href="menudesign.html">Troggle Menu Design</a> - options for replacing the menuing system<br>
 </ul>
 <a href="serverconfig.html">Troggle server configuration</a> - how to get troggle running on a new machine<br>
-<a href="unittests.html">Troggle Unit Tests</a> - test suite for programmers<br>
+<a href="unittests.html">Troggle unit tests</a> - test suite for programmers<br>
 <a href="trogstatus.html">Troggle & Expo Systems - status update</a> - where we are now<br>
 
 <br>

handbook/troggle/trogmanual.html

@@ -31,6 +31,8 @@
 <hr />
 Go on to: <a href="trogarch.html">Troggle architecture</a><br />
 Return to: <a href="trogintro.html">Troggle intro</a><br />
+Troggle index: 
+<a href="trogindex.html">Index of all troggle documents</a><br />
 <hr />
 </body>
 </html>