|
|
|
|
@@ -9,56 +9,112 @@
|
|
|
|
|
<h2 id="tophead">CUCC Expedition: Data Maintenance Manual</h2>
|
|
|
|
|
<h1>Expo Data Maintenance Manual</h1>
|
|
|
|
|
|
|
|
|
|
<p><span style="color:red">[This page currently being restructured and edited to make it more appropriate to the task. Many fragments have been moved here but not yet properly edited together. Also there are no links to other pages which will be needed.]
|
|
|
|
|
</span>
|
|
|
|
|
|
|
|
|
|
<h2><a id="manual">Expo data maintenance manual</a></h2>
|
|
|
|
|
<h2><a id="manual">Oh No! Something has changed.</a></h2>
|
|
|
|
|
<p>It happens all the time,
|
|
|
|
|
<ul>
|
|
|
|
|
<li>somebody annoyingly links your new entrance to an existing cave
|
|
|
|
|
<li>or your new discovery is discovered to be the same as something explored in the 1980s
|
|
|
|
|
<li>or two people each created a new online wallet for the same trip
|
|
|
|
|
<li>or somebody didn't read the <a href="../survey/">survey manual</a> carefully enough (tsk.)
|
|
|
|
|
</ul>
|
|
|
|
|
<p>so now you need to fix things.
|
|
|
|
|
|
|
|
|
|
<h2>Do not despair - no nerd needed</h2>
|
|
|
|
|
<p>OK, <em>probably</em> what you need is written up somewhere in the 7-stage '<a href="">complete process for recording cave data</a>', possibly in one of the side-pages which you skipped through when you read it.
|
|
|
|
|
|
|
|
|
|
<p>You already have the <a href="#password">password</a>, so just using troggle web pages you can already
|
|
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
<li>This page is for cavers wanting to edit any expo data on their own machine. So that's the website, survey data, or drawn up surveys</li>
|
|
|
|
|
<li>This page is <i>not</i> for cavers wanting to know how to type in logbooks or upload photographs or edit data on the expo laptop.
|
|
|
|
|
|
|
|
|
|
<li>There is another page with more info on <a href="#yourownlaptop">the software expo uses and setting up your own laptop</a>.
|
|
|
|
|
<li>Edit any existing survex files, save them, and run survex on them <em>on the server</em>
|
|
|
|
|
<li>Create entirely new survex files, including creating intermediate subdirectories (see below)
|
|
|
|
|
<li>Edit the cave description text and technical data fields for existing caves
|
|
|
|
|
<li>Edit the entrance description text and technical data fields for existing caves
|
|
|
|
|
<li>Create new entrances on existing caves
|
|
|
|
|
<li>Reconnect an entrance to a different cave
|
|
|
|
|
<li>Edit HTML to add an existing uploaded photo into the description text for an extrance or cave
|
|
|
|
|
<li>Create entirely new caves in the system by filling out online forms
|
|
|
|
|
<li>Upload scanned notes to an online wallet
|
|
|
|
|
<li>Edit any HTML page in the online handbook: correct errors, update phone numbers
|
|
|
|
|
<li>Edit the HTML of any online expo logbook
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h3>Data maintenance task list</h3>
|
|
|
|
|
<p>We have an online list of outstanding data maintenance tasks. See the <a href="contribute.html#surveydata">'Survey Data' to-do</a> list
|
|
|
|
|
|
|
|
|
|
<h3><a id="usernamepassword">Getting a username, password and key</a></h3>
|
|
|
|
|
|
|
|
|
|
<p>You don't need a password to view most things, but you will need one to change them.</p>
|
|
|
|
|
<h3>Clever use of Survex file editor</h3>
|
|
|
|
|
<p>You will have seen this when following a link, e.g. from <a href="/survexfile/204">cave 204</a> to <a href="/survexfile/caves-1623/204/nearend/stitchthis.svx">stitchthis.svx</a>.
|
|
|
|
|
<p>But if you hand-edit the address bar in your browser to, say, <br /><a href="/survexfile/caves-1623/2020-W-01/mynewcave.svx">/survexfile/caves-1623/2020-W-01/mynewcave.svx</a> the page will load at that new address and pre-fill the editing window with default survex content. If you edit this in the webpage and then click the "Save this edited svx file' button (you will need to remove all the square brackets while you do that). This will create both the file 'mynewcave.svx' and the directory '2020-w-01' within the existing 'caves-1623' directory on the server in the <var>:loser:</var> repository directory.
|
|
|
|
|
<p>Note that you should have set the '*ref' field correctly to the number of the plastic wallet you are using.
|
|
|
|
|
|
|
|
|
|
<p>Use these credentials for access to the troggle site. The user is 'expo',
|
|
|
|
|
with a cavey:beery password. Ask someone if this isn't enough clue for you.
|
|
|
|
|
<b>This password is important for security</b>. The whole site <strong>will</strong> get hacked by spammers or worse if you are not careful with it. Use a secure method for passing it on to others that need to know (i.e not unencrypted email), don't publish it anywhere, don't check it in to the data management system by accident. A lot of people use it and changing it is a pain for everyone so do take a bit of care.
|
|
|
|
|
<p>You will use this when creating a new survex file from your hand-written notes (but only after you have photographed them and put them in the plastic wallet in the potato hut of course).
|
|
|
|
|
|
|
|
|
|
<p>This is the method you will use when setting <a href="https://survex.com/docs/manual/genhowto.htm">'*equate' and '*export' survey points</a> between different cave surveys to link everything together later, and for adding missing *ref references, correcting the spelling of surveyors' surnames etc.
|
|
|
|
|
|
|
|
|
|
<p>You can also 'move' survex files by the method, with careful use of cut and paste, but you cannot delete them. Also you cannot save an empty file: it has to be a valid survex format and include the required fields *begin and *end.
|
|
|
|
|
|
|
|
|
|
<p>Always click the button: 'Run cavern on this svx file' after you have edited any survex file. This will check that there is no typo and so will not crash the bulk import of 1,200 survex files when troggle starts up.
|
|
|
|
|
|
|
|
|
|
<p>You can create new directories to any depth of nesting by this method - all at once.
|
|
|
|
|
|
|
|
|
|
<p>Editing or creating new survex files means that the <var>:loser:</var> repository will need to be updated [automation of this is a pending task].
|
|
|
|
|
|
|
|
|
|
<h3>Clever use of the Cave editor</h3>
|
|
|
|
|
<em>[ New cleverness to be added in here]</em>
|
|
|
|
|
|
|
|
|
|
<p>Editing or creating cave description data files means that the <var>:expoweb:</var> repository will need to be updated [automation of this is a pending task].
|
|
|
|
|
|
|
|
|
|
<h3>Clever use of Entrance editor</h3>
|
|
|
|
|
<em>[ New cleverness to be added in here]</em>
|
|
|
|
|
|
|
|
|
|
<p>Editing or creating entrance description data files means that the <var>:expoweb:</var> repository will need to be updated [automation of this is a pending task].
|
|
|
|
|
|
|
|
|
|
<h3>Clever use of the Scan Upload form</h3>
|
|
|
|
|
<em>[ New cleverness to be added in here]</em>
|
|
|
|
|
|
|
|
|
|
<p>Editing or uploading scan files is in /expofiles/ and so not in a version-controlled repository [be extra careful].
|
|
|
|
|
|
|
|
|
|
<h3>Clever use of 'Edit this page'</h3>
|
|
|
|
|
<p>You can create new pages as well as edit existing pages. This is all documented in the <a href="/hbmanual1.html">handbook editing manual</a>
|
|
|
|
|
<em>[ New cleverness to be added in here]</em>
|
|
|
|
|
|
|
|
|
|
<p>Editing or creating handbook or logbook HTML files means that the <var>:expoweb:</var> repository will need to be updated [automation of this is a pending task].
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<h3 id="password">The expo password</h3>
|
|
|
|
|
|
|
|
|
|
<p>The username is 'expo',
|
|
|
|
|
with a cavey:beery password. It is written on the notice-board inside the potato hut.
|
|
|
|
|
<b>This password is important</b> - keep it safe.
|
|
|
|
|
<p>The whole site <strong>will</strong> get hacked by spammers or worse if you are not careful with it. Use a secure method for passing it on to others that need to know (i.e not ordinary email), don't publish it anywhere, don't check it in to the data management system by accident. A lot of people use it and changing it is a pain for everyone so do take a bit of care.
|
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<p>This password is all you need to log in to troggle and to use the troggle control panel (very few people need to do this). But if you want to update webpages (a much more common requirement) or to edit the software itself (very rare), then
|
|
|
|
|
you will also need to get a login (register a key with the server). See <a href="keyexchange.html">key-pair setup</a> for details.
|
|
|
|
|
|
|
|
|
|
<p>Pushing cave data to the :loser: and :drawings: <a href="../computing/repos.html">repositories</a> also needs a key. So cavers entering their cave survey data have to use a machine on which this already set up. These machines are
|
|
|
|
|
the <i>expo laptop</i> and the laptop '<i>aziraphale</i>' which live in the potato hut during expo. If you want to use your own laptop then
|
|
|
|
|
see <a href="#yourownlaptop">below</a>.
|
|
|
|
|
|
|
|
|
|
<h3><a id="cavepages">Updating cave pages</a></h3>
|
|
|
|
|
<span style="color:red">
|
|
|
|
|
<p>Public cave description pages are automatically generated by troggle from a set of
|
|
|
|
|
cave files in /cave_data/ and /entrance_data/. These files
|
|
|
|
|
are named <area>-<cavenumber>.html (where area is 1623 or 1626), e.g. /cave_data/1623-115.html
|
|
|
|
|
<p>
|
|
|
|
|
Read the survey handbook section on <a href="../survey/caveentry.html">creating a new cave</a> in the system for instructions on how to name caves and the files you use to recoird them.
|
|
|
|
|
<p>Cave names do not have leading zeros
|
|
|
|
|
They are stored by number/ID in the dataset, not by name.
|
|
|
|
|
<p>Caves with a provisional number consisting of a year and a serial number
|
|
|
|
|
should be hyphenated, thus 2002-04 not 2002_04 or any of the various other
|
|
|
|
|
variants
|
|
|
|
|
|
|
|
|
|
<p>Clicking on 'New cave' (at the bottom of the cave index) lets you enter a new cave. <a href="caveentry.html">Info on how to enter new caves has been split into its own page</a>.</p>
|
|
|
|
|
<p>This password is all you need to log in to troggle. There is also an a systems account 'expoadmin' with a different password which enables the <a href="/controlpanel">import/export control panel</a> for re-importing <em>all</em> the input data files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<p>This may be a useful reminder of what is in a survex file <a href="/expofiles/documents/surveying/survex-guide.pdf">how to create a survex file</a>.
|
|
|
|
|
<h2>Beyond the easy stuff</h2>
|
|
|
|
|
<p>There are several standard data maintenance jobs that haven't yet got trogglized. So if:
|
|
|
|
|
<ul>
|
|
|
|
|
<li>We get a new Austrian kataster number for a cave, so we need to move and rename a lot of files
|
|
|
|
|
<li>A cave has got so big that we need to create sudirectories for the long and complicated cave descriptions in separate HTML files
|
|
|
|
|
<li>Some scanned notes have been uploaded into the wrong online wallet
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
we will need to use the things* installed on the <em>expo laptop</em> or on <a href="basiclaptop.html">your own laptop</a> if you are not in the potato hut on expo. <a href="fzconfig.html">Filezilla</a> will do most of what you need for moving files.
|
|
|
|
|
We also have <a href="uploading.html#android">andftp Android instructions</a> for file manipulation.
|
|
|
|
|
|
|
|
|
|
<p>While Filezilla (including the digital key) is enough for moving files in <a href="/expofiles">expofiles</a>, moving files in the version-controlled <a href="repos.html">repositories</a> means you need to find someone who knows git (see <a href="qstart-git.html">git cheatsheet</a>) to clean up everything after you have finished.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<p>* footnote: the 'things' include the <a href="keyexchange.html">digital key</a> that allows the laptop to be trusted by the server, as well as various installed software.
|
|
|
|
|
<hr />
|
|
|
|
|
Return to:
|
|
|
|
|
<a href="../computing/onlinesystems.html">expo online systems overview</a><br />
|
|
|
|
|
Troggle index:
|
|
|
|
|
<a href="../troggle/trogindex.html">Index of all troggle documents</a><br /><hr />
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
|
|
|
|
|
|
|
|
|
|
Philip Sargent