Closed alishaevn closed 2 years ago
originally posted: sept 9, 2022. last edited: sept 20, 2022.
update as of 9/20/22:
this works because of the individual access token that I provide as the "Bearer token" param.
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}.json
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}.json
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}/participating_provider.json
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}/proposals.json
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}/notes.json
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}.json
https://{{domain}}.scientist.com/api/v2/quote_groups/{{quote-group-id}}/quoted_wares/{{quoted-ware-id}}/purchase_orders.json
1.
2.
use the ancestor_slugs
value on each category (see: "api result") to determine the path taken to get to the final sub-category. (see: "browser view").
there are 3 ways to make a request:
clicking on an item (ware) under a research area
https://acme.scientist.com/request (do we need this option for the mvp?)
once a user selects the type of thing they want to request, the request form is returned. this logic is not all in the api. it's a mix of controller methods and view logic. dynamic forms are published to certain organizations
spoke with steven about the "make a request" calls above.
simply using the rx app as a basis for the webstore api isn't....suggested. there's way too much logic in the views in the rx app.
the api as is, is mainly for reading. we'll need to either update specific controllers to understand json the way we need it, or add create/update functionality to the api.
although the rx-lite repo is outdated (both the react version and the api calls), it might be useful to see how this same/similar idea was being thought about 5 years ago.
https://{{base_path}}/providers/20267/wares.json?q=dna
https://{{base_path}}/providers/20267/wares.json
should show which category each ware relates tohttps://{{base_path}}/wares.json
https://{{base_path}}/wares.json
to determine what the categories (research areas) for a ware should be. (some of those facets, like "keywords", shouldn't be there though)talked with @cpetersen and @crisr15 about this. in addition to some new api calls that we need, some of the existing calls are returning results that chris is not expecting. he's going to talk to ron about what changes may need to be made.
once direction is decided, we can create issues against the api v2 repo: https://github.com/assaydepot/scientist_api_v2/issues
some of the items in the mock ups in this comment reference a view page and not an api call. e.g., "send message" at the upper left of the supplier review mock up:
summary
determine which api calls will be necessary in order to implement the search, browse, create request and view all/one request features of the mvp.
acceptance criteria
we will need api calls for each of the following scenarios
resources
notes