Merge branch 'zuphilip-patch-1'

Author: gbilder

demos/crossref-api-demo.ipynb

@@ -17,7 +17,7 @@
     "[`https://www.crossref.org/works`](https://api.crossref.org/works)\n",
     "\n",
     "\n",
-    "This means the REST API is pretty easy to use with basic low level HTTP libraries(e.g. Python's `requests`), but for this tutorial we are going to use a [higher level python library](https://github.com/fabiobatalha/crossrefapi) developed by Fabio Batalha C. Santos at [Scielo](www.scielo.org).\n",
+    "This means the REST API is pretty easy to use with basic low level HTTP libraries(e.g. Python's `requests`), but for this tutorial we are going to use a [higher level python library](https://github.com/fabiobatalha/crossrefapi) developed by Fabio Batalha C. Santos at [SciELO](http://www.scielo.org).\n",
     "\n",
     "The examples here are in Python 3. Sorry- but you're going to have to make the move sometime ;)\n",
     "\n",
@@ -91,7 +91,7 @@
    "source": [
     "## Working with \"works\"\n",
     "\n",
-    "Let's start by looking briefly looking at\"works\". The route refers to items identified by a DOI in the index. These can be articles, books, components, etc.\n",
+    "Let's start by looking briefly at\"works\". The route refers to items identified by a DOI in the index. These can be articles, books, components, etc.\n",
     "\n",
     "**TIP:** Crossref does not use \"works\" in the [FRBR](https://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records) sense of the word. In Crossref parlance, a \"work\" is just a thing identified by a DOI. In practice, Crossref DOIs are used as citation identifiers. So, in FRBR terms, this means, that a Crossref DOI tends to refer to one _expression_ which might include multiple _manifestations_. So, for example, the ePub, HTML and PDF version of an article will share a Crossref DOI because the differences between them should not effect the interpretation or crediting of the content. In short, they can be cited interchangeably. The same is true of the \"accepted manuscript\" and the \"version-of-record\" of that accepted manuscript.\n",
     "\n",
@@ -153,7 +153,7 @@
     }
    },
    "source": [
-    "Note that above I said \"How many Crossref DOIs\". There are several other [DOI registration agencies](https://www.doi.org/registration_agencies.html). Crossref is by far the largest DOI RA, and the other RAs tend to specialize in orthogonal areas (e.g. Music & Video, Local language translations of publications, etc.) but it is important to note that this API will not work with non-Crossref DOIs (though [DataCite](www.datacite.org]), another RA, provides a very similar API).\n",
+    "Note that above I said \"How many Crossref DOIs\". There are several other [DOI registration agencies](https://www.doi.org/registration_agencies.html). Crossref is by far he largest DOI RA, and the other RAs tend to specialize in orthoganal areas (e.g. Music & Video, Local language translations of publications, etc.) but it is important to not that this API will not work with non-Crossref DOIs (though [DataCite](https://www.datacite.org/), another RA, provides a very similar API).\n",
     "\n",
     "**TIP:** Not all DOIs are Crossref DOIs. If you are having trouble using a DOI with Crossref's API, check to see if it is a Crossref DOI.\n",
     "\n",
@@ -303,7 +303,7 @@
    "source": [
     "Um... That was complicated. What does 'vor' mean?\n",
     "\n",
-    "**TIP:** Publishers sometimes record information for multiple versions of the content identified by a DOI. These versions should be interchangeable from the point of view of citation, but sometimes one version has more \"features\" than another. For example, it might be typset or have references linked, etc. The two versions might also have different licenses and different URLs. The terminology publishers use for identifying versions comes from the [NISO standard called JAV (Journal Artcle Version)](http://www.niso.org/publications/rp/RP-8-2008.pdf) and, although this terminology is [sometimes problematic](https://f1000research.com/articles/6-608/v1), you should be aware of it. In particular, you will see two terms used  in Crossref metadata:\n",
+    "**TIP:** Publishers sometimes record information for multiple versions of the content identified by a DOI. These versions should be interchaneable from the point of view of citation, but sometimes one version has more \"features\" than another. For example, it might be typset or have references linked, etc. The two versions might also have different licenses and different URLs. The terminology publishers use for identifying versions comes from the [NISO standard call JAV (Journal Article Version)](http://www.niso.org/publications/rp/RP-8-2008.pdf) and, although this terminology is [sometimes problematic](https://f1000research.com/articles/6-608/v1), you should be aware of it. In particualr, you will see two terms used  in Crossref metadata:\n",
     "\n",
     "- `VOR` = Version of Record\n",
     "- `AM` = Accepted Manuscript\n",
@@ -332,7 +332,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The above has given us a brief overview of how to get a record and elements of a record identified with a Crossref DOI. Obviously, the goald is to do this in bulk. That is, to select and process records for multiple Crossref DOIs. Before we do that, it is helpful to familiarise yourself with some of the other \"routes\" supported by the REST API. This is because more advanced usage of the API typically involves combining information from several routes. "
+    "The above has given us a brief overview of how to get a record and elements of a record identified with a Crossref DOI. Obviously, the goal is to do this in bulk. That is, to select and process records for multiple Crossref DOIs. Before we do that, it is helpful to familiarise yourself with some of the other \"routes\" supported by the REST API. This is because more advanced usage of the API typically involveds combining information from several routes. "
    ]
   },
   {
@@ -867,8 +867,7 @@
    "source": [
     "from crossref.restful import Works\n",
     "works = Works()\n",
-    "zika_sample = [work for work in works.query('zika').sample(10)]\n",
-    "zika_sample"
+    "works.query('zika').url"
    ]
   },
   {
@@ -886,7 +885,8 @@
    "source": [
     "from crossref.restful import Works\n",
     "works = Works()\n",
-    "works.query('zika').url"
+    "zika_sample = [work for work in works.query('zika').sample(10)]\n",
+    "zika_sample"
    ]
   },
   {