From 6192de94b41911f8cc58c94e141620ae974f860c Mon Sep 17 00:00:00 2001 From: "Philip Sargent (muscogee)" <philip.sargent@gmail.com> Date: Sun, 29 Dec 2019 00:36:42 +0000 Subject: [PATCH] Extracted the bit about creating a new year in the online systems into a separate file --- handbook/computing/newyear.html | 58 +++++++++++++++++++++++++++++++++ handbook/manual.html | 25 ++++++++++++-- 2 files changed, 81 insertions(+), 2 deletions(-) create mode 100644 handbook/computing/newyear.html diff --git a/handbook/computing/newyear.html b/handbook/computing/newyear.html new file mode 100644 index 000000000..20802a363 --- /dev/null +++ b/handbook/computing/newyear.html @@ -0,0 +1,58 @@ +<!DOCTYPE html> +<html> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<title>CUCC Expedition Handbook: Programmers manual</title> +<link rel="stylesheet" type="text/css" href="../../css/main2.css" /> +</head> +<body> +<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2> +<h1>Expo Data Maintenance - Creating a New Year</h1> + +<h2><a id="manual">Creating a New Year in the Expo online systems</a></h2> + +<ul> + +<li>This page <i>is a checklist for programmers</i> who are configuring the systems for next year's expo . +</ul> + +<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 repositories. +<ul> +<li>Create a new folder e.g. /2020/ in each of +<ul> +<li>expoweb/years/ +<li>expoweb/accounts/ +<li>expofiles/videos/ - optional. We don't do this much. +<li>expofiles/writeups/ +<li>expofiles/photos/ +<li>expofiles/gpslogs/ +<li>expofiles/surveyscans/ +</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/2020/ of the form /2020#01/, /2020#02/ etc. +<li>edit /expoweb/index.htm - edit the title and make it link to e.g. expoweb/years/2020/ +<li>edit expoweb/folk/folk.csv - see below +<li>edit troggle/templates/base.html - change the title and adda link to this year's expo +<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/2020/ along with the scanned logbook). +<li>copy the contents of the previous year's expoweb/years/ folder, e.g. /2019/ to 2020/ and edit all the files therein. You should start with at least an index.html and a mission.html +</ul> +<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 were there, and +a -1 for people who were there but didn't go caving. Add new lines for +new people, with the right number of columns.</p> + +<p>This proces is tedious and error-prone and ripe for improvement. +Adding a list of people, from the bier book, and their aliases would be +a lot better, but some way to make sure that names match with previous +years would be +good.</p> + +Return to the main <a href="../manual.htm">online systems manual</a>. + +<hr /> +</body> +</html> + diff --git a/handbook/manual.html b/handbook/manual.html index 0f601ed9e..662a4aec4 100644 --- a/handbook/manual.html +++ b/handbook/manual.html @@ -252,6 +252,7 @@ editing these files.</p> superseded in 2012).</p> <p>This may be a useful reminder of what is in a survex file <a href="survey/how_to_make_a_survex_file.pdf">how to create a survex file</a>. + <h3><a id="updatingyears">Updating expo year pages</a></h3> <p>Each year's expo has a documentation index which is in the folder</p> @@ -264,7 +265,27 @@ superseded in 2012).</p> <p> Once you have pushed your changes to the repository you need to update the server's local copies, by ssh into the server and running hg update in the expoweb folder. </p> -<h3>Adding a new year</h3> +<h3>Adding a new yearin 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. Chnages to expoweb and troggle must be done using the version control system as these are repositories. +<ul> +<li>Create a new folder e.g. /2020/ in each of +<ul> +<li>expoweb/years/ +<li>expoweb/accounts/ +<li>expofiles/videos/ - optional. We don't do this much. +<li>expofiles/writeups/ +<li>expofiles/photos/ +<li>expofiles/gpslogs/ +<li>expofiles/surveyscans/ +</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/2020/ of the form /2020#01/, /2020#02/ etc. +<li>edit /expoweb/index.htm - edit the title and make it link to e.g. expoweb/years/2020/ +<li>edit expoweb/folk/folk.csv - see below +<li>edit troggle/templates/base.html - change the title and adda link to this year's expo +<li>create initial versions of the bierbook and the seshbook in expoweb/documents/bierbook +<li>copy the contents of the previous year's expoweb/years/ folder, e.g. /2019/ to 2020/ and edit all the files therein. You should start with at least an index.html and a mission.html +</ul> <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 were there, and @@ -272,7 +293,7 @@ a -1 for people who were there but didn't go caving. Add new lines for new people, with the right number of columns.</p> <p>This proces is tedious and error-prone and ripe for improvement. -Adding a list of people, fro the bier book, and their aliases would be +Adding a list of people, from the bier book, and their aliases would be a lot better, but some way to make sure that names match with previous years would be good.</p>