Clinical Key

Hi Everyone
I'm not sure if this is the right question to ask but does zotero work with Clinical Key? Is there a "site translator" for it?

When I search in Clinical Key using Zotero with the Firefox browser the "save to zotero" icon is grayed out and saves minimal data when clicked. Thank you!
  • No, there's no translator and this is the first time that's been requested. My sense would be this is less used in academic environments and more for practitioners, is that correct?
  • @mmckone - I've started working on a translator for Clinical Key; I'll try to update this thread if it progresses.

    @adamsmith - I think it is aimed at practitioners. However, my institute's library look-up service sometimes links me to articles within clinical key, which is why I'm trying to write a site translator.
  • Hi! I have found one translator for C K books on GitHub but not for the articles. Let me know if there is any out there! My institution uses C K for a significant portion of the resources!
  • A while back, I reached out to Clinical Key and asked them to embed the metadata in the page or include a DOI. They never responded to my email (not surprisingly).

    I tried working on an XPath solution but got annoyed and gave up. https://groups.google.com/forum/#!topic/zotero-dev/MycHojw-Zdc

    Since then, I've found that there may be a solution for the articles. The only identifier supplied in Clinical Key is the PIIs (Publisher Item Identifier). Elsevier's API (which can retrieve PIIs) conditions wouldn't cover this use case. However, we could use the CrossRef REST API (https://github.com/CrossRef/rest-api-doc/blob/master/rest_api.md) and performing a query (http://api.crossref.org/works?query=...) with the PII to retrieve metadata for the publication.

    I think that leveraging this REST API could be implemented into Zotero. However, that would require the development team to be interested in employing an additional look-up tool. We already use another CrossRef look-up service to query DOIs (openurl)(https://github.com/zotero/translators/blob/e04633baeaac2c62eddb4435e517ae7d51c89a73/CrossRef.js#L335). And, as @adamsmith pointed out in the google group link above, it is a less than ideal solution.

    After Zotero 5.0 is rolled out, I'll see if the developers find this solution (CrossRef REST API) to be an acceptable route for Clinical Key.
  • edited January 20, 2017
    Since DOI metadata actually comes straight from the publisher (publisher deposit it with CrossRef) I'd be OK with that lacking other options. It's much more precise and less error-prone than ISBNs which have no centralized metadata holder.

    Typical REST APIs (and I'm pretty sure that applies here) just require a simple GET call to get an item response (some type of JSON here that you could then pass), this should be relatively straightforward on the Zotero side and I don't think CrossRef requires a user key for that one.

    Edit: that said -- have you tested this? I see no mention of piis or similar inernal IDs on the CrossRef docs.
  • "I don't think CrossRef requires a user key for that one."
    --You're right; as far as I understand, that's the case with this API

    "have you tested this? I see no mention of piis or similar internal IDs on the CrossRef docs"
    --You're right, the docs don't mention it (as far as I've found). On a whim, I gave it a try and it worked. Here are a few different requests from an assortment of PIIs:

    Journal Articles
    http://api.crossref.org/works?query=S0143416016300951
    http://api.crossref.org/works?query=S1424390312001962
    http://api.crossref.org/works?query=S0016508512009250
    http://api.crossref.org/works?query=S073510971001154X


    The query doesn't seem to work with ISBNs & books. However, as @jmeyerszary pointed out, there is a translator in the github repository that works for Clinical Key books, but not journal articles.

    https://github.com/zotero/translators/blob/master/Clinical Key.js

    At a quick glance, it seems to have functions for both scraping the page for metadata and the ISBN look-up tool. Perhaps this REST API could be added to the translator and expand it functionality.
  • yes, we'd want this added to the existing Clinical Key translator which is pretty new. We discussed the ISBN solution when accepting it and decided that while not ideal it was better than scraping from the page.
  • @jmeyerszary with the help of @adamsmith, we were able to get a translator to handle journal articles in addition to books (but not journal or book table of contents).

    I'm not sure how long it will take before the next update is pushed out, but you should see it soon.
    While I sometimes use Clinical Key, it is very infrequent. Since it sounds like you use it quite frequently, let us know how it works out.
  • Translators are updated automatically every 24hs, i.e. this should work for everyone now.
Sign In or Register to comment.