IDigBio API Software: Difference between revisions

No edit summary
Line 6: Line 6:
=== Software ===
=== Software ===


The core of our API services is [https://www.elastic.co/ Elasticsearch]. This distributed document store is where we keep the current versions of all our specimen and media records. Both indexed fields and raw data are kept in this store. User queries expressed in the [https://github.com/iDigBio/idigbio-search-api/wiki/Query-Format iDigBio query syntax] are translated in to Elasticsearch queries and JSON results from Elasticsearch are then formatted and passed through to the user.
The core of our search API service is [https://www.elastic.co/ Elasticsearch]. This distributed document store is where we keep the current versions of all our specimen and media records. Both indexed fields and raw data are kept in this store. User queries expressed in the [https://github.com/iDigBio/idigbio-search-api/wiki/Query-Format iDigBio query syntax] are translated in to Elasticsearch queries and JSON results from Elasticsearch are then formatted and passed through to the user.


The search API server is written in Node.js and is [https://github.com/iDigBio/idigbio-search-api available] under the GPL3 license from Github. Mapping requests including image tile generation are done with the Mapnik library.
The search API server is written in Node.js and is [https://github.com/iDigBio/idigbio-search-api available] under the GPL3 license from Github. Mapping requests including image tile generation are done with the Mapnik library.
82

edits