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

removed text to new file - online edit of handbook/troggle/namesredesign.html

Browse Source
This commit is contained in:
Philip Sargent
2025-10-22 16:31:22 +01:00
committed by Expo on server
parent 6e1aa53637
commit 2982cd26a7
1 changed files with 2 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

53
handbook/troggle/namesredesign.html
View File

@@ -20,9 +20,9 @@
<li><a href="#whatold">What we have now</a> <li><a href="#whatold">What we have now</a>
</ul> </ul>
<span style="color:red">This was basically fixed in 2023. A root-and-branch replacement of peoples names with a 'slug' derived from peoples' names. However we still have things we could do to implrove 'folk'</span> <span style="color:red">This was basically fixed in 2023. A root-and-branch replacement of peoples names with a 'slug' derived from peoples' names. However we still have things we could do to improve 'folk'</span>
<ul> <ul>
<li><a href="#otherfolk">Further options for folk</a> <li><a href="folkredesign.html#otherfolk">Further options for folk</a>
</ul> </ul>
<h2 id="why">Names: Why it is a problem</h2> <h2 id="why">Names: Why it is a problem</h2>
@@ -85,57 +85,8 @@ Naturally this failed horribly even for relatively straightforward names such as
</code> </code>
which is a lot easier to maintain. which is a lot easier to maintain.
<h4>Troggle folk data importing</h4>
<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>
<h2 id="otherfolk">Folk: pending possible improvements</h2>
<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
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
<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...
<hr /> <hr />
Return to: <a href="trogdesign.html">Troggle design and future implementations</a><br /> Return to: <a href="trogdesign.html">Troggle design and future implementations</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br /> Return to: <a href="trogintro.html">Troggle intro</a><br />