New York Times – Article Search API v. 2
From the documentation page:
With the Article Search API, you can search New York Times articles from Sept. 18, 1851 to today, retrieving headlines, abstracts, lead paragraphs, links to associated multimedia and other article metadata.
The prior Article Search API described itself as:
With the Article Search API, you can search New York Times articles from 1981 to today, retrieving headlines, abstracts, lead paragraphs, links to associated multimedia and other article metadata.
An addition of one hundred and eighty years of content for searching. No bad for a v. 2 release.
On cursory review, the API does appear to have changed significantly.
For example, the default fields for each request in version 1.0 were body, byline, date, title, url.
In version 2.0, the default fields returned are: web_url, snippet, lead_paragraph, abstract, print_page, blog, source, multimedia, headline, keywords, pub_date, document_type, news_desk, byline, type_of_material, _id, and word_count.
Five default fields for version 1.0 versus seventeen for version 2.0.
There are changes in terminology that will make discovering all the changes from version 1.0 to version 2.0 non-trivial.
Two fields that were present in version 1.0 that I don’t see (under another name?) in version 2.0 are:
dbpedia_resource:
DBpedia person names mapped to Times per_facet terms. This field is case sensitive: values must be Mixed Case.
The Times per_facet is often more comprehensive than dbpedia_resource, but the DBpedia name is easier to use with other data sources. For more information about linked open data, see data.nytimes.com.
dbpedia_resource_url:
URLs to DBpedia person names that have been mapped to Times per_facet terms. This field is case sensitive: values must be Mixed Case.
For more information about linked open data, see data.nytimes.com.
More documentation is promised, which I hope includes a mapping from version 1.0 to version 2.0.
Certainly looks like the basis for annotating content in the New York Times archives as part of a topic map.
Where users input their authentication details for the New York Times and/or other pay-per-view sites.
I can’t imagine anyone objecting to you helping them sell their content. 😉