XML API TIPS: Moving Archives That Have Been Repaired
One common workaround that customers do (or Adobe support may do on behalf of customers) to fix recordings that have some sort of sync or playback issue, is to download the archive (recording) zip, potentially run it through a repair tool, and then re-upload the zip package back to Connect as a content object in the ‘Content’ directory. A common request may be to move that archive from the Content directory, to another location or even back underneath the Meeting’s ‘Recording’ directory. The problem is that with failed recordings (recordings that didn’t fully process) and/or re-uploaded recordings, they will not have a ‘date-end’ parameter for the sco, like normal recordings do. So when you try to (for example) move the archive to the original Meeting’s Recordings directory (which can really only be done using the API), you will get the following error:
API Call = Sco-Move:
where sco-id = the sco-id of the re-uploaded archive
where folder-id = the sco-id of the original meeting (which is also the sco-id of the Recordings directory for that meeting)
<invalid field=”sco-id” type=”string” subcode=”recording-is-in-progress“/>
This is because the sco does not have a date-end param/value. You can see this by running the sco-info call on the sco-id. You will see no date-end.
What you need to do before you can move the sco, is set a date-end param using the sco-update API. You would set the date-end value to some date in the past.
Here is an example:
Now, when you do a sco-info on that sco you should see the date-end param and value.
You can now also move the recording to it’s desired location (say back to the Meeting’s recording directory):