Service - Catalog Standard: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 23: Line 23:
<syntaxhighlight lang="JavaScript">
<syntaxhighlight lang="JavaScript">
{
{
configTag: "CategoryManagerServiceName"
configTag: "CatalogManagerServiceName"
configKey: "CategoryManagerServiceName"
configKey: "CatalogManagerServiceName"
configValue: xxx // eg: "CatalogManager"
configValue: xxx // eg: "CatalogManager"
}
}
Line 31: Line 31:
<syntaxhighlight lang="JavaScript">
<syntaxhighlight lang="JavaScript">
{
{
configTag: "CategoryTreeServiceName"
configTag: "TranslationsServiceName"
configKey: xxx // categoryTreeServiceNameTag, eg: "CategoryTreeStandard", this is what is saved in each catalog record
configKey: "TranslationsServiceName"
configValue: {
configValue: xxx // eg: "Translations"
serviceName: xxx // eg: "CategoryTreeStandard", this is the actual deployed service name}
}
}
}
</syntaxhighlight>
</syntaxhighlight>
Line 41: Line 39:
<syntaxhighlight lang="JavaScript">
<syntaxhighlight lang="JavaScript">
{
{
configTag: "TranslationsServiceName"
configTag: "CategoryTreeService"
configKey: "TranslationsServiceName"
configKey: xxx // categoryTreeServiceNameTag, eg: "CategoryTreeStandard", this is what is saved in each catalog record
configValue: xxx // eg: "Translations"
configValue: {
serviceName: xxx // eg: "CategoryTreeStandard", this is the actual deployed service name}
}
}
}
</syntaxhighlight>
</syntaxhighlight>

Revision as of 05:35, 7 March 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: "CatalogServiceNameTag"
	configKey: "CatalogServiceNameTag"
	configValue: xxx // this own services CatalogServiceTag, eg "CatalogStandard"
}
{
	configTag: "CatalogManagerServiceName"
	configKey: "CatalogManagerServiceName"
	configValue: xxx // eg: "CatalogManager"
}
{
	configTag: "TranslationsServiceName"
	configKey: "TranslationsServiceName"
	configValue: xxx // eg: "Translations"
}
{
	configTag: "CategoryTreeService"
	configKey: xxx // categoryTreeServiceNameTag, eg: "CategoryTreeStandard", this is what is saved in each catalog record
	configValue: {
		serviceName: xxx // eg: "CategoryTreeStandard", this is the actual deployed service name}
	}
}

Neptune graph database

Service - Catalog Graph

Vertices

catalog

vertexId: catalog_{catalogId}

Properties:

  1. filter
    stringified object containing default search result filter
  2. requiredData
    stringified object containing default search result requiredData
  3. searchType
    product|variant|variantProduct
  4. categoryTreeServiceName
    eg: "CategoryTreeStandard"

Service - Translations Graph

Vertices

catalogName

vertexId: catalogName_{catalogId}

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.

Working documents

Catalog Standard