Content workflow: Difference between revisions
No edit summary |
|||
| Line 27: | Line 27: | ||
The process starts with raw content from a source. This could have been created specifically for OLPC or re-purposed from any one of thousands of existing content collections. There are a number of steps that have to be done to this content before it can be made into a library bundle. |
The process starts with raw content from a source. This could have been created specifically for OLPC or re-purposed from any one of thousands of existing content collections. There are a number of steps that have to be done to this content before it can be made into a library bundle. |
||
=== Document === |
=== Document the content === |
||
The first step is to add the content to the wiki. This is an important first step for many reasons: |
The first step is to add the content to the wiki. This is an important first step for many reasons: |
||
* Its unlikely that this way that two people will duplicate effort |
* Its unlikely that this way that two people will duplicate effort |
||
| Line 51: | Line 51: | ||
This example for [[Dive into Python]] isn't a bad example of what this data should look like. It doesn't quite satisfy all of the information that is needed but it is a start. |
This example for [[Dive into Python]] isn't a bad example of what this data should look like. It doesn't quite satisfy all of the information that is needed but it is a start. |
||
=== Check the license === |
|||
The best material, and the material that OLPC can pass on to children is material that has an Open license. If it doesn't have an acceptable license you need to make a note on the [[Licensing petitions]] page. That page is for users to contact the owners of the copyright of said material and explain Creative Commons to them and see if they are interested in letting this material be used. |
|||
Obviously if the material already is licensed then this need not be done. But a record of the license needs to be registered. |
|||
== Formatting == |
|||
== Examples == |
== Examples == |
||
Revision as of 00:53, 22 June 2008
|
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
|
Content Workflow
Hundreds of thousands of logical collections of media exist that could be in bundles for the XO. OLPC has countless hundreds of volunteers who want to help. But relatively few bundles have been created, why?
The answer is roughly that the process for creating a bundle is not clear. Also, not everyone is capable of completing all of the technical or organizational tasks needed to make a bundle. It makes sense to complete document the steps of this process and try to flesh out tools, processes and even groups to facilitate this process. It is not and has never been a hard task, just a few little ones.
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
Steps
The above diagram is a little rough, so lets walk through the steps in order.
Raw content
The process starts with raw content from a source. This could have been created specifically for OLPC or re-purposed from any one of thousands of existing content collections. There are a number of steps that have to be done to this content before it can be made into a library bundle.
Document the content
The first step is to add the content to the wiki. This is an important first step for many reasons:
- Its unlikely that this way that two people will duplicate effort
- If you (the finder or creator) stop working on the project, the work can be picked up by someone else
This initial documentation should contain some basic information:
| Name of Collection | Filetype(s) | Language | URL to Content | Submitted by | License |
|---|---|---|---|---|---|
| Diveintopython | http, pdf, xml, | it, fr, es, cz, kr, ru, | http://diveintopython.org/ | Seth | GFDL |
This example for Dive into Python isn't a bad example of what this data should look like. It doesn't quite satisfy all of the information that is needed but it is a start.
Check the license
The best material, and the material that OLPC can pass on to children is material that has an Open license. If it doesn't have an acceptable license you need to make a note on the Licensing petitions page. That page is for users to contact the owners of the copyright of said material and explain Creative Commons to them and see if they are interested in letting this material be used.
Obviously if the material already is licensed then this need not be done. But a record of the license needs to be registered.
Formatting
Examples
Photos
- I am a non-profit with a large digital stock of scanned historical maps from Africa
- I have a series of photos of puppets from around the world
Vetting of Content
Depending on how much information was recorded by the content's finder and initial logger to the wiki, additional information will likely need to be recorded.
License
One of the most important pieces of information would be the current license status of the work. Content for OLPC must be in some acceptable form of Open-Content license like Creative Commons or the GFDL. Content that has an unknown status, or is of unacceptable license should a special tag and/or place on the wiki.
A team should be formed for tracking down of copyright information on content, correct attribution, and in some cases, opening discussions with the copyright holder on releasing the content into an acceptable license.
Cross Posting
The last step involves cross posting any materials to other websites that the content may belong on. For instance an audiobook could go to archive.org or to librivox. An illustration would be uploaded to Wiki Commons.