Lookup¶
The lookup resource allows to lookup and fetch metadata based on the resource URI. This is intended to be used with reverse proxying where it is necessary to re-route external (sub)domains transparently. I.e., the impression to the metadata consumer is that the delivered data originates from the external resource URI; it is not obvious that EntryStore delivers the metadata.
The lookup mechanism can be used globally or per context. In the event of several matching entries, only one is returned. Only publicly available metadata is returned.
Usage¶
GET {baseurl}/[{context-id}/]lookup?uri={resource-uri}[&scope=all|local|external&format={format}]
The scope is either all, local or external, with all being default. In the case of all, and if available, both the local and the external metadata are merged in the returned graph. If no context ID is provided, the lookup is executed globally.
See next section for supported formats.
Supported formats¶
A specific format can be requested using either HTTP content negotiation or the format URL parameter.
The following RDF serialization formats are supported (the same as with the ordinary metadata resource):
- application/json
- application/ld+json
- application/rdf+xml
- text/rdf+n3
- application/x-turtle
- application/trix
- application/x-trig
The default format is RDF/XML.
Examples¶
http://localhost:8181/lookup?uri=http%3A%2F%2Fdbpedia.org%2Fdata%2FThe_Lord_of_the_Ringshttp://localhost:8181/lookup?uri=http%3A%2F%2Fdbpedia.org%2Fdata%2FThe_Lord_of_the_Rings&scope=all&format=application/json