Scott Chamberlain
Scott Chamberlain
@cboettig Okay, added a route `/listfields` https://github.com/ropensci/fishbaseapi/blob/master/api_docs.md#listfields - we can rename to anything you want. Restarted server and getting same problem as yesterday though, so it's not up yet
when it's up try: - `fishbase.ropensci.org/listfields` - `fishbase.ropensci.org/listfields?fields=Year` - `fishbase.ropensci.org/listfields?fields=Year,Genus` - `fishbase.ropensci.org/listfields?fields=Year,Genus&exact=true`
WRT searching anywhere in the DB, I imagine Solr is our best bet, or ES as long as we're sure it can be secured properly. Guess it's a matter of...
see also https://fishbaseapi.readme.io/v1.0/discuss/5ceeefef9dd565022c894dbf
Added fuzzy search for the `/taxa` route only, for only the params genus and species
@cboettig pinging you again so we can get this done - i think we should go with limiting what fields can be queried on, agreed? then add more as needed
okay, cool, yeah, I don't want to break anything
@cboettig from #18 seems like you're saying we should restrict queryable fields to `species`, `genus`, and `speccode` - should I implement that now?
right, ok
@cboettig updating the docs a bit - since the query-able fields are unlimited right now, I'm only putting in the fields always avail. (`limit`, `offset`, `fields`), and a few other...