... | @@ -3482,21 +3482,19 @@ schema, they are represented directly as attributes in the data block of the rec |
... | @@ -3482,21 +3482,19 @@ schema, they are represented directly as attributes in the data block of the rec |
|
1. These relationships do not require any mention in the schema. They are represented within
|
|
1. These relationships do not require any mention in the schema. They are represented within
|
|
the `data.relationships` block of the record.
|
|
the `data.relationships` block of the record.
|
|
2. ExtensionProperties block in the file metadata record is used to provide additional information for ingestion. We can use this block to provide relationship information. There are three ways of providing this information:
|
|
2. ExtensionProperties block in the file metadata record is used to provide additional information for ingestion. We can use this block to provide relationship information. There are three ways of providing this information:
|
|
1. In the `relationships` block, with the entity name and a list of parent record ID(s). The ID(s)
|
|
1. In the `relationships` block, with the entity name and a list of parent record ID(s). The ID(s) provided here are directly used to establish relationships.
|
|
provided here are directly used to establish relationships.
|
|
2. In the `relatedNaturalKey` block, as an entity that requires a search of the targetKind using the natural keys provided to establish a relationship.
|
|
2. In the `relatedNaturalKey` block, as an entity that requires a search of the targetKind using
|
|
`sourceColumn`: Column name of the CSV file which refers to the key parent attribute.
|
|
the natural keys provided to establish a relationship.
|
|
`targetKind`: Schema ID of the parent record.
|
|
sourceColumn: Column name of the CSV file which refers to the key parent attribute.
|
|
`targetAttribute`: The key attribute of the parent record which is used to search the parent record.
|
|
`targetKind`: Schema ID of the parent record.
|
|
|
|
`targetAttribute`: The key attribute of the parent record which is used to search the parent record.
|
|
|
|
If the `targetAttribute` is nested attribute, it must be . separated.
|
|
If the `targetAttribute` is nested attribute, it must be . separated.
|
|
Pre-requisites: CSV file should have the key attributes of the parent records.
|
|
- Pre-requisites: CSV file should have the key attributes of the parent records.
|
|
In the `relatedNaturalKey` block, as an entity that has the related parent record ID directly in
|
|
- In the `relatedNaturalKey` block, as an entity that has the related parent record ID directly in
|
|
the CSV file under the `sourceColumn` of the keys block.
|
|
the CSV file under the `sourceColumn` of the keys block.
|
|
`sourceColumn`: Column name of the CSV file which refers to the parent record ID.
|
|
- `sourceColumn`: Column name of the CSV file which refers to the parent record ID.
|
|
Pre-requisites: The parent record ID should be present under the `sourceColumn` of the CSV file.
|
|
- Pre-requisites: The parent record ID should be present under the `sourceColumn` of the CSV file.
|
|
|
|
|
|
``json
|
|
```json
|
|
{
|
|
{
|
|
"ExtensionProperties": {
|
|
"ExtensionProperties": {
|
|
"FileContentsDetails": {
|
|
"FileContentsDetails": {
|
... | | ... | |