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

moving data maintenance text into handbook

Browse Source
This commit is contained in:
Philip Sargent 2023-03-22 13:50:10 +00:00 committed by Wookey
parent 39b96b63b3
commit a8abe8fb47
3 changed files with 51 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/computing/hbmanual1.html
View File

@ -53,6 +53,8 @@ so you cannot use "Edit this page". These pages will not show "Edit this page" i
<p>You link your new page into the handbook by editing another page in which you want to create a link. For example if you have created a new page describing your wonderful new sleeping bag/hammock technique, then you might want to add a link in to <a href="../kitlist.html">Expo Personal Gear List</a>. Unfortunately the "create link" icon (a picture of 3 links of a chain) is disabled in the on-line editor so you would have to click on the HTML icon and insert the link by editing the HTML directly using an <em>&lt;a href="filename"&gt;</em> tag. <p>You link your new page into the handbook by editing another page in which you want to create a link. For example if you have created a new page describing your wonderful new sleeping bag/hammock technique, then you might want to add a link in to <a href="../kitlist.html">Expo Personal Gear List</a>. Unfortunately the "create link" icon (a picture of 3 links of a chain) is disabled in the on-line editor so you would have to click on the HTML icon and insert the link by editing the HTML directly using an <em>&lt;a href="filename"&gt;</em> tag.
<h3>Conventions</h3> <h3>Conventions</h3>
[This should all be moved to a different page as it covers all files and names, just just the handbook pages.]
<h4>Encoding</h4> <h4>Encoding</h4>
<ul> <ul>
<li>We specify that pages are encoded using <a href="https://www.w3schools.com/charsets/ref_html_utf8.asp">UTF-8</a> for all content. <li>We specify that pages are encoded using <a href="https://www.w3schools.com/charsets/ref_html_utf8.asp">UTF-8</a> for all content.

33
handbook/computing/regular.html
View File

@ -23,13 +23,8 @@
<li>Every couple of months, to keep things clean and honest (and to check that the semiautomated OS updates on the server haven't broken anything). <li>Every couple of months, to keep things clean and honest (and to check that the semiautomated OS updates on the server haven't broken anything).
</ul> </ul>
<h2>All files</h2>
<h3>Data entry TO-DO list</h3>
<p>A user-editable online to-do list for data management is now <a href="todo-data.html">part of the expo online systems</a>. Review this regularly to see what needs doing, and please *delete* jobs that have been done.
<h3>Wallets and Surveyscans</h3>
<h4>2020#00</h4>
<p> The <b>#00</b> wallet directory (e.g. /2020/2020<b>#00</b>/ ) contains orphan files that have been found on the expo laptop in odd places, or have been scanned from bits of notebook found inside other documents. Keep an eye on it and re-file the contents as you discover what they are.
<h4>EOL and UTF8</h4> <h4>EOL and UTF8</h4>
<p>This is much less of a problem now that we have nearly all the file uploading done by troggle forms. <p>This is much less of a problem now that we have nearly all the file uploading done by troggle forms.
<p>The most common <a href="https://en.wikipedia.org/wiki/UTF-8">UTF8</a> problem is with files uploaded containing German language umlaut characters which have been encoded using an extended-ASCII code such as ISO-8055-1 or Windows-1251. (All umlauts in webpages and logbook entries should be using &amp;uml;. So this is an issue mostly with survex files and survey files such as topo or tunnel.) <p>The most common <a href="https://en.wikipedia.org/wiki/UTF-8">UTF8</a> problem is with files uploaded containing German language umlaut characters which have been encoded using an extended-ASCII code such as ISO-8055-1 or Windows-1251. (All umlauts in webpages and logbook entries should be using &amp;uml;. So this is an issue mostly with survex files and survey files such as topo or tunnel.)
@ -37,6 +32,32 @@
find . -not -type d -exec file "{}" ";" | grep CRLF >crlf.txt find . -not -type d -exec file "{}" ";" | grep CRLF >crlf.txt
`awk -F: '// {print "dos2unix \"" $1 "\""}' crlf.txt`</code></pre> `awk -F: '// {print "dos2unix \"" $1 "\""}' crlf.txt`</code></pre>
<p>Also a good idea to run on all of expofiles once every few years as many GPX exports <p>Also a good idea to run on all of expofiles once every few years as many GPX exports
The dataset is kept with unix linefeed style. DOS (and mac) files get
checked-in regularly, and from time to time someone uses an editor so
dim that that it makes files mixed-lineend.
<p>
This handy command will unixfy all the DOS-style .svx files int he <var>:loser:</var> repository:
<p>
<pre><code>find . -not -type d -name "*.svx" -exec file "{}" ";" | grep CRLF |
awk '{print $1}' | sed -e 's/:$//' | xargs fromdos -v</code></pre>
It needs 'tofrodos' package installed. 'unix2dos' can be used instead.
See <a href="hbmanual1.html">manual</a> for more on encoding conventions for cave names, filenames and HTML formatting.
<h4>Cave names</h4>
Cave names do not have leading zeros
They are stored by number/ID in the dataset, not by name.
create them like this: <a href="../survey/caveentry.html">Cave Entry</a> and <a href="manual.html">Data Maintenance</a>.
<h3>Data entry TO-DO list</h3>
<p>A user-editable online to-do list for data management is now <a href="todo-data.html">part of the expo online systems</a>. Review this regularly to see what needs doing, and please *delete* jobs that have been done.
<h3>Wallets and Surveyscans</h3>
<h4>2020#00</h4>
<p> The <b>#00</b> wallet directory (e.g. /2020/2020<b>#00</b>/ ) contains orphan files that have been found on the expo laptop in odd places, or have been scanned from bits of notebook found inside other documents. Keep an eye on it and re-file the contents as you discover what they are.
from phones are a bit variable in how they do EOL characters. from phones are a bit variable in how they do EOL characters.
<h3>Tunnel files (Drawings)</h3> <h3>Tunnel files (Drawings)</h3>

22
years/2018/logbook.html
View File

@ -1396,6 +1396,28 @@ Verliessmeinenkompassbeideranderenh&ouml;hle h&ouml;hle. Note the duplicated
h&ouml;hle is necessary. Waypoint in prospecting GPX file. h&ouml;hle is necessary. Waypoint in prospecting GPX file.
Photos uploaded to expofiles/photos/PhilipWithnall. Photos uploaded to expofiles/photos/PhilipWithnall.
} }
<pre>
:loser:/caves-1623/277/prospecting-coordinates.txt
MOVED to logbook. Guessed that this is the right trip.
2018 Philip Withnall
Description (talk to Philip to decipher) Coordinates (UTM, OsmAnd+ on Android, Philip’s phone)
10, no, just a pocket 33N 411932 5283707
11, no, down sloping rift 33N 411940 5283712
12, choked twin shafts 33N 412043 5283693
12, steep scree narrow pitch, needs torch and rope, probably choked 33N 412046 5283663
13, steep rift, floor mostly choked, no draft, need a rope and light, probably choked 33N 412021 5283649
16, deep drippy rift, draft, leg 18m, deeper than that 33N 411954 5283576
16, deep wide rift, 40m+, drippy, promising, 14m disto leg to first ledge 33N 411943 5283565
CUCC OK1 2012 33N 411898 5283590
9, need torch 33N 411879 5283658
8, no 33N 411792 5283631
2017NR02 33N 411873 5283527
6, needs rope and spade 33N 411764 5283545
2, probably not 33N 411787 5283480
1 33N 411804 5283452
2017NR01 33N 411811 5283442
</pre>
<div class="timeug">T/U: 0.0 hours</div> <div class="timeug">T/U: 0.0 hours</div>
<hr /> <hr />