expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-01-18 00:42:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

rename Blaubeer slug field with different capitalisation

Browse Source
This commit is contained in:
Philip Sargent 2023-09-26 18:32:59 +03:00
parent 9ce56f1103
commit 6c6b3f8ab1
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cave_data/1623-Blaubeer.html
View File

@ -17,7 +17,7 @@ the form documented at
<cave>
<non_public>False</non_public><!-- 'False' or 'True'. True if the cave should only be visible to logged-in users. Caves are normally public, so enter 'False' unless you know otherwise. -->
<caveslug>1623-BLAUBEER</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<caveslug>1623-Blaubeer</caveslug><!--(Required). Internal I.D. used to refer to this cave in entrance data files. Typically the same as the filebase, e.g. '1623-195' -->
<official_name></official_name><!-- Name of the cave (normally in German) Use &uuml; for u+Umlaut and &ouml; for o+umlaut eg H&ouml;hle for Hohle and Gl&uuml;ck for Gluck-->
<area>1623</area><!-- the CUCC-defined areas shown in http://expo.survex.com/areas.htm -->
<kataster_code></kataster_code><!-- 'length-or-depth/type exploration'
@ -39,7 +39,7 @@ code used in the Austrian kataster e.g '1/S +' - https://expo/.survex.com/katast
<unofficial_number>Blaubeer</unofficial_number><!-- (Either this or kataster_number is required). Initial temporary cave ID used until kataster number is allocated e.g. '2012-DD-01'-->
<entrance>
<entranceslug>1623-BLAUBEER</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<entranceslug>1623-Blaubeer</entranceslug><!-- Internal ID to refer to each entrance instance in the entrance files (typically the same as that filename (e.g. 1623-161c). Matches the 'slug' field in the entrance file -->
<letter></letter><!--Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. Generally matches the entranceslug ID. -->
</entrance>

2
entrance_data/1623-BLAUBEER.html → entrance_data/1623-Blaubeer.html
View File

@ -19,7 +19,7 @@ though, you do not need to do a data import as it happens automatically -->
<br>
<entrance>
<non_public>False</non_public>
<slug>1623-BLAUBEER</slug> <!-- one entrance and one slug per entrance_data file -->
<slug>1623-Blaubeer</slug> <!-- one entrance and one slug per entrance_data file -->
<name></name>
<entrance_description></entrance_description>
<explorers></explorers>