Skip to content

Suggesting videos for the site

Jump to bottom
Sheila Miguez edited this page Oct 18, 2015 · 13 revisions

If you are a conference organizer/volunteer and want to have your videos posted to pyvideo.org, here are some guidelines. Open a new issue giving us a link to your conference and the videos you've posted.

In general, we like if you can provide us with machine readable information linking metadata to the videos.

We do not get machine readable information in practice, so here are some guidelines.

Videos

  • We'd like to have one video per talk. We understand that this is hard to do for lightning talk sessions, so don't fret.
  • We prefer videos released with free licenses (definition).
  • We'd like to provide persistent links to downloadable files. archiving suggestions: Internet Archive (the internetarchive project is helpful), Wikimedia Commons

Information we'd like per talk

  • a url to where the video is posted
  • a list of speaker(s)
  • a lengthy description with markdown allowed.
  • license information
  • (optional but nice to have) a short summary that will look good on a page listing all the videos in the conference. markdown not allowed.
  • (optional but nice to have) a url to video files so that we can archive them on archive.org.
  • (optional optional but nice to have) related urls such as repos, slides, transcripts, etc.
  • (optional) tags

If you don't have all of the above, that is okay, but things will take longer.

Information that would be nice to have in Youtube descriptions

For conferences, unless Carl or Ryan is recording an event, we scrape youtube for the metadata. If you are a conference organizer responsible for how videos are uploaded to youtube, we can handle things quickly if you have a well structured description that contains the above information. For example, in the youtube description you could put

Title: put the real title in the description. When people upload videos they often label the youtube video with the conference and speaker names, this is okay for youtube, but then I'll need to clean up the titles by hand and they are usually not well formed enough to parse automatically.

Speaker:

  • speaker one
  • speaker two

Summary: (optional)

A short summary that will look good in list next to a talk thumbnail. This isn't added often, and I'll often just use the description.

Description:

a lengthy description of the talk. When this isn't provided I'll try to scrape the conference website. This makes things take longer.

For advanced users

We use a tool called steve for scraping information and pushing it to pyvideo. A typical workflow involves

  • running steve-cmd to scrape a youtube channel,
  • cleaning up the resulting json data,
  • then pushing it to pyvideo. If this makes sense to you, take a look at how steve uses the richard api. If you can give us a directory of richard api-compliant json files per each video, that would be excellent.

For more about richard see http://richard.readthedocs.org

The api for video resources is not fully documented, for which I apologize. It might be easier to get an idea of what the fields are by looking at an example http://pyvideo.org/api/v2/video/3820

Clone this wiki locally