Webconfig-model.xml

webconfig-model.xml configures aspects of how data appears on the InterMine webapp.

It is not required that all classes in your model appear in this file. If a class is not included in this file, the fields will be displayed according to the default behaviour (see below).

NB: This file allows for inheritance - a subclass will inherit the 'long displayers' from its parent class, but only if that subclass has no long displayers set. Configuration settings for the parent class do not overwrite settings for the subclass.

See: Tagging, CustomiseWebapp for more customisation options.

Field Configuration

You can configure which fields are displayed on report and result pages for each class in your model.

attribute name	purpose	required?	default
fieldExpr	field name	yes	-
displayer	custom displayers for fields	no	-
showInInlineCollection	show field in inline collection	no	true
showInSummary	add field to query when user clicks on 'Summary' button in QueryBuilder	no	true
showInResults	show field in results table	no	true

For example:

  <class className="org.flymine.model.genomic.ArtificialDeletion">
    <fields>
      <fieldconfig fieldExpr="primaryIdentifier"/>
      <fieldconfig fieldExpr="secondaryIdentifier"/>
      <fieldconfig fieldExpr="length" displayer="/model/sequenceShortDisplayerWithField.jsp" />
      <fieldconfig fieldExpr="chromosomeLocation" displayer="/model/chromosomeLocDisplayer.jsp" showInResults="false" />
      <fieldconfig fieldExpr="chromosome.primaryIdentifier" showInInlineCollection="false" showInSummary="false" />
      <fieldconfig fieldExpr="chromosomeLocation.start" showInInlineCollection="false" showInSummary="false" />
      <fieldconfig fieldExpr="chromosomeLocation.end" showInInlineCollection="false" showInSummary="false" />
      <fieldconfig fieldExpr="available"/>
    </fields>
    <!-- inherits longdisplayers -->
  </class>

Displayer Configuration

For any class in the model, custom JSP pages can be inserted into the report pages under the "Further information" section. These custom JSPs are referred to as "long displayers". Please see Custom data displayers for detailed information on building and using displayers.

  <class className="org.flymine.model.genomic.BindingSite">
    <fields>
      <fieldconfig fieldExpr="primaryIdentifier"/>
    </fields>
    <longdisplayers>
      <displayer src="attributeLinkDisplayer.tile"/>
      <displayer src="/model/locatedSequenceFeatureImage.jsp"/>
    </longdisplayers>
  </class>

See: Custom data displayers

Export Configuration

Users can export data from InterMine in comma or tab-delimited files and in MS Excel format. InterMine also allows for the addition of custom exporters. To add a custom exporter, create a Java class to format the data and add an entry to the web config file, for example:

  <tableExportConfig id="sequenceExporter" actionPath="/exportAction?type=sequenceExporter"
                     className="org.intermine.bio.web.export.SequenceHttpExporter"/>
  <tableExportConfig id="gff3Exporter" actionPath="/exportAction?type=gff3Exporter"
                     className="org.intermine.bio.web.export.GFF3HttpExporter"/>

Widget Configuration

At the bottom of the config file are the configuration entries for widgets. Please see Widgets for detailed information about how to configure widgets.

      <enrichmentwidgetdisplayer id="protein_features" title="UniProt Features"
                                 link="org.intermine.bio.web.widget.UniProtFeaturesURLQuery"
                                 dataSetLoader="org.intermine.bio.web.widget.UniProtFeaturesLdr"
                                 label="Feature"
                                 description="UniProt features enriched for proteins in this list."
                                 filters=""
                                 filterLabel=""
                                 typeClass="org.flymine.model.genomic.Protein"
                                 max="0.10"  />

See: Widgets