Data Maintenance - new cave id

Expo Data Maintenance

Experts only

The initial cave id, e.g. 2018-dm-07, is chosen by the discoverers the same day as the discovery and usually on the plateau at the cave entrance. Its very first mention in the troggle system would be in one or more of:

a logbook entry (possibly a copy of a callout notice)
a survex file
a wallet entry with scan of in-field handwritten notes

These are temporary identifiers. If the cave is big enough, and after an initial survey, we will apply to the Austrians for an official number. These are usually batched up and requested over the winter after the expedition. When we receive the official "kataster" number, we edit our records. E.g. Homecoming had to be renamed from 2018-dm-07 to 1626-356.

We do not need to go back and edit old logbooks and wallets

Logbooks and wallets are entirely managed by troggle, so a single edit to the troggle 'cave name alias list' at /cave_data/cavealiases.txt is enough.
e.g. ("1626-2018-dm-07", "1626-356"),
See Cave Aliases below for full examples.

We do need to edit the survex files and cave_data filenames

Survex: in the :loser: repo

the survex files must be renamed
many survex files must be edited to match the new names

Troggle: in the :expoweb: repo

The files in :expoweb:/cave_data/ and :expoweb:/entrance_data must be renamed
the folder names in, :expoweb:/1623/, :expoweb:/1626/ etc. must be renamed

Edit the cave_data filenames

more here..

Edit the survex files

more here.. Need to edit this neatly.. taken from:loser:/kataster-renumbering-README.txt

README for renumbering caves using new kataster numbers

e.g. 2023-ASH-15 => 1623-303

NB We are moving the survex files to new directories, but (not yet) moving the cave description and entrance description files.

expoweb/cave_data/1623-2023-ASH-15.html
1. Edit the cave file expoweb/cave_data/1623-2023-ASH-15.html and change to 1623-303
2. Add the new kataster number: 303
3. Leave this untouched: 2023-ASH-15
4. Don't touch the 1623-2023-ASH-15 field for all the entrances

In the loser repo, rename the folder
loser/2023-ASH-15/
to
loser/303/

and then inside that folder rename the file
2023-ASH-15.svx
to
303.svx

And then edit any survex files which refer to that survex data ! (more explanation needed)

Change *fix points in loser/fixedpts/gps/gps23.svx from
*fix 1623.p2023-ASH-15 ...
to
*fix 1623.p303...

This may well not work due to the crapness of the "system" of recording fixed points. Much
time can now be wasted tracking down how the cave is located, furtling around in the innards
of files sprinkled all over the database. Remember that 1626 caves are stored in a completely
different way to 1623 caves.

Now go back and edit all the entrances of the cave to refer to this new *fix point
in the entrance editing page on
/1623/303/303.html
Select each entrance and look at the field
"Tag station: Survex station id, e.g. 1623.p2023-aa-01: "
and change
1623.p2023-ASH-15
to
1623.p303

If there is more than one entrance, this would be
1623.p2023-ASH-15a
to
1623.p303a

for a, b. c etc.

Find all the wallets for this cave
/cave/scans/1623-2023-ASH-15
and in each of them use the wallet edit page to correct the svx file link from
['caves-1623/2023-ASH-15/2023-ASH-15.svx']
to
['caves-1623/303/303.svx']

Cave Aliases

Cave alias names can be edited by any logged-in user using an online form: /cave_data/cavealiases.txt
However, if you make a formatting mistake, all of troggle will break instantly.

go to the webpage https://expo.survex.com/cave_data/cavealiases.txt_edit
Add the alias to some sensible place in this file, e.g. (using the example above)
("2023-ASH-15", "1623-303"),
Save and exit.

adding this alias means that old logbook entries and wallets that refer to '2023-ASH-15' will be redirected to 1623-303 properly.

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.

 # 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%)

        ("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"),

We also use this alias file to cope with cavers using variant spellings for cave names in wallets and logbooks, e.g.

        ("balcony", "1623-264"),
        ("balkon", "1623-264"),
        ("balconhoehle", "1623-264"),
        ("balkonhoehle", "1623-264"),
        ("balkonhohle", "1623-264"),
        ("balconhohle", "1623-264"),
        ("Balkon Hoehle", "1623-264"),

Some troggle pages will use a new alias immediately, others (most, in fact) will not take any notice until after a DatabaseReset is done.

Return to: data maintenance
Return to: expo online systems overview
Troggle index: Index of all troggle documents