> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/api/guides/import-api/import-commands/importing-assets.md).
# Importing assets
## Command structure
```json
[
{
"resourceType": "Asset",
"identifier": {
"name": "Asset 1",
"domain": {
"name": "Business Data Domain 1",
"community": {
"name": "Data Community"
}
}
},
"domain": {
"id": "43215678-1234-1234-1234-123456788765"
},
"name": "New Asset 1",
"displayName": "A1",
"type": {
"name": "Column"
},
"attributes": {
"Original Column Name": [
{
"value": "XXX_COLUMN_1"
}
],
"00000000-0000-0000-0001-000500000011": [
{
"value": "True"
}
]
},
"relations": {
"00000000-0000-0000-0000-000000007062:SOURCE": [
{
"name": "Asset 2",
"domain": {
"name": "Data Asset Domain 1",
"community": {
"name": "Data Community"
}
}
}
],
"00000000-0000-0000-0000-000000007038:SOURCE": [
{
"name": "Table representation Asset",
"domain": {
"name": "Business Asset Domain 2",
"community": {
"name": "Business Community"
}
}
}
]
},
"status": {
"name": "Accepted"
},
"tags": [
"sample",
"technical",
"crucial"
],
"responsibilities": {
"00000000-0000-0000-0000-000000005018": [
{
"user": {
"id": "00000000-0000-0000-0000-000000900001"
}
}
],
"Business Steward": [
{
"userGroup": {
"id": "00000000-0000-0000-0000-000001000002"
}
}
]
}
}
]
```
## Identifier
You can use any of the following fields as the identifier for an asset but only one at a time:
* `id`
* `name` and `domain` identified by `id`
* `name` and `domain` identified by `name` and by `community` identified by `id` or by `name`
* `externalSystemId` and `externalEntityId`
### Identifier structure
```json
{
"id": "12345678-1234-1234-1234-123456788765"
}
```
```json
{
"name": "Sample Asset Name",
"domain": {
"name": "Sample Domain Name",
"community": {
"name": "Sample Community Name"
}
}
}
```
```json
{
"externalSystemId": "EXT_SYSTEM",
"externalEntityId": "Asset_1234"
}
```
{% hint style="info" %}
* The `community` and `domain` fields have the same structure and requirements as the community and domain identifiers.
* Code snippets in this section may show redundant data to demonstrate the fields accepted by the import API.
{% endhint %}
## Optional fields
| Field name | Field type | Remarks |
| ---------------------------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| type | `id`, `name`, or `publicId` | Updates the asset type. |
| [attributes](#importing-attributes) | The attribute type and the value or an array of values. | Sets or updates the asset attributes. |
| domain | The identifier of a domain. | Moves the asset to the domain. Should only be used for updates. |
| name | String | Updates the asset full name. Should only be used for updates.
The full name must be unique per domain. For more details, see Asset names.
True: Enable importing responsibilities at asset level.
False (default): Disable importing responsibilities at asset level.
|
{% hint style="info" %}
When the setting is disabled and responsibilities are defined at asset level, you get an error.
{% endhint %}
{% hint style="danger" %}
Setting specific responsibilities on a large number of assets will affect the performance and stability of the system.
{% endhint %}
{% hint style="success" %}
Define responsibilities on communities or domains so that the assets can automatically inherit those responsibilities.
{% endhint %}
You define a responsibility by specifying a resource role, identified by name or ID, and assigning to it one or more users or user groups, identified by ID:
```json
{
"00000000-0000-0000-0000-000000005018": [
{
"user": {
"id": "00000000-0000-0000-0000-000000900001"
}
}
],
"Business Steward": [
{
"userGroup": {
"id": "00000000-0000-0000-0000-000001000002"
}
}
]
}
```
{% hint style="info" %}
The resource roles, users and user groups that define the imported responsibilities must already exist in Collibra.
{% endhint %}
You must specify each role only once in the list of responsibilities.
You can assign multiple users and multiple user groups to the same role:
```json
"responsibilities": {
"Chief Data Officer": [
{
"user": {
"id": "00000000-0000-0000-0000-000000900001"
}
},
{
"user": {
"id": "00000000-0000-0000-0000-000000900002"
}
},
{
"userGroup": {
"id": "00000000-0000-0000-0000-000001000002"
}
}
]
}
```
The Import API performs a query for the responsibilities in Collibra and:
* If the same responsibilities exist, the Import API performs no action.
* If responsibilities other than the ones provided in the input exist, they remain unchanged.
* If a responsibility exists with the same role but different assignees, the Import API deletes the existing responsibility and replaces it with the one provided in the input.
* If the responsibilities do not exist, the Import API creates them.
## Importing tags
When you provide tags in the input command, they replace any tags that the asset already has. After processing the import command for an asset, only the tags provided in the input are assigned. If you provide an empty tag list in the input, all tags are deleted from the asset.