There are several processes run after the data loading is completed, one of which the objectstore summarisation. This step counts the number of objects of particular classes, identifies any empty references/collections and collects values to be appear in dropdowns in the query builder and templates. The summarisation process also constructs the indexes needed for “type-ahead” autocompletion, this is configured by adding entries to the ObjectStore Summary file.
Some fields have only a few different values, and are represented as dropdowns on forms so that users may see all possible values. You can set the maximum number of values to display, the default is 200.
To update a template query’s dropdowns to only legal values, navigate to the templates page in “my mine” and click on the “summarise” link.
Also, if your database has tables that should be ignored, you can set this too:
# in objectstoresummary.config.properties ignore.counts=org.intermine.model.bio.GOAnnotation.withText org.intermine.model.bio.Location.subject
Fields in template queries and the QueryBuilder can have type-ahead autocompletion to assist in selecting valid terms. As you start to type, possible matches are fetched from the database; the text you have typed can match anywhere within the terms and multiple words can be matched. This is particularly useful for ontology terms or protein domain names.
You can set up autocompletion by completing these steps:
<post-processing> ... <post-process name="create-autocomplete-index"/> </post-processing>
# in malariamine/postprocess $ ant -Daction=create-autocomplete-index
This process will add all fields set in this properties file to the autocompletion index.
Now, when you release your webapp, fields you’ve configured will suggest similar terms as users are typing in the QueryBuilder or the template form.
To make a template constraint optional: