Catarse Specification

[jellegerbrandy]

For integration in the Catarse platform consists of two, independent, parts:

1. The upload functinonality that is to be inserted in the existing flow for project creation
2. The player itself, that is to be embedded on the project pages

1. Upload functionality

Use case is the refence: #5 (we need to choose between the 3.* options)

In each case, what we need is:

1.a. functionality for ripping vids from youtube and vimeo AND/OR
1.b. a place to upload vids and add data about them (either embedded or on http://paratii.video/uploader)

1.a. Rip vids

Integration with catarse at this level means simply:

• adapt catrase's video page along the lines of 3.3 in the [upload in iframe] Catarse, a crowdfunding platform, wants to allow their users to host project's videos on Paratii. #5
• [?] we'd need some type of public "service" API that eats a YT link and creates a video on Paratii

1.b. upload tool

For the catarse case, this can be relatively simple, as we do not yet need to think about managing playlists and such. It would just be a drag-n-drop interface followed (or preceded) by forms to fill out information

2. Customized player

See use case #10.

• we probably want to use a slightly simplified player version - without playlists and discovery features, so we need options
• catarse needs be able to embed paratii vids
• [at a later stage we might want to integrate catarse accounts with Parati in some way, as suggested in Catarse player and sharing options #10]