CloudNiner
commented
1 month ago Ordering with STAPI seems to be confined to supporting tasking orders, understandingly, but ordering from archive is also often a requirement for vendors.
The STAPI spec as it stood at the end of the last tasking sprint explicitly supported this use case! In fact, the demo we built for that sprint implemented a real live working Archive Product. See:
https://github.com/stapi-spec/stapi-fastapi-umbra/blob/main/src/stat_fastapi_umbra/products.py
In a similar vein to #203, a unified ordering solution seems like a necessity. Ordering with STAPI seems to be confined to supporting tasking orders, understandingly, but ordering from archive is also often a requirement for vendors.
So I want to ask: how does STAPI address this need? Again, maybe it doesn't, and explicitly stating that is, I think, an possible resolution to this issue. That said, I think if STAPI is supporting orders then wondering how to support archive orders is a legitimate concern to consider.
Just as STAPI currently outlines that orders should be placable via an opportunity, maybe that model also points to a solution of supporting an order for an item from a STAC catalog via said item. For example, the item could include an order link as part of its set of links.
One thing this idea doesn't address is related to the order parameters as proposed in #199. If an item links to an order endpoint, how does the client know what parameters they can submit with that order to control the order behavior (such as generating derived products, delivering the item in some way (S3 bucket push for example), etc). If, as proposed in #199 the order parameters are defined as an aspect of a product in STAPI, how do we get that to map to items in STAC to facilitate this order process?
Again, 🍔 for 💭.