Service - Catalog Manager: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Notes) |
||
Line 31: | Line 31: | ||
* Client can pass in additional filters, these get combined into final Search Result request by [[Service - Category Tree (handlers)]]. | * Client can pass in additional filters, these get combined into final Search Result request by [[Service - Category Tree (handlers)]]. | ||
* Client can overwrite default searchType | * Client can overwrite default searchType, if invalid gets set to categoryTreeNode default. | ||
* Client can add requiredData to request | * Client can add requiredData to request. | ||
* locationTreeAreaNodeId and browseQuantity are added by the client into additionalParams, Category Tree handler adds these to the request, or set to default if invalid. | |||
= Working documents = | = Working documents = |
Revision as of 14:32, 19 December 2020
Overview
Maintains a table of all catalogs, each catalog is handled by a Service - Catalog (handlers) and a Service - Category Tree (handlers) service, links to these are stored for efficiently handling browse requests.
Browse requests from client pass this service, the Search Result request is built and sent to Service - Search Result Main service and id/s to poll for results are sent to client.
Repository
https://bitbucket.org/stb_vit/catalog-manager/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
..
Catalog
Fields
- catalogId
- (partition key)
- catalogServiceName
- eg: "CatalogStandard"
- categoryTreeServiceName
- eg: "CategoryTreeStandard"
Notes
- Client can pass in additional filters, these get combined into final Search Result request by Service - Category Tree (handlers).
- Client can overwrite default searchType, if invalid gets set to categoryTreeNode default.
- Client can add requiredData to request.
- locationTreeAreaNodeId and browseQuantity are added by the client into additionalParams, Category Tree handler adds these to the request, or set to default if invalid.