CUCC Expeditions to Austria: 1976 - 2025

This cave needs to be "katastered". If you have the new number issued by the Austrians, we can do it now.

New kataster no.

Rename the .html files in expoweb

• Edit the 'kataster'number' field inside the cave_data file.
• Edit the 'survex_file' field inside the cave_data file.
• Edit the 'entranceslug' field inside each 'entrance' field in the cave_data file.
• Rename all the files listed above - always do this last otherwise it is hard to automatically discover which edits have not been done.

Rename the cave description directory in expoweb

• Edit all the 'href=' and 'src=' URLS (if they exist) inside all the cave_data and entrance_data files descriptive text to refer to the new directory
• Rename the directory (if it exists) inside the areacode directory, e.g. rename /1623/2015-dl-02/ as /1623/9999/ (if 9999 is the correct new kataster number). Do this last.

Rename the survex directory in loser

• Beware that the capitalisation of the directory name in the loser repo may be different from the cave name in the expoweb repo.
• Find the survex files for this cave and edit the *include inside the survex files to use the new kataster number
• find and edit the '*_station' tags in each entrance_data file and in the fixed points files in the loser repo.
• Rename the survex files
• Run 'cavern caves-1623/9999/9999.svx' and check it all works as you hope
• Run 'cavern caves-1623/caves.svx' and check it all works as you hope

Sort out the *fix point(s) in both loser and in expoweb

• Find the survex station point for each entrance (one or more in each entrance_data file) in expoweb. There are two fields on an Entrance where there might be a location: 'tag_station', or 'other_station'. These refer to a survex survey point, which might be *fix elsewhere or one of the survey points in one of the cave survex files.
• Change the name of each survex point in the relevant survex file in loser (usually done by renaming the *begin/*end block and patching any *equate statements)
• Make the same name change(s) in each entrance (i.e. in each entrance_data file) in expoweb

Without fully parsing the entire survex *include tree (which this code does not do), it is impossible to find the *fix declaration file from the 'station' fields in the entrance_data files. However we conventionally store the *fix in a "known" place, so we try.

Edit these Entrance files:

Check the wallet links to survex files in drawings

Edit these Wallet files

• 2017#54 : survex files ['caves-1623/2015-dl-02/1.svx']
• 2017#55 : survex files ['caves-1623/2015-dl-02/2.svx']
• 2017#56 : survex files ['caves-1623/2015-dl-02/3c.svx']

If doing this manually, it is much easier to do this using the online wallet edit form than to mess with the raw format of the JSON files, which we never touch and so will be unfamiliar to everyone.

Set the historic alias forwarder in expoweb

• Add the line
  ("1623-2015-dl-02", "1623-9999"),
  to the end of the file cave_data/cavealiases.txt (don't forget the comma at the end of the line)

This will cause lots of errors until the cave "1623-9999" has been created by a full database reset OR we can do an online rename of the "Cave" object in the database [code yet to be written] by pressing this button [button not yet implemented].

Finally

• cd loser
  git add *
  git commit -m 'Katastering 1623-2015-dl-02 to 1623-9999'
  git pull
  git push
  cd ../expoweb
  git add *
  git commit -m 'Katastering 1623-2015-dl-02 to 1623-9999'
  git pull
  git push
  
• It is then vital to do a complete databaseReset as troggle has internally indexed all those 1623-2015-dl-02 files, the indexes are now out of date and horrible things will happen when people try to use troggle with any cave that has been altered:
  uv run databaseReset reset K9999
  OR we can do an online rename of the "Cave" object in the database [code yet to be written] by pressing the button above [button not yet implemented].
• Look in the reset import warnings and errors report to see if anything has gone wrong: expo.survex.com/dataissues
  (in fact, look at this before you do any of this, so you can see what chnages.)

Ideal scenario

Ideally you do this renumbering on a standalone instance of troggle running on a ⚒ troggle development laptop and you don't push any of the git commits to the server until you have got all the niggles out of the conversion, i.e. the databaseReset runs locally without any warnings or errors introduced by your renaming and 'cavern' runs without any new survex errors.

Copy this script and edit it to match the directory names on your PC