About

This is an example of a WordPress page, you could edit this to put information about yourself or your site so readers know where you are coming from. You can create as many pages like this one or sub-pages as you like and manage all of your content inside of WordPress.

  1. 2013-08-02 at 17:46

    Received the following sarcastic comment on this page from “Carissa”: “I am sure this paragraph has touched all the internet users, its really really pleasant piece of writing on building up new weblog.”

    I’m not approving the comment, because it looks like spam, but I did think it was very funny.

  2. 2015-06-18 at 09:23

    Hi Odontoma,

    I recently read this article of yours:
    https://odontomachus.wordpress.com/2011/05/04/crossrefs-gift-of-metadata/

    I’m just getting into this whole crossref thing, and I’m wondering if you can email to help me display meta data from pubmed articles on my website, given only the DOI.

    If you can help, it would be great šŸ™‚

    • 2016-03-12 at 22:38

      This comment showed up as ‘pending’ so I’m replying now, a bit late I admit. I think your mention of pubmed is a red herring; if you have a DOI you can get the metadata, whether the article is in pubmed or not. Use curl or wget or any http client library, with an ‘accept’ header giving application/json as the media type (there are other syntax options as well). For example:

      curl -v -H “accept: application/json” -L http://dx.doi.org/10.1080/00031305.2016.1154108
      * Adding handle: conn: 0x7f8d6b003a00
      * Adding handle: send: 0
      * Adding handle: recv: 0
      * Curl_addHandleToPipeline: length: 1
      * – Conn 0 (0x7f8d6b003a00) send_pipe: 1, recv_pipe: 0
      * About to connect() to dx.doi.org port 80 (#0)
      * Trying 38.100.138.162…
      * Connected to dx.doi.org (38.100.138.162) port 80 (#0)
      > GET /10.1080/00031305.2016.1154108 HTTP/1.1
      > User-Agent: curl/7.30.0
      > Host: dx.doi.org
      > accept:application/json
      >
      < HTTP/1.1 303 See Other
      * Server Apache-Coyote/1.1 is not blacklisted
      < Server: Apache-Coyote/1.1
      < Vary: Accept
      < Location: http://data.crossref.org/10.1080%2F00031305.2016.1154108
      < Expires: Sat, 12 Mar 2016 22:45:42 GMT
      < Content-Type: text/html;charset=utf-8
      < Content-Length: 197
      < Date: Sat, 12 Mar 2016 22:30:56 GMT
      GET /10.1080%2F00031305.2016.1154108 HTTP/1.1
      > User-Agent: curl/7.30.0
      > Host: data.crossref.org
      > accept:application/json
      >
      < HTTP/1.1 200 OK
      < Access-Control-Allow-Origin: *
      < Access-Control-Allow-Headers: X-Requested-With, Accept, Accept-Encoding, Accept-Charset, Accept-Language, Accept-Ranges, Cache-Control
      < Access-Control-Expose-Headers: Link
      < Link: ; rel=”canonical”
      < Content-Type: application/json
      < Content-Length: 1669
      * Server http-kit is not blacklisted
      < Server: http-kit
      < Date: Sat, 12 Mar 2016 22:30:56 GMT
      <
      * Connection #1 to host data.crossref.org left intact
      {"indexed":{"date-parts":[[2016,3,10]],"date-time":"2016-03-10T10:35:24Z","timestamp":1457606124712},"reference-count":0,"publisher":"Informa UK Limited","DOI":"10.1080\/00031305.2016.1154108","type":"journal-article","created":{"date-parts":[[2016,3,7]],"date-time":"2016-03-07T14:21:40Z","timestamp":1457360500000},"page":"00-00","update-policy":"http:\/\/dx.doi.org\/10.1080\/tandf_crossmark_01","source":"CrossRef","title":"The ASA's statement on p-values: context, process, and purpose","prefix":"http:\/\/id.crossref.org\/prefix\/10.1080","author":[{"affiliation":[],"family":"Wasserstein","given":"Ronald L."},{"affiliation":[],"family":"Lazar","given":"Nicole A."}],"member":"http:\/\/id.crossref.org\/member\/301","published-online":{"date-parts":[[2016,3,7]]},"container-title":"The American Statistician","deposited":{"date-parts":[[2016,3,7]],"date-time":"2016-03-07T17:38:56Z","timestamp":1457372336000},"score":1.0,"subtitle":[],"issued":{"date-parts":[[2016,3,7]]},"alternative-id":["10.1080\/00031305.2016.1154108"],"URL":"http:\/\/dx.doi.org\/10.1080\/00031305.2016.1154108","ISSN":["0003-1305","1537-2731"],"subject":["Statistics, Probability and Uncertainty","Statistics and Probability","Mathematics(all)"],"assertion":[{"label":"Peer Review Statement","name":"peerreview_statement","order":1,"value":"The publishing and review policy for this title is described in its Aims & Scope."},{"label":"Aim & Scope","name":"aims_and_scope_url","order":2,"URL":"http:\/\/www.tandfonline.com\/action\/journalInformation?show=aimsScope&journalCode=utas20","value":"http:\/\/www.tandfonline.com\/action\/journalInformation?show=aimsScope&journalCode=utas20"}]}

      Then write a script in any programming language to convert the JSON into the form you need.

      I’m not crazy about the details of the protocol; but protocol design is much less important than the fact of the availability of this information.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: