expoweb/handbook/computing/folkupdate.html
2022-08-31 18:02:23 +03:00

75 lines
3.6 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expedition Handbook: People Update</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body><style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>The list of people on expo</h1>
<p>These are nerd-instructions. Find a nerd if you think this needs to be done.
<h3 id="import">The folk list</a></h3>
<p>This is part of the <a href="newyear.html">"new expo year"</a> preparations.
The folk.csv file is stored on the server under version control in the <var>:expoweb:</var> <a
href="../computing/repos.html">repository</a> in
<code>expoweb/folk/folk.csv</code>
<p>Note that this area is subject to a <a href="../troggle/namesredesign.html">redesign proposal</a>.
<p>Before expo starts the folk.csv file is updated.
<p>Edit folk/folk.csv, adding the new year to the end of the header line, a new column, with just a comma (blank cell) for people
who weren't there, a 1 for people who are there, and a -1 for people who are there but didn't go caving.
This is adding an extra column to every line in the file.
<p>
Add new lines for new people, with the right number of columns.
<p>This process is tedious and error-prone and ripe for improvement especially as expo proceeds and you have many more names to
add. Adding a list of people from the bier book and their aliases (the name in brackets) would be a lot better, but some way to
make sure that names match with previous years would be good.
<p>
Contrary to what you might expect we find that it is much more reliable to edit this using a text editor rather than a spreadsheet
program.
<p>The nerd can log in using the 'expo' userid.
<p>The nerd needs to do this:
<ol>
<li>Upload the edited copy of folk.csv to the server using the version control system.
<li>Log in to the expo server and run the update script (see below)
<li>Watch any error messages scroll by.
<li>Look at the new folk list HTML file at <a href="http://expo.survex.com/folk/">http://expo.survex.com/folk/</a>
<li>Re-run the import script until you have got rid of all the import errors.
</ol>
<p>This is how you login and run the script:
<pre><code>ssh expo@expo.survex.com
cd expoweb/folk
chmod +w index.htm
python ../scripts/make-folklist.py &lt;folk.csv &gt;index.htm
</code></pre>
<p>If there are no errors, you will just see the prompt reappear in your ssh session
and you will see the result online at <a href="http://expo.survex.com/folk/">http://expo.survex.com/folk/</a>.
<p>It is recommended that the nerd does this locally on their own laptop first. It does not need to be an expo laptop, even a
Windows 10 laptop is fine if the script is run in a WSL terminal. The only software you need to install is the default python
package.
<h4>Readme</h4>
<p>The script and CSV file also have a <a href="/folk/README.txt">README.txt</a> file in the folk folder which contains more
detailed coding notes re interactions with other troggle code.
<h4>History</h4>
<p>This bizarre Folk update process is a relic of the pre-troggle "<a href="../website-history.html">script and spreadsheet</a>"
phase of the Expo website.
Another relic is <a href="../troggle/scriptsqms.html">the complex QM process</a>.
The <a href="../survey/onlinewallet.html"><var>wallets.py</var> script</a> actually post-dates troggle, but was written stand-alone
because of the steep learning curve of getting to grips with Django and because troggle in those days was undocumented.
All these will (2021+) eventually be merged into troggle - we hope.
<hr />
</body>
</html>