CUCC Expedition Handbook - Online systems

New Expo Maintenance - Creating a New Year

Creating a New Year in the Expo online systems

• This page is a checklist for programmers who are configuring the systems for next year's expo .
• We are steadily automating these tasks, so the list is shorter every year.

Adding a new year in the Expo online systems

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.

Several troggle pages will automatically notice that it is after 31st December in the year of the most recent expedition, and will helpfully create the things you need for the coming expedition. Not everything though.

Some website pages generated by troggle will fail for the new yearnext expedition until you do the folk-update process to create a new year column (see below). ]

Well before Expo as these pages are used in planning

• Manually edit these HTML pages as lots of other pages link to them and they are not troggle pages. Longer job, replace each of these hard-coded HTML pages with a troggle page.
  • Edit expoweb/infodx.htm with the new year number (top and bottom). - 130 pages link to this...
  • Edit expoweb/pubs.htm with the new year number. - 165 pages link to this...
  • Edit expoweb/index.htm - edit the title and make it link to e.g. expoweb/years/2025/ - 1,212 pages link to this...
• edit troggle/templates/base.html - change the title and add a link to this year's expo.   Now automatic, after 31st Dec.
• edit troggle/templates/walletform.html - change to this coming year   Now automatic, after 31st Dec.
• edit /expedition - change to this coming year   Now automatic, after 31st Dec.
• Create a new expoweb website folder e.g. /2025/ in expoweb/years/   Now automatic, after 31st Dec.
• 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
• edit expoweb/folk/folk.csv - see below - just 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.
• Create the Bank of Expo boe for the expected attendees. This is done directly in an ssh terminal session on the server.

Whenever you like before Expo

• Create new subfolders e.g. /2025/ in expofiles/, in each of
  • expofiles/writeups/
  • expofiles/photos/   Now automatic, after 31st Dec.
  • expofiles/gpslogs/
  • expofiles/accounts/ - optional. Used for archiving after expo.
  • expofiles/videos/ - optional. We don't do this much.
  • expofiles/surveyscans/ - this now happens automatically when a wallet is created
• Test that the bierbook and seshbook LaTeX scripts expoweb/documents/bierbook work on your machine. Or use an online LaTeX system to generate them, e.g. Overleaf.com (free plan, for the moment)

A week or so before Expo

• 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/2025/ along with the scanned logbook). These need an updated names.txt file of expoers.
• update the gear tape colours for the expected expoers in /expoweb/handbook/geartape.html
• edit expoweb/folk/folk.csv - 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.

Edit expoweb/folk/folk.csv according to the instructions in the Folk Update process.