Supplementary Data links for Publishers

PANGAEA provides several REST-based services to link supplementary data at publisher's abstract pages:

Simple REST service for banner-based linking

The REST service for banner-based linking provides two functions.

All example URLs are suited only for an "example publisher". Other publishers will get their custom banner using their own one design requirements. Also for tracking purposes, the URLs below may never be used unmodified for other publishers! Other publishers will get the "/example-publisher/" part of the URL replaced by their name.

Linking Banner

REST service generates a GIF image with a banner image, if a data set is available. The encoding of the paper DOI name must be in the same format like dx.doi.org needs it. Any special characters should be urlencoded using the UTF-8 encoding. For most DOIs consisting of only ASCII chars, no encoding is needed most times:

http://linkinghub.pangaea.de/example-publisher/supplementBanner/doi:10.1016/j.margeo.2006.07.006 

If no data is available, the service returns a transparent one-pixel-gif image:

http://linkinghub.pangaea.de/example-publisher/supplementBanner/doi:10.1016/somefakedoi

This image can be included as SRC-Attribute for a HTML <img/> tag.

The second REST service is a resolver/redirector:

http://linkinghub.pangaea.de/example-publisher/redirectToSupplement/doi:10.1016/j.margeo.2006.07.006 

Encoding is the same, only the action is different. This link redirects the user to the supplementary dataset behind the paper DOI name. You may put this URL in a <a href=”…”> around the image. If the image is empty (1 pixel, the user is normally not able to click on it, if he does, he will be directed to an information page on www.pangaea.de, describing that there is no supplement available). If it works you get a 301 redirect (because the linking hub url is not generally available and should not be indexed by search engines, search engines should use the DOI-link of PANGAEA, this is why it is a permanent redirect).

General Usage

In complete you can insert the following HTML into your artcle abstract webpage (replacing the DOI name to the encoded current article’s DOI name):

<a href="http://linkinghub.pangaea.de/example-publisher/redirectToSupplement/doi:10.1016/j.margeo.2006.07.006">
 <img src="http://linkinghub.pangaea.de/example-publisher/supplementBanner/doi:10.1016/j.margeo.2006.07.006" style="border:none" />
</a>

In real life the link looks like this: "", if no supplement available: "" (you should see nothing)

Scholix Framework

As a replacement for previous banner-linking and Gadget (Elsevier only, retired) approaches, PANGAEA now reports all dataset/reference links to the Scholix framework by using the DLI Service.

The goal of the Scholix initiative is to establish a high level interoperability framework for exchanging information about the links between scholarly literature and data. It aims to enable an open information ecosystem to understand systematically what data underpins literature and what literature references data. The DLI Service is the first exemplar aggregation and query service fed by the Scholix open information ecosystem. The Scholix framework together with the DLI aggregation are designed to enable other 3rd party services (domain-specific aggregations, integrations with other global services, discovery tools, impact assessments etc).

Scholix is an evolving lightweight set of guidelines to increase interoperability. It consists of:

• A consensus among a growing group of publishers, datacentres, and global/ domain service providers to work collaboratively and systematically to improve exchange of data-literature link information
• Information model: conceptual definition of what is a Scholix scholarly link
• Link metadata schema: metadata representation of a Scholix link

Options for exchange protocols (forthcoming)

Scholix is the “wholesaler to wholesaler” exchange framework, to be implemented by existing hubs or global aggregators of data-literature link information such as DataCite, CrossRef, OpenAIRE, or EMBL-EBI. These hubs in turn work with their natural communities of data centres or literature publishers to collect the information through existing community-specific workflows and standards. Scholix thus enables interoperability between a smaller number of large hubs and leverages the existing exchange arrangements between those hubs and their natural communities (eg between CrossRef and journal publishers). Scholix is a technical solution to wholesale information aggregation; it will need to be complemented by other policy, practice and cultural change advocacy initiatives. This approach could be extended over time to other types of research objects in and beyond research (e.g. software, tweets, etc).