Add info on new version of existing datasets

[sashakames]

Three potential scenarios for how the architecture might handle publication that updates an existing dataset with a new version.

[rhysrevans3]

Comments

STAC's Transaction Extension's Update/PUT functionality replace the record rather than setting latest=False and creating a new record. This would likely have to be two separate requests update and create.

Any "administrative exemption that can overwrite a record" should go through the message queue to prevent indexes getting out of sync and so the changes are seen in the "materialised view".

Questions

1. Are non latest records ever returned in search? If not do we need to keep old records (latest=False) in the indexes? If we have a "materialised view" of events this would give us the records "history" and so we could just keep the latest in the indexes.
2. Same question for redacted records.
3. Is there anything special about the "original" asset or are all original/replicas equal?
4. Are retraction and replica remove currently separate commands? It seems like there are now two commands: retraction to remove the full record and "data no longer available from this location" to remove an individual asset?
5. For retracting a full record with replicas would this also remove replicas?
6. If the original location is no longer available should they nominate an alternate asset to become the main or should one be chosen random?