[Bulkupload] Updating mediafiles in combination with <collections> and/or <categories> tags will give errors

[Frans]

When using <action>update</action> in the formats section to replace the existing mediafile you will see an error in the bulkupload response indication that the asset can't be placed in the given collection or category because it already exists there.

“Errors:
 - MM - the asset is already present in the collection
 - Error while adding asset '3GmAnFtk1MtDEg0KP54gkmNX' to collection '80D5Q9h8bvhtrwIsmHCqW41X'
 - MM - the asset is already present in the collection
 - Error while adding asset '4BVZIK8gpwDUFGyR8nnDiL7V' to collection '80D5Q9h8bvhtrwIsmHCqW41X'
 - MM - the asset is already present in the collection
 - Error while adding asset '3ddB2FRVemLl2IJ1IbpxugqZ' to collection '80D5Q9h8bvhtrwIsmHCqW41X'
 - MM - the asset is already present in the collection
 - Error while adding asset '3GmAnFtk1MtDEg0KP54gkmNX' to category '4'
 - MM - the asset is already present in the collection
 - Error while adding asset '4BVZIK8gpwDUFGyR8nnDiL7V' to category '4'
 - MM - the asset is already present in the collection
 - Error while adding asset '3ddB2FRVemLl2IJ1IbpxugqZ' to category '4'

Je moet het probleem eerst verhelpen alvorens je het nogmaals kan proberen.

Je .vuf upload file is verwijderd, de rest van de files zijn blijven staan zodat je deze niet nogmaals hoeft te plaatsen.:”

Would suggest a similar behavior when using action=update in combination with <collections> or <catagories> tags:
- not supplied -> let the asset be in the existing collection
- supplied -> update the collection the asset is part of

[Frans]

No idea if this is still appropriate, since the bulkupload is refactured in MM 2.2

[forgacs]

We have fixed this issue. There was a bug in the /asset/$asset_id/collection_relation/delete REST call, and it was a development in the XML parser process.php file to clean the collections.