mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 23:31:56 +00:00
115 lines
4.3 KiB
HTML
115 lines
4.3 KiB
HTML
<html>
|
|
<head>
|
|
<title>Expo Systems Exptl. To-Do List</title>
|
|
<meta charset="utf-8">
|
|
</head>
|
|
<body>
|
|
<link rel="stylesheet" type="text/css" href="x-todo-styles.css">
|
|
<h1>Expo Systems Exptl. To-Do List</h1>
|
|
<button onclick="window.location.href = 'x-todo.html_edit';">Update this to-do list</button>
|
|
<label for="toggle-1">Toggle sub-items</label>
|
|
<input type="checkbox" id="toggle-1">
|
|
<h2>Documentation</h2>
|
|
<ul>
|
|
<li>Wallets & new-cave
|
|
<ul>
|
|
<li>Explain (in the wallets process) how to view the surveys
|
|
online so that <br>(1) you can see an example of how to do your new one,
|
|
and <br>(2) so that you can check that you have done it properly when you
|
|
have finished.</li>
|
|
<li>Explain how to link a new cave into the other caves in
|
|
troggle filesystem</li>
|
|
</ul>
|
|
</li>
|
|
<li>Troggle architecture
|
|
<ul>
|
|
<li>Handbook: explain how troggle works - much better and simpler. Fix
|
|
mistakes I wrote. For future system maintainers</li>
|
|
<li>Copy the .wiki material into the documentation somewhere</li>
|
|
</ul>
|
|
</li>
|
|
<li>Surveyscans
|
|
<ul>
|
|
<li>explain where the image files are referenced from: svx, tunnel/therion, and why there are so many broken links</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<h2>Photos</h2>
|
|
<ul>
|
|
<li>Capitalisation in filenames problem
|
|
<ul>
|
|
<li>run the duplicate filename script on the server in
|
|
/photos/xml/ as there are files which differ only in
|
|
capitalisation of their names.</li>
|
|
<li>Fix such duplicates in the /photos/ folders where this
|
|
problem originates</li>
|
|
<li>Document this issue of duplicate photo filenames produced by
|
|
multiple cameras running similar software</li>
|
|
<li>somehow fix the photo filenames which use capital letters on
|
|
import or upload, or by a cron job</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<h2>Surveys data entry</h2>
|
|
<ul>
|
|
<li>2019 surveyscans
|
|
<ul>
|
|
<li>edit all the content.json</li>
|
|
<li>try to autocomplete the content.json by parsing .svx files</li>
|
|
<li>Put personal names into canonical form</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<h2>Troggle</h2>
|
|
<h2>Expo Server</h2>
|
|
<ul>
|
|
<li> www-data:www-data permissions
|
|
<ul>
|
|
<li>Fix permissions so that all files served by troggle have
|
|
www-data:www-data ownership and group ownership, otherwise the
|
|
"Edit this page" fails with a permissions error, or
|
|
</li>
|
|
<li>Or fix group
|
|
membership for the process running django so that it can write
|
|
files owned by 'expo'
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<h2>
|
|
<font color="darkviolet">This to-do-list gadget itself</font>
|
|
</h2>
|
|
<ul>
|
|
<li>Eventual aim
|
|
<ul>
|
|
<li>to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
|
|
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</li>
|
|
<li>We need two of these: <br>1.for expo systems work (troggle & scripts) - the current priority as we have nowhere currently that Wookey is willing to use
|
|
<br>2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit)
|
|
</ul>
|
|
</li>
|
|
|
|
<li>Try to automate simple functions in javascript
|
|
<ul>
|
|
<li>to control this document
|
|
in-place (tick, delete) instead of using the <a
|
|
href="https://www.tiny.cloud/docs/general-configuration-guide/use-tinymce-inline/">
|
|
tinymce</a> HTML editor in Django</li>
|
|
<li>Maybe restructure whole page as JSON and use
|
|
javascript editor to create (edit), re-order and demote items. So long
|
|
as the content is inserted into the DOM, it should work ?</li>
|
|
<li>Implement comments on an issue, mimicking GitHub issues wiki</li>
|
|
<li>Use javascript to skip over the _edit page and submit changes
|
|
direct to server when updating</li>
|
|
<li>checkboxes so that items can be ticked
|
|
(which also does strike-through)</li>
|
|
<li>bin icon to delete an item? Better to have an archive process.</li>
|
|
</ul>
|
|
</li>
|
|
|
|
</ul>
|
|
<hr>
|
|
|
|
</body>
|
|
</html>
|