expoweb/handbook/troggle/trogmanual.html

60 lines
3.2 KiB
HTML

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Handbook Troggle Intro</title>
<link rel="stylesheet" type="text/css" href="../../css/main2.css" />
</head>
<body>
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Troggle - Maintenance Manuals</h1>
<p>Troggle is the software which runs the the expo cave survey data management and website.
<p>If you are looking for how to manage or correct cave survey data then this is not the right place. You want the
<a href="../computing/manual.html"><em>Data</em> Maintenance</a> manual.
<p>Troggle attempts to be an exemplar of best-practice in Research Software Engineering. See
<a href="https://society-rse.org/about/">The Society of Research Software Engineering</a> founded in 2019. See also the
<a href="https://www.software.ac.uk/about">the UK Software Sustainability Institute</a>.
<p><em>"From short, thrown-together temporary scripts to solving a specific problem, through an abundance of complex
spreadsheets analysing collected data, to the hundreds of software engineers and millions of lines of code behind
international efforts such as the Large Hadron Collider and the Square Kilometre Array, there are few areas of research
where software does not have a fundamental role."</em>
<p>This part of the handbook is intended for people maintaining the troggle <em>software</em>:
<a href="https://www.goodreads.com/book/show/1155986.The_Tricky_Troggle">
<img border="1" class="onright" width="150px" src='tricky-troggle.jpg' alt='git logo'/></a>
<ul>
<li><a href="../computing/newyear.html">Annual tasks</a>: preparing for next year, finishing last year.
<li><a href="../computing/regular.html">Regular tasks</a>: housekeeping as surveys are digitised.
<li><a href="trogimport.html">Reimporting data</a>: reloading the database from scratch.
<li><a href="trogdocm.html">Maintain troggle</a> itself. The code is public on repository <a href="../computing/repos.html">:troggle:</a>
<li><a href="scriptsother.html">Other scripts</a> - photos, folk, wallets - not integral parts of troggle.
<li><a href="trogarch.html">Troggle and database</a> architecture: how it all fits together
<li><a href="trogdesign.html">Design decisions</a> inc. troggle replacement e.g. new systems for <a href="menudesign.html">website menus</a>
<li><a href="trogdjango.html">Troggle and django</a> - Upgrading to later django versions
<li><a href="trognotes.html">Programmers' guide</a> - and index to other documentation
</ul>
<p>Troggle is completely unlike any other django installation: it has a database, but the database is rebuilt from files every time it starts.
<p>Most of the data entry into troggle happens during or just after the expedition: i.e. once a year.
><p>but do also scan
<ul>
<li><a href="trogindex.html">Index of all troggle documents</a> - list of everything you can do with troggle.
</ul>
<p>* "Troggle eats just one very big meal a year."
<hr />
Go on to: <a href="trogarch.html">Troggle architecture</a><br />
Return to: <a href="trogintro.html">Troggle intro</a><br />
Troggle index:
<a href="trogindex.html">Index of all troggle documents</a><br />
<hr /></body>
</html>