jszajgin
commented
6 years ago @AlexMountain - I think this is a good step in the right direction because some things exported from GRiD are more like "data" and some are more like "products" and some are very much like (or will be) very formal spec driven products - so, to me, there is a range of data to product and there is a range of how formally that product might be specified - I think whatever we do needs to reflect that operational reality
When exporting using the GRiD UI, users select from a list of "Collects" to choose from. Under the hood of GRiD, Collects are compromised by one or more Product objects, and what the users are actually selecting are "Products" from the list in the UI.
For clarity, we'd like to unify the terms across the UI and API to be the generally more accepted term, "collects". This also helps avoid confusion when using the term "products" to describe post processing tool products.
For these reasons I am planning to deprecate the "products" endpoint and replace it with "collects". The change will be made in v4 as to not affect v3 endpoints.