Information for Publishers
How to ensure Mendeley Web Importer can read references from your website
Mendeley Web Importer tries to get reference metadata from pages in four ways.
1. DOI lookup (Recommended)
If the DOI (Digital Object Identifier) of the reference on the page is tagged correctly, Mendeley Web Importer will automatically read it and retrieve metadata for the reference.
We recommended specifying DOIs on your pages using the following META syntax:
<meta name="citation_doi" content="10.1038/nature09108">
2. HTML Meta Elements (Supported)
Sometimes a reference does not have a DOI, so Mendeley Web Importer also supports reading other META elements directly.
For catalog pages, HTML meta elements should be specified in the HTML HEAD section.
There are 5 supported "standards" for describing articles in the META elements:
- Highwire Press tags
- bepress tags
- Eprints tags
- PRISM tags
- Dublin Core
Presenting more than one set of tags is not a problem. Use Dublin Core tags only as a last resort because they lack unambiguous fields for journal articles.
Here is an example of how an HTML page may be marked up with META elements:
<meta name="citation_title" content="Global and local fMRI signals driven by neurons defined optogenetically by type and wiring.">
3. Metadata extraction (Fallback)
It is sometimes not possible or feasible to implement HTML META elements for standalone PDF content.
In this case, Mendeley Web Importer will upload the PDF file to its PDF metadata extraction service to identify metadata heuristically. (The uploaded PDF is discarded after processing and not stored on the server.)
It is not possible for this service to operate with 100% accuracy. Providing DOI or HTML META elements specifying metadata is preferred.
4. COinS – ContextObjects in Spans (Legacy)
COinS was a method of making metadata available within <span> elements in HTML, but is now largely unsupported. We are no longer officially supporting COinS, but we retain our legacy COinS parsers within the application as a last resort for legacy compatibility.
Please note that we only currently support the following OpenURL metadata description formats:
Both 0.1 and 1.0 OpenURL versions should work, but no assurances is made regarding compatibility.