Scratch Pad

• Have GAIA produce a config script for Apache from its own server_config.php file. Allow it to be generated as a commmand-line function only! (Or maybe from localhost).
  

• Have a definitions.js JavaScript page which is created by PHP, which defines useful URLs, etc. Then knowledge only needs to be embedded in the database, and maybe some PHP scripts (eg server_config.php).
  

• Configure Apache so that missing accesses to a cached data directory call a PHP (or Perl?) script which untars images for the selected day to the data directory.
  • Have some kind of lock file using symbolic links (atomic) which prevent race conditions.
  • The untarred images should be kept somewhere different to the original tar files, so that tmpwatch can be used safely.
  • For optimum performance the cached data directory should be operating on a filesystem with atime enabled.
  • Image-colourising and rotation options create different versions of cached images.
  • Ensure the apache configuration script sets appropriate headers so that images are cached for a reasonable amount of time to reduce load on the web server.
  • Consider use of mod_asis; if the images are prepended with HTTP headers they can be sent 'as is', which may provide a reduced latency, or increased delay when untarring.

• In the database create a project_pi table, with columns project_id, and contact_id. This allows mutliple PIs for each project. Create a similar tables project_contacts and project_institutes. Remove the pi_id and contact[1-4]_id columns from the programs table. Rename programs table to projects to follow THEMIS notation and avoid confusion with the term computer program.