Talk:Content workflow

From OLPC

Revision as of 15:45, 27 March 2012 by Cjl (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Content Workflow Diagram

                     Found Content------License Vetting
                         |                     |             |----Translate----
Search for Content       |                     |             |                |
            |            |                     |             |                |
          Add Content to Wiki     Initial Review/Prioritize-------Transcode--------Content Bundling--Content Stamping
            |            |                     |             |                |
Wanted Content           |                     |             |                |
                         |                     |             |----Edit---------
                     Created Content----License Release

Existing Content

Content Searching

If people are looking for content, or happen to come across something they need to create a page on the wiki for it, and tag it Category:Content

Initial Content review

Basic info about the content needs to be registered on the Content's page. Info should be at least Name, URL, language, format, media type (text, music, etc), and many other quality/quantity evaluations.

Content Review

Ideally and eventually this will be done by the Content Review system. The Content Review system would involve filling in any additional meta-data that the initial uploader didn't complete, as well as alternate opinion.

At this point, based on what the Content does or doesn't has it could go to any number of task-groups

I like the task groups idea. Mchua 13:28, 25 May 2008 (EDT)
It works for Ubuntu and wikipedia Seth 19:13, 30 May 2008 (EDT)

License Vetting

A lot of work isn't going to have a clear copyright or an acceptable copyright for OLPC. A team could work on opening such copyright and double checking actual copyright status. This group/position of the chain should also work on proper attribution of contributors.

Reformatting

Content should always be in the smallest, most open, and most accessible format before it is bundled. This includes speex for audio, theora for video and png for images.

Content Bundling

    • Putting content together into the correct format with all of the structure and .pot files is a task that needs it's own team


Translating Content

  • Much quality content, such as photos, need some basic translation of meta-data and name
  • Some worthwhile content should be translated in entirety
  • The existing Pootle system would be great for this, especially with .xol bundles.


Content Reviewing

    • Content needs to be reviews and meta-tagged for a variety of terms; age, format, language(s)
    • See Content Review for more information on this project


Re-purposing

If a Content Project creates content of more than one mime type, that content could be re-purposed. If any new work that we did were uploaded to wiki-commons it would be beneficial to both communities, as well as becoming part of a larger database of open work

Potentially related group, or a separate one: implementation and feedback from implementations, closing the communications loop between content providers/contributors and those using the content in their classrooms. Mchua 13:28, 25 May 2008 (EDT)
Good idea. This is something that ought to be taking place on the Official OLPC level, IMO, but we can trySeth 19:13, 30 May 2008 (EDT)

Worth tracking

UNESCO Open Education Resources wiki, in particular this page shows some promise:

http://oerwiki.iiep-unesco.org/index.php?title=UNESCO_OER_Toolkit

It might be a good idea to focus on documenting more OLPC-specific aspects of content (i18n, bundling, etc.) and see how much of this UNESCO OER stuff can be adapted to cover the earlier stages of content development.

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox