The following text contains short notes about missing functionality,
bad usability, bugs etc. Its roughly sorted by importance. Not all
of this is going to be implemented. Its just the stuff I'm thinking
about.

++January-March++

* Manika Prasad
  Research Assoc, Dep of GY
  SRB Proj
  397 Panama Mall, Mitchell B51
  Stanford U
  650-723-8547
  manika.prasad@stanford.edu
  pangea.stanford.edu/~manika/manika.html

* use DBD and DBI instead of Mysql (more portable)

* find all pp>pc and flag as "bad data" with explanation

* better handling of times in output (how we show them) and input (how the user inputs them)

* re-submit to search engines

* why can't I import to excel on crusher.mines.edu via the clipboard?

* do away with %DESCRIPTION_NAME. what is that anyway?

* whats the copyright of our data? Can we get sued? Printout all our refs
  and ask (somebody? Who?)

* refs for minerals? what does E1 E2 E3 mean?

* nicer image-buttons for the "Go!" at the last step of the beginners and the experts?

* the help texts are specific to rock- or mineral properties. i.e. for photos, descs,
  refs this is not really appropriate
  --> do this if/when we ever make a real redesign?

* mailinglist

* is it possible to run it on windows/mac?

* how easy is it to install mirrors/ install it standalone? windows?

++rewrite sometime++

* perl_mod
   * much faster
   * allows for persistent data instead initializing each time
* use strict, real modules, object oriented
* use www.masonhq.com or Maypole or any of the other DB<->Web modules 
  and stylesheets to separate content and style
* code documentation
* reimplementation. I wrote this when I was new to perl and it shows
* cache DB access

++always++

* validate all html

++maybe++

* ?split references into date, author, journal, title, other? (why?)

* put sql syntax "select ... limit offset,number" in it 
  -> no, since it screws up $sth->numrows() & Co.
  -> yes, since it would be faster