1: \subsubsection{Archimedes}
2: \label{sec:archimedes}
3:
4: \paragraph{Where things are}
5: NOTE: ``CVS'' indicates that item is also available on CVS
6: \begin{enumerate}
7: \item \url{/docuserver/images/archimedes} -- toc.cgi objects for corpus 1
8: \item \url{/docuserver/images/archimedes/log} -- log files -- error log for
9: toc.cgi; error log for search program
10: \item \url{/usr/local/httpd/cgi-bin/toc} -- toc.cgi script CVS
11: \item \url{/usr/local/httpd/cgi-bin/toc/.toc_config} -- toc.cgi
12: configuration info CVS
13: \item \url{/usr/local/httpd/cgi-bin/toc/.toc_config/config.xml} -- toc.cgi
14: configuration file (with internal DTD and inline documentation). CVS
15: \item \url{/home/bcfuchs/bin} -- some helper apps; makelemma.pl makefast.pl
16: \item \url{/home/bcfuchs/perl/docuimages} -- some helper apps; addarch.pl
17:
18:
19:
20: \end{enumerate}
21:
22: \paragraph{collection structure}
23:
24: toc.cgi display data are grouped in ``collections''. Each collection
25: consists of one or more ``works''. For historical reasons, the
26: structure of the collection follows the unix filesystem structure: a
27: collection consists of a directory with one subdirectory for each
28: ``work'' belonging to the collection. Thus, a collection might look
29: something like this:
30:
31: \url{/archimedes}\\
32: \url{/archimedes/agricola}\\
33: \url{/archimedes/baif}\\
34: \url{/archimedes/borro}
35:
36: The configuration file ``config.xml'' defines the number of collections
37: and gives the path to the collection directory. It is assumed that all
38: collection directories will be stored locally.
39:
40: \paragraph{work structure ARCHIMEDES}
41:
42:
43: %%% Local Variables:
44: %%% mode: latex
45: %%% TeX-master: "texttools"
46: %%% End:
47:
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>