Revision: 16490
http://sourceforge.net/p/gate/code/16490
Author: valyt
Date: 2013-01-25 14:56:09 +0000 (Fri, 25 Jan 2013)
Log Message:
-----------
Updated the documentation for version 5.0-SNAPSHOT.
Modified Paths:
--------------
mimir/trunk/doc/admin.tex
mimir/trunk/doc/changes.tex
mimir/trunk/doc/extending.tex
mimir/trunk/doc/indexing.tex
mimir/trunk/doc/mimir-guide.pdf
mimir/trunk/doc/quickstart.tex
mimir/trunk/doc/searching.tex
Modified: mimir/trunk/doc/admin.tex
===================================================================
--- mimir/trunk/doc/admin.tex 2013-01-24 16:13:11 UTC (rev 16489)
+++ mimir/trunk/doc/admin.tex 2013-01-25 14:56:09 UTC (rev 16490)
@@ -10,14 +10,15 @@
plugins, leveraging the CREOLE plugin framework of GATE Embedded).
\item[plugins/db-h2] The default annotation storage implementation. This
-stores annotation data using H2, an in-process embedded SQL database.
+stores annotation data using H2\footnote{\url{http://h2database.com}}, an
+in-process embedded SQL database.
\item[plugins/sesame] An alternative annotation storage implementation that
stores its annotation data in a triple store using the Sesame API
(\url{http://www.openrdf.org/}). Annotations with an ``inst'' feature are
treated as links into the knowledge base, supporting richer semantic queries.
-\item[plugins/sparql] A helper that is layered on top of a generic storage
+\item[plugins/sparql] A helper that can be layered on top of any other storage
implementation to provide semantic querying against a separate knowledge base,
accessible at a SPARQL endpoint.
@@ -30,19 +31,13 @@
\item[mimir-client] The client side of the \Mimir\ remote protocol, to support
distributed indexing and querying.
-\item[mimir-web] A Grails plugin (\url{http://grails.org}) providing
+\item[mimir-web] A Grails\footnote{\url{http://grails.org}} plugin providing
both the user interface to create and query indexes over the web, and also the
server side of the remote protocol to expose several distributed \Mimir\
indexes as a single {\em federated} index for clients. This is provided as a
plugin rather than an application to make it more easily customisable.
-\item[mimir-demo] The simplest possible Grails application using the above
-plugin. This application is not actually included in the source tree; it is
-instead generated by the build process. See Section~\ref{sec:building} for
-details on how to do that. Once created, it is ready to use as-is or as a base
-for customisation to add security, look and feel customisation, etc.
-
-\item[mimir-cloud] A fully fledged Grails application, that uses the mimir-web
+\item[mimir-cloud] An example Grails application, that uses the {\tt mimir-web}
plugin and also includes security support. This is the exact implementation
used
for \Mimir{} servers supplied on the GATECloud.net
platform\footnote{\url{https://gatecloud.net}: a platform for running
GATE-based
@@ -53,9 +48,6 @@
\section{Building and Running a \Mimir{} Web
Application}\label{sec:building}
-\subsection{Which \Mimir{} Web Application}
-\label{sec:webapps}
-
The {\tt mimir-core} Java library provides support for indexes that are
represented as an on-disk directory -- named {\em Local Indexes} in the rest of
this document (see the discussion about index types in
@@ -65,51 +57,46 @@
build and run a web application. All the web elements of \Mimir{} are
implemented as the {\tt mimir-web} Grails plugin, which can easily be included
in any Grails-based web application. The standard \Mimir{} distribution
provides
-two such web applications:
-\begin{description}
-\item[mimir-demo] The {\tt mimir-demo} module is intended to be the simplest
- possible demonstration of how to use the {\tt mimir-web} Grails plugin in a
- Grails application. This application is suitable for experimentation and
- local use, but as it includes no security or authentication support it may
not
- be appropriate for production deployment. These concerns are addressed
further
- in Section~\ref{sec:extend:customapp}.
-
- If you are just starting with \Mimir{}, or you are only experimenting with
- \Mimir{} indexes that you do not intend to open to remote users, then this is
- the recommended web application to use.
-
- You should also use {\tt mimir-demo} (as a starting point) if you are an
- experienced Grails developer and need a basic application to which you intend
- to add your own security solution.
-\item[mimir-cloud] The {\tt mimir-cloud} application is the actual software
- implementation behind the {\Mimir} servers deployed on the GATE Cloud
- platform\footnote{\url{https://gatecloud.net}}. In addition to the \Mimir{}
- plugin, it also includes some basic support for user authentication (using
- the Spring Security Grails plugin), and support for packaging and downloading
- local indexes. This is probably the most suitable choice if you just need a
- stand-alone web application with \Mimir{} functionality, and you do not
intend
- to develop your own security solution.
-\end{description}
+such a web application, named {\tt mimir-cloud}.
-The rest of this chapter talks about the {\tt mimir-demo} application, as the
-simpler of the two. However, everything said also applies to the {\tt
-mimir-cloud} application.
+\subsection{The {\tt mimir-cloud} Web Application}
+\label{sec:mimir-cloud}
+The {\tt mimir-cloud} web application is the actual version of the \Mimir\
+software that is used on the GATECloud platform. As such, it is configured for
+that particular usage scenario, where indexes have two different URLs
(depending
+on whether they are accessed from within the same cloud region or not), and
+where the local configuration page is not made available to the user. However,
+some of this behaviour is switched off when the application detects that it is
+not running on the cloud, to allow it to be used as a general purpose
+\Mimir{}-enabled web application.
+In addition to the {\tt mimir-web} plugin, it also includes some basic support
+for user authentication (using the Spring Security Grails plugin), and support
+for packaging and downloading local indexes. This is probably a suitable choice
+if you just need a stand-alone web application with \Mimir{} functionality, and
+you do not intend to develop your own security solution.
+If you are an experienced Grails developer and you intend to add your own
+security solution, then you should use the {\tt mimir-web} Grails plugin
+directly in your own application, as described in
+Section~\ref{sec:extend:customapp}.
+While we include this application as an example of a fully-fledged Grails
+application using the {\tt mimir-web} plugin, you may need to modify it
slightly
+to make it mode suitable to your actual usage scenario.
+
\subsection{Prerequisites}
-To build the \Mimir\ demo app you will need:
+To build the \Mimir\ web application you will need:
\begin{itemize}
\item A Java 6 JDK. \Mimir\ has been tested with the Sun/Oracle and OpenJDK
JVMs on Linux and the Apple JVM on Mac OS X.
\item Apache Ant 1.8.1 or later.
-\item Grails (\url{http://grails.org}). The \Mimir\ plugin was developed with
- version 1.3.7 but later 1.3.x versions should also work (you will need to run
- {\tt grails upgrade} in the {\tt mimir-web} directory if you use a version
- other than 1.3.7). You need to set the JAVA\_HOME environment variable to
- point to your JDK, the GRAILS\_HOME environment variable to point to your
- Grails installation and put \$GRAILS\_HOME/bin on your PATH.
+\item The Grails framework: the \Mimir\ plugin was developed using Grails
+ version 2.1.1. Other versions of Grails are not guaranteed to work, so you
+ should use the same one. You need to set the JAVA\_HOME environment variable
+ to point to your JDK, the GRAILS\_HOME environment variable to point to your
+ Grails installation and add \$GRAILS\_HOME/bin to your PATH.
\end{itemize}
While not strictly a pre-requisite, \Mimir\ performs much better on 64-bit
@@ -117,7 +104,7 @@
memory to the process, but also because the larger address space allows MG4J to
memory-map many of the files that make up the index.
-To run a local instance of \Mimir\ you can use the standard {\tt grails prod
+To run a local instance of \Mimir\ you can use the standard \cmd{grails prod
run-war} command, but to deploy a production instance you will need a separate
servlet container such as Tomcat.
@@ -125,26 +112,20 @@
There is a top-level Ant build.xml file that should build all the modules in
the correct order. To do that simply change to the top level directory
-containing the \Mimir\ source code, and run the {\tt ant} command. To perform
+containing the \Mimir\ source code, and run the \cmd{ant} command. To perform
the same build process manually, you need to change to the following
directories
and run the following {\tt ant} commands in this order:
\begin{enumerate}
-\item {\tt mimir-core}: {\tt ant publish}
-\item {\tt mimir-client}: {\tt ant publish}
-\item {\tt plugins}: run {\tt ant} in each sub-directory of the plugins
+\item {\tt mimir-core}: \cmd{ant publish}
+\item {\tt mimir-client}: \cmd{ant publish}
+\item {\tt plugins}: run \cmd{ant} in each sub-directory of the plugins
directory in turn (order is not important here, the plugins do not depend on
one another).
-\item {\tt mimir-web} - {\tt grails compile} followed by {\tt grails
+\item {\tt mimir-web}: \cmd{grails compile} followed by \cmd{grails
compile-gwt-modules}.
\end{enumerate}
-Once the plugin is built you need to generate the source folder for the demo
-application. You can do that by running the {\tt ant mimir-demo} command in the
-top level folder of the \Mimir\ source tree. This will create a new directory
-(named {\tt mimir-demo}) inside the top level directory, which contains a
simple
-Grails-based web application, that uses the \Mimir\ Grails plugin.
-
-The next step is to configure the {\tt mimir-demo} web application, and is
+The next step is to configure the {\tt mimir-cloud} web application, and is
described in the following Section.
\subsection{Configuring}\label{sec:admin:config}
@@ -255,17 +236,18 @@
\subsection{Running}
-The easiest way to run the \Mimir\ demo web app is to use the normal Grails
-commands {\tt run-app} or {\tt run-war}. For performance, {\tt grails prod
-run-war} is preferable. For anything more than the smallest toy index it is
-advisable to increase the memory available to \Mimir\ by using the JAVA\_OPTS
-environment variable. For example (using bash or a similar POSIX shell):
+The easiest way to run the \Mimir\ cloud web app is to use the normal Grails
+commands \cmd{grails run-app} or \cmd{grails run-war}. For performance,
+\cmd{grails prod run-war} is preferable. For anything more than the smallest
+toy index it is advisable to increase the memory available to \Mimir\ by using
+the JAVA\_OPTS environment variable. For example (using bash or a similar
POSIX
+shell):
\begin{verbatim}
$ JAVA_OPTS='-Xmx4G' grails prod run-war
\end{verbatim}
-To shut down a web app started using {\tt run-app} or {\tt run-war}, simply
-create an empty file in the {\tt mimir-demo} directory named
+To shut down a web app started using \cmd{grails run-app} or \cmd{grails
+run-war}, simply create an empty file in the {\tt mimir-cloud} directory named
``{\tt .kill-run-app}''. Grails watches for this file and will shut down
gracefully when it detects that the file has been created.
@@ -276,7 +258,7 @@
installing the Tomcat available through {\tt apt-get} as the latter is
configured by default with a security manager that interferes with \Mimir.
-When deployed to a servlet container the demo application reads configuration
+When deployed to a servlet container the web application reads configuration
at run-time from two locations using the Grails standard ``externalised
configuration'' mechanism:
\begin{itemize}
@@ -295,28 +277,6 @@
// as the ROOT web application
\end{lstlisting}
-
-\subsection{The {\tt mimir-cloud} Web Application}
-
-The {\tt mimir-cloud} web application is the actual version of the \Mimir\
-software that is used on the GATECloud\footnote{\url{https://gatecloud.net}}
-platform. As such, it is configured for that particular usage scenario, where
-indexes have two different URLs (depending on whether they are accessed from
-within the same cloud region or not), and where the local configuration page is
-not made avaialble to the user.
-
-While we include this application as an example of a fully-fledged Grails
-application using the {\tt mimir-web} plugin, you may need to modify it
slightly
-to make it mode suitable to your actual usage scenario. In particular, the
-default local configuration uses a known writeable location for the creation of
-local indexes (the {\it Index base directory} is set to be under {\tt /data}).
-If such a path does not exist on your system, or is not writeable by the system
-user running \Mimir{}, you will need to modify the configuration to provide a
-more suitable value. The web page for modifying the configuration is not linked
-from the administration page, but can still be accessed at a URL like {\tt
-http://localhost/:8080/mimir/admin/mimirConfiguration/edit}\footnote{You may
-need to change the host name and/or port number accordingly.}.
-
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Indexes in \Mimir}
Modified: mimir/trunk/doc/changes.tex
===================================================================
--- mimir/trunk/doc/changes.tex 2013-01-24 16:13:11 UTC (rev 16489)
+++ mimir/trunk/doc/changes.tex 2013-01-25 14:56:09 UTC (rev 16490)
@@ -6,10 +6,23 @@
\item The {\em mimir-demo} example web application has been removed.
\item The {\em mimir-cloud} has been modified to make it more suitable as a
generic example web application.
- \item \Mimir{} now uses Grails 2.1.1 to build the mimir-cloud web
- application.
+ \item New query operator: {\bf MINUS} (also -) performs the set minus
+ operation on result sets (see Section~\ref{sec:minus-query}).
\item \Mimir{} now supports the construction of direct indexes (see
- Section~\ref{sec:direct-indexes}).
+ Section~\ref{sec:direct-indexes}). Direct indexes are used to support a new
+ family of queries, that use document ID as query terms, and which return
terms
+ as results. Currently these are only available as a Java API, and can be
found
+ in the {\tt gate.mimir.search.terms} package.
+ \item Semantic annotation helpers are now capable of 'describing' a matched
+ mention. The S-A-H implementations included in the main distribution provide
+ default implementations for this functionality, which can be replaced by
+ pluggin-in alternative versions.
+ \item \Mimir{} now uses Grails 2.1.1 and GWT 2.5.0 to build the mimir-cloud
+ web application.
+ \item Bugfix: you can now use a string on the right hand side of a \verb!<!,
+ \verb!>!, \verb!<=! and \verb!>=! in annotation queries. This was always
+ documented, but did not work before.
+ \item Many other bugfixes.
\end{itemize}
\section{Version 4.1.3 (September 2012)}
\begin{itemize}
@@ -66,7 +79,7 @@
\item Replaced the old GWT based UI with a new implementation (see
Section~\ref{sec:search:gus}).
\item Added the mimir-cloud web application to the source tree (see
- Section~\ref{sec:webapps}).
+ Section~\ref{sec:mimir-cloud}).
\end{itemize}
\section{Version 3.4.0 (November 2011)}
Modified: mimir/trunk/doc/extending.tex
===================================================================
--- mimir/trunk/doc/extending.tex 2013-01-24 16:13:11 UTC (rev 16489)
+++ mimir/trunk/doc/extending.tex 2013-01-25 14:56:09 UTC (rev 16490)
@@ -2,11 +2,11 @@
many use cases, but if your application needs more functionality that they
cannot provide it is easy to add your own custom helper implementations using a
plugin mechanism. This process is described in
-section~\ref{sec:extend:helpers}. Similarly, the basic \Mimir\ demo
-application shows the simplest way to use the \Mimir\ Grails plugin, but it
-provides no authentication or security, for example. To add these kinds of
-features you can install the \Mimir\ plugin into your own custom Grails
-application, as described in section~\ref{sec:extend:customapp}.
+section~\ref{sec:extend:helpers}. Similarly, the basic \Mimir\ cloud
+application shows a simple way to use the \Mimir\ Grails plugin, but it
provides
+no other features. If you have different requirements, you can install the
+\Mimir\ plugin into your own custom Grails application, as described in
+section~\ref{sec:extend:customapp}.
\section{Creating New Semantic Annotation Helpers}\label{sec:extend:helpers}
@@ -250,11 +250,10 @@
\section{Embedding \Mimir\ in a Custom Grails Application}
\label{sec:extend:customapp}
-The demo Grails application provided with \Mimir\ provides access to the
-functionality of the \Mimir\ Grails plugin but is deliberately kept simple. It
-does not address concerns such as security and authentication, but these can be
-handled by installing the \Mimir\ plugin into a custom Grails application and
-adding these functions there.
+The {\tt mimir-cloud} Grails application provided with \Mimir\ provides access
+to the functionality of the \Mimir\ Grails plugin but is deliberately kept
+simple. For more complex needs, you can install the \Mimir\ plugin into a
custom
+Grails application.
\subsection{Installing the \Mimir\ Plugin}
@@ -315,9 +314,9 @@
There are a number of established and mature Grails plugins that implement user
registration, authentication and security in various ways for Grails
-applications. By design, the \Mimir\ plugin and demo app do not provide any
-security of their own, but for production deployments you may wish to consider
-any or all of the following.
+applications. By design, the \Mimir\ plugin does not provide any
+security of its own, allowing it to integrate with any security solution. For
+production deployments you may wish to consider any or all of the following.
\begin{itemize}
\item Place your application behind an Apache HTTPD or other similar front-end
Modified: mimir/trunk/doc/indexing.tex
===================================================================
--- mimir/trunk/doc/indexing.tex 2013-01-24 16:13:11 UTC (rev 16489)
+++ mimir/trunk/doc/indexing.tex 2013-01-25 14:56:09 UTC (rev 16490)
@@ -190,6 +190,49 @@
order to function correctly. Other metadata helpers may be added to the list
if required.
+\subsection*{Direct Indexes}
+\label{sec:direct-indexes}
+Starting with version 5, \Mimir{} can build direct indexes as well as inverted
+ones. By default only inverted indexes are created, which are used to associate
+terms to documents. Direct indexes encode the inverse relation from documents
to
+terms, hence a direct index can be used to find out which terms occur in any
+given document.
+
+To enable direct indexes for tokens, the configuration in the index template
+needs to be modified like in the following example:
+\begin{lstlisting}
+tokenFeatures = {
+ string(directIndex:true)
+ category(directIndex:true)
+ root()
+}
+\end{lstlisting}
+
+In this case, direct indexes will be built for the {\tt string} and {\tt
+category} features of \verb!{Token}! annotations, but not for the {\tt root}
+feature.
+
+In the case of semantic annotations, direct indexes are enabled in a similar
+fashion:
+\begin{lstlisting}
+index(directIndex:true) {
+ annotation helper:new DefaultHelper(...)
+ ...
+}
+\end{lstlisting}
+
+Note that direct indexes can only be enabled at the level of a {\tt index}
+element in the template, and not for individual annotation types.
+
+Direct indexes are built during the closing of the index, so enabling them will
+slightly increase the time taken for the close operation, but will not affect
+the indexing time. They are stored in separate files from the default indirect
+indexes, so they will not affect the functionality that does not require direct
+indexes at all.
+
+Direct indexes can currently only be searched via the Java API provided by the
+{\tt gate.mimir.search.terms} package.
+
\section{Adding Documents to an Index}\label{sec:indexing:add-docs}
Once an index has been created in {\em indexing} mode, the next stage is to add
Modified: mimir/trunk/doc/mimir-guide.pdf
===================================================================
(Binary files differ)
Modified: mimir/trunk/doc/quickstart.tex
===================================================================
--- mimir/trunk/doc/quickstart.tex 2013-01-24 16:13:11 UTC (rev 16489)
+++ mimir/trunk/doc/quickstart.tex 2013-01-25 14:56:09 UTC (rev 16490)
@@ -50,24 +50,28 @@
\cmd{like this}.
\begin{enumerate}
\item {\bf Download the \Mimir{} sources}, if you do not already have a copy.
- Instructions for doing so are available on \Mimir{}'s web page at:
+ You can get either an archive of the entire source tree, or check it out
+ directly from our subversion repository. Instructions for doing so are
+ available on \Mimir{}'s web page at:
\url{http://gate.ac.uk/mimir/index.html}.
- If using a .tar.gz source tree archive on Windows we recommend not using the
+ If you downloaded the .tar.gz archive on Windows we recommend not using the
popular Winzip utility, as that sometimes mangles the file names.
7-Zip\footnote{\url{http://www.7-zip.org/}} and the Cygwin ``tar'' utility
are
known to work correctly in this respect, and other free archiving tools are
available that support the {\tt .tar.gz} format.
- Unpacking a source archive (or checking the source code out with subversion)
- will create a new directory called {\tt mimir} containing all the source
files.
+ Unpacking a source archive (or checking out the source code with subversion)
+ will create a new directory called {\tt mimir} containing all the source
+ files.
\item {\bf Build \Mimir{}:} change to the top level directory where you
unpacked the downloaded \Mimir{} sources. If you can see the {\tt
mimir-core},
{\tt mimir-client}, {\em etc.} directories, then you are in the correct
directory. Execute the \cmd{ant} command. This will download all the
required dependencies, compile all the \Mimir{} libraries, and build the {\tt
mimir-web} Grails plugin.
+
If you have multiple Grails versions installed, and Grails 2.1.1 is not the
default, you must give priority to Grails 2.1.1. Do so by executing
- \cmd{export GRAILS\_HOME=/path/to/grails-2.1.1} + and then
+ \cmd{export GRAILS\_HOME=/path/to/grails-2.1.1}, and then use the following:
\cmd{ant -Dgrails.bin=\$GRAILS\_HOME/bin/grails} (instead of \cmd{ant}) to
override the default Grails settings.
\item {\bf Run the mimir-cloud application:} change to the {\tt
@@ -80,10 +84,10 @@
\section{Create, Populate, and Search an Index}
%
\begin{enumerate}
-\setcounter{enumi}{4}
+\setcounter{enumi}{3}
\item {\bf Set-up your new \Mimir{} application:}
- navigate to the administration page. You will be prompted to configure your
\Mimir{} instance.
- After clicking the link, enter the path to a local writable directory
+ navigate to the administration page. You will be prompted to configure your
+ \Mimir{} instance. After clicking the link, enter the path to a local
writable directory
where new indexes will be created, and click the {\em Update}.button.
\item \label{step:create} {\bf Create a new index:} navigate back to the
administration page (by clicking the link at the top of the page). Under the
{\em Local Indexes}
@@ -122,7 +126,7 @@
\end{enumerate}
To shut down the running web application, create a file named {\tt
-.kill-run-app} in the {\em mimir-demo} directory, and wait for the application
+.kill-run-app} in the {\em mimir-cloud} directory, and wait for the application
to shut itself down. If that does not work (creating files with `.' at the
start
of their names is sometimes difficult on Windows), then you can just focus the
command prompt window where you started the application and interrupt it by
@@ -132,6 +136,6 @@
you would need to re-import them).
To deploy the \Mimir{} web application to an application server (such as Apache
-Tomcat) run the \cmd{grails prod war} command in the mimir-demo directory. A
-{\tt mimir-demo-\{version\}.war} file will be created for you in the {\tt
-target} sub-directory.
+Tomcat) run the \cmd{grails prod war} command in the mimir-cloud directory. A
+{\tt mimir-cloud-\{version\}.war} file will be created for you in the {\tt
+target} sub-directory.
\ No newline at end of file
Modified: mimir/trunk/doc/searching.tex
===================================================================
--- mimir/trunk/doc/searching.tex 2013-01-24 16:13:11 UTC (rev 16489)
+++ mimir/trunk/doc/searching.tex 2013-01-25 14:56:09 UTC (rev 16490)
@@ -142,7 +142,7 @@
\subsection{MINUS Operator: ``{\tt -}''}\label{sec:minus-query}
The {\tt MINUS} (also `-`) operator is a binary operator that takes a left and
-a right operand. It returns the hits from the left sub-query that are anot also
+a right operand. It returns the hits from the left sub-query that are not also
valid hits for right sub-query. For example:
\begin{description}
\item[Query1 - Query2] will match all the hits of {\tt Query1} that are
@@ -266,11 +266,11 @@
that can be accessed through a simple HTTP interface. All requests are
performed
by calling an action with a set of parameters; the results of a call are
encoded
in XML and returned as the response to the request. All the example URLs in
-this section assume the {\tt mimir-demo} application with its
+this section assume the {\tt mimir-cloud} application with its
default URL mappings, running on {\tt localhost} port 8080.
The \Mimir\ web service can be accessed at a URL like:\\
-{\tt http://localhost:8080/mimir-demo/\{index ID\}/search/\{action\}},
+{\tt http://localhost:8080/mimir-cloud/\{index ID\}/search/\{action\}},
where the {\tt action} value is the name of one of the supported actions,
described below. The actual URL (with the correct index ID included) can be
obtained from the {\em index information page} presented by the \Mimir\ web
@@ -324,7 +324,7 @@
or an error message if there were any problems while parsing the query.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/postQuery?queryString=%22the%22!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/postQuery?queryString=%22the%22!
Example response:
\begin{lstlisting}[language=XML]
@@ -357,7 +357,7 @@
completed, or the total number of result documents otherwise.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentsCount?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentsCount?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0!
Example response:
\begin{lstlisting}[language=XML]
@@ -399,7 +399,7 @@
that returned by calling {\tt documentsCount}.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentsCurrentCount?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentsCurrentCount?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0!
Example response:
\begin{lstlisting}[language=XML]
@@ -443,7 +443,7 @@
any problems.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentId?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=3!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentId?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=3!
Example response:
\begin{lstlisting}[language=XML]
@@ -478,7 +478,7 @@
any problems.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentScore?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=3!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentScore?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=3!
Example response:
\begin{lstlisting}[language=XML]
@@ -513,7 +513,7 @@
each individual hit.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentHits?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=3!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentHits?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=3!
Example response:
\begin{lstlisting}[language=XML]
@@ -567,7 +567,7 @@
hit.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentText?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=1&termPosition=100&length=10!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentText?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=1&termPosition=100&length=10!
Example response:
\begin{lstlisting}[language=XML]
@@ -617,7 +617,7 @@
there were any problems.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentMetadata?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&documentId=1!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/documentMetadata?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&documentId=1!
Example response:
\begin{lstlisting}[language=XML]
@@ -655,7 +655,7 @@
\lstinline[language=HTML]!<span class="mimir-hit">...</span>!.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/renderDocument?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=1!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/renderDocument?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0&rank=1!
\end{minipage}\\
\hline
@@ -680,7 +680,7 @@
available.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/renderDocument?documentId=11!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/renderDocument?documentId=11!
\end{minipage}\\
\hline
@@ -708,7 +708,7 @@
An XML message with a success or failure value.
Example request:\\
-\lstinline[language=XML]!http://localhost:8080/mimir-demo/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/close?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0!
+\lstinline[language=XML]!http://localhost:8080/mimir-cloud/a4300d00-2dd1-4797-8eaa-e65b0c7d879b/search/close?queryId=a28656e2-18f4-4b58-b9d3-9a9378eb14d0!
Example response:
\begin{lstlisting}[language=XML]
@@ -743,14 +743,14 @@
Google Web Toolkit, and the source code is included in the \Mimir\ Grails
plugin.
-In the demo web application with its default URL mappings, the Web UI interface
-for an index in searching mode is available at\\
-\verb!http://localhost:8080/mimir-demo/{index ID}/search/index!. The initial
+In the {\tt mimir-cloud} web application with its default URL mappings, the Web
+UI interface for an index in searching mode is available at\\
+\verb!http://localhost:8080/mimir-cloud/{index ID}/search/index!. The initial
page, shown in figure~\ref{fig:gus:front-page}, provides a text area into which
-you can type queries in the \Mimir\ query language. It provides
-auto-completion for annotation types and features (by asking the index what
-types it was configured with when it was created). Clicking the Search button
-starts a search on the server.
+you can type queries in the \Mimir\ query language. It provides
auto-completion
+for annotation types and features (by asking the index what types it was
+configured with when it was created). Clicking the Search button starts a
search
+on the server.
\begin{figure}[tbp]
\begin{center}
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
GATE-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gate-cvs
