{% extends "base.html" %} {% block title %}Cave re-labelling from unofficial identifier to official Kataster number {% endblock %} {% block content %}

Cave re-labelling from unofficial identifier to official Kataster number

Cave {{cave.slug|safe}} '{{cave.official_name|safe}}'

{% if cave.kataster_number %} This cave has already been "katastered". area:{{cave.areacode |safe}} number:{{cave.kataster_number |safe}} {% else %} This cave needs to be "katastered". If you have the new number issued by the Austrians, we can do it now.

{% csrf_token %} {{form.as_p}}
{% endif %}

Rename the .html files in expoweb

{{cave_data|safe}}

{% for e in entrance_data %} {{e|safe}}
{% endfor %}

Rename the cave description directory in expoweb

Rename the survex directory in loser

{{loser_name|safe}}/

{% for f in loser_data %}    {{f|safe}}
{% endfor %}

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

Set the historic alias forwarder in expoweb

Finally

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. {% endblock %}