Stop Collection update endpoint from deleting sub Items

[rhysrevans3]

Issue
When updating Collections all items are deleted. My workflow requires the ability to add Items to a Collection as they are generated. Currently I would need to rebuild all existing Items every time an Item is created.

Solution
Default Collections update endpoint to not delete all sub items.

Alternative solution
Add a flag to allow for choice of whether items are deleted.

[jonhealy1]

This looks really good so far. I think you are right and updating a collection shouldn't delete all the sub items.

[rhysrevans3]

Thanks @jonhealy1. Wondered if you (or anyone else) had any strong opinions on either of these points:

• If a collection should be updated at /collections or at /collections/{collection_id}? I would be interested to know the reason behind choosing /collections, as my intuition was to look at /collections/{collection_id}.
• Should a collection's id be updatable? I've included this feature in my pull request but it requires an additional query parameter so I was unsure if this was a desired behaviour or if a user should delete and rebuild a collection if they want to change it's id.

[jonhealy1]

@rhysrevans3 Have you looked at the stac-api spec? I understand what you are saying and you make some good logical points. I am not sure what the api-spec says about these items if anything? https://github.com/radiantearth/stac-api-spec/tree/v1.0.0

[rhysrevans3]

I couldn't find anything about the transactions in the api-spec but in the collection-transaction extension it looks like it should be at /collections/{collection_id}. I will raise an issue in the stac-fastapi repo.