From Cambridge University Caving Club - CUCC wiki
Jump to: navigation, search
(→‎Current status)
Line 1: Line 1:
−
Troggle is a system under development for keeping track of all expo data in a logical and easily accessible way, and displaying it on the web.
+
Troggle is a system under development for keeping track of all expo data in a logical and accessible way, and displaying it on the web.
  
−
It uses Django and a Postgresql database. Potentially, it could replace the old system of csv files and scripts which produce the expo website.
+
<table border="1">
−
 
+
  <tr>
−
==Current status==
+
    <td><p>Feature</p></td>
−
In development.
+
    <td><p>Old expo website</p></td>
−
 
+
    <td><p>Troggle: planned</p></td>
−
==Done so far==
+
    <td><p>Troggle: progress so far</p></td>
−
*Necessary django data models written
+
    <td><p>Troggle: link</p></td>
−
:*Expos
+
  </tr>
−
:*Caves
+
  <tr>
−
:*Entrances
+
    <td><p>Cave stats generated from survex file</p></td>
−
:*Cavers
+
    <td><p>Yes</p></td>
−
:*Trips
+
    <td><p>Yes</p></td>
−
:*QMs
+
    <td><p>Done</p></td>
−
 
+
    <td><p><br />
−
*Import scripts from the old csv files
+
    </p></td>
−
:*cavetabReader.py imports caves from CAVETAB2.CSV
+
  </tr>
−
:*tripReader.py imports logbook entries from the format used on this wiki
+
  <tr>
−
:*folkReader.py imports people from the old folk.csv file
+
    <td><p>QM lists generated automatically</p></td>
−
:*204qmReader.py imports the qm csv tabe from 204.
+
    <td><p>Depends on the cave. Each cave had a different system.</p></td>
−
:*makeExpos.py simply creates expos for 1976 to present, skipping 1986
+
    <td><p>Yes; unified system.</p></td>
−
 
+
    <td><p>Done, but only 204 and 234 Qms have been imported from old system so far.</p></td>
−
*The beginnings of templates / views written
+
    <td><p><br />
−
:*Who was on which expo table
+
    </p></td>
−
:*Main cave index
+
  </tr>
−
 
+
  <tr>
−
==To do==
+
    <td><p>Web browser used to enter data</p></td>
−
*The rest of the templates / views
+
    <td><p>No</p></td>
−
:*Individual cave template / view
+
    <td><p>Yes</p></td>
−
:*Logbook view(s)
+
    <td><p><br />
−
:*QM list views
+
    </p></td>
−
 
+
    <td><p><br />
−
*Import bits and bobs
+
    </p></td>
−
:*non-204 QMs
+
  </tr>
 +
  <tr>
 +
    <td><p>Cave and passage descriptions</p></td>
 +
    <td><p>Yes, manually html coded.</p></td>
 +
    <td><p>Yes, wiki-style.</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Expo handbook</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
    <td><p>Not yet</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Table of who was on which expo</p></td>
 +
    <td><p>Yes</p></td>
 +
    <td><p>Yes</p></td>
 +
    <td><p>Done</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Automatic calendar for each year of who will be on expo when</p></td>
 +
    <td><p>No, manually produced some years</p></td>
 +
    <td><p>Yes</p></td>
 +
    <td><p>Mostly done</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>System for keeping contact, medical and next of kin info</p></td>
 +
    <td><p>No</p></td>
 +
    <td><p>Yes</p></td>
 +
    <td><p>Not yet</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Survey workflow helper</p></td>
 +
    <td><p>Yes; minimal. surveys.csv produced an html table of whose surveys were not marked “finished”</p></td>
 +
    <td><p>Yes. Makes table of surveys per expo which shows exactly what needs doing. Displays scans. Integrated with survex, scanner software, and tunnel.</p></td>
 +
    <td><p>Survex, scanner, and tunnel integration still needs doing.</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Automated photo upload and gallery</p></td>
 +
    <td><p>No; some manual photo galleries put together with lots of effort</p></td>
 +
    <td><p>Yes</p></td>
 +
    <td><p>Photo upload done, gallery needs writing</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Logbook</p></td>
 +
    <td><p>Yes; manually formatted each year</p></td>
 +
    <td><p>Yes; wiki-style</p></td>
 +
    <td><p>Done</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
  <tr>
 +
    <td><p>Search</p></td>
 +
    <td><p>No</p></td>
 +
    <td><p>Yes</p></td>
 +
    <td><p>Done</p></td>
 +
    <td><p><br />
 +
    </p></td>
 +
  </tr>
 +
</table>

Revision as of 05:53, 20 January 2009

Troggle is a system under development for keeping track of all expo data in a logical and accessible way, and displaying it on the web.

Feature

Old expo website

Troggle: planned

Troggle: progress so far

Troggle: link

Cave stats generated from survex file

Yes

Yes

Done


QM lists generated automatically

Depends on the cave. Each cave had a different system.

Yes; unified system.

Done, but only 204 and 234 Qms have been imported from old system so far.


Web browser used to enter data

No

Yes



Cave and passage descriptions

Yes, manually html coded.

Yes, wiki-style.



Expo handbook



Not yet


Table of who was on which expo

Yes

Yes

Done


Automatic calendar for each year of who will be on expo when

No, manually produced some years

Yes

Mostly done


System for keeping contact, medical and next of kin info

No

Yes

Not yet


Survey workflow helper

Yes; minimal. surveys.csv produced an html table of whose surveys were not marked “finished”

Yes. Makes table of surveys per expo which shows exactly what needs doing. Displays scans. Integrated with survex, scanner software, and tunnel.

Survex, scanner, and tunnel integration still needs doing.


Automated photo upload and gallery

No; some manual photo galleries put together with lots of effort

Yes

Photo upload done, gallery needs writing


Logbook

Yes; manually formatted each year

Yes; wiki-style

Done


Search

No

Yes

Done


Retrieved from "https://caving.soc.srcf.net/wiki/index.php?title=Troggle&oldid=1329"