Ability to add videos from other sites

[and]

Create the ability to take videos from Vimeo, YouTube?, blip.tv, etc and add them to a Plumi site.

This will enable broader sharing of content. Videomakers will not have to re-upload their video to another site (the Plumi site) if they have already done so elsewhere. It will also allow site editors to curate content from other sites into a Plumi site.

• external videos offered as same content type as ordinary videos, but instead of uploading a video the user can add a link / embed code from Vimeo, Youtube or other site

• ability to list external videos separately from normal videos on the site (not sure yet in which listings we need to differentiate them)

(FIXED DELIVERABLE)

[anonymous]

Talking to someone from foe today they were looking at updating to the latest version of kupu which allows embedded videos. This is a bit simpler than what I was envisioning but could be good to have available.

Other possibilities include  http://plone.org/products/atgooglevideo/

[mike]

we need to think about how videos hosted on external sites will be displayed for the user.

the viewer of these videos will have a different experience to viewing a normal video - you will not be able to download it. we need to then explain in the UI that this is the case...

or should videos hosted externally be quite separate from internal videos?

• anna

[anna]

Ok, we discussed how these videos might work. The proposal has been added to the ticket description.

[anna]

Mike suggests using the same PlumiVideo? content type, with option to add link / embed code instead of upload a file (but still be able to differentiate these videos from normal videos, and thus list them differently on the site), and also to split off the changes to publish form into another ticket.

Ticket for changes to publish form: http://plumi.org/ticket/529

[anna]

Moving this to the re-factoring milestone, as Unweb advise that this should be done after changing Plumi video content type into schema extender

[dimo]

This is not something that can be completed in this milestone & contract. My suggestion is to do it in parallel with the video publish form redesign

[and]

I will convert the remaining 4.2 tickets to a 4.3 milestone and shift the rest back a version also. Major means it won't actually go in 4.2.

[and]

In previous conversations we discussed doing this as part of the publish form refactor so that it was already integrated, if we're doing the refactor in the 4.3 release shouldn't add it into 4.3?

[anna]

This apparently can't happen in 4.5, but moving to 4.6 to indicate this as a priority.

[anonymous]

I will use Plumi if this is implemented!

[and]

Let us know if you can help!