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

added to do for folk list - online edit of handbook/troggle/trogdesign.html

Browse Source
This commit is contained in:
Philip Sargent
2025-10-21 10:39:35 +01:00
committed by Expo on server
parent 5108cb2bb8
commit 8542a03485
1 changed files with 49 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
handbook/troggle/trogdesign.html
View File

@@ -17,7 +17,7 @@
<li><h4><a href="#change">New Things Troggle will need to Manage</a></h4>
<li><h4><a href="#specific">Specific, Immediate problems</a></h4>
</ul>
<p><em>Updated: 5 September 2023</em>
<p><em>Updated: 21 October 2025</em>
<h2 id="fail">Things Troggle Doesn't Do</h2>
<p>Mostly these are not just a problem just with troggle, but things where expo procedures have never been
@@ -38,7 +38,7 @@ is generated quite separately from the survex files and fixed-points. And it is
<a href="/eastings">the troggle 'ents' page</a> into WGS84 and display it in the entrance description pages.
<p>We really want a prospecting map showing entrances which are clickable,
so that the entrance description pops up.
<p>Our procedures for 'tag', 'exact tag', and 'other tag' are undocumented and need to be redone.
<p>Our procedures for 'tag' <strike>, 'exact tag',</strike>, and 'other' are undocumented and need to be redone.
<h3>Using Question Marks in active exploration</h3>
<p>See <a href="scriptsqms.html">the current ugly situation</a>.
@@ -59,7 +59,7 @@ location for the illutrating photographs - which were very good. [We now have a
<p>We seem to have lost the expo twitter account credentials.
<p>We have an expo Facebook account (deprecated as many Expo users hate FB)
<p>We used to use Slack and (in 2022) use Trello for expo organisation. We have moved from Slack to
Element, which we can archive ourseleves, and maybe we can use Kanboard (ditto) next year instead of Trello.
Element, which we can archive ourseleves, and we use Kanboard now instead of Trello.
<h2 id="badly">Things Troggle Does Badly</h2>
@@ -84,10 +84,7 @@ in survex files.
<p>We have an imperfect report <a href="/therionissues">therionissues</a> on references within in Therion files
<p>We could do with better reports on survex files which have neved been drawn up ("tunnelled").
<strike><h3>Managing people's names</h3>
<p>As of 2022, there are 15 people troggle can't cope with at all because their name is not structured as
"Forename Surname": where it is only two words and each begins with a capital letter (with no other punctuation,
capital letters or other names or initials).</strike> See the design document <a href="namesredesign.html">handling people's names properly</a>.
<h3>Online Wallet Management</h3>
<p>[Much better now that an external script has been incorporated into troggle and a form has been created for editing wallet data in July 2022. See <a href="/wallets/year/2019">2019 Wallets</a>]
@@ -117,20 +114,57 @@ Informally, several expo nerds have complete copies, but some better means of ma
the maintenance is difficult because several different epochs of software techniques are munged together.
So this makes future enhancement slower and more difficult as historic special cases need to be re-done.
This is technical debt.
<p>We import <b>cavers' names</b> in three separate places: the folk list, the names of the surveyors in
survex files, and the names of expoers in the logbooks. <strike>These are inconsistently validated.</strike>
These now all use the same code.
<ul>
<li>We have the HTML folder structure for complex caves in the same <b>URL namespace as the cave descriptions</b>
generated by troggle. This is a fossil from when the cave descriptions were actual HTML files (generated
offline) and needed to be local so that they would have simple access to the linked photographs and passage
description pages. This prevents us using "EditThisPage" on those complex descriptions, which thus adds
another level of pain on doing this task which is already much more difficult than it needs to be.
<p>
<li>The folk list and updating people present on expo, see the <a href="folkupdate.html">Folk Update process</a><p>
The folk update procedure which we have used for many decades
does not give instant feedback as to whether the editor has got it
right or not. It does not make the most recent changes visible, so a
mistake in putting someone in say 2023 instead of 2024 does not leap
out at you.
<p>
The historical record is probably in error in loads of places. (It
is much better than it was now that the logbook entries and the *team
people in survex files are now checked for consistency for that expo
year.)
<p>
There are too many steps for the whole procedure and the steps get out
of sync, so it looks as if an edit has not been done when actually it
has, but the server has just not had the final script update run on it
(that, at least, could be automated).
<p>
Hand editing the folk.csv file is getting increasingly unwieldy as the
file gets bigger and bigger.
<p>
There is no automated cross-check with bank of expo, which uses a
different person-naming-scheme, and which also includes people who
actually never make it to expo in that year.
<p>
Looking through historical photo archives, there are people we
can't match up with attendees, so that indicates some errors.
</ul>
<h4>Fossils done</h4>
<strike>
<p>We have half a dozen different <b>logbook HTML dialects</b> for different eras of expo logbooks. These should be
converted into one, simpler form. Then we can reduce the size of the logbooks parsers substantially.
</strike> We now (March 2023) have just one logbook format in use, and the last old logbook has been converted (Sept.2023).
<p>We have the HTML folder structure for complex caves in the same <b>URL namespace as the cave descriptions</b>
generated by troggle. This is a fossil from when the cave descriptions were actual HTML files (generated
offline) and needed to be local so that they would have simple access to the linked photographs and passage
description pages. This prevents us using "EditThisPage" on those complex descriptions, which thus adds
another level of pain on doing this task which is already much more difficult than it needs to be.
<p>We import <b>cavers' names</b> in three separate places: the folk list, the names of the surveyors in
survex files, and the names of expoers in the logbooks. <strike>These are inconsistently validated.</strike>
These now all use the same code.
<strike>
<p>As of 2022, there are 15 people troggle can't cope with at all because their name is not structured as
"Forename Surname": where it is only two words and each begins with a capital letter (with no other punctuation,
capital letters or other names or initials).</strike> See the design document <a href="namesredesign.html">handling people's names properly</a>.
<h2 id="change">New Things Troggle will need to Manage</h2>
<h3>Users with Only a Phone, No Computer</h3>