expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

updates - online edit of handbook/troggle/trogdesign.html

Browse Source
This commit is contained in:
Expo on server 2023-09-05 10:01:33 +01:00
parent fa3cbb51c9
commit bb45b76226
1 changed files with 13 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
handbook/troggle/trogdesign.html
View File

@ -17,7 +17,7 @@
<li><h4><a href="#change">New Things Troggle will need to Manage</a></h4>
<li><h4><a href="#specific">Specific, Immediate problems</a></h4>
</ul>
<p><em>Updated: 3 August 2022</em>
<p><em>Updated: 5 September 2023</em>
<h2 id="fail">Things Troggle Doesn't Do</h2>
<p>Mostly these are not just a problem just with troggle, but things where expo procedures have never been
@ -26,7 +26,7 @@ enough to persist with.
<h3>Finding and identifying entrances</h3>
<p>This is abolutely crap. We have a manual, undocumented, probably incomplete offline set of scripts which
produced a GPX file in 2019,
produced a GPX file in 2019 and again in 2023 (Mark Shinwell),
which we have no easy way of delivering to a mobile device.
The troggle pages for the cave and entrance descriptions do not have any location information on them, as it
is generated quite separately from the survex files and fixed-points. And it is all in Austrian grid coordinates not WGS84 too.
@ -54,12 +54,10 @@ which is different for every machine as we have no recommended standard setup.
<p>We have no procedure for this. And also no proper procedures (or even agreed single final location) for rigging topos either. We have a bucket folder for final drawn-up surveys on expofiles.
<h3>Use with Common Social Media</h3>
<p>The 2019 expo was documented on two different blogs and the content has still not got copied into
our own expo logbooks. One of these is UK caving, and for one post the caver used an ephemeral
location for the illutrating photographs - which were very good. We have these archived on expofiles
somewhere. [We now have a documented, but convoluted, procedure for managing this, see <a href="/handbook/computing/log-blog-parsing.html">log-blog-parsing</a>.]
<p>The 2019 expo was documented on two different blogs. One of these is UK caving, and for one post the caver used an ephemeral
location for the illutrating photographs - which were very good. [We now have a documented, but convoluted, procedure for managing this, see <a href="/handbook/computing/log-blog-parsing.html">log-blog-parsing</a>.]
<p>We seem to have lost the expo twitter account credentials.
<p>We have an expo Facebook account.
<p>We have an expo Facebook account (deprecated as many Expo users hate FB)
<p>We used to use Slack and (in 2022) use Trello for expo organisation. We have moved from Slack to
Element, which we can archive ourseleves, and maybe we can use Kanboard (ditto) next year instead of Trello.
@ -71,18 +69,17 @@ Element, which we can archive ourseleves, and maybe we can use Kanboard (ditto)
capital letters or other names or initials). See the design document <a href="namesredesign.html">handling people's names properly</a>.
<h3>Writing Cave Descriptions</h3>
<p>In 2022 we have a working online form to create or edit the cave and entrance descriptions. But the URL
<p>Since 2022 we have a working online form to create or edit the cave and entrance descriptions. But the URL
namespace of the form is different from where the cave description will be actually published, so getting
the A HREF tags and IMG SRC tags correct for the referenced passage text and photos, and also to relevant
bits of logbook, is unnecessarily convoluted.
<p>This needs a small but significant re-design.
<p>We have an incresing number of "pending" caves where we have some data about them, but nobody has written even the beginnings of a cave description file. See the pending list from the most recent import in <a href="/dataissues">caves</a>.
<p>Martin added image-adding to the HTML editor which helps a lot.
<p>We have an increasing number of "pending" caves where we have some data about them, but nobody has written even the beginnings of a cave description file. See the pending list from the most recent import in <a href="/dataissues">caves</a>.
<h3>Consistency Checking between Input Sources</h3>
<p>We have a manual, offline, poorly-documented script <a
href="scriptscurrent.html#survex">check-xml.sh</a> which does some checks on Tunnel file references
to survex files. We have the beginnings of a parser to do the same for Therion drawings. These are
currently no better than proof-of-concept and need to be rewritten in troggle.
<p>The input parser 'drawings' does some very-limited checks on Tunnel file references
to survex files. Problems are reported in <a href="/dataissues">DataIssues</a> and links to wallets in <a href="/dwgfiles/">expo.survex.com/dwgfiles/</a>. We have the beginnings of a parser to do the same for Therion drawings. These are
currently no better than proof-of-concept.
<p>We could do with reports that identify survex files with no equivalent logbook entry (which would show
up all the ARGE surveys, but we could filter those out).
<p>We could do with finding drawn-up Tunnel and Therion files with no documented link to their source data
@ -110,7 +107,7 @@ special-purpose front-end yet.
and there are extensive previous discussions on <a href="https://app.slack.com/client/TQF95LK8T/CSCD0HW3S/thread/CQUM4L3HD-1579458900.001800">Slack</a>.
<h3>Expofiles archiving</h3>
The <a href="/expofiles">expofiles</a> folders are 40 GB of folders with no documnted archiving or backup procedures.
The <a href="/expofiles">expofiles</a> folders are 40 GB of folders with no documented archiving or backup procedures.
Informally, several expo nerds have complete copies, but some better means of managing it are overdue.
<h3>Fossil Software that needs Replacing</h3>
@ -124,7 +121,7 @@ survex files, and the names of expoers in the logbooks. These are inconsistently
<strike>
<p>We have half a dozen different <b>logbook HTML dialects</b> for different eras of expo logbooks. These should be
converted into one, simpler form. Then we can reduce the size of the logbooks parsers substantially.
</strike> We now (March 2023) have just one logbook format in use, but one old logfile (1979) is still in an old format and needs to be converted.
</strike> We now (March 2023) have just one logbook format in use, and the last old logbook has been converted (Sept.2023).
<p>We have the HTML folder structure for complex caves in the same <b>URL namespace as the cave descriptions</b>
generated by troggle. This is a fossil from when the cave descriptions were actual HTML files (generated