There are four programs written to assist in the continued maintainance
of the WAAW site: the spider, the search engine, sitemap_maker and davezilla.

1) The Search Engine
	This is a CGI program. It has two versions: one pointing to the
	SLA page and the other to the Stargate site.
	As long as you keep the database up to date, there should be no
	problem with this.
	
2) The Spider
	The spider program is in 
	/home/stargate/a/sig/artemis/public-web/Search/spider.pl . This is the
	program that creates the database that the Search engine draws from.
	It reads the filesystem on Stargate to create this database, which is
	a faster way to read the text. To call this program, you change 
	directories to the public-web/Search directory and call 
	`./spider.pl waaw.ser`. waaw.ser is the conviguration file for
	the spider, telling it what words are legal, what types of file
	are allowable for reading and the like. When running this script, 
	watch for how the program exits. If it just closes without
	an error, then it worked successfully. However, if it closes with 
	a line such as:

ndbm store returned -1, errno 28, key "copy" at Search/spider.pl line 195, <TDIR> chunk 15.

	, your data set (the public-web directory) contains more instances
	of that particular word than the database can handle. You will have
	to add it to the end of the WORDS field in you waaw.ser file.
	
3) sitemap_maker
	sitemap_maker goes through the file system and finds the pages big
	enough to be included in the sitemap, then prints a formatted
	sitemap to standard out, which means the command line. We use
	this to double-check that the program is working before we overwrite
	the sitemap. We first change directory to     
		/home/stargate/a/sig/artemis/public-web  
	and type this: `./sitemap_maker | less` . This allows us to look through
	the results. Once we're sure that something isn't broken, we 
	type this: `./sitemap_maker > sitemap.html` . This repaces the sitemap
	with the new sitemap. This is, strictly speaking, only necessary if
	new files are created or if page titles change.

4) davezilla
	This is my little web browser. Right now, I have it in the
	public-web directory. Now that development is done, it is more
	acceptable to have the 'SLA->Stargate' development plan than
	it was before. So, after the pages have been FTPd to SLA, you
	can log on to Stargate, change directory to the public-web directory,
	and type 
	'./dz http://www.sla.purdue.edu/waaw/some/page/here.html > some/page/here.html`
	to replace the page here.html in the directory public-web/some/page .