Skip to content

fix typos in Jupyter notebook #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 25, 2018
Merged

fix typos in Jupyter notebook #282

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 16 additions & 16 deletions demos/crossref-api-demo.ipynb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
"\n",
"The examples here are in Python 3. Sorry- but you're going to have to make the move sometime ;)\n",
"\n",
"To use this librarary you can:\n",
"To use this libra ry you can:\n",
"\n",
"`pip install crossrefapi`\n",
"\n",
Expand Down Expand Up @@ -91,9 +91,9 @@
"source": [
"## Working with \"works\"\n",
"\n",
"Let's start by looking breifly 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 looking 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 identifed by a DOI. In practice, Crossref DOIs are used as citaton 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 interchangeabley. The same is true of the \"accepted manuscript\" and the \"version-of-record\" of that accepted manuscript.\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",
"In order to start querying information about works, we need to import the library and make things convenient."
]
Expand Down Expand Up @@ -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 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](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 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",
"\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",
Expand Down Expand Up @@ -244,7 +244,7 @@
}
},
"source": [
"This is bascially a huge JSON object, so you can retreive individual elements from it. Here is the publisher:"
"This is basically a huge JSON object, so you can retrieve individual elements from it. Here is the publisher:"
]
},
{
Expand Down Expand Up @@ -272,7 +272,7 @@
}
},
"source": [
"And here is the license for the \"verson of record\":"
"And here is the license for the \"version of record\":"
]
},
{
Expand Down Expand Up @@ -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 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 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 particualr, 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 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",
"\n",
"- `VOR` = Version of Record\n",
"- `AM` = Accepted Manuscript\n",
Expand Down Expand Up @@ -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 involveds 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 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. "
]
},
{
Expand Down Expand Up @@ -402,7 +402,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"Let's look at a partciularmember, Hindawi:"
"Let's look at a partciular member, Hindawi:"
]
},
{
Expand All @@ -425,7 +425,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"**TIP:** Many people make the mistake of thinking that a \"DOI prefix\" can be used to identify the member responsible for a Crossref DOI. This is not true. DOI prefixes merely serve as a namspace form which a member can create new DOIs without worrying about collisions. But, once created, Crossref DOIs are often transfered between publishers and so a Crossref member will often be responsible for DOIs with a variety of prefixes. So, for example, above, Hindawi is responsible for several prefixes:"
"**TIP:** Many people make the mistake of thinking that a \"DOI prefix\" can be used to identify the member responsible for a Crossref DOI. This is not true. DOI prefixes merely serve as a namespace form which a member can create new DOIs without worrying about collisions. But, once created, Crossref DOIs are often transfered between publishers and so a Crossref member will often be responsible for DOIs with a variety of prefixes. So, for example, above, Hindawi is responsible for several prefixes:"
]
},
{
Expand Down Expand Up @@ -679,7 +679,7 @@
}
},
"source": [
"A publisher record also contains a useful summary of the member's metadata and the Crossref services that they particpate in.\n",
"A publisher record also contains a useful summary of the member's metadata and the Crossref services that they participate in.\n",
"\n",
"Let's look at what percentage of their metadata includes certain information:"
]
Expand Down Expand Up @@ -727,7 +727,7 @@
}
},
"source": [
"Now let's see what Crossref services they particpate in:"
"Now let's see what Crossref services they participate in:"
]
},
{
Expand All @@ -742,8 +742,8 @@
},
"outputs": [],
"source": [
"particpation = [[key,pub['flags'][key]] for key in pub['flags'].keys()]\n",
"f = pd.DataFrame(particpation)\n",
"participation = [[key,pub['flags'][key]] for key in pub['flags'].keys()]\n",
"f = pd.DataFrame(participation)\n",
"f.columns = ['service','paticipation']\n",
"f"
]
Expand Down Expand Up @@ -796,7 +796,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"## Some outher resources\n",
"## Some other resources\n",
"\n",
"### Types"
]
Expand Down Expand Up @@ -915,7 +915,7 @@
}
},
"source": [
"Works records indexed _today_ that have affiliatioon data"
"Works records indexed _today_ that have affiliation data"
]
},
{
Expand Down