Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Products endpoint change to be Collects #37

Open
AlexMountain opened this issue Mar 7, 2018 · 1 comment
Open

Products endpoint change to be Collects #37

AlexMountain opened this issue Mar 7, 2018 · 1 comment
Assignees
Milestone

Comments

@AlexMountain
Copy link
Contributor

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.

@AlexMountain AlexMountain added this to the v4 milestone Mar 7, 2018
@AlexMountain AlexMountain self-assigned this Mar 7, 2018
@jszajgin
Copy link

jszajgin commented Mar 7, 2018

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants