mirror of
https://expo.survex.com/repositories/expoweb/.git/
synced 2024-11-22 07:11:55 +00:00
223 lines
12 KiB
HTML
223 lines
12 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>Expo Systems - To-Do List</title>
|
|
<meta charset="utf-8">
|
|
<meta name="keywords" content="NOEDIT">
|
|
|
|
</head>
|
|
<body>
|
|
<style>
|
|
body {
|
|
background: #fff url(/images/style/bg-system.png) repeat-x 0 0
|
|
}
|
|
/* Use grey for system/programming/nerd pages as a visual reminder */
|
|
</style>
|
|
<script src="todo.js" defer></script>
|
|
<link rel="stylesheet" type="text/css" href="todo-styles.css" />
|
|
|
|
<h1>Expo Systems To-Do List</h1>
|
|
<button onclick="window.location.href = 'todo.html_edit';">Edit this to-do list</button>
|
|
|
|
<!-- ------------------- Don't touch anything above this line --------------------------->
|
|
|
|
|
|
<h2>How this works</h2>
|
|
|
|
<p><b>Click twice on a sub-heading to reveal</b> the individual to-do items. Click again to hide.<br />
|
|
If a heading is in italics, then there are hidden items.
|
|
<p><b>Click on the main "How this works" heading</b> to toggle reveal/hide <b>everything.</b>
|
|
<p>Printing this page uses a much smaller font. Complain to <a href="mailto:expo-tech@lists.wookware.org">the nerd list</a> if you don't like this behaviour.
|
|
|
|
<p>Edit this page by clicking on the big blue button. It uses the same "Edit this page" function that you may have used before. Just be careful not to touch the code at the top and bottom of the page.
|
|
|
|
<p>We are working on a more capable and easier-to-use system which will mimic how <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">GitHub Issues</a> do this sort of thing.
|
|
|
|
<p>To see the "data maintenance" and "survey data-entry" to-do lists, go to <a href="todo-data.html">the other TO-DO list</a>
|
|
|
|
<h3>Process Documentation</h3>
|
|
<dl>
|
|
<dt><!--2020-03-26 psargent-->Wallets and new-cave</dt>
|
|
<dd><!--2020-03-26 psargent-->Explain how to link a new cave into the other caves in
|
|
troggle filesystem</dd>
|
|
<dd><!--2020-03-26 psargent-->Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves</dd>
|
|
<dt><!--2020-04-13 psargent-->svx check</dt>
|
|
<dd>explain command line to run on newly typed survex file to check for format errors '$cavern xxxx.svx'
|
|
<dd>explain when to use svxtrace.py <a href="troggle/scriptscurrent.html">current scripts</a>
|
|
<dd>Making an svx - explain how to make link to *ref to wallet folder
|
|
<dd>explain how to put stuff in the wallet folder and how to look at expofiles/photos/xml/
|
|
<dd>Add to user data manual how to upload to expofiles - in the "survey manual"
|
|
<dd>Add in description of *where* to put the drawings files
|
|
</dl>
|
|
<h3>Surveys data entry documentation</h3>
|
|
<dl>
|
|
<dt>Write code to automatically extract ref info about wallets from tunnel xml files
|
|
<dd><!--2020-04-03 psargent-->This will replace :drawings:chk-xml.txt as used by :drawings:check-xml.sh
|
|
<dd><!--2020-04-03 psargent-->Do similar for Therion files when people start using #REF comments
|
|
|
|
<dt><!--2020-03-26 psargent-->2019 surveyscans
|
|
|
|
<dd><!--2020-03-26 psargent-->edit all the content.json files</dd>
|
|
<dd><!--2020-03-26 psargent-->try to autocomplete the content.json by parsing .svx files</dd>
|
|
<dd><!--2020-03-26 psargent-->Put personal names into canonical form</dd>
|
|
<dt>2014 contents.json
|
|
<dd><!--2020-04-03 psargent-->parse all the svx files to extract people, dates & svx references
|
|
</dl>
|
|
|
|
<h3>Handbook</h3>
|
|
<dl>
|
|
<dt><!--2020-04-11 psargent-->Desperately needs Navigation - Location Context, Situational Awareness
|
|
<dd><!--2020-04-11 psargent-->No overall view of what there is: need a user-friendly diagrammatic overview <a href="https://en.wikipedia.org/wiki/Site_map">sitemap</a>. There are 4,869 files in :expoweb:</dd>
|
|
<dd><!--2020-04-11 psargent-->Not fixed by menus - breadcrumbs needed?</dd>
|
|
<dd><!--2020-04-11 psargent-->Diagrams of major sections: survey handbook, rigging handbook, computing handbook, Areas, cave data..</dd>
|
|
<dd><!--2020-04-11 psargent-->Chase Airoa to help fix <a href="../troggle/menudesign.html">the menus for phones</a></dd>
|
|
<dd><!--2020-04-11 psargent-->Look at <a href="https://www.gov.uk/guidance/government-design-principles">gov.uk guidelines</a> for inspiration</dd>
|
|
|
|
</dl>
|
|
<h3>Areas and prospecting guides</h3>
|
|
<dl>
|
|
|
|
<dt>Areas (these are the sub-areas)
|
|
<dd><!--2020-05-01 psargent-->Downgrade the "areas" aspect of the documentation as we don't use these now
|
|
<dd><!--2020-05-01 psargent-->Add links to these resurrected area guides from relevant other parts of the handbook</dd>
|
|
<dt>Prospecting Guides & slippy map & GPS tracks
|
|
<dd><!--2020-05-01 psargent-->This whole subsystem needs a good examination and possible rewriting. :expoweb:/noinfo/prospecting_guide_scripts
|
|
|
|
|
|
</dl>
|
|
<h3>Photos</h3>
|
|
<dl>
|
|
|
|
<dt><!--2020-04-03 psargent-->Fix the BINS package (Wookey is looking for replacement)
|
|
<dd><!--2020-04-03 psargent-->set up git on the BINS software? Fix base url sautret.org</dd>
|
|
<dd><!--2020-04-03 psargent-->set up a cron / Makefile job to run BINS</dd>
|
|
<dd><!--2020-04-03 psargent-->why is 'updatephotos' script in expofiles? </dd>
|
|
<dd>Document the ~expo/webphotos/ directory and how it works
|
|
<dd>Why does expofiles/photos/xml/ get created containing all the generated xml files? Fix this.
|
|
<dt>galley thumbs etc.
|
|
<dd>:expoweb:/galley/0.htm thumbnails not loading
|
|
|
|
|
|
</dl>
|
|
|
|
<h3>Laptop config.</h3>
|
|
<dl>
|
|
<dt><!-- 2020-04-11 psargent --> imagemagick convert
|
|
<dd><!--2020-04-03 psargent-->Not working for PDFs on current version of xubuntu ! Fix & document. Also not working on WSL ubuntu. Needed to work with logbook images easily & to extract PDFs, JPEGs. Need to edit /etc/ImageMagick-6/policy.xml
|
|
<a href="https://cromwell-intl.com/open-source/pdf-not-authorized.html">cromwell-intl.com/open-source/pdf-not-authorized.html</a>
|
|
|
|
</dl>
|
|
<h3>System Documentation</h3>
|
|
<dl><!-- 2020-04-11 psargent -->
|
|
<dt><!--2020-04-11 psargent-->Document how we generate the SMK overall lengths and stats</dt>
|
|
<dd><!--2020-04-20 psargent-->scripts and manual actions in cavern
|
|
<dd>smklengths.sh script
|
|
<dd>smklengsths.odt
|
|
<dt><!--2020-04-20 psargent-->:loser:/docs/ files
|
|
<dd>Questions.txt
|
|
<dd>SMKlog.txt
|
|
|
|
|
|
<dt><!--2020-03-26 psargent-->Troggle architecture</dt>
|
|
|
|
<dd><!--2020-03-26 psargent-->Handbook: add package diagram totroggle architecture documentation. For future system maintainers</dd>
|
|
<dd><!--2020-04-10 psargent-->Regenerate the diagram of the tables in the database & document</dd>
|
|
<dd><!--2020-04-10 psargent-->Describe the parsing/import procedures so non-nerds can do it</dd>
|
|
<dd><!--2020-03-26 psargent-->Copy [some of] the .wiki material into the documentation somewhere?</dd>
|
|
|
|
|
|
<dt><!--2020-03-26 psargent-->Surveyscans</dt>
|
|
|
|
<dd><!--2020-03-26 psargent-->explain where the image files are referenced from: svx, tunnel/therion, and </dd>
|
|
<dd>Be exhaustive in checking all the broken links between svx & wallets</dd>
|
|
|
|
<dt>non-troggle scripts
|
|
<dd><!--2020-04-03 psargent-->DOCUMENT them all - have we got ? //expofiles/unidentified_scripts/ !
|
|
<dt>Makefile
|
|
<dd>Get it working ! How many of <a href="../troggle/scriptsother.html">other scripts</a> should be in it ? Should we do data imports to schedule too ?
|
|
|
|
|
|
</dl>
|
|
|
|
<h3>Troggle</h3>
|
|
<dl>
|
|
<dt>Better import error messages
|
|
<dd><!--2020-04-03 psargent-->REPORT if import surveyscan file failure into database error log -> "DataIssue" register
|
|
<dd><!--2020-04-20 psargent-->REPORT 'folder not recognised' errors into error log inside database -> "DataIssue" register
|
|
<dd><!--2020-04-03 psargent-->WHY are total lengths of surveyed cave different between expo server and WSL server for 2019 and a few other years only ?
|
|
<dd><!--2020-04-20 psargent-->DEBUG - too many messages - reduce the number unless we need them
|
|
<dd><!--2020-05-14 psargent-->FIND where that default cave print __unicode__() is happening
|
|
<dt>Missing .3d files
|
|
<dd><!--2020-04-25 psargent-->REPORT if there is no .3d file - make it if it is not there ? O rjust leave it to Makefile ?
|
|
<dt><!-- 2020-04-11 psargent -->Troggle parser/viewer
|
|
<dd>Explain how FLATPAGES work. refer to computing/hbmanual1.html
|
|
|
|
<dt>Logbook data model: unfilled fields?
|
|
<dd><!--2020-04-03 psargent-->'cave' of location field missing on nearly all logbook entries. Missing from logbook templates. Fill in manually for pre-2017 logbooks.
|
|
</dl>
|
|
|
|
|
|
<h3>Expo Server</h3>
|
|
<dl>
|
|
<dt><!--2020-03-26 psargent--> document directory structure
|
|
<dd><!--2020-04-03 psargent-->as per Julian's GitHub list - then close that issue.
|
|
Use 'tee' to cretae ascii art for this.</dd>
|
|
|
|
<dt>permissions
|
|
<dd><!--2020-04-03 psargent-->do we need a cron job or has the group membership fix fixed it ? either way, document it.
|
|
<dd><!--2020-04-03 psargent-->Makefile - and permissions.
|
|
|
|
<dt>Apache & MySQL configuration
|
|
<dd><!--2020-04-03 psargent-->DOCUMENT How to set up a server
|
|
<dd><!--2020-04-10 psargent-->Fix and document permissions for cron jobs
|
|
<dd><!--2020-05-14 psargent-->Document "anacron" / cron system on server
|
|
<dd><!--2020-04-10 psargent-->Explain why Docker containers can be a maintenance nightmare
|
|
<dd><!--2020-04-25 psargent--> /expofiles/ needs config , refer to apache/django docm.
|
|
<dd><!--2020-04-25 psargent--> /static/ needs config - refer to django docm.
|
|
</dl>
|
|
|
|
|
|
<h3>
|
|
<font color="fuchsia">This to-do-list gadget itself</font>
|
|
</h3>
|
|
<dl>
|
|
<dt>Status
|
|
<dd>Make it only click once to change display state of the DT tag
|
|
|
|
<dt><!--2020-03-26 psargent-->Eventual aim
|
|
|
|
<dd><!--2020-03-26 psargent-->to replace GitHub <a href="https://github.com/CaveSurveying/CUCCexposurveyissues/issues">
|
|
CUCCexposurveyissues</a> for non-tunnel, non-GIS issues.</dd>
|
|
|
|
<dt><!--2020-03-26 psargent-->Try to automate simple functions in javascript
|
|
|
|
<dd><!--2020-03-26 psargent-->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</dd>
|
|
<dd><!--2020-03-26 psargent-->Maybe restructure whole page as JSON and use
|
|
javascript editor to create (edit), re-order and demote items. </dd>
|
|
<dd><!--2020-03-26 psargent-->if using tinymcs, use the INLINE mode. </dd>
|
|
<dd><!--2020-03-26 psargent-->Implement comments on an issue, mimicking GitHub issues wiki</dd>
|
|
<dd><!--2020-03-26 psargent-->Use javascript to skip over the _edit page and submit changes
|
|
direct to server when updating. Needs direct POST and include the javascript in the posted content.</dd>
|
|
<dd><!--2020-03-26 psargent-->checkboxes so that items can be ticked (which also does strike-through)</dd>
|
|
<dd><!--2020-04-03 psargent-->promotion/demotion options?</dd>
|
|
<dd><!--2020-03-26 psargent-->bin icon to delete an item? Better to have an archive process.</dd>
|
|
<dt>Local WSL server
|
|
<dd><!--2020-04-03 psargent-->Why is it using recuced-capability tinymce, a paths problem ?
|
|
<dt>Italics management
|
|
<dd><!--2020-04-03 psargent-->Put DL into italics when *any* DD is hidden
|
|
</dl>
|
|
|
|
<!-- ------------------- Do not touch anything below here either ------------------------>
|
|
<!--2020-03-26--> Testing area..
|
|
<div id="demo">Demonstation text as initially read from disc</div>
|
|
|
|
<hr>
|
|
See also <a href="todo-data.html">Data maintenance to-do list</a><br />
|
|
Back to <a href="onlinesystems.html">Online Systems manual</a>
|
|
|
|
<hr /></body>
|
|
</html>
|