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

moved folk stuff to specific page - online edit of handbook/troggle/trogdesign.html

Browse Source
This commit is contained in:
Philip Sargent
2025-10-22 16:41:50 +01:00
committed by Expo on server
parent 2982cd26a7
commit 4d141b63bd
1 changed files with 3 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
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="#change">New Things Troggle will need to Manage</a></h4>
<li><h4><a href="#specific">Specific, Immediate problems</a></h4> <li><h4><a href="#specific">Specific, Immediate problems</a></h4>
</ul> </ul>
<p><em>Updated: 21 October 2025</em> <p><em>Updated: 22 October 2025</em>
<h2 id="fail">Things Troggle Doesn't Do</h2> <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 <p>Mostly these are not just a problem just with troggle, but things where expo procedures have never been
@@ -123,32 +123,8 @@ description pages. This prevents us using "EditThisPage" on those complex descri
another level of pain on doing this task which is already much more difficult than it needs to be. another level of pain on doing this task which is already much more difficult than it needs to be.
<p> <p>
<li>The folk list and updating people present on expo, see the <a href="/handbook/computing/folkupdate.html">Folk Update process</a><p> <li>The folk list and updating people present on expo, see the <a href="/handbook/troggle/folkdesign.html">Folk import redeisgn proposals</a>
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> </ul>
<h4>Fossils done</h4> <h4>Fossils done</h4>