upload with FTP, create with Media Write API?

[steevhise]

I'm wondering if there's a way to upload a video file to the BC cloud via FTP or Aspera but then assign all the metadata via the Media API from the start, rather than sending an XML manifest file.  We want our entire workflow to be on our CMS, and yet we want to be able to upload video files that are larger than 2GB, so we don't want to upload via HTTP.  I don't see any reference to this sort of thing in the Media API documentation.

Thanks,

steev

[BC-Jonathan]

Would you be open to uploading the asset via FTP (no meta data) and then use the Media API call "update_video" call to achieve this?

Thanks

[steevhise]

---

BC-Jonathan wrote:

Would you be open to uploading the asset via FTP (no meta data) and then use the Media API call "update_video" call to achieve this?

Thanks

---

Yes, using update_video was exactly what I was hoping i could do - but if I don't have a refID yet, how would I do that? can I identify the video just by its filename at that early in the process?

Thanks,

steev

[BC-Jonathan]

My mistake as you would need a videoID to reference, but you wouldn't know what that is unless you were really creative and did something like: use "search_videos" and search on reference ID, get the videoID back and then update.

Sorry for confusion.

Thanks

[steevhise]

---

BC-Jonathan wrote:

My mistake as you would need a videoID to reference, but you wouldn't know what that is unless you were really creative and did something like: use "search_videos" and search on reference ID, get the videoID back and then update.

Sorry for confusion.

Thanks

---

Right, when I upload all I will know is the filename.  So, can I search on filename with search_videos?

[steevhise]

or perhaps there's a way to just get all videos, including in-process ones, and search through them to get the id, using the "unfiltered Read API methods"?  or is there just no way to do what i'm talking about?

thanks,

steev

[BC-Jonathan]

Well in your XML, you could assign a reference ID, so upon upload the video already has a reference ID that you could then search on.

[steevhise]

---

BC-Jonathan wrote:

Well in your XML, you could assign a reference ID, so upon upload the video already has a reference ID that you could then search on.

---

well, yes, but as i said in my original post, I was hoping we could avoid the whole xml manifest step.

[BC-Jonathan]

If you get in contact with your account manager then you can request to have the Aspera UI Upload enabled.  This will remove the 2GB cap and then you can proceed with meta data.

http://support.brightcove.com/en/docs/using-accelerated-upload-media-module

How does that sound?

Thanks

[steevhise]

Unless I'm mistaken, whether we use FTP or Aspera, the question remains of whether and how we can skip the XML manifest step and save all of the metadata via the Media API.  We just want to streamline the workflow as much as possible so that all our editorial staff needs to do is upload the video file and then enter metadata using our drupal CMS admin interface.

thanks,

steev