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

moved text around again - online edit of handbook/troggle/folkredesign.html

Browse Source
This commit is contained in:
Philip Sargent
2025-10-22 17:06:45 +01:00
committed by Expo on server
parent 180eae16ac
commit 4067368ca8
1 changed files with 43 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

73
handbook/troggle/folkredesign.html
View File

@@ -1,8 +1,45 @@
<html><head><title>CUCC Expedition Handbook: folk.csv redesign</title></head><body>
<h2 id="otherfolk">Folk: pending possible improvements</h2>
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<h2 id="tophead">CUCC Expedition Handbook - folk.csv redesign options</h2>
<h1>Redesign the folk.csv process</h1>
<ul>
<li>Read <a href="/handbook/computing/folkupdate.html">folklist script</a> - how it works, how troggle imports the data
<li>See the <a href="/handbook/troggle/namesredesign.html">names management redesign</a> - done
</ul>
<h2>Problems which need resolving</h2>
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.) Looking through historical photo archives, there are people we
can't match up with attendees, so that indicates some errors.
<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 and the lines get longer.
<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.
<h3 id="otherfolk">Folk: possible improvements</h3>
<p>Read about the <a href="../computing/folkupdate.html">folklist script</a> before reading the rest of this.
<p>This does some basic validation: it checks that the mugshot
<p>The folk.csv parser in troggle does some basic validation: it checks that the mugshot
images and blurb HTML files exist.
<p> The folk.csv file could be split:
@@ -20,35 +57,11 @@ folk-0 will be for awkward buggers whose attendance spans decades. This needs up
one of these lags attends:
AERW, Becka, Mark Dougherty, Philip Sargent, Chris Densham, Mike Richardson
<p>
Currently (July 2023) the software ignores folk-0, -1, -2 and we have used the old folk.csv for
the 2023 expo. But we hope to have this fixed next year...
<h3>Troggle folk data importing</h3>
<p>
This still needs fixing [Feb.2024]
<p>
Troggle reads the mugshot and blurb about each person.
It reads it direct from folk.csv which has fields of URL links to those files.
It does this when troggle is run with
<code>python databaseReset.py people</code>
<p>
Troggle generates its own blurb about each person, including past expeditions and trips
taken from the logbooks (and from parsing svx files)
A link to this troggle page has been added to folk/index.htm
by making it happen in make-folklist.py
<p>
Troggle scans the blurb and looks for everything between &lt;body&gt; and &lt;hr&gt;
to find the text of the blurb
(see <var>parsers/people.py</var>)
<p style="margin:20px">
[This now seems to have have been fixed (July 2023):<ul><li>
All the blurb files have to be .htm - .html is not recognised by people.py
and trying to fix this breaks something else (weirdly, not fully investigated).
<li>
There seems to be a problem with importing blurbs with more than one image file, even those the code
in people.py only looks for the first image file but then fails to use it.]</ul>
<h3>Issues</h3>
<ul>
<li>The 2025 code and csv format update which allows both mugshots and blurbfiles to exist independently is not properly populated yet in the folk.csv file. The url of the mugshot (one of them: ideally the first one is a head portrit) needs to be extracted from the blurbfile and put in explicitly into the folk.csv file
</ul>