<p>See <ahref="basiclaptop.html">configuring a Basic laptop</a>.
<h3>With a Survey Laptop</h3>
<p>A survey laptop has Tunnel and Therion, and you use it for cave survey production from raw data. Generally it is not what you use to fix things that have gone wrong - unless what is wrong is simply that something is missing because a job has not been done.
<p>See <ahref="surveylaptop.html">configuring a Survey laptop</a>.
<h3>With a Bulk Update Laptop</h3>
<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>
<p>See <ahref="bulkupdatelaptop.html">configuring a Bulk Update laptop</a>.
we will need to use the things* installed on the <em>expo laptop</em> or on <ahref="basiclaptop.html">your own laptop</a> if you are not in the potato hut on expo. <ahref="fzconfig.html">Filezilla</a> will do most of what you need for moving files.
We also have <ahref="uploading.html#android">andftp Android instructions</a> for file manipulation.
<p>While Filezilla (including the digital key) is enough for moving files in <ahref="/expofiles">expofiles</a>, moving files in the version-controlled <ahref="repos.html">repositories</a> means you need to find someone who knows git (see <ahref="qstart-git.html">git cheatsheet</a>) to clean up everything after you have finished.
<p>* footnote: the 'things' include the <ahref="keyexchange.html">digital key</a> that allows the laptop to be trusted by the server, as well as various installed software.
<p>We have an online list of outstanding data maintenance tasks. See the <ahref="contribute.html#surveydata">'Survey Data' to-do</a> list
<h3>Clever use of Survex file editor</h3>
<p>You will have seen this when following a link, e.g. from <ahref="/survexfile/204">cave 204</a> to <ahref="/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/><ahref="/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>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 <ahref="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 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].
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>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 <ahref="/controlpanel">import/export control panel</a> for re-importing <em>all</em> the input data files.
