mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2025-12-08 14:54:28 +00:00
Online edit of cave 1623-2025-ft-02
This commit is contained in:
committed by
Expo on server
parent
7728cedbcf
commit
899d2ed3f1
@@ -37,66 +37,7 @@ Squeeze over constricion gains a second chamber which is choked. No draught, no
|
||||
<equipment>None</equipment>
|
||||
<references></references>
|
||||
<survey>1623.2025-ft-02.svx</survey>
|
||||
<notes>This cave in is the "pending" state.
|
||||
<p>This can happen for 3 reasons:
|
||||
<ul>
|
||||
<li>A reference has been found to this cave id in a survex file, [MOST LIKELY]
|
||||
<li>or on a wallet,
|
||||
<li>or this cave id is listed in the "pending caves" list.
|
||||
</ul>
|
||||
but no <em>Cave Description</em> exists yet [see below]. <p>
|
||||
|
||||
INSTRUCTIONS: <br />
|
||||
Open 'This survex file' elsewhere on this page to find the date and info. Then
|
||||
<ol>
|
||||
|
||||
<li>search in the survex file (<em>caves-1623/2025-ft-02/2025-ft-02.svx</em>) for the *ref to find
|
||||
a relevant wallet, e.g.<a href='/survey_scans/2009%252311/'>2009#11</a> and
|
||||
read the notes image files n the wallet.
|
||||
<ul>
|
||||
<li>Scroll down to the bottom of the wallet page where you will find a list of logbook entries,
|
||||
wallets and survex files which have all been dated to <em>the same day</em>.
|
||||
Check all these to see if there is any other relevant information about this cave.
|
||||
</ul><br><br>
|
||||
|
||||
<li>search in the Expo for that year e.g. <a href='/logreport/2009'>2009</a> to find a relevant logbook entry,
|
||||
remember that the date may have been recorded incorrectly, so check for trips
|
||||
i.e. logbook entries involving the same people as were listed in the survex file,
|
||||
and you should also check the scanned copy of the logbook (linked from each logbook entry page)
|
||||
just in case a vital trip was not fully transcribed (sketch images are missing for many years in the online logbooks).
|
||||
|
||||
<li>check the <a href="/noinfo/cave-number-index">cave number index</a> just in case there are notes for this cave, <br><br>
|
||||
</ol>
|
||||
Then
|
||||
<ol>
|
||||
<li>click on 'Edit this cave' [menu item on the left hand side of this page] to type in the <em>Cave Description</em>
|
||||
and copy the information you find in the survex file, the wallet and the logbook and
|
||||
delete all the dummy default text in the 'Notes' section of the <em>Cave Description</em> - which is the text you are reading now.
|
||||
|
||||
<li>Read the documentation of all the fields on 'Edit this cave' form.
|
||||
It is in <a href='/handbook/survey/caveentryfields.html'>handbook/survey/caveentryfields</a><br><br>
|
||||
|
||||
<li>You will also need to create a new entrance from the 'Edit this cave' page.
|
||||
Ignore the existing dummy one, it will evaporate on the next full import.<br><br>
|
||||
|
||||
<li>When you Submit the Cave form it will create a new file in expoweb/cave_data/ <br><br>
|
||||
|
||||
<li><em>Only now</em> can you edit the entrance info:
|
||||
click on Edit below for the dummy entrance. and then Submit to save it.<br><br>
|
||||
|
||||
- Finally, if there was an entry in the pending list,
|
||||
edit the file '<var>expoweb/cave_data/pendingcaves.txt</var>' to remove
|
||||
the line referring to <br><var>2025-ft-02</var><br> as it is no longer 'pending' but 'done'.
|
||||
Do this using this link: <a href="/cave_data/pendingcaves.txt_edit">edit the pending list</a>. Well Done.
|
||||
</ol>
|
||||
|
||||
<h4>Explanatory footnote</h4>
|
||||
A reference to this cave would be in
|
||||
</ul>
|
||||
<li>A survex file, which is stored in the <var>:loser:</var> repo.
|
||||
<li>A wallet, which is stored in the <var>walletjson</var> folder inside the <var>:drawings:</var> repo.
|
||||
<li> the pending caves file in the <var>:expoweb:</var> repo. Read the notes in <a href='/cave_data/pendingcaves.txt'>pendingcaves.txt</a>
|
||||
</ul></notes>
|
||||
<notes></notes>
|
||||
<length></length>
|
||||
<depth></depth>
|
||||
<extent></extent>
|
||||
|
||||
Reference in New Issue
Block a user