After moving items to a new folder using loc:create-folder to create the folder and loc:move-items to move items to it any referenced assets remain in the original location. To reproduce:

1. Use Interplay Access to observe a sequence, note the presence of the referenced assets
2. Use CTMS to create a new folder and move the sequence to it
3. Use Access to observe the sequence in the new location, note the absence of referenced assets
4. Use Access Relatives inspector on the sequence to identify the referenced assets and note that they still show up in the original folder

Hi Michael, you can't move assets to a folder. You can only move the whole folder with the assets.

http://developer.avid.com/ctms/api/rs_loc/rs_loc_item.html#_loc_move_items

I have to test if you can move referenced assets.

Adri Vermeulen

Yoruba, software development

Hi Adri,

I think you may have misunderstood the point I was querying. I have not attempted to move an asset as such, only the folder item that references it (accessed as a loc:item) and would appear to be supported as per the documentation "A non-folder item: the item is moved from its original folder to the current folder". This works perfectly, for example if you identify a sequence or master clip using loc:item it will be moved quite successfully to the destination folder.

It should not be necessary to do anything with referenced assets which, after all, probably never existed in the source folder in the first place. What you would expect to see is the references to those assets showing up in the destination folder after the move. This of course is what happens if you use Access, or indeed Web Services, to move items between folders. If the CTMS equivalent dosn't perform in the same way then frankly it isn't a great deal of use.

Mike

Hi Mike,

I'm not sure the reference did not exist, they probably have folder items which get moved as well when using Access.

This sounds to me like a bug in the CTMS implementation, I'd recommend contacting developer support and posting a bug to them.

Cheers,
Tilman

Hi Mike,

Thanks for reporting the issue.

We have reproduced this behavior internally and submitted an investigation bug against engineering team. The reference number is IPI-3001 if you'd like to ping for an update later.

Vadym