Files
expoweb/handbook/troggle/trogstatus.html

70 lines
6.0 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Handbook Troggle Status</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 & Expo Systems - status update</h1>
<p>Troggle is the software which runs the the expo cave survey data management and website.
<p>For earlier history see <a href="../website-history.html">Website history</a>.
<h4>July 2023</h4>
<p>Because Nadia asked nicely, we now have a rename form for uploaded files in wallets. This year we also have a 'create wallet' form.
<p>In the potato hut the blue netbook crashed horribly during expo and although Mark Shinwell coaxed it back to life, repreated fsck means that it needs to be retired before next year. The netbook was running Wookey's carefully curated drivers for the replacement USB-WiFi antenna which restored reasonable internet access in the hut this year.
<h4>September 2023</h4>
<p>
Too late for expo, but we now have a logbook entry creation and editing form running in a webpage.
Hopefully this will reverse the trend in recent years for many fewer people writing up trips in the logbook and many fewer trip records in general. The whiteboard at topcamp is a wonderful thing, but it gets erased so we no longer have a callout book permanent record of trips.
<h4>July 2024</h4>
<p>During the early days of this expo a generic "edit text files online" capability was finalised. This is so that anyone can
<ul>
<li>edit the "cave alias" list, see <a href="/handbook/computing/newkataster.html#cavealiases">New Kataster Number</a> procedure
<li>edit the "<a href="/cave_data/pendingcaves.txt">pending caves</a>" list or the documentation <a href="/cave_data/README.txt">README.txt</a> for newly discovered caves during expo
</ul>
Simply append "_edit" to the end of the URL for any .txt text file and you will be able to edit it.
<h4>August 2024</h4>
<p>The online logbook data entry (typing entries instead of writing them in longhand) has been a great success and was used intensively during the 2024 expedition. Many, many glitches were discovered and fixed during expo. James Waite still manages to crash it when nobody else does and we don't know why.
<p>The HTML files holding the cave and entrance data and descriptions (e.g. <var>expoweb/cave_data/1623-231.html</var> and <var>expoweb/entrance_data/1623-231d.html</var> etc. ) now omit the field for the cave identifier ('caveslug') or the entrance identifier ('slug'): these are now read directly from the filenames. This prevents pointless duplications, which always get out of step when a cave is renamed.
<h4>December 2024</h4>
<p>We have greatly simplified setting up separate 'development' and 'server mimic' environments on troggle development laptops, and also simplified their initial configuration. This is because we are now using a new tool <a href="https://docs.astral.sh/uv/">uv</a>. This should make 'on-boarding' new programmers easier.
<p>All data entry forms which commit to any of the git repositories now has a cookie-remembered field for the name of the person doing the updating. This is stored in the git history but not otherwise within troggle.
<h4 id="jan25">January 2025</h4><p>Becka did heroic work (as usual) on "katastering" the caves we have discovered which are significant enough to be issued official Austrian "kataster numbers". We now have an online form which will make this tedious job quicker in future, but it is definitely for experts only. It is online at <a href="/kataster/1623-2023-mg-03">kataster form</a> and the process is (mostly) documented in the handbook at <a href="/handbook/computing/newkataster.html">handbook/computing/newkataster</a>.
<h4 id="feb25">February 2025</h4>
<p>We now have a user registration system for use of the website, which substitutes for, and will eventually replace, the shared 'expo' logon we have been using since about 2009. This is not tied into anything much as yet. We expect to keep using 'expo' for a year or so yet.
<p>We also have a voluntary cookie-based "who am i" identification system which ties a particular laptop/computer/browser to a person. This is intended to give us some visibility of who exactly is editing any particular cave description, survex file, handbook webpage, wallet uploads etc. etc. This will help us track down glitches and mistakes much more easily. It is now enabled on all the forms which upload or edit data online. The first time you do anything on a new personal machine, you have to type in something like:<br />
<code>"Anathema Device &lt;anathema@potatohut.expo&gt;"</code>
and it will remember who you are for two years after you last do an update. [Managing Crowley and Aziraphale, the shared expo laptops, is a work in progress.]
<p>The user registration system for people who have previously been on expo is now working. A similar registration for people who have not yet gone on expo is being developed.
<h4 id="sep25">September 2025</h4>
<p>The coloured boxes marking the various sorts of status of a wallet (e.g. <a href="/wallets/year/2017">wallets 2017</a>) are a bit of a mess, particularly with the introduction of electronic surveys which messes up what was previously a fairly simple situation. During the 2025 expo a new column "tunnelled" was introduced but this failed to simplify the situation. Various shades of green are used for how certain troggle is that the data in a wallet have been "tunnelled".
<hr />
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
Return to: <br />
<a href="../website-history.html">Website history</a><br /><br /><br />
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br /><br />
Troggle index:
<a href="trogindex.html">Index of all troggle documents</a><br />
<br />
<hr /></body>
</html>