Service - Import Data: Difference between revisions
Jump to navigation
Jump to search
(Created page with "= Overview = Orchestrates importing of objects/data into project. = Repository = https://bitbucket.org/izara-core-import-export-data/izara-core-import-data-import-data/src/master/ = DynamoDB tables = == Standard Config Table Per Service == === Configuration tags === <syntaxhighlight lang="JavaScript"> { configKey: "objectType", configTag: "xx" // {eg: sellOffer/Product/VariantProduct etc..} configValue: { createObectServiceName: "xx" // {service name serv...") |
No edit summary |
||
Line 23: | Line 23: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
= Object hierarchy and field schema = | |||
* Some fields will be required, some optional | |||
* some fields possibly have system defaults | |||
* perhaps user can setup default templates (do later if has value) | |||
* schema will need to state identifier fields for each object, if set in feed Import Data knows is pointing to existing child/parent object, if empty needs to create new | |||
* perhaps each objectType states it's child objects, as more likely to be aware of these than parent objects | |||
== where to store/set schema == | |||
Considering external service delivers this to ImportData in Initial Setup, as seed data. | |||
= Working documents = | = Working documents = |
Revision as of 14:05, 28 October 2022
Overview
Orchestrates importing of objects/data into project.
Repository
https://bitbucket.org/izara-core-import-export-data/izara-core-import-data-import-data/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configKey: "objectType",
configTag: "xx" // {eg: sellOffer/Product/VariantProduct etc..}
configValue: {
createObectServiceName: "xx" // {service name service that handles this type}
}
},
Object hierarchy and field schema
- Some fields will be required, some optional
- some fields possibly have system defaults
- perhaps user can setup default templates (do later if has value)
- schema will need to state identifier fields for each object, if set in feed Import Data knows is pointing to existing child/parent object, if empty needs to create new
- perhaps each objectType states it's child objects, as more likely to be aware of these than parent objects
where to store/set schema
Considering external service delivers this to ImportData in Initial Setup, as seed data.