The SuperUser is the administrator of your InterMine webapp. The SuperUser can use tagging to configure the appearance and functionality of the webapp.
The SuperUser account is created when the UserProfile database is built using the properties specified in the Intermine properties file.
All logged in users can create template queries, but the SuperUser can make them available to all users by tagging them as public templates. Making a template query is an easy way to get users of your webapp to the data they want very quickly.
The SuperUser can change where templates and lists appear by adding tags via the templates and lists pages in the MyMine section of the webapp. Only the administrator can apply/view/edit tags starting at
im: . The tag data is stored in the user-profile database.
|make list/template viewable by all users
|put list on home page
|template used in generating links in the ‘Convert’ section on the list analysis page
|template appears underneath specified category. For instance, template with im:aspect:Genomics tag will be displayed in Genomics category on the report page and on the home page
|allows template to be displayed on report or list analysis page
|specify the order lists should go in (on homepage only currently). If two lists have the same Integer “n” value, natural ordering on the list name will be applied as a decisive criterion
 Editable by all admins
The SuperUser can change how fields are displayed by adding tags via the report page.
|hides the field/collection
|adds collection to ‘Summary’ section of report page
|collection appears underneath category
The SuperUser can change how classes are displayed by adding tags via the model browser.
|class appears on aspect page
|class appears first in the class selection
If a template is tagged with
im:converter, it is:
- Used by the list analysis page, in the "Convert" section.
- Used by the list upload page to convert between types.
- E.g., the user pastes in a protein identifier, but chooses "Gene" from the type dropdown menu. A converter template can be used to look up the
Genecorresponding to the given
To work as a converter, the template must follow the following pattern:
- the top-level class in the query must be the class we wish to convert from (eg.
- there must be exactly one editable constraint - the
idfield of the top level class (eg.
- the fields selected for output must be
Gene.idand the id field of the class to convert to
id field isn't shown in the query builder and probably isn't useful in other queries. Only the administrator user can create queries using the
id field. Here is an example converter template: