Difference between revisions of "OJ Break v2 Geographic Place Reference"
(→Procedural Reference) |
(→See also) |
||
| Line 90: | Line 90: | ||
* [[OJ_Break v2 Literature Reference|Literature]] | * [[OJ_Break v2 Literature Reference|Literature]] | ||
* [[OJ_Break v2 Locality Reference|Locality]] | * [[OJ_Break v2 Locality Reference|Locality]] | ||
| − | |||
* [[OJ_Break v2 Occurrence Reference|Occurrence]] | * [[OJ_Break v2 Occurrence Reference|Occurrence]] | ||
* [[OJ_Break v2 Search Reference|Search]] | * [[OJ_Break v2 Search Reference|Search]] | ||
* [[OJ_Break v2 Taxon Reference|Taxon]] | * [[OJ_Break v2 Taxon Reference|Taxon]] | ||
Revision as of 17:26, 5 January 2015
Introduction
OJ_Break is the name of the xBio:D RESTful API service to facilitate discovery of data within the xBio:D database. The API can respond with JavaScript Object Notation (JSON), XML, or JSON with padding (JSONP) and accepts HTTP GET and POST requests indiscriminately. The backend of the API is written in Oracle's PL/SQL database language, which is fast but often inflexible, while a Python presentation layer mitigates request handling and authentication.
OJ_Break Version 2 is a new and improved edition of the work started in Version 1. Version 2 introduces a completely restructured and standardized data model to further enhance the functionality of the xBio:D database.
Contents
API Information and Access
This page specifies the methods and data defined by OJ_Break Version 2, more precisely those that are defined by the Geographic Place data domain. To get information on any of the other data domains defined in OJ_Break Version 2, visit the See also section.
Using the OJ_Break Version 2 API requires calling methods with corresponding, method specific parameters (found on this page) and a few other required parameters. These required parameters include specifying a return format, an API access key, and a version number.
Example: http://osuc.biosci.ohio-state.edu/OJ_Break/getAgentInfo?agent_id=2&format=json&key=FBF57A9F7A666FC0E0430100007F0CDC&version=2
Notice the specification of the version parameter at the end of the example method call. With the introduction of OJ_Break Version 2, the version parameter has a default value of 2 making the specification in the example unnecessary. To read more about using the OJ_Break Version 2 API, go to OJ_Break API Access.
Procedural Reference
Geographic Place
getPlaceInfo
Description
Parameters
- place_id: number
- format: string
- key: string
- version: number
Return
- PlaceExtended
Example
getPlaceSubdivisions
Description
Parameters
- place_id: number
- pol_level: number (optional)
- format: string
- key: string
- version: number (optional)
Return
- PlaceReturnSubdivisions
Example
getPlaceTaxa
Description
Parameters
- place_id: number
- format: string
- key: string
- version: number
Return
- PlaceReturnTaxa
Example
getPlaceOccurrences
Description
Parameters
- place_id: number
- format: string
- key: string
- version: number
Return
- PlaceReturnOccurrences
Example
getPlaceInstitutions
Description
Parameters
- place_id: number
- format: string
- key: string
- version: number
Return
- PlaceReturnInstitutions
Example
See also
Visit any of the below links to find information about the other data domains defined by OJ_Break Version 2.
