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
-
-
-
Troggle architecture
-
-
Handbook: explain how troggle works - much better and simpler. Fix
- mistakes I wrote. For future system maintainers
-
Copy the .wiki material into the documentation somewhere
-
-
-
Surveyscans
-
-
explain where the image files are referenced from: svx, tunnel/therion, and why there are so many broken links
-
-
-
-
Photos
-
-
Capitalisation in filenames problem
-
-
run the duplicate filename script on the server in
- /photos/xml/ as there are files which differ only in
- capitalisation of their names.
-
Fix such duplicates in the /photos/ folders where this
- problem originates
-
Document this issue of duplicate photo filenames produced by
- multiple cameras running similar software
-
somehow fix the photo filenames which use capital letters on
- import or upload, or by a cron job
-
-
-
-
Surveys data entry
-
-
2019 surveyscans
-
-
edit all the content.json
-
try to autocomplete the content.json by parsing .svx files
-
Put personal names into canonical form
-
-
-
-
Troggle
-
Expo Server
-
-
www-data:www-data permissions
-
-
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
-
-
Or fix group
- membership for the process running django so that it can write
- files owned by 'expo'
-
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. So long
- as the content is inserted into the DOM, it should work ?
-
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
-
checkboxes so that items can be ticked
- (which also does strike-through)
-
bin icon to delete an item? Better to have an archive process.
-
-
-
-
-
- Testing area..
-
Demonstation as initially read from disc
-
-
+
+
+
Expo Systems Exptl. To-Do List
+
+
+
+
Documentation
+
+
Wallets & 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
+
+
+
Troggle architecture
+
+
Handbook: explain how troggle works - much better and simpler. Fix
+ mistakes I wrote. For future system maintainers
+
Copy the .wiki material into the documentation somewhere
+
+
+
Surveyscans
+
+
explain where the image files are referenced from: svx, tunnel/therion, and why there are so many broken links
+
+
+
+
Photos
+
+
Capitalisation in filenames problem
+
+
run the duplicate filename script on the server in
+ /photos/xml/ as there are files which differ only in
+ capitalisation of their names.
+
Fix such duplicates in the /photos/ folders where this
+ problem originates
+
Document this issue of duplicate photo filenames produced by
+ multiple cameras running similar software
+
somehow fix the photo filenames which use capital letters on
+ import or upload, or by a cron job
+
+
+
+
Surveys data entry
+
+
2019 surveyscans
+
+
edit all the content.json
+
try to autocomplete the content.json by parsing .svx files
+
Put personal names into canonical form
+
+
+
+
Troggle
+
Expo Server
+
+
www-data:www-data permissions
+
+
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
+
+
Or fix group
+ membership for the process running django so that it can write
+ files owned by 'expo'
+
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. So long
+ as the content is inserted into the DOM, it should work ?
+
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
+
checkboxes so that items can be ticked
+ (which also does strike-through)
+
bin icon to delete an item? Better to have an archive process.