Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
InterMine Tool Integration

Thanks to Vivek for his great proposal!


  • Dependencies are bundled into the app (requirejs, browserify, webpack)

Our justification is that sharing dependencies between third party tools introduces levels of complexity that are expensive (time consuming) and can be challenging to developers. If we find that third party apps are truly to large then we'll reconsider a more complicated approach.

App structure:

+-- myapp/
|   +-- app.css (optional)
|   +-- config.json (required)
|   +-- package.json (required)
|   +-- src/myapp.js (reflected in package.json as "main")
|   +-- template.html (optional)


  "accepts": ["id" "ids" "list" "lists" "records" "rows"],
  "classes": ["Gene" "Protein" "*"]
  • id: a single database id
  • ids: multiple database ids
  • list: a single list name
  • lists: multiple list names
  • records: a raw result from POSTing to /query/results with format "jsonobjects"
  • rows: a raw result from POSTing to /query/results with format "json"

Plurality (i.e. id vs ids) will help to determine which context a tool can appear (report page, list analysis page)

Records and Rows can also be accepted. The advantage here is that BlueGenes has likely already run and stored the query results in memory, so the tool can skip a redundant call to the server.


Must export a constructor function with the same package name found in package.json

var MyApp = function(el, service, package, state) {
  // ...
  • el: the id of a dom element where the tool will render
  • service: an object representing an intermine service
  "root": "",
  "token": "bananacakes"
  • package: an object representing the data passed to the app
  "class": "Gene",
  "format": "ids",
  "value": [123, 456]
  • state: the last state of the tool (more on this later)


This must have property specifying the entry point

  "main": "[some]/[app].js"


This is an optional chunk of HTML that will be injected into the div during initial rendering. No <head> or <body> tags.


If found it will be automatically namespaced and injected into the target element


  • Apps will be installed to bluegenes/resources/public/apps/[someapp]
  • If an app.css is present it will be preprocessed using LESS to provide a namespace
  • We will use jQuery's getScript() function to load the app on demand
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment