Pong: /* notificationTypeId */

2026-03-10T05:10:57Z

notificationTypeId

← Older revision		Revision as of 05:10, 10 March 2026
Line 226:		Line 226:
	== notificationTypeId ==		== notificationTypeId ==

	* hash of ~~relType~~ object		* hash of notificationType object

	== identifiers ==		== identifiers ==

Sven the Barbarian at 23:09, 9 March 2026

2026-03-09T23:09:26Z

← Older revision		Revision as of 23:09, 9 March 2026
Line 205:		Line 205:
	</syntaxhighlight>		</syntaxhighlight>
	use to identify which serviceTag that flow schema is located		use to identify which serviceTag that flow schema is located

			== systemTextType ==
			<syntaxhighlight lang="JavaScript">
			{
			namespace: "xxx",
			systemTextTag: "yyy"
			}
			</syntaxhighlight>
			identify a system text

	== notificationType ==		== notificationType ==

Sven the Barbarian at 00:31, 3 March 2026

2026-03-03T00:31:41Z

← Older revision		Revision as of 00:31, 3 March 2026
Line 390:		Line 390:
	</syntaxhighlight>		</syntaxhighlight>

			= Working documents =

	[[~~Category~~:~~Working documents\| 2025-01-23]]~~		[[:Category:Working_documents - Standard Data Structures\| Standard Data Structures]]
	[[Category:~~Working documents~~ - ~~Per Service Schemas~~\| ~~2025-01-23~~]]

Sven the Barbarian: Created page with "= Overview = Standard structure and definitions. = Definition = == objType == { serviceTag: "xxx", objectType: "yyy" } use to identify which serviceTag that object schema located * serviceTag: service tag that stored object schema * objectType: name of object schema == objTypeConcat == _ * objTypeConcat: "serviceTag" + "_" + "objectTy..."

2026-03-03T00:29:35Z

Created page with "= Overview = Standard structure and definitions. = Definition = == objType == <syntaxhighlight lang="JavaScript"> { serviceTag: "xxx", objectType: "yyy" } </syntaxhighlight> use to identify which serviceTag that object schema located * serviceTag: service tag that stored object schema * objectType: name of object schema == objTypeConcat == <syntaxhighlight lang="JavaScript"> <serviceTag>_<objectType> </syntaxhighlight> * objTypeConcat: "serviceTag" + "_" + "objectTy..."

New page

= Overview =
Standard structure and definitions.

= Definition =

== objType ==
<syntaxhighlight lang="JavaScript">
{
serviceTag: "xxx",
objectType: "yyy"
}
</syntaxhighlight>
use to identify which serviceTag that object schema located
* serviceTag: service tag that stored object schema
* objectType: name of object schema

== objTypeConcat ==
<syntaxhighlight lang="JavaScript">
<serviceTag>_<objectType>
</syntaxhighlight>
* objTypeConcat: "serviceTag" + "_" + "objectType"
* now use as the name of node label in graph database

== objTypeId ==
* hash of objType object

== relType ==
<syntaxhighlight lang="JavaScript">
{
serviceTag: "xxx",
relationshipTag: "yyy"
}
</syntaxhighlight>
use to identify which serviceTag that relationship schema located
* serviceTag: service tag that stored object schema
* relationshipTag: name of relationship schema

== relTypeConcat ==
<syntaxhighlight lang="JavaScript">
<serviceTag>_<relationshipTag>
</syntaxhighlight>
* relTypeConcat: "serviceTag" + "_" + "relationshipTag"
* now use as the name of relationshipType in graph database

== relTypeId ==
* hash of relType object

== relTypeAndDirection ==
<syntaxhighlight lang="JavaScript">
{
relType: {
serviceTag: "xxx",
relationshipTag: "yyy"
},
relationshipDirection: "to", // "from" || "to"
relationshipProperties: {}
}
</syntaxhighlight>

== objectLinks ==
<syntaxhighlight lang="JavaScript">
[
{
base:{
objType:{
serviceTag: "xx",
objectType: "yy",
},
requiredOnCreate:true,
linkType:"one",
direction:"to"
},
other:{
objType:{
serviceTag: "xx",
objectType: "yy",
},
requiredOnCreate:false,
linkType:"one",
direction:"from"
},
relType:{
serviceTag:"xx"
relationshipTag:"xx"
}
},
// ... another objectLinks
]
</syntaxhighlight>
* This format will receive it when use function getObjectLinks and base objType use it own objType.
* It show all link that connect with that objType.

== objectLink ==
<syntaxhighlight lang="JavaScript">
{
base:{
objType:{
serviceTag: "xx",
objectType: "yy",
},
requiredOnCreate:true,
linkType:"one",
direction:"to"
},
other:{
objType:{
serviceTag: "xx",
objectType: "yy",
},
requiredOnCreate:false,
linkType:"one",
direction:"from"
},
relType:{
serviceTag:"xx"
relationshipTag:"xx"
}
}
</syntaxhighlight>
* Object structure of one objectLink

== linkConfig ==
<syntaxhighlight lang="JavaScript">
{
from: {
serviceTag: "xx",
objectType: "yy",
},
to: {
serviceTag: "xxx",
objectType: "yyy"
},
relType: {
serviceTag: "xxxx",
relationshipTag: "yyyy"
},
relationshipDirection: "to", // "from" || "to"
requestProperties: {
// to calculate orderPrices we need one identifier for each of the below objTypes
tag_deliverTo: {
requestPropertyType: "objectIdentifier",
objType: {
serviceTag: "Locations",
objectType: "locationNode" // deliversToLocationNode
},
identifiersFieldName: "locationNodeId"
},
// ... other request properties
}
}
</syntaxhighlight>
config of each link between 2 objType

