Information for Publishers

Import Button

Mendeley provides a mechanism for importing of articles based on some basic information: an article URL or DOI. With this mechanism it is possible to embed an "Add to Mendeley" button on your website. Typically we ask that sites embed a small Mendeley logo button for this purpose. If you wish to embed the button where it utilises the article page URL, please adapt the following HTML for your website:

<a title="Add this article to your Mendeley library" href="[CURRENT-PAGE-URL]"><img src=""/></a>

(replacing [CURRENT-PAGE-URL] with the current article page URL in URL encoded format.)

Please note that passing URLs will only work if your website is supported by the Mendeley Web Importer. If your website is not currently supported, please refer to the Web Importer support for your website section for support instructions.

If you wish to utilise DOIs, please adapt the following HTML for your website:

<a title="Add this article to your Mendeley library" href="[CURRENT-ARTICLE-DOI]"><img src=""/></a>

(replacing [CURRENT-ARTICLE-DOI] with the current article DOI in URL encoded format.)

Web Importer support for your website

The Mendeley Web Importer will attempt to extract metadata from pages in a variety of ways. The preferred mechanism for support is for websites to represent article metadata embedded within the page markup. The Mendeley Web Importer currently supports two types:

HTML Metatags

It is possible to detail document metadata in the HTML HEAD element of article pages by utilising the META element. The Mendeley Web Importer will attempt to extract details from appropriate META elements. There are 4 supported "standards" for describing articles in the META elements, listed in the order of usage preference:

  • Highwire Press tags (citation_*)
  • Eprints tags (eprints.*)
  • PRISM tags (prism.*)
  • Dublin Core (dc.*/dcterms.*)

Presenting more than one set of tags is not a problem; Mendeley Web will utilise the tags in order of preference. Please refer to the below examples (note that not all possible tags are covered), and to the Google Scholar inclusion guidelines for implementation information for these metatag formats.


<meta name="citation_title" content="Global and local fMRI signals driven by neurons defined optogenetically by type and wiring.">
<meta name="citation_authors" content="Lee, Jin Hyung; Durand, Remy; Gradinaru, Viviana; Zhang, Feng; Goshen, Inbal; Kim, Dae-Shik; Fenno, Lief E; Ramakrishnan, Charu; Deisseroth, Karl">
<meta name="citation_journal_title" content="Nature">
<meta name="citation_publisher" content="Nature Publishing Group">
<meta name="citation_issue" content="7299">
<meta name="citation_volume" content="465">
<meta name="citation_doi" content="10.1038/nature09108">
<meta name="citation_firstpage" content="788">
<meta name="citation_lastpage" content="792">
<meta name="citation_date" content="2010">
<meta name="citation_abstract_html_url" content="">
<meta name="citation_abstract_pdf_url" content="">

<meta name="eprints.title" content="Global and local fMRI signals driven by neurons defined optogenetically by type and wiring.">
<meta name="eprints.creators_name" content="Lee, Jin Hyung">
<meta name="eprints.creators_name" content="Durand, Remy">
<meta name="eprints.creators_name" content="Gradinaru, Viviana">
<meta name="eprints.creators_name" content="Zhang, Feng">
<meta name="eprints.creators_name" content="Goshen, Inbal">
<meta name="eprints.creators_name" content="Kim, Dae-Shik">
<meta name="eprints.creators_name" content="Fenno, Lief E">
<meta name="eprints.creators_name" content="Ramakrishnan, Charu">
<meta name="eprints.creators_name" content="Deisseroth, Karl">
<meta name="eprints.type" content="article">
<meta name="eprints.datestamp" content="2010-07-20 00:12:35">
<meta name="eprints.ispublished" content="pub">
<meta name="" content="2010">
<meta name="eprints.date_type" content="published">
<meta name="eprints.publication" content="Nature">
<meta name="eprints.volume" content="465">
<meta name="eprints.pagerange" content="788-792">

<meta name="prism.volume" content="465">
<meta name="prism.number" content="7299">
<meta name="prism.startingPage" content="788">
<meta name="prism.endingPage" content="792">
<meta name="prism.publicationName" content="Nature">
<meta name="prism.issn" content="0028-0836">
<meta name="prism.publicationDate" content="2010">
<meta name="prism.doi" content="10.1038/nature09108">

<meta name="dc.title" content="Global and local fMRI signals driven by neurons defined optogenetically by type and wiring.">
<meta name="dc.publisher" content="Nature Publishing Group">
<meta name="dc.format" content="text/html">
<meta name="dc.creator" content="Jin Hyung Lee">
<meta name="dc.creator" content="Remy Durand">
<meta name="dc.creator" content="Viviana Gradinaru">
<meta name="dc.creator" content="Feng Zhang">
<meta name="dc.creator" content="Inbal Goshen">
<meta name="dc.creator" content="Dae-Shik Kim">
<meta name="dc.creator" content="Lief E Fenno">
<meta name="dc.creator" content="Charu Ramakrishnan">
<meta name="dc.creator" content="Karl Deisseroth">
<meta name="dc.identifier" content="pmid:20473285">
<meta name="dc.identifier" content="doi:10.1038/nature09108">
<meta name="" content="2010">

COinS (ContextObjects in Spans)

Websites can embed any number of COinS into their pages. The Mendeley Web Importer will parse and extract metadata from the OpenURL strings. Assuming there is enough meaningful data available in the OpenURL strings, the document(s) will be made available for import. For information on embedding COinS onto your site, please visit the COinS website. You may also wish to refer to the OpenURL KEV implementation guidelines. Please note that we only currently support the following OpenURL metadata description formats:

Additionally, please note that whilst we support both 0.1 and 1.0 OpenURL versions, 1.0 is highly preferred.

The Mendeley Web Importer will make use of as much data as possible, so it is recommended you utilise as many OpenURL fields as possible. Providing the article DOI or PMID is also advisable -- this can be achieved by utilising the rft_id parameter (rft_id=info:doi/[DOI] or rft_id=info:pmid/[PMID], replacing [DOI] and [PMID] appropriately.)