Banner Image Widget API

Overview:

This API provides banner images that can be used on external websites to link to Dryad content.

GET /widgets/bannerForPub
When making a GET request to, it will respond with an image. If the provided Article identifier (parameter ) is linked to a data package in Dryad, the pipeline returns the 'Data in Dryad' image banner (shown to the right). If the Article identifier is not found, the pipeline returns a 1x1 transparent gif.

Parameters:
 * : an article DOI or PubMed ID. The identifier may be expressed with a prefix of "pmid:", "doi:", or "http://dx.doi.org/". The identifier must be URL-encoded. Example: doi%3A10.1186%2F1471-2148-12-60
 * : a self-created identifier for the tool/entity using the widget, URL encoded. Required, but not currently used in determining the response. This code is logged internally so Dryad can provide statistics related to use of the widget. Examples: BMC, Elsevier, JDataSharing

GET /widgets/dataPackageForPub
When making a GET request to, the server responds with a redirect to the Dryad Data Package resource page (e.g., http://datadryad.org/resource/doi:10.5061/dryad.8h5p7p00) if there is a data package in Dryad for the provided article  , and to an empty page (http://datadryad.org/resource/) otherwise.

Parameters:
 * : an article DOI or PubMed ID. The identifier may be expressed with a prefix of "pmid:", "doi:", or "http://dx.doi.org/". The identifier must be URL-encoded. Example: doi%3A10.1186%2F1471-2148-12-60
 * : an identifier for the tool/entity using the widget, URL encoded. Required, but not currently used in determining the response. This code is logged internally so Dryad can provide statistics related to use of the widget. Examples: BMC, Elsevier, JDataSharing

Usage
As an example, the widget can be constructed to automatically display a linked banner if Dryad has data for the article doi:10.1186/1471-2148-12-60 as follows:

  

Technical Implementation
This feature is implemented as a cocoon pipeline that is mounted at /widgets (see sitemap.xmap in XMLUI and widgets.xmap)

Implementing this pipeline as an aspect (See Manakin Reference) was attempted, but the cocoon pipeline used by the Manakin aspects is "internal-only". Dynamically reading and returning an image instead of an XML document will result in an error: org.apache.cocoon.ProcessingException: Streaming of an internal pipeline is not possible with a reader..

The switching logic is implemented by WidgetBannerSelector.java, which returns true if the provided DOI can be resolved, and false otherwise.

The resolution of the appropriate response uses WidgetBannerAction.java to obtain the Dryad Data Package DOI that corresponds to the provided Article DOI.

Both URLs expect a publisher and an identifier (The DOI of an article) as query parameters. These parameters should be URL-encoded, e.g. http://datadryad.org/widgets/bannerForPub?referrer=SSE&pubId=doi%3A10.1111%2Fj.1558-5646.2007.00022.x http://datadryad.org/widgets/dataPackageForPub?referrer=SSE&pubId=doi%3A10.1111%2Fj.1558-5646.2007.00022.x