<p>We used to use CAPITAL LETTERS for cave names, e.g. 2014-MF-03, but <b>lower case</b> for the names of files, e.g. 2014-mf-03.svx . However so many people have done the revere that we have stopped caring.
<p>However we do still always use lower case for entrance identifiers 'a', 'b', 'c' etc.
<p>So a new cave would be 2023-ZZ-01 and its entrances would be 2023-ZZ-01a, 2023-Z-01b and 2023-ZZ-01c.
<p>Our generic guidance for typing logbooks, handbook pages etc. applies particularly to cave descriptions and entrance descritpions where we have to be particularly picky about the formats and character encodings, so now read:
<p>The filename <em>must</em> be the name of the cave, with ".html" as a suffix, e.g. 1623-309.html or 1623-2024-XX-01.html . The filename is used by troggle to create the unique identifier for the cave, so don't screw this up.
<dd>(<i>Obsolete - being removed</i>).The Kataster area (always 1623, 1624, 1626 or 1627). This will <em>always</em> be the first 4 characters of the filename. We don't use this field any more, we read the kataster area from the filename.
<dd>(<i>Either this or unofficial_number is required</i>). Offical number in Austrian kataster if one has been allocated.</dd>
</dl>
<dl>
<dt>unofficial_number</dt>
<dd>(<i>Either this or kataster_number is required</i>). Initial temporary cave ID used until kataster number is allocated. (e.g. 2012-DD-01) If you do not give this (or the kataster_number if issued) then your cave <em>will not appear</em> in the caves list (<ahref="http://expo.survex.com/caves">Main Index/caves</a>).</dd>
</dl>
<dl>
<dt>entrance</dt>
<dd>Enclosing tag for each entrance, containing an entranceslug ID and a letter (if more than one entrance)</dd>
<dd>Internal ID to refer to each entrance instance in the entrance files (must be the same as that filename (e.g. 1623-161a in entrance_data/1623-161a.html). </dd>
<dd>Leave blank for single-entrance cave. If there is more than one entrace then the letter needs to be given. This must be the same as the last character of the filename e.g. a for entrance_data/1623-161a.html or nothing at all for entrance_data/1623-114.html which has no letter.</dd>
<dd>Club (CUCC) and year(s) of exploration. To distinguish from caves explored by foreign groups. Names can be given too if it was a small cave. HTML freeform field.</dd>
<dd>Underground description (the description of the approach and entrance goes in entrance file). For a small cave this will be the entire description. For larger caves it will be the front page of the description, or a short intro, containing links to other pages with the cave description in. You can leave this field empty and put a filename in description_file instead, in which case that will be used. HTML freeform field.</dd>
<dd>For a small cave, summary of gear needed to descend. For longer caves it could be blank, a table, or just refer to the description/topos. Leave blank if this info is in the description. HTML freeform field.</dd>
<dd>Drawn-up surveys. Scans of paper surveys or images/PDFs of electronic surveys. Should include HTML to display current plan and elevation, with links to larger versions (See section on URLs and files). Could list links to multiple years of survey, or even a separate survey page if it's complicated enough. HTML freeform field.</dd>
<dd>Normally empty but can be used for notes on process of getting cave into Austrian kataster. (e.g. 'Too small to be in Kataster', 'Number applied for on 'date', awaiting allocated number). HTML freeform field.</dd>
<dd>A text field: set to 'In dataset' if there is a survex file in the right plac ein the Loser repository. Blank if not, or notes about status such as 'surveyed, but no entrance fix so not yet in dataset'. HTML freeform field.</dd>
<dd>Cave length. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) We should probably scrap this field.</dd>
<dd>Cave depth. Can be left blank and system should fill it in automatically from survey data (it doesn't yet) We should probably scrap this field.</dd>
<dd>Cave extent(as defined by survex. Not very useful. Best left blank and system could fill it in automatically from survey data (it doesn't yet). We should probably scrap this field.</dd>
<dd>Name of top-level survex file for this cave. Relative to the 'loser' <ahref="../computing/repos.html">survex repository</a>. So for most caves that's <tt>caves-{area}/cavenum/cavenum.svx</tt> e.g. 'caves-1623/204/204.svx'</dd>
<dd>Filename: the name of top-level description file for this cave, when a separate file is used. Used instead of above entrance_description field for large caves with complex descriptions. Blank if the description is in the 'underground_description' field. </dd>
<dd>(<i>Obsolete</i>). URL of this cave. i.e the URL this cave appears at on the website. It is now fixed as <tt>area/cavenum/cavenum.html</tt> e.g '1623/165/165.html' or '1626/2023-BL-10/2023-BL10.html'. This is no longer something the user inputs and it is ignored during file import if it is there</dd>.
These are XML files, not HTML files, using special tags which are used by the online system to create the webpages in combination with numerical survey data. Instructions are within each file. These are copies (and may be out of date), the master copies are in troggle/templates/dataformat/ .
