initial rename script textarea

1 files changed, 14 insertions, 4 deletions

diff --git a/templates/cave_kataster.html b/templates/cave_kataster.html
index eaee28c..771f89e 100644
--- a/templates/cave_kataster.html
+++ b/templates/cave_kataster.html
@@ -75,19 +75,24 @@ This cave needs to be "katastered". If you have the new number issued by the Aus
 
 <h3>Sort out the *fix point(s) in both <var>loser</var> and in <var>expoweb</var></h3>
 <ul style="list-style: disc">
-<li> Find the *fix point for each entrance (one or more in each <samp>entrance_data</samp> file) in <var>expoweb</var>. There are three fields where there might be a *fix value: <samp>'tag_station', 'exact_station'</samp> and <samp>'other_station'</samp>
-
+<li> Find the *fix point for each entrance (one or more in each <samp>entrance_data</samp> file) in <var>expoweb</var>. There are two fields on an Entrance where there might be a location: <samp>'tag_station', or <samp>'other_station'</samp>. 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.
 <li> Change the name of each *fix point in the relevant survex file in  <var>loser</var> 
 <li> Make the same name change(s) in each entrance file (in each <samp>entrance_data</samp> file) in <var>expoweb</var>
 </ul>
 <p>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 <samp>'station'</samp> fields in the entrance_data files. However in area 1623 we conventionally store the *fix in a "known" place. This does not work for area 1626.
+<p>Edit these Entrance files:<br />
+{% for e in entrances %}
+<samp>
+{{e}}.html<br />&nbsp;&nbsp;&nbsp;{% if e.tag_station%}</samp>tag_station: <samp>{{e.tag_station}}{% endif %}
+{% if e.other_station%}</samp>other_station: <samp>{{e.other_station}}{% endif %}<br /><samp>
+{% endfor %}
 
 <h3>Set the historic alias forwarder  in <var>expoweb</var></h3>
 <ul style="list-style: disc">
 <li> Add the line <br /><samp>("{{cave.slug|safe}}", "<span style="color:blue">{{cave.areacode |safe}}-{{knum}}</span>"),</samp></br /> to the end 
 of the file <var><a href="/cave_data/cavealiases.txt_edit">cave_data/cavealiases.txt</a></var> (don't forget the  comma at the end of the line)
 </ul>
-<p>This will cause lost of errors until the cave <samp>"<span style="color:blue">{{cave.areacode |safe}}-{{knum}}</span>"</samp> has been created by a full database reset.
+<p>This will cause lots of errors until the cave <samp>"<span style="color:blue">{{cave.areacode |safe}}-{{knum}}</span>"</samp> 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].
 <!--or by editing & saving the cave description page <a href="/{{cave.areacode |safe}}/{{knum}}">/{{cave.areacode |safe}}/{{knum}}</a> after renaming. (Editing a cave description page regenerates some of the internal indices.)
 -->
 
@@ -105,7 +110,8 @@ git pull<br />
 git push<br />
 </samp>
 <li>It is then vital to do a complete databaseReset as troggle has internally indexed all those {{cave.slug}} 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:<br />
-<samp>uv run databaseReset reset <span style="color:blue">K{{knum}}</span></samp>
+<samp>uv run databaseReset reset <span style="color:blue">K{{knum}}</span></samp><br />
+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].
 <li>Look in the reset import warnings and errors report to see if anything has gone wrong:
 <var><a href="http://expo.survex.com/dataissues">expo.survex.com/dataissues</a></var><br />
 (in fact, look at this before you do any of this, so you can see what chnages.)
@@ -114,4 +120,8 @@ git push<br />
 <h3>Ideal scenario</h3>
 <p>
 <p>Ideally you do this renumbering on a standalone instance of troggle running on a <var> &#9874; <a href="/handbook/troggle/troglaptop.html">troggle development laptop</a></var> 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 <em>and</em> 'cavern' runs without any new survex errors.
+<p>
+<textarea id="script" name="script" rows="15" cols="100" style="font-size:small">
+{{script}}
+</textarea>
 {% endblock %}