Conflicted Asset Upload Metadata Type Handling

August 11, 2023
2 minute read

We have recently identified an issue with consistency between different upload experiences across Acquia DAM.

What’s changing

This change affects asset uploads via version 2.0 of the API that match the following conditions:

The file being uploaded will conflict with an existing asset
The upload profile used for the upload is set to auto-version the asset
The upload profile sets a metadata type that is different from the asset that the upload will conflict with

Currently, v2.0 of the API will replace the metadata type on the existing asset with the metadata type associated with the upload profile.

To be more consistent with v1.0 of the API and other asset upload methods available across Acquia DAM, we are changing this behavior to retain the existing metadata type.

Affected resources

Only version 2.0 of the API is affected.

Here is the API endpoint that will be updated:

Asset Upload
```
POST /v2/assets
```

How to test the new behavior

You can test this change in behavior now before it goes live by making use of an early access toggle. When making requests to the affected resource listed above, the following header can be supplied, which will ensure the new upload behavior is applied:

x-widen-api-toggle: conflicted-upload-metadata-type

For example, when uploading an asset:

curl --request POST \
     --url 'https://api.widencollective.com/v2/assets' \
     --header 'authorization: Bearer wat_demo_abc123def456' \
     --header 'x-widen-api-toggle: conflicted-upload-metadata-type' \
     --header 'content-type: multipart/form-data' \
     --data-binary '{form data goes here}'