WebappConfig > Summarising an ObjectStore

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 latter is configured by adding entries to the objectstoresummary.config.properties; be sure to select those fields that only have a few possible values and should be shown in a dropdown.

An example from malariamine/dbmodel/resources/objectstoresummary.config.properties

Autocompletion

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:

1. Add all fields you want to be autocompleted to this file, like so:

   # in MINE_NAME/dbmodel/resources/objectstoresummary.config.properties
   org.intermine.model.bio.Disease.autocomplete = description
   

2. Add the postprocess to your MINE_NAME/project.xml file.

     <post-processing>    
       <post-process name="create-autocomplete-index"/>
     </post-processing>
   

3. In the /postprocess directory, run this command:

   # 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.

See: PostProcessing

---

Back: WebappConfig