expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-09 07:14:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

fixes to /noinfo/ description links

Browse Source
This commit is contained in:
Philip Sargent
2021-04-10 19:05:24 +01:00
parent f52b3d87ae
commit 900f120de1
14 changed files with 54 additions and 230 deletions
Download Patch File Download Diff File Expand all files Collapse all files

84
handbook/computing/manual.html
View File

@@ -21,59 +21,6 @@
<li>There is another page with more info on <a href="#yourownlaptop">the software expo uses and setting up your own laptop</a>.
</ul>
<p>Editing the expo data management system is an adventure. Learning
it by trial and error is non-trivial. There are lots of things we
could improve about the system, and anyone with some computer nous is
very welcome to muck in. It is slowly getting better organised.</p>
<p>This manual is organized in a how-to sort of style. The categories,
rather than referring to specific elements of the data management system, refer to
processes that a maintainer would want to do.</p>
<p>Note that to display the survey data you will need a copy of the <a href="../getsurvex.html">survex</a> software.
<p>Follow these links if you have reached this page by accident and this is what you want to know:
<ul>
<li><a href="../uploading.html">How to upload photos</a></li>
<li><a href="../logbooks.html">Typing in logbook entries</a></li>
<li><a href="../gpxupload.html">Recording the GPS location of a cave</a></li>
<li><a href="../survey/index.htm">How to do cave surveying</a></li>
<li><a href="../index.htm">List of "How to" pages for everything else</a></li>
</ul>
<ul>
<li><a href="newyear.html">Manual: Creating a new 'year' in the system</a></li>
<li><a href="">Manual: Expo survey data maintenance manual</a></li>
<li><a href="manual.html#update">Manual: Updating the cave guidebook descriptions</a></li>
</ul>
<h2><a id="update">Updating the online systems - overview</a></h2>
<h3 id="troggle">Troggle - what it is</a></h3>
<p>Troggle runs the expo cave survey data management, presents the data on the website and manages the Expo Handbook. See the <a href="../troggle/trogintro.html">troggle intro</a>.
</p>
<p>A version control system is inefficient for scanned survey notes which are large files that
do not get modified, so they are kept as a plain directory of files 'expofiles'.
The same goes for holiday photographs and GPS logs.</p>
<h3>Contents </h3>
<ol>
<li><a href="#usernamepassword">Getting a username, password and key</a></li>
<li><a href="../computing/repos.html">The repositories</a></li>
<li><a href="#quickstart">Quick start</a></li>
<li><a href="#cavepages">Updating cave pages</a></li>
<li><a href="#updatingyears">Updating expo year pages</a></li>
<li><a href="#surveystatus">Maintaining the survey status table</a></li>
<li><a href="#menu">Cave pages and handbook menu system</a></li>
</ol>
Appendices:
<ul>
<li><a href="../website-history.html">Website history</a> - a history of the data management system up to 2019</li>
<li><a href="../c21bs.html">Taking Expo Bullshit into the 21st Century</a> - initial report from 1996</li>
<li><a href="useany.html">Platform portability</a> - making the website work widely [2006]</li>
</ul>
<h3><a id="usernamepassword">Getting a username, password and key</a></h3>
@@ -94,8 +41,8 @@ see <a href="#yourownlaptop">below</a>.
<h3><a id="cavepages">Updating cave pages</a></h3>
<span style="color:red">
<p>Public cave description pages are automatically generated by troggle from a set of
cave files in noinfo/cave_data/ and noinfo/entrance_data/. These files
are named <area>-<cavenumber>.html (where area is 1623 or 1626).
cave files in /cave_data/ and /entrance_data/. These files
are named <area>-<cavenumber>.html (where area is 1623 or 1626), e.g. /cave_data/1623-115.html
<p>
Read the survey handbook section on <a href="../survey/caveentry.html">creating a new cave</a> in the system for instructions on how to name caves and the files you use to recoird them.
<p>Cave names do not have leading zeros
@@ -104,39 +51,12 @@ They are stored by number/ID in the dataset, not by name.
should be hyphenated, thus 2002-04 not 2002_04 or any of the various other
variants
<p>Use <tt>python databaseReset.py
caves</tt> in /expofiles/troggle/ to update the site/database after
editing these files.
Use <tt>python databaseReset.py
</tt> on its own to get a list of command options and brief explanations.</p>
<p>Clicking on 'New cave' (at the bottom of the cave index) lets you enter a new cave. <a href="caveentry.html">Info on how to enter new caves has been split into its own page</a>.</p>
<p>This may be a useful reminder of what is in a survex file <a href="/expofiles/documents/surveying/survex-guide.pdf">how to create a survex file</a>.
<h3><a id="updatingyears">Updating expo year pages</a></h3>
<p>Each year's expo is recorded in the folder</p>
<tt>/expoweb/years/</tt>
<p>which contains a number of files used to manage and record that year's expo. Have a look at
expoweb/years/2018/ for a recent well-documented expo (the weather was good).
Files are added and edited using the version control system for the expoweb <a href="../computing/repos.html">repository</a>.</p>
<p>To create a new 'year' for next year's expo see <a href="newyear.html">adding a new year</a>.
<h3><a id="surveystatus">Maintaining the survey status table</a></h3>
<p>See the <a href="../survey/onlinewallet.html">documentation</a> on updating the online surveyscans folders using the lever-arch file of plastic wallets.
<h3><a id="menu">Cave pages and handbook menu design</a></h3>
<p>See the <a href="menudesign.html">menu design history and proposals</a>
page on where we are and what we might do to improveand fix menus.
</span>
<hr />
</body>