...
| Authority | Results Format | Extent of Data Returned | Example Search API URL | Documentation | Comments |
|---|---|---|---|---|---|
| AGROVOC | JSONLD - skos ontology | URI, skos:prefLabel | http://agrovoc.uniroma2.it/agrovoc/rest/v1/search/?query=*milk*&lang=en&maxhits=10 | SKOSMOS REST APIs | Additional Information |
| Getty | |||||
| ISNI | RDF/XML, JSON-LD | http://isni-acc.oclc.org/sru/DB=1.2/?query=pica.na+%3D+%22Piketty%2C+Thomas%22&operation=searchRetrieve&recordSchema=isni-rdf | to be released | See ISNI below | |
| Library of Congress - Search API | HTML, ATOM/XML, ATOM/JSON | URI (with some formats), preferred label | See "Searching" and "Search Limits..." | See LC Search API below | |
| Library of Congress - Suggest API | JSON | Preferred label, URI | http://id.loc.gov/authorities/names/suggest/?q=camus | See LC Suggest API below | |
| MeSH | |||||
| OCLC | |||||
| ShareVDE | |||||
| Wikidata | |||||
| add additional authorities |
...
Information about these can be found at How to Access AGROVOC (Technical Documentation for all Endpoints).
ISNI
ISNI is the ISO certified global standard number for identifying the millions of contributors to creative works and those active in their distribution. The mission of the ISNI International Agency (ISNI-IA) is to assign to the public name(s) a persistent unique identifying number in order to resolve the problem of name ambiguity in search and discovery; and diffuse each assigned ISNI across all repertoires in the global supply chain so that every published work can be unambiguously attributed to its creator wherever that work is described. By achieving these goals, the ISNI will act as a bridge identifier across multiple domains and become a critical component in Linked Data and Semantic Web applications.
ISNI as Linked Data is still in test phase, but a first version is expected to be released, soon.
- The on-line search facility is based on SRU (See above) and allows multiple search keys as well as multiple result formats (xml, rdf/xml, jsonld)
- Linked Data serializations can be retrieved using content negotiation on the ISNI canonical form (isni.org/isni/{ISNI})
- A data dump for testing purposes will soon be available.
LC Search API
LC's HTML results and ATOM results (either as XML or JSON) are actually serializations of the output from LC's internal search API. There is no daylight, therefore, between the types of searches that can be performed by a human using the HTML UI or by a machine making requests of the service. LC Search supports generic keyword searching, with no limits of any kind, but only labels and a few other key data points are actually searched. Notes, for example, are not searchable. It supports limiting searching to specific datasets and date ranges (undocumented, which is an oversight). It supports targeted searches for specific labels, tokens (such as LCCNs), or codes. It supports wildcards, boolean keywords, and negation. Results are sorted by relevancy and, depending on the type of search, results may be weighted to preference "higher value" resources, such as Names, Subjects, or BF Resources, versus resources that play a supporting role in library data, such as regional encodings or broadcast standards. With the use of key search limits/filters and wildcarding, it is theoretically possible to make the generic search service closely mimic the LC Suggest API, at least in terms of results (not sure if the sort order can be manipulated easily). The Search API's output is intentionally generic.
...