expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 23:04:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

New docum. and logbook/blog update

Browse Source
This commit is contained in:
Philip Sargent
2022-12-17 18:34:39 +00:00
parent 2dfcc42bd4
commit 8d3f22f1ad
8 changed files with 2066 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
handbook/computing/logbooks-parsing.html
View File

@@ -23,6 +23,12 @@
<p>Ideally this would all be done on a stand-alone laptop to get the bugs in the logbook parsing sorted out before we upload the corrected file to the server. Unfortunately this requires a full troggle software development laptop as the parser is built into troggle. The <var>expo laptop</var> in the potato hut is not set up to do this (yet - 2022).
<p>However, the <var>expo laptop</var> (or any 'bulk update' laptop) is configured to allow an authorized user to log in to the server itself and to run the import process directly on the server.
<h4>Importing the Blog</h4>
<p>During expo lots of people post text and photos to the UK Caving (rope competition) website. During the winter after expo, an extra nerd task is to fold in all those entries into the main logbook so that
the trips are indexed and we can see who was doing what where.
<p>This is sufficiently complicated that it is documented
<a href="log-blog-parsing.html">in another page</a>. But read this page first.
<h4>Current situation</h4>
<p>The nerd needs to do this:
<ol>
@@ -76,6 +82,7 @@ which takes between 300s and 15 minutes on the server.
<p>Older logbooks (prior to 2007) were stored as logbook.txt with just a bit of consistent markup to allow troggle parsing.</p>
<p>The formatting was largely freeform, with a bit of markup ('===' around header, bars separating date, <place> - <description>, and who) which allows the troggle import script to read it correctly. The underlines show who wrote the entry. There is also a format for time-underground info so it can be automagically tabulated.</p>
<p>There were also several previous (different) styles of using HTML. The one we are using now is the 5th variant. These older variants are steadily being reformatted into the current HTML format so that we only need to maintain the code for one parser.
<!--
<p>So the format should be:</p>
@@ -88,8 +95,10 @@ which takes between 300s and 15 minutes on the server.
T/U: Jess 1 hr, Emma 0.5 hr
</code>
-->
<hr />
<p>
<a href="../logbooks.html">Back to Logbooks for Cavers</a> documentation.
Back to <a href="../logbooks.html">Logbooks for Cavers</a> documentation.<br>
Forward to <a href="log-blog-parsing.html">Importing the UK Caving Blog</a>.
<hr />
</body>