expoweb/folk
2025-01-17 22:12:16 +00:00
..
i folklist updates 2025-01-17 22:12:16 +00:00
l 76.htm links fixed to .html 2024-12-17 19:27:45 +00:00
to-do new mugshots 2024-11-08 02:39:41 +00:00
author.htm ../css -> /css 2024-12-16 22:11:42 +00:00
folk-0.csv folk redesign 2021-04-16 01:53:55 +01:00
folk-1.csv folk redesign 2021-04-16 01:53:55 +01:00
folk-2.csv folk redesign 2021-04-16 01:53:55 +01:00
folk.csv folklist updates 2025-01-17 22:12:16 +00:00
index.html folklist updates 2025-01-17 22:12:16 +00:00
mosaic.htm ../css -> /css 2024-12-16 22:11:42 +00:00
mosaic.jpg [svn r3779] Added HTML files. 2001-08-15 20:29:27 +02:00
README.txt folk errors fixed 2025-01-17 21:49:27 +00:00

Convert the folk.csv to fold/index.htm like this:
$ cd :expoweb:/folk
$ python ../scripts/make-folklist.py <folk.csv >index.html

This does some basic validation: it checks that the mugshot
images and blurb HTML files exist.

*** See current outstanding re-design proposal at /handbook/troggle/namesredesign.html ***

Troggle *also* reads the mugshot and blurb about each person.
It reads it direct from folk.csv
It does this when troggle is run with 
python3 databaseReset.py people

but only do that when testing folk import, it leaves the database in a bad state. 
You always need to finish with
python3 databaseReset.py reset
which re-imports everything

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

Troggle scans the blurb and looks for everything between <body> and <hr
to find the text of the blurb
(see :troggle:/parsers/people.py)

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).

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.

PENDING
this is planned to be split:
folk-1.csv will be for old cavers who will not come again, so this file need never be touched.
folk-2.csv will be for recent cavers and the current expo, this needs editing every year

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.

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

Currently (January 2025) the software ignores folk-0, -1, -2 and you will need to use the old folk.csv for 
the 2025 expo. But we hope to have this fixed next year...

ANOTHER redesign proposal:
1. regenerate the index.htm file on the fly by troggle, but using stuff in the database not from the 
folk.csv file.
2. Make it use HTML fragments which can be edited online (using the http://webpage.html_edit idiom) so that Becka can make changes to the text.
3. Properly filter the number of *active* cavers in total (for Becka and grant proposals)

4. Fix the popup mugshots to get one from the /l/ html fragment if that is tehre instead of the /i/image, in fact re-do that whole thing completely: change the folk.csv format to include a link to /l/ AND to /i/