mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2025-12-08 14:54:28 +00:00
Cave Alias mechanism documented. - online edit of handbook/computing/newkataster.html [PosixPath('/home/philip/expo/expoweb/handbook/computing/newkataster.html')]
This commit is contained in:
@@ -1,9 +1,88 @@
|
||||
<html><head><title>New Katasetr Number Procedure</title></head><body>
|
||||
<h2>Experts only</h2>
|
||||
<h2 id="tophead">Data Maintenance - new cave id</h2>
|
||||
<h1>Expo Data Maintenance</h1>
|
||||
|
||||
<p>The cave id on discovery, e.g. and on its very first mention in the system, which would be in one or more of:
|
||||
|
||||
|
||||
<h2 id="intro">Experts only</h2>
|
||||
|
||||
<p>The cave id on discovery, e.g. <b>2018-dm-07</b> and on its very first mention in the system, which would be in one or more of:
|
||||
<ul>
|
||||
<li>a logbook entry
|
||||
<li>a survex file
|
||||
<li>a wallet entry with scan of in-field handwritten notes
|
||||
</ul></body></html>
|
||||
</ul>
|
||||
e.g. Homecoming had to be renamed from <b>2018-dm-07</b> to <b>1626-356</b>.
|
||||
|
||||
<h3>We do <em>not</em> need to go back and edit old logbooks and wallets</h3>
|
||||
<p>Logbooks and wallets are entirely managed by troggle, so a single edit to the troggle 'cave name alias list'
|
||||
at <a href="/cave_data/cavealiases.txt">/cave_data/cavealiases.txt</a> is enough.
|
||||
<br />e.g. <var>("1626-2018-dm-07", "1623-356"),</var><br />See <a href="#cavealiases">Cave Aliases</a> below for full examples.
|
||||
|
||||
<h3>We <em>do</em> need to edit the survex files and cave_data filenames</h3>
|
||||
Survex: in the :loser: repo
|
||||
<ul>
|
||||
<li>the survex files must be renamed
|
||||
<li> many survex files must be edited to match the new names
|
||||
</ul>
|
||||
Troggle: in the :expoweb: repo
|
||||
<ul>
|
||||
<li>The files in :expoweb:/cave_data/ and :expoweb:/entrance_data must be renamed
|
||||
<li> the folder names in, :expoweb:/1623/, :expoweb:/1626/ etc. must be renamed
|
||||
</ul>
|
||||
|
||||
|
||||
<h2>Edit the survex files</h2>
|
||||
<p> more here..
|
||||
|
||||
<h2>Edit the cave_data filenames</h2>
|
||||
<p> more here..
|
||||
|
||||
|
||||
<h2 id=cavealiases>Cave Aliases</h2>
|
||||
<p> Cave alias names can be edited by any logged-in user using an online form:
|
||||
<a href="/cave_data/cavealiases.txt_edit">/cave_data/cavealiases.txt</a>
|
||||
<p><em>However</em>, if you make a formatting mistake, all of troggle will <em>break instantly</em>.
|
||||
|
||||
<p>When a lot are being done, as Becka did in 2024 when she got the new kataster numbers 1623-303 to 1623-316, it is a good idea to cross check (or to edit with a macro) the output from git, e.g.
|
||||
<pre><code> # rename caves-1623/{2023-ASH-15/2023-ASH-15.svx => 303/303.svx} (94%)
|
||||
# rename caves-1623/{2023-mg-02/2023-mg-02.svx => 304/304.svx} (90%)
|
||||
# rename caves-1623/{2023-mg-01/2023-mg-01.svx => 305/305.svx} (94%)
|
||||
# rename caves-1623/{2023-ASH-17/2023-ASH-17.svx => 306/306.svx} (94%)
|
||||
# rename caves-1623/{2023-ASH-05/2023-ASH-05.svx => 307/307.svx} (89%)
|
||||
# rename caves-1623/{2023-ASH-08/2023-ASH-08.svx => 308/308.svx} (93%)
|
||||
# rename caves-1623/{2023-ASH-09/2023-ASH-09.svx => 309/309.svx} (94%)
|
||||
# rename caves-1623/{2023-mg-04/2023-mg-04.svx => 310/310.svx} (91%)
|
||||
# rename caves-1623/{2023-ASH-16/2023-ASH-16.svx => 311/311.svx} (93%)
|
||||
# rename caves-1623/{2023-RAWDB-02/2023-RAWDB-02.svx => 312/312.svx} (92%)
|
||||
# rename caves-1623/{2023-RAWDB-01/2023-RAWDB-01.svx => 313/313.svx} (92%)</code></pre>
|
||||
|
||||
to <pre><code> ("2023-ASH-15", "1623-303"),
|
||||
("2023-mg-02", "1623-304"),
|
||||
("2023-mg-01", "1623-305"),
|
||||
("2023-ASH-17", "1623-306"),
|
||||
("2023-ASH-05", "1623-307"),
|
||||
("2023-ASH-08", "1623-308"),
|
||||
("2023-ASH-09", "1623-309"),
|
||||
("2023-mg-04", "1623-310"),
|
||||
("2023-ASH-16", "1623-311"),
|
||||
("2023-RAWDB-02", "1623-312"),
|
||||
("2023-RAWDB-01", "1623-313"),</code></pre>
|
||||
|
||||
We also use this alias file to cope with cavers using variant spellings for cave names in wallets and logbooks, e.g.<pre><code> ("balcony", "1623-264"),
|
||||
("balkon", "1623-264"),
|
||||
("balconhoehle", "1623-264"),
|
||||
("balkonhoehle", "1623-264"),
|
||||
("balkonhohle", "1623-264"),
|
||||
("balconhohle", "1623-264"),
|
||||
("Balkon Hoehle", "1623-264"),</code></pre>
|
||||
|
||||
<p>Some troggle pages will use a new alias immediately, others (most, in fact) will not take any notice until after a DatabaseReset is done.
|
||||
|
||||
<hr />
|
||||
Return to:
|
||||
<a href="/handbook/computing/manual.html">data maintenance</a><br />
|
||||
Return to:
|
||||
<a href="/handbook/computing/onlinesystems.html">expo online systems overview</a><br />
|
||||
Troggle index:
|
||||
<a href="/handbook/troggle/trogindex.html">Index of all troggle documents</a><br /><hr /></body></html>
|
||||
|
||||
Reference in New Issue
Block a user