version 1.12, 2004/01/15 09:03:23
|
version 1.16, 2004/03/17 09:31:01
|
Line 52 The input metadata file must have the fo
|
Line 52 The input metadata file must have the fo
|
\item An overview of toc.cgi architecture |
\item An overview of toc.cgi architecture |
\item A walk-through of typical cgi queries for toc.cgi |
\item A walk-through of typical cgi queries for toc.cgi |
\item An index of cgi parameters and values with short descriptions of function |
\item An index of cgi parameters and values with short descriptions of function |
|
\item The TOC Perl modules |
\end{enumeration} |
\end{enumeration} |
|
|
\paragraph{Overview of toc.cgi architecture} |
\paragraph{Overview of toc.cgi architecture} |
Line 136 get a work from default corpus with thum
|
Line 137 get a work from default corpus with thum
|
get a page of text from a work from default corpus |
get a page of text from a work from default corpus |
|
|
|
|
|
\paragraph{TOC Perl Modules} |
|
\subparagraph{general}The documentation for the Toc Perl Modules is |
|
located in the modules themselves in POD format. The POD is the |
|
definitive documentation for the modules. |
|
|
|
The modules are available to archimedes staff from cvs on the archimedes server at |
|
141.14.236.86:/perseus/cvsroot in the module |
|
/perseus/cvsroot/mpitexts/perl/perllib. To get them, log on to the |
|
archimedes server and use the commandline command: |
|
|
|
cvs -d /perseus/cvsroot co /perseus/cvsroot/mpitexts/perl/perllib |
|
|
|
or from a remote location |
|
|
|
bash; export CVS_RSH=ssh; cvs -d :ext:myusername@141.14.236.86:/perseus/cvsroot co /perseus/cvsroot/mpitexts/perl/perllib |
|
|
\subsubsection{Indexing} |
\subsubsection{Indexing} |
\label{sec:indexing} |
\label{sec:indexing} |
Line 157 archimedes/data/db/PROJECT_NAME/CORPUS_N
|
Line 172 archimedes/data/db/PROJECT_NAME/CORPUS_N
|
server the other on the client [this is the 1st implementation bcs |
server the other on the client [this is the 1st implementation bcs |
its easiest and there are no port issues, but probably it'd be |
its easiest and there are no port issues, but probably it'd be |
better to have a separate port]. |
better to have a separate port]. |
\item client cgi: indexinput -- sends 1. list of files to index |
\item client cgi: getindex -- sends 1. list of files to index |
2. uri to which xml notification of completion is to be sent. Upon |
2. uri to which xml notification of completion is to be sent. Upon |
notification, activates backend prog that fetches and installs the |
notification, activates backend prog that fetches and installs the |
indices. |
indices. |
Line 202 Parameters
|
Line 217 Parameters
|
No parameter--update all lemmatization indices |
No parameter--update all lemmatization indices |
[latin | ital | greek | en | nl | de]-- update this language |
[latin | ital | greek | en | nl | de]-- update this language |
|
|
|
\subsubsection{summary of differences btwn the archimedes toc.cgi |
|
implementation and the echo toc.cgi impelementation (toc.x.cgi)} |
|
|
|
\paragraph{missing in archimedes} |
|
\begin{enumeration} |
|
|
|
\item html templates (coded but phased out of cvs branch) |
|
\end{enumeration} |
|
|
|
\paragraph{missing in echo} |
|
\begin{enumeration} |
|
|
|
\item word-coloring? |
|
\item remote text method may work differently |
|
|
|
|
|
|
|
\end{enumeration} |
|
\paragraph{differences} |
|
\begin{enumeration} |
|
\item structure of info.xml |
|
\item resource-discovery algorithm for info.xml |
|
\end{enumeration} |
|
|
|
|
|
|
%%% Local Variables: |
%%% Local Variables: |
%%% mode: latex |
%%% mode: latex |
%%% TeX-master: "texttools" |
%%% TeX-master: "texttools" |