\subsubsection{Archimedes}
\label{sec:archimedes}

\paragraph{Where things are}
NOTE: ``CVS'' indicates that item is also avail on CVS
\begin{enumeration}
\item /docuserver/images/archimedes -- toc.cgi objects for corpus 1
\item /docuserver/images/archimedes/log -- log files -- error log for
toc.cgi; error log for search program
\item /usr/local/httpd/cgi-bin/toc -- toc.cgi script CVS
\item /usr/local/httpd/cgi-bin/toc/.toc_config -- toc.cgi
configuration info CVS
\item /usr/local/httpd/cgi-bin/toc/.toc_config/config.xml -- toc.cgi 
configuration file (with internal DTD and inline documentation). CVS
\item /home/bcfuchs/bin -- some helper apps; makelemma.pl makefast.pl
\item /home/bcfuchs/perl/docuimages -- some helper apps; addarch.pl 



\end{enumeration}

\paragraph{collection structure}

toc.cgi display data are grouped in ``collections''. Each collection
consists of one or more ``works''. For historical reasons, the
structure of the collection follows the unix filesystem structure: a
collection consists of a directory with one subdirectory for each
``work'' belonging to the collection. Thus, a collection might look
something like this: 

/archimedes
/archimedes/agricola
/archimedes/baif
/archimedes/borro

The configuration file ``config.xml'' defines the number of collections
and gives the path to the collection directory. It is assumed that all
collection directories will be stored locally. 

\paragraph{work structure ARCHIMEDES}


%%% Local Variables: 
%%% mode: latex
%%% TeX-master: "texttools"
%%% End: