To Do:

-> in progress.  Change to using a configuration file for at least the database options
in the scripts.


General
--------
- Need to handle situation when there are no command line arguments.
(listftndb & nl2ftndb)

- Change to use placeholders for the dbi sql functions.

- Change to useing a hash instead of individual options in the module
subroutine calls.

- Need to clarify the parameters for $db_name & $database? For instance;  to
differientate between the database name as part of the DSN used to connect to
the server and the name of a database being created or dropped on a server.

- Review all pod documentation and update/correct as neccessary.

- Move configuring the log file in the scripts to the configuration file.

- The option used to define which type of database to use does not currently
do any error checking on that type;  the script will fail if a correct DBD name
is not used.  If do not explicitly do such error or other checking, document
the standard names for DBI DBD modules like SQlite (default), mysql, cvs, and
postgresql.

- The use of special characters like periods in table names is a more general
issue where it is not a good idea to use them at all.  Redo the comments in
scripts and modules regarding that, to generalize it.  (Derive function to
validate it and add that to the FTN::Database module?)

- Change to using the options hash from GetOpt::Std instead of the individual
option variables like $opt_l.

- Use the "if (defined $opt_l)" construct for checking options?

- Move the parsing of the options in the bin/* scripts into a subroutine?

- Separate out the submodules, like FTN::Database::Nodelist and
FTN::Database::Echolist (when implemented), into separate distributions
so that only the functionality that's wanted needs to be installed?


FTN::Database
--------------
- Export by default the commonly used functions.
- Derive a generic drop_table subroutine from the drop_nodelist_table.
- Create set_ftndb_acl subroutine? (Same reasoning as for create_ftndb.)
- Possible function/subroutine that checks if a valid database table name is
  being used?  And corrects it if possible?


FTN::Database::Nodelist
------------------------
- Export by default the commonly used functions.
- Derive and move a function for executing queries on the nodelist table from
  the code used in the listftndb subroutine.
- As part of adding statistics related functions, add a function that counts
  the number of nodes that have a particular flag associated with it.  Could
  use the name get_nodelist_flag_count($dbh,$nodelist_flag).  Also add 
  something that counts the number of things like hubs, nodes marked as
  private, etc. 
- Derive and move function to insert or update an entry from nl2ftndb. Separate
  functions for insert & update, or different options in same function?
- Move get_nodelist_filename subroutine from nl2ftndb script?
- Use a different datatype than "TIMESTAMP" for the 'updated' field in the
  nodelist table?  (Not generic enough?)

  
FTN::Database::Echolist
------------------------
- Create an FTN database module for echolists which:  Creates or Drops an
  echolist table, default name "Echolist"?  Basic table would consist of
  (at least) the following fields:  name, description, source.
- Export by default the commonly used functions.
- Create or drop an index on that basic echolist table.
- Create an el2ftndb script, patterned after the nl2ftndb script, which can
  be used to load the echolist table?  Or add the functionality to one of 
  the existing scripts?  Name it "ftnpldb-echolist" ?


ftndbadm
-------- 
- Use variables with subroutine calls, rather than depend on the globals.
- Come up with a single option for the name of the object being created or
  dropped, to replace the -d & -t options for the database_name and the
  nodelist_table_name variables?  Perhaps "-N" ?
- Add better error checking.
- Add quiet option, -q, for logging only operation ? 
- Rename as ftnpldb?  Or as something like ftnpldb-admin?


nl2ftndb
---------
- Move the load nodelist code in to a subroutine.
- Since the nodelist directory option is required;  change it to being
  defined in the configuration file rather than on the command line?
- Add cammand/options to create or drop the ftnnode index on the nodelist
  table?
- Move create_ftn_nodelist_table to what is currenly named nl2ftndb, but
  also leave a generic create_ftn_table subroutine in ftndbadm. 
- Change to using placeholders in the insert nodelist code by:
    Change the build sql statement code to being an 'prepare' function that
  builds the insert sql statment using placeholders for the table fields.
  Use the prepare cached version of it?  This will also allow moving that
  part of it out of the loop, so only the execute is in the loop.  Later,
  could move it into the F-D-NL module?  Use $insert_handle as the handle
  returned by the prepare?
    Change the 'do' function to an execute function on the handle from the
  prepare.  (http://www.perlmonks.org/?node_id=7548)  This will also allow
  removal of the existing code to removing single quotes and other code
  needed to make the data safe for insertion into the database as when
  using prepare/execute DBI automatically does any neccessary quoting 
  to insert the data safely.  Note that will still need to keep the code
  for taking care of the EOLs because of cross platform issues.
- Get quoteing working properly for entry into the database for fields like
  $location and $name, so do not have to take out characters like single
  quotes, etc.
- Script does not seem to properly handle a file that ends in just blank
  lines, instead of a content line or a ^Z character. (Should fail gracefully
  for a badly formatted file.)
- The nodelist file list is being reverse sorted when there are multiple
  nodelists of the same basename being processed;  that takes care of a set
  of files all from the same year but not ones that are from different years.
- Add quiet option, -q, for logging only operation ? 
- Add a test nodelist for use with this?...


listftndb
----------
- Change to using something like Text::Template for creating the output.
- Change default output to STDOUT;  i.e., print to the screen?  Selected if the
  "-o" variable is not set?
- Besides the print to screen output & output to text file, add option for html
  formatted output?  And/or just add formated output using a template file?
- Add quiet option, -q, for logging only operation ? 
- Move functionality into the nl2ftndb script as a List command?


Testing
-------
- Procedure in test script?    
1) get temp directory
2) create working directory there
3) ...  testing...
4) remove test working directory
5) done
  