-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are basic and advanced search compatible? #10
Comments
@m-mohr sorry I've been away at a conference so haven't had a chance to look at this. But yes I think you're right in their current implementation they're not compatible. I think the simplest solution would be to add commas to the advanced search. For POST could the advanced terms be separate into a list for example:
This would mean that |
This seems pretty weird. I think keeping them separate makes more sense. They can be in the same extension, but I think it could be made clear that they are not compatible. The basic one is compatible with Records, the more advanced one is an addition from STAC... |
Ah I didn't think of that as an option. That sounds like a great idea. Would this use a flag to differentiate between the two or use completely separate parameters? |
Are basic and advanced search compatible? Can they be implemented at the same time?
I'm not sure yet because in basic OR needs to be separated by comma, but in advanced the comma is not mentioned at all. There space is used.
Also how to handle the differences in POST?
The text was updated successfully, but these errors were encountered: