expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 14:54:28 +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
Download Patch File Download Diff File Expand all files Collapse all files

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).
</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>
<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.)
@@ -37,6 +32,32 @@
find . -not -type d -exec file "{}" ";" | grep CRLF >crlf.txt
`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
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.
<h3>Tunnel files (Drawings)</h3>