Authorities Summary
Quick summary of primary information about each authority.
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 | |||||
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 |
Additional Information
Details that are helpful in understanding and working with authorities.
Agrovoc
AGROVOC is a controlled vocabulary covering all areas of interest of the Food and Agriculture Organization (FAO) of the United Nations, including food, nutrition, agriculture, fisheries, forestry, environment etc. It is published by FAO and edited by a community of experts.
Stores data in Fuseki triple store and provides SKOSMOS rest API for searching and browse. Includes endpoints...
- SKOSMOS REST APIs - search API (in table above),
- ONLINE : SKOSMOS : Search & browse
- File for DOWNLOAD. Two distributions are provided: (a) CORE , which only includes AGROVOC concepts (RDF and NT format), and (b) Linked Open Data (LOD) which includes AGROVOC concepts + links to outside resources (NT and NQ format).
- Public SPARQL endpoint, served by Fuseki version 3.6.0
Information about these can be found at How to Access AGROVOC (Technical Documentation for all Endpoints).
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.