These are nerd-instructions. Find a nerd if you think this needs to be done. + +
This is part of the "new expo year" preparations.
+The folk.csv file is stored on the server under version control in the ::expoweb:: repository in
+expoweb/folk/folk.csv
+
+
Before expo starts the folk.csv file is updated. + +
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. +
+Add new lines for new people, with the right number of columns. + +
This process is tedious and error-prone and ripe for improvement especially as expo proceeds and youhave 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. + +
+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. + +
The nerd can log in using the 'expo' userid. + +
The nerd needs to do this: +
This is how you login and run the script: +
ssh expo@expo.survex.com
+cd folk
+python ../scripts/make-folklist.py <folk.csv >index.htm
+If there are no errors, you will just see this on your ssh session: + +
+ +
And you will see the result online at http://expo.survex.com/folk/. +
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. + +
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.
- -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.
+Edit folk/folk.csv according to the instructions in the Folk Update process +
Return to the main online systems manual. diff --git a/handbook/logbooks.html b/handbook/logbooks.html index 10de1e03f..bd1fc86cc 100644 --- a/handbook/logbooks.html +++ b/handbook/logbooks.html @@ -1,5 +1,7 @@ + +As soon as possible after a trip finishes, a hand-written write-up of the trip is made in the nearest logbook: -the base camp logbook or the top camp logbook. All these logbook entries are then typed into a laptop (often the expo laptop) -which is then synchronised the version control system. +the base camp logbook or the top camp logbook. -
Recent logbooks:
The logbook writeup is the oldest and most basic way of recording your trip but it must not be neglected. This is also where you put your speculations and ideas for what looks promising and what is obvious but doesn't go: things that are vital to future expoers. And please, please do lots of sketches in the logbook. -
If you are at basecamp, then it is an excellent idea to -type your logbook trip report instead of writing it by hand - see below. - - -
The contents of both the topcamp logbook and the basecamp logbook are typed into the same -"logbook.html" file for archiving. The drawings are scanned and stored in the same place, and hand-edited -into the logbook.html file after expo finished. +
Always, always write the date, your name and the names of other people involved at the top of each entry. +If you mention a cave location, please also write down the cave name somewhere. In 10 years no-one will know +where "Lemon Snout" is.
If this is all new to you, please now read Cave data management, and why we make surveys and then the Survey Handbook + +
If you are at basecamp, then it is an excellent idea to +type the text of your logbook trip report instead of writing it by hand - see below. But still do lots of drawings in the paper logbook. + + +
The contents of both the topcamp logbook and the basecamp logbook are typed into the same +"logbook.html" file for future use in tracking down leads and surveys. The drawings are scanned and stored in the same place, and hand-edited +into the logbook.html file after expo finished. The typed notes are uploaded into the expo server database and +correlated with survey data done on the same day or by the same people. + + + +
Recent logbooks: +
+All these logbook entries are then typed into a laptop (often the expo laptop) +which is then synchronised the version control system. +
The result is a webpage reporting who did what and what was done by whom on expo, +e.g. see the 2018 expo report. +
If you are at basecamp, then it is an excellent idea to type up your logbook trip report. You can then print this and stick it in the logbook, adding any sketches by hand. @@ -60,11 +84,13 @@ Then start it up again from the vertical icon menu as before.
Now type in your trip report using whatever format you like, but please leave a blank line between paragraphs. -
If you are using the expo laptop just edit this file: -
-/home/expo/expoweb/years/2018/logbook.html -+
If you are using the expo laptop just edit this file (if you are on expo in 2025):
+
+
+/home/expo/expoweb/years/2025/logbook.html
+
+
copy the format you can see other people have used;
and other people will take care of synchronising it with the version control system.
@@ -83,46 +109,84 @@ ensure that the updates from all the people entering trip data are OK and don't
Logbooks are typed up and kept in the [expoweb]/years/[nnnn]/ directory as 'logbook.html'.
-Rather than editing logbook.html when you type up your trip, it is a much better idea to type up just your trip(s) in a separate file, e.g. "logbook-mynewtrip.txt", and email it to a nerd if you are sitting at a different laptop. -
Do whatever you like to try and represent the logbook in html. The only rigid structure is the markup to allow troggle to parse the files into 'trips':
-
+
<div class="tripdate" id="t2007-07-12B">2007-07-12</div>
<div class="trippeople"><u>Jenny Black</u>, Olly Betts</div>
<div class="triptitle">Top Camp - Setting up 76 bivi</div>
-<div class="timeug">T/U 10 mins</div>
-
+<div class="timeug">T/U 10 mins</div>
Note that the ID's must be unique, so are generated from 't' plus the trip date plus a,b,c etc. when there is more than one trip on a day.
T/U stands for "Time Underground" in hours (6 minutes would be "0.1 hours").
Older logbooks (prior to 2007) were stored as logbook.txt with just a bit of consistent markup to allow troggle parsing.
The formatting was largely freeform, with a bit of markup ('===' around header, bars separating date,
So the format should be:
-
-===2009-07-21|204 - Rigging entrance series| Becka Lawson, Emma Wilson, Jess Stirrups, Tony Rooke===
-
-<Text of logbook entry>
-
+
+===2009-07-21|204 - Rigging entrance series| Becka Lawson, Emma Wilson ===
+
+{Text of logbook entry}
+
T/U: Jess 1 hr, Emma 0.5 hr
-
+
+This is usually done after expo but it is in excellent idea to have a nerd do this a couple of times during expo to discover problems while the people are still around to ask. + +
The nerd needs to login to the expo server using their own userid, not the 'expo' userid. The nerd also needs to be in the group that is allowed to do 'sudo'. + +
The nerd needs to do this: +
The procedure is like this. It will be familiar to you because +you will have already done most of this for the Folk Update process. + +
ssh {youruserid}@expo.survex.com
+cd ~expo
+cd troggle
+sudo python databaseReset.py logbooks
+It will produce a list of errors like this, starting with the most recent logbook which will be the one for the expo you are working on. +You can abort the script (Ctrl-C) when you have got the errors for the current expo that you are going to fix +
Loading Logbook for: 2017
+ - Parsing logbook: 2017/logbook.html
+ - Using parser: Parseloghtmltxt
+Calculating GetPersonExpeditionNameLookup for 2017
+ - No name match for: 'Phil'
+ - No name match for: 'everyone'
+ - No name match for: 'et al.'
+("can't parse: ", u'\n\n<img src="logbkimg5.jpg" alt="New Topo" />\n\n')
+ - No name match for: 'Goulash Regurgitation'
+ - Skipping logentry: Via Ferata: Intersport - Klettersteig - no author for entry
+ - No name match for: 'mike'
+ - No name match for: 'Mike'