Collection search draft

[ccancellieri]

Related Issue(s):

Hi, I'm using this branch to discuss about collection search which is an hot topic for me and I needed to sort it out as per this pull request.

I'm encountering the following problems:

• We still need to use the POST to create new Collection(s) but the incoming expexted body is different
• Incompatible with Transactional (how to have it working?)

[The pull request uses another endpoint to avoid the clash]

Questions:

• Why the specifications define a new endpoint to search for items: .../search while for the collections we are overloading the /collections ?
• Do you have any working example about having both search and creation working at the same time?

Description:

This patch reduced code duplication and implements the same search capabilities that we have over items but over collections returning a standard (?) /collections search response with the result of the search in the collection index.

The collectionID list for now is simply ignored.

PR Checklist:

• Code is formatted and linted (run pre-commit run --all-files)
• Tests pass (run make test)
• Documentation has been updated to reflect changes, if applicable
• Changes are added to the changelog

[jonhealy1]

Hi @ccancellieri. Could you open an issue here. Your concerns are valid I think. We are limited by the stac-fastapi parent libraries and then also the stac-api-spec.

[ccancellieri]

here it is:
stac-utils/stac-fastapi#749

[jonhealy1]

@ccancellieri great thank you!

[ccancellieri]

stac-api-extensions/collection-search#17