Service - Catalog Standard: Difference between revisions
Jump to navigation
Jump to search
| Line 37: | Line 37: | ||
= Filter for each categoryTreeNode = | = Filter for each categoryTreeNode = | ||
* In most cases all categoryTreeNodes will share the same filter, matching the catalog's filter, but allow for each categoryTreeNode to set its own. When this happens it will likely add to the default filter, to maintain a standard experience for the user. | * In most cases all categoryTreeNodes will share the same filter and requiredData, matching the catalog's filter and this service's default requiredData, but allow for each categoryTreeNode to set its own. When this happens it will likely add to the default filter, to maintain a standard experience for the user. | ||
* When creating a new categoryTreeNode for a catalog the requiredData and filter for the node can be set, if not set the default is to inherit from that node's parent categoryTreeNode. If is a top level node it inherits from the catalog's (default) filter. | * When creating a new categoryTreeNode for a catalog the requiredData and filter for the node can be set, if not set the default is to inherit from that node's parent categoryTreeNode. If is a top level node it inherits from the catalog's (default) filter. | ||
* Not sure how to handle updating catalog's (default) filter, perhaps have a bool in the categoryTreeNode that sets whether it's filter should track and update when catalog filter updates. | * Not sure how to handle updating catalog's (default) filter, perhaps have a bool in the categoryTreeNode that sets whether it's filter should track and update when catalog filter updates. | ||
Revision as of 10:03, 21 February 2021
Overview
Handler service for the standard catalog type.
Repository
https://bitbucket.org/stb_working/catalog-standard/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configTag: "CatalogTreeServiceName"
configKey: {eg: "CatalogTreeServiceName"}
configValue: {eg: "CatalogTreeStandard"}
}
Catalog
Fields
- catalogId
- (partition key)
- filter
- stringified object containing default search result filter
- searchType
- product|variant|variantProduct
- default searchType
- categoryTreeServiceName
- eg: "CategoryTreeStandard"
Filter for each categoryTreeNode
- In most cases all categoryTreeNodes will share the same filter and requiredData, matching the catalog's filter and this service's default requiredData, but allow for each categoryTreeNode to set its own. When this happens it will likely add to the default filter, to maintain a standard experience for the user.
- When creating a new categoryTreeNode for a catalog the requiredData and filter for the node can be set, if not set the default is to inherit from that node's parent categoryTreeNode. If is a top level node it inherits from the catalog's (default) filter.
- Not sure how to handle updating catalog's (default) filter, perhaps have a bool in the categoryTreeNode that sets whether it's filter should track and update when catalog filter updates.
Ideas
- One filter that will normally be on, but could be removed, is to only show items that have available quantity, this will tie into the locationtreenodeid.