Release Notes: 2015-03-10

Abstract Retrieval API

·         Return of ‘article-number’ in ‘coredata’ section of the response.

Abstract Citation Count API

·         New functionality to return citation count as metadata responses. This supports the ability to retrieve the counts for multiple identifiers. Note that the ability to retrieve this metadata is considered a separate resource, which is not enabled by default for all users.

Article Usage API

·         Revisions to support request payload as defined by the Content-Type application/vnd.crossref.det-envelope+json;v=1.0.0. The payload looks something like this:

{
"uuid": "e583eca0-fdf4-45ff-8c8e-2c3ce1196ea7",
"message-type": "counter-download",
"source-token": "hZqJDbcbKSSRgRG_PJxSBA",
"message":

{ "doi": "10.1016/S0014-5793(01)03313-0", "content-type": "application/pdf", "user-ip": "127.1.1.1" }
}

Where:

uuid: an identifier that uniquely defines the envelope and is meant to enable idempotent processing of reported events. This will functionally replace passing the query string parameter ‘reqId’ or the HTTP header ‘X-ELS-ReqId’.

message-type: a string that identifies the content type of the message


message: a JSON object containing the application-specific message.

Article Entitlement API

Enhancement:

·         Supports the ability to specify ‘application/xml’ as a response format.

·         Support of comma-delimited list of identifiers in the query string parameters ‘pii’, ‘doi’, or ‘eid’. Note that use of scopus_id and pubmed_id are not supported as multi-identifier requests.

·         Return of ‘scopus_id’ or ‘pubmed_id’ in the response payload when either of those identifiers is used in the request.

Scopus Search API

Enhancement:

·         Omit initials from ‘authname’ element if given-name is provided. This eliminates the potential duplication of initials when given-name contains initials.

·         Return of ‘pii’ in the response, when available.

Serial Title Metadata API

Enhancement:

·         Return of metric ‘IPP’ in response, which is returned as an element or list of elements similar to SJR and SNIP.

Smart Content Annotation API

Bug fix:

·         Responses with UTF-8 characters are not properly encoded.