Click on a sub-heading to reveal the individual to-do items. Click again to hide.
If a heading is in italics, then there are hidden items.
Click on the main "How this works" heading to toggle reveal/hide everything.
Printing this page uses a much smaller font. Complain to the nerd list if you don't like this behaviour.
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.
We are working on a more capable and easier-to-use system (see x-todo.html) which will mimic how GitHub Issues do this sort of thing.
Process Documentation
Wallets and new-cave
Explain (in the wallets process) how to view the surveys
online so that (1) you can see an example of how to do your new one,
and (2) so that you can check that you have done it properly when you
have finished.
Explain how to link a new cave into the other caves in
troggle filesystem
Explain how to add photos with the correct URL format to sub-HTML files attached to New Caves
svx check
explain command line to run on newly typed survex file to check for format errors '$cavern xxxx.svx'
explain when to use svx2qm.py -> qms.csv-> tablize-qms.pl current scripts
explain when to use find-dead-qms.py and qmreader.pl current scripts
Surveys data entry
QMs check
Collect together the old "to do" and "readme" notes and put them in a standard place: expoweb/[year]/TODO.html(with self-edit instructionslike this page)
Write code to automatically extract ref info about wallets from tunnel xml files
This will replace :drawings:chk-xml.txt as used by :drawings:check-xml.sh
Do similar for Therion files when people start using #REF comments
2019 surveyscans
edit all the content.json
try to autocomplete the content.json by parsing .svx files
Put personal names into canonical form
2014 contents.json
parse all the svx files to extract people, dates & svx references
Logbook fettling
2019 Logbook
transcribe the rest of those UKcaving blog entries into expoweb/years/2019/logbook.html
copy the photos from the UKCaving blog into expofiles/photos/2019// -- in fact many of those photos are already there
edit in the links to those photos in the right place in 2019/logbook.html
Garlic cave
edit logbook entries 2018, 2019 to link to extensive photos of Garlic cave area {Withnall 2018} , {Becka 2019}
Past logbooks - missing images?
Which previous years HTML logbooks are missing images extracted from scanned PDF copies of the logbooks?
imagemagick convert
Not working for PDFs on current version of xubuntu ! Fix & document. Also not working on WSL ubuntu. Needed to work with logbook images easily.
2018 Logbook
Check Natalie Uomini's typed entries and extensive photos are minimized and linked in properly to the HTML logbook
Add missing images to logbooks
2000, 2008, 2009, 2011
fix corrupted image in 2001 log
2011 logbook:
type up via-ferrate & bolt-testing writeups (In paper book, not in scan or HTML)
Why are so many surveyscan foolder missing after import?
WHY are total lengths of surveyed cave different between expo server and WSL server for 2019 and a few other years only ?
NOEDIT flag
Describe how this is implemented using <meta name="keywords" content="NOEDIT">
Logbook data model: unfilled fields?
'cave' of location field missing on nearly all logbook entroies. Missing from logbook templates. Where is this used and how can we fill it it in? Is it useful?
Expo Server
document directory structure
as per Julian's GitHub list - then close that issue
permissions
do we need a cron job or has the group membership fix fixed it ? either way, document it.
Tackle Store Records
No authoritative list of where the expo paper records are!
NO expo paperwork at all prior to 2008 in Tackle Store - where is it ?
FIND where all the wallet binders are, and the logbooks.
<
BUY A4 plastic boxes for filing cabinet for logbooks getting damp there.
2017, 2018, 2019 wallet binders are in Philip S.'s house.
We need two of these: 1.for expo systems work (troggle & scripts) - the current priority as we have nowhere currently that Wookey is willing to use
2.for survey data progress/issues (though troggle itself can be used for some of this if cleaned up a bit)
Try to automate simple functions in javascript
to control this document
in-place (tick, delete) instead of using the
tinymce HTML editor in Django
Maybe restructure whole page as JSON and use
javascript editor to create (edit), re-order and demote items.
if using tinymcs, use the INLINE mode.
Implement comments on an issue, mimicking GitHub issues wiki
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.
checkboxes so that items can be ticked (which also does strike-through)
promotion/demotion options?
bin icon to delete an item? Better to have an archive process.
Local WSL server
Why is it using recuced-capability tinymce, a paths problem ?