mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2025-12-07 22:34:37 +00:00
73 lines
3.2 KiB
HTML
73 lines
3.2 KiB
HTML
<html><head><title>CUCC Expedition Handbook: folk.csv redesign</title></head><body>
|
|
<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>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:
|
|
<br>
|
|
folk-1.csv will be for old cavers who will not come again, so this file need never be touched.
|
|
<br>
|
|
folk-2.csv will be for recent cavers and the current expo, this needs editing every year
|
|
|
|
<p>
|
|
The year headings of folk-1 and folk-2 need to be accurate , but they do not need to be
|
|
the same columns. So folk-2 can start in a much later year.
|
|
|
|
<p>
|
|
folk-0 will be for awkward buggers whose attendance spans decades. This needs updating whenever
|
|
one of these lags attends:
|
|
AERW, Becka, Mark Dougherty, Philip Sargent, Chris Densham, Mike Richardson
|
|
|
|
|
|
<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>
|
|
|
|
|
|
|
|
<hr />
|
|
Return to: <a href="trogdesign.html">Troggle design and future implementations</a><br />
|
|
Return to: <a href="trogintro.html">Troggle intro</a><br />
|
|
Troggle index:
|
|
<a href="trogindex.html">Index of all troggle documents</a><br /><hr /></body></html>
|