== linkType ==
<syntaxhighlight lang="JavaScript">
{
firstObjType: {
serviceTag: "xx",
objectType: "yy",
},
secondObjType: {
serviceTag: "xxx",
objectType: "yyy"
},

relType: {
serviceTag: "xxxx",
relationshipTag: "yyyy"
},
relationshipDirection: "to" // "from" || "to"
}
</syntaxhighlight>
use to identify relationship between 2 objectSchema

== linkTypeId ==
create hash id from linkType

== pathLinkType ==
<syntaxhighlight lang="JavaScript">
{
objType: {
serviceTag: "xxx",
objectType: "yyy"
},
relType: {
serviceTag: "xxxx",
relationshipTag: "yyyy"
},
relationshipDirection: "to" // "from" || "to"
}
</syntaxhighlight>
* pathLinkType is used at each step of traversal/path
* when joined with the previous objType/baseObjType can be used to create linkType (and request linkConfig)

== pathLinkTypeId ==
* create hash id from pathLinkType

== flowType ==
<syntaxhighlight lang="JavaScript">
{
serviceTag: "xxx",
flowTag: "yyy"
}
</syntaxhighlight>
use to identify which serviceTag that flow schema is located

== notificationType ==
<syntaxhighlight lang="JavaScript">
{
serviceTag: "xxx",
notificationTag: "yyy"
}
</syntaxhighlight>
identify a system notification

== notificationTypeId ==

* hash of relType object

== identifiers ==
An object that has fieldName’s identifiers inside
=== example identifiers ===
* example identifiers inside objectSchema
<syntaxhighlight lang="JavaScript">
identifiers:[
{
type: "partitionKey",
fieldNames: ["xx","yy"],
name: "zz"
}
]
</syntaxhighlight>
* example identifiers object
<syntaxhighlight lang="JavaScript">
{
xx:"xx value",
yy:"yy value"
}
</syntaxhighlight>

The example above identifiers is the value of fieldNames that part of identifiers

== identifiersBase ==
concatenated identifiers object
=== example identifiersBase ===
* example identifiers inside objectSchema
<syntaxhighlight lang="JavaScript">
identifiers:[
{
type: "partitionKey",
fieldNames: ["xx","yy"],
name: "zz"
}
]
</syntaxhighlight>
* example identifiersBase object
<syntaxhighlight lang="JavaScript">
{
zz:"xxValue_yyValue",
}
</syntaxhighlight>

The example above identifiersBase is the value of each identifier of objectSchema

== identifiersId ==
hash of identifiers object

== identifiersConcat ==
string that concatenate all identifiers
* Note!: Will ordered concatenate value by objectSchema.identifiers array

== objInstanceBase ==
result from dynamoDB that contains relevant and not relevant data of objectSchema
* identifiers from in objInstanceBase will concatenated or not concatenated depending on objectSchema
* izContext field not relevant with objectSchema but it contains inside objInstanceBase

== objInstance ==
similar objInstanceBase but split concatenateIdentifier to each fieldName

== objInstanceFull ==
object that separated fields and identifiers and identifiers cannot concatenated
<syntaxhighlight lang="JavaScript">
{
identifiers:{
//... identifiers fieldName of objectSchema
},
fields:{
//.. data of objectSchema
}
}
</syntaxhighlight>
* identifiers: contains identifiers data
* fields: another data except

== example data ==
=== example objectSchema ===
<syntaxhighlight lang="JavaScript">
// example objectSchema
{
fieldNames:{
id:{
type:”string”,
// … another fieldName settings
},
createTime: {}, // filedName settings
location: {}, // filedName settings
value: {}, // filedName settings
},
identifiers:[
{
type: "partitionKey",
fieldNames: ["id","createTime"], // composite partition keys in DynamoDB
deliminator: "_", // optional, defaults to "_"
name: "createId" // name of field in database
},
{
type: "sortKey",
fieldName: “location”
}
]
}
</syntaxhighlight>

=== objInstanceBase ===
<syntaxhighlight lang="JavaScript">
// example objInstanceBase data
{
createId:"id_createTime",
location:"cnx",
value:199,
errorsFound:[],
izContext:{
// ...izContext
},
}
</syntaxhighlight>
Normally objInstanceBase is the result from dynamoDB and it will include data that is not relevant to objectSchema. In example above errorsFound and izContext not contain in objectSchema.

=== objInstance ===
<syntaxhighlight lang="JavaScript">
// example objInstance data
{
id:"id",
createTime:"createTime"
location:"cnx",
value:199,
errorsFound:[],
izContext:{
// ...izContext
},
}
</syntaxhighlight>
objInstance is object that already refactored identifiers but another fields same as objInstanceBase

=== objInstanceFull ===
<syntaxhighlight lang="JavaScript">
// example objInstanceFull data
{
identifiers:{
id:"id",
createTime:"createTime"
location:"cnx",
},
fields:{
value:199,
}
}
</syntaxhighlight>

=== identifiersBase ===
<syntaxhighlight lang="JavaScript">
// example identifiersBase data
{
createId:"id_createTime",
location:"cnx"
}
</syntaxhighlight>

=== identifiers ===
<syntaxhighlight lang="JavaScript">
// example identifiers data
{
id: "id",
createTime: "createTime",
location: "cnx"
}
</syntaxhighlight>

[[Category:Working documents| 2025-01-23]]
[[Category:Working documents - Per Service Schemas| 2025-01-23]]

Standard Data Structures - Revision history

Pong: /* notificationTypeId */

Sven the Barbarian at 23:09, 9 March 2026

Sven the Barbarian at 00:31, 3 March 2026