todo items collated into todo document

handbook/computing/onlinesystems.html

@@ -41,13 +41,14 @@ This page is the overview. The online systems manuals are split into these secti
 
 <p>How to use basecamp computers and networks, how to configure your phone for GPS, how to use your own laptop and "how to expo" in general are all part of the <em>handbook content</em>:
 <ul>
-<li><a href="yourlaptop.html">Configuring your own laptop</a></li>
+  <li><a style="color: blue" href="contribute.html">How can I contribute?</a>  
 <li><a href="../uploading.html">Uploading your photos</a></li>
 <li><a href="../logbooks.html">Uploading typed logbooks</a></li>
 <li><a href="../gpxupload.html">Uploading GPS tracks</a></li>
 <li><a href="../survey/newcave.html">Recording a new cave discovery</a></li>
 <li><a href="../survey/status.html">Monitoring the cave survey workflow status</a></li>
-  <li><a style="color: blue" href="contribute.html">How can I contribute?</a>  
+<li><a href="manual.html">Data maintenance</a> - finding and updating cave survey data using online tools
+<li><a href="yourlaptop.html">Configuring your own laptop</a> - for fixing /expofiles/ files with rsync and software work</li>
 </ul>
 <p><strong>Surveying and recording survey data is the  reason all this exists.</strong> The "survey handbook" part of this handbook gives instructions to beginners for how to record discoveries and surveys. <p><a href="../survey/why.htm"><img class="onleft" src="go-caving-th.jpg"></a>The "data maintenance" manual is where to look for help when things go wrong: the data has been entered incorrectly, or software has crashed due to corrupt input data.
 <p>The "system maintenance" manual may of interest to a caver who wonders how it is all put together but should not be needed by most people.

handbook/computing/todo.html

@@ -35,6 +35,11 @@ If a heading is in italics, then there are hidden items.
 
 <p>To see the "data maintenance" and "survey data-entry" to-do lists, go to <a href="todo-data.html">the other TO-DO list</a>
 
+<h3>Module to-do texts</h3>
+<p>These are extracted directly from the <var>todo = &apos;&apos;&apos;Thing to do &apos;&apos;&apos;</var> string at the top of each file of troggle code:</p>
+<hr>
+<embed type='text/text' height='200px' width='800px' src="/todo/tests">
+<hr>
 
 <h3>Process Documentation</h3>
     <details><summary><!--2020-03-26 psargent-->Wallets and new-cave</summary>
@@ -83,8 +88,7 @@ If a heading is in italics, then there are hidden items.
         <dd><!--2020-05-01 psargent-->Downgrade the "areas" aspect of the documentation as we don't use these now
       <dt>Prospecting Guides & slippy map & GPS tracks
         <dd><!--2020-07-24 psargent-->Redesign to be used as overlay on phone/tablet using essentials.gpx data 
-        <dd><!--2020-07-24 psargent-->Replace jpeg images in prospecting_image with OpenStreetMaps data 
+        <dd><!--2020-05-01 psargent-->This whole subsystem needs a good examination and  rewriting. :expoweb:/noinfo/prospecting_guide_scripts
-        <dd><!--2020-05-01 psargent-->This whole subsystem needs a good examination and possible rewriting. :expoweb:/noinfo/prospecting_guide_scripts
 
 
 </dl>
@@ -125,7 +129,7 @@ If a heading is in italics, then there are hidden items.
 
         <dd><!--2020-04-10 psargent-->Regenerate the diagram of the tables in the database & document</dd>
         <dd><!--2020-04-10 psargent-->Describe the parsing/import procedures so non-nerds can do it</dd>
-        <dd><!--2020-03-26 psargent-->Copy [some of] the .wiki material into the documentation somewhere?</dd>
+        
 
 
     <dt><!--2020-03-26 psargent-->Surveyscans</dt>
@@ -184,7 +188,7 @@ If a heading is in italics, then there are hidden items.
         <dd><!--2020-07-24 psargent-->as per Wookey on new server Debian 10
     <dt><!--2020-03-26 psargent--> document directory structure
         <dd><!--2020-04-03 psargent-->as per Julian's GitHub list - then close that issue.
-        Use 'tee' to cretae ascii art for this.</dd>
+        Use 'tee' to create ascii art for this.</dd>
 
     <dt>permissions
         <dd><!--2020-04-03 psargent-->do we need a cron job or has the group membership fix fixed it ? either way, document it.

handbook/troggle/unittests.html

@@ -31,7 +31,13 @@ is to ensure that all the settings are imported correctly, and it sets up a very
 No tests are run with the real expo database.
 <p>The tests can be run at a more verbose level by setting the <var>-v 3</var> flag.
 
-<p>As yet we have no test database set up, so the in-memory database is entirely empty.
+<p>As yet we have no test database set up, so the in-memory database is entirely empty. However we have 'fixtures' in 
+<var>troggle/core/fixtures/ </var>
+which are JSON files containing dummy data which is used in the more complex tests. 
+
+<p>If you want to write some tests and are having trouble finding something which is untested, have a look at the list of
+url paths in the routing system in <var>troggle/urls.py</var>
+and look for types of url which do not appear in the test suite checks.
 
 <hr />
 Go on to: <a href="trogarch.html">Troggle architecture</a><br />