-
Notifications
You must be signed in to change notification settings - Fork 1
Initial /api/searchLocations API #367
Comments
Initial design:
Arguments:
|
Default JSON shape will be: {
"results": [
{"id": "...", "name": "..."},
{"id": "...", "name": "..."},
{"id": "...", "name": "..."}
],
"total": 1023
} This leaves room to add extra keys for things like pagination later. |
This will start out unauthenticated but we may want to start requiring |
Now live on staging, docs here: https://vial-staging.calltheshots.us/api/docs#get-apisearchlocations |
Concordances are now populated, so this API can grow options to search by concordance ID reference. |
For concordance filtering this works: locations = Location.objects.filter(
concordances__in=ConcordanceIdentifier.objects.filter(
Q(authority = 'cvs', identifier='#11344') | Q(authority = 'google_places', identifier='ChIJ3S7I3CE9hYARLpUyyZ21Q2A')
)
) |
I'm going to try and get the streaming option to work next. I'm bumping the lat/lon/radius thing to another ticket. |
|
... that seemed to work! It gave me a 8MB JSON file with 10,562 locations in it
|
We need a basic search API with the following features:
LIKE
but we can add PostgreSQL FTS soon afterwards)This issue is to get a basic framework up and running with those features. Will be adding plenty more features later on as and when we need them.
The text was updated successfully, but these errors were encountered: