Creating Expo 2021 and documenting annual updates

This commit is contained in:
Philip Sargent 2021-02-05 20:08:22 +00:00
parent dc26f5f1be
commit 79bfb742a4
4 changed files with 38 additions and 47 deletions

31
.gitignore vendored
View File

@ -439,35 +439,10 @@ svx-refs.ok.html
expofiles
.vscode/
years/2019/logbook.html.cache
years/2018/logbook.html.cache
years/2010/logbook.html.cache
years/2011/logbook.html.cache
years/2012/logbook.html.cache
log.htm.cache
logbook.html.cache
years/2009/2009logbook.txt.cache
years/2007/logbook.html.cache
years/2006/logbook/logbook_06.txt.cache
years/2001/log.htm.cache
years/2002/logbook.html.cache
years/2003/logbook.html.cache
years/2004/logbook.html.cache
years/2005/logbook.html.cache
years/2008/2008logbook.txt.cache
years/2013/logbook.html.cache
years/2014/logbook.html.cache
years/1993/log.htm.cache
years/1994/log.htm.cache
years/1995/log.htm.cache
years/1991/log.htm.cache
years/2000/log.htm.cache
years/2015/logbook.html.cache
years/2016/logbook.html.cache
years/1996/log.htm.cache
years/2017/logbook.html.cache
years/1992/log.htm.cache
years/1999/log.htm.cache
years/1997/log.htm.cache
years/1998/log.htm.cache
syntax: regexp
years/2006/logbook.html.cache
scripts/make-folklist.py.bak
cripts/make-folklist.py.bak

View File

@ -48,6 +48,12 @@ python ../scripts/make-folklist.py <folk.csv >index.htm
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>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>

View File

@ -18,40 +18,50 @@
<h3>Adding a new year in the Expo online systems</h3>
<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly overwriting what is on the server. Changes to expoweb and troggle must be done using the version control system as these are <a href="../computing/repos.html">repositories</a>.
<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly
overwriting what is on the server. Changes to <var>:expoweb:</var> and <var>:troggle:</var> must be done using the version control
system as these are <a href="../computing/repos.html">repositories</a>.
<h4>Well before Expo as these pages are used in planning</h4>
<ul>
<li>Create a new folder e.g. /2021/ in each of
<li>Create a new <var>expoweb</var> website folder e.g. /2021/ in
<ul>
<li>expoweb/years/
<li>expofiles/writeups/
<li>expofiles/photos/
<li>expofiles/gpslogs/
<li>expofiles/surveyscans/
<li>expofiles/accounts/ - optional. Used for archiving after expo.
<li>expofiles/videos/ - optional. We don't do this much.
</ul>
<li>edit /expoweb/index.htm - edit the title and make it link to e.g. expoweb/years/2021/
<li>edit troggle/templates/base.html - change the title and add a link to this year's expo
<li>copy the contents of the previous year's expoweb/years/ folder, e.g. /2016/ to /2017/ and edit all the files therein. You should start with at least an index.html and a mission.html
<li>edit <var>expoweb/index.htm</var> - edit the title and make it link to e.g. <var>expoweb/years/2021/</var>
<li>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo
<li>copy the contents of the previous year's <var>expoweb/years/</var> folder, e.g. /2016/ to /2017/ and edit all the files therein. You should start with at least an index.html and a mission.html
<li>edit <var>expoweb/folk/folk.csv</var> - see below - to add a column for the coming year. Until that year column exists, the online system will be unaware that there is an expedition that year.
</ul>
<h4>Whenever you like before Expo</h4>
<ul>
<li>copy wallets.py from the previous year's folder in expofiles/surveyscans/ into the current year
<li>create 50 folders in the new surveyscans year folder e.g. in expofiles/surveyscans/2021/ of the form /2021#01/, /2021#02/ etc.
<li>Test that the bierbook and seshbook LaTeX scripts expoweb/documents/bierbook work on your machine</li>
<li>Create new subfolders e.g. /2021/ in <var>expofiles/</var>, in each of
<ul>
<li>expofiles/writeups/
<li>expofiles/photos/
<li>expofiles/gpslogs/
<li>expofiles/surveyscans/
<li>expofiles/accounts/ - optional. Used for archiving after expo.
<li>expofiles/videos/ - optional. We don't do this much.
</ul>
<li>copy <var>wallets.py</var> from the previous year's folder in <var>expofiles/surveyscans/</var> into the current year
<li>create 50 folders in the new surveyscans year folder e.g. in <var>expofiles/surveyscans/2021/</var> of the form /2021#01/, /2021#02/ etc.
<li>Test that the bierbook and seshbook LaTeX scripts <var>expoweb/documents/bierbook</var> work on your machine</li>
</ul>
<h4>A week or so before Expo</h4>
<ul>
<li>create initial versions of the bierbook and the seshbook in expoweb/documents/bierbook (the final copies after expo will be scanned and put in e.g. expofiles/writeups/2021/ along with the scanned logbook). These need an updated names.txt file of expoers.
<li>update the gear tape colours for the expected expoers in <a href="../geartape.html">/expoweb/handbook/geartape.html</a> </li>
<li>edit expoweb/folk/folk.csv - see below
<li>create initial versions of the bierbook and the seshbook in <var>expoweb/documents/bierbook</var>
(the final copies after expo will be scanned and put in
e.g. <var>expofiles/writeups/2021/</var> along with the scanned logbook). These need an updated <var>names.txt<var> file of expoers.
<li>update the gear tape colours for the expected expoers in <a href="../geartape.html"><var>/expoweb/handbook/geartape.html</a> </li>
<li>edit <var>expoweb/folk/folk.csv</var> - see below - to add people. Until a name is recorded in the Folk file that person will not be recognised within the online system as a cave surveyor or logbook entry writer.
<li>Create the Bank of Expo <a href="../bankofexpo.html"><var>boe</var></a> for the expected attendees.
This is done directly in an <var>ssh</var> terminal session on the server.
</ul>
<p>Edit folk/folk.csv according to the instructions in the <a href="folkupdate.html">Folk Update process</a>
<p>Edit <var>expoweb/folk/folk.csv</var> according to the instructions in the <a href="folkupdate.html">Folk Update process</a>.
</p>
Return to the main <a href="manual.html">online systems manual</a>.

View File

@ -13,7 +13,7 @@
<div id="homebox" style="color:black; background-color: rgba(255, 255, 255, 0.6); padding: 1% 5% 5%; margin-right:10%">
<h1 style="color:black">CUCC in Austria <a style="color:black" href="years/1976/report.htm">1976</a>-<a style="color:black" href="years/2020/">2020</a></h1>
<h1 style="color:black">CUCC in Austria <a style="color:black" href="years/1976/report.htm">1976</a>-<a style="color:black" href="years/2021/">2021</a></h1>
<p>Welcome to the website of the <a style="color:black" href="https://camcaving.uk" target="_blank">Cambridge University Caving Club</a> expeditions to Austria</p>