Afrikaans Translation Hackathon

I just wanted to quickly dump a few thoughts about a big event we’re about to run. I’ve been slipping behind in my blogging and thought I’d inflict a quick core dump on you. Tomorrow (7th May 2011) we are holding a translation hackathon at the University of Stellenbosch. The objective is extremely ambitious, translate [...]

No Comments »
FHSST Editing Sprint Review

It came to pass recently that we (and by we I mean just short of 100 volunteers from all over the world!) edited the FHSST textbooks in the space of 9 days. In writing this blog post reviewing what happened and what comes next, I have realised that it was an incredibly stupid thing to even attempt (impossible actually) and I’m still amazed that we were able to successfully complete the task, all due to the generosity of volunteers.

Ideal Process:

  1. Access books on a.nnotate.com (links available on http://www.markhorner.net):
      Mathematics Grade 10: http://a.nnotate.com/php/pdfnotate.php?d=2010-10-08&c=SHkkygd2

      Mathematics Grade 11: http://a.nnotate.com/php/pdfnotate.php?d=2010-10-08&c=dHbcYbbw

      Mathematics Grade 12: http://a.nnotate.com/php/pdfnotate.php?d=2010-10-08&c=M4p01euS

      Physical Science Grade 10: http://a.nnotate.com/php/pdfnotate.php?d=2010-10-08&c=3sCc82qY

      Physical Science Grade 11: http://a.nnotate.com/php/pdfnotate.php?d=2010-10-08&c=hW2hgnQP

      Physical Science Grade 12: http://a.nnotate.com/php/pdfnotate.php?d=2010-10-08&c=enzaEmdn

  2. Select an exercise in any book that has no solution and no annotation about a solution on FullMarks
  3. Highlight the question and an annotation window pops up – annotate the question saying that you are working on a solution
  4. Create a question on FullMarks with the full step-by-step model solution and finalise it (see details a bit later for some guidance on this)
  5. View your finalised question and answer on FullMarks – copy the url
  6. Return to a.nnotate.com and add the url you copied to the annotation in the book that you created in step 3
  7. Log in to www.fhsst.org (this is at the very bottom of the FHSST page)
  8. Create a short url by going to www.fhsst.org/shorten selecting “Shorten url” option from the menu and pasting the full question url into the box and submitting
  9. Copy the resulting code from the short url (i.e. just copy XYZ when the short url is www.fhsst.org/answers/XYZ) and add this to the annotation in the book as well
  10. Return to step 1. and repeat for another question

This will ensure that we have a short code to redirect learners to a full model solution for every question in the book. They will also then be able to see similar questions on FullMarks as well. We have adapted this slightly for the hackathons but always ensuring that the files on a.nnotate.com have the latest information regarding what has been and is being worked on.

Hackathon Process
Get a paper chapter assignment from the relevant Siyavula team member so they can manage what is being worked on – do this to help them even if you can follow ideal process.
Buddy up with someone to discuss any issues which might arise. Some questions may not be clear or the text may have an error or you may just want some input on the simplest way to approach the solution.
Access to the internet Computer but no access to the internet No computer
  • Follow ideal process
  • Develop the solutions in OpenOffice rather than on FullMarks
  • Transfer solutions file to a Siyavula team member who will:
    • update annotate
    • upload solution to FullMarks
    • generate the shorturl
  • Develop the solutions on paper
  • Hand it in to the Siyavula team member who will:
    • update annotate
    • upload solution to FullMarks
    • generate the shorturl

This will ensure that we have a short code to redirect learners to a full model solution for every question in the book. They will also then be able to see similar questions on FullMarks as well.

I’m very passionate about the problem of affordable textbooks (and academic publishing more generally), especially in maths. I came from an underprivileged background and I know there are many brilliant people out there who have no opportunity to flourish due to lack of materials. I also have a friend in a third-world country (PNG) who is a teacher, and I could imagine the benefit he would derive from a textbook scheme as you have organised in South Africa.

Once this is complete we will turn to suggestions and improvements related to the conceptual explanations incorporation, where appropriate, links to the Khan Academy videos and the PHET Simulations. From there we can develop the teachers’ guides and submit the books to the formal review process at the DBE for inclusion on the approved books list. Should they be included schools will be able to purchase FHSST textbooks as part of the official procurement process but at approximately 1/5 of the cost of publishers alternatives.

--> 5 Comments »
FHSST v0.5 Books on a.nnotate.com

Just a quick post to let people know that the FHSST v0.5 books are up on a.nnotate.com – this is primarily to support hackathons but will also be used to capture errata and suggestions.

1 Comment »
Help FHSST from anywhere in the world

We’re on a mission to get the FHSST books completely proof-read by next week. We were doing a lot manually which required people be in Cape Town if they wanted to help out but we’ve since uploaded the books to a.nnotate.com where anyone in the world can browse and annotate errors etc. so you can [...]

6 Comments »
Calling scientists and mathematicians!

Our schools are struggling due to the nation wide strike. Learning needs to continue at the schools, many of whom are running on skeleton crews. A group of volunteers have authored a set of open source textbooks and resources that can to support learners and educators in this time. The open copyright license allows the [...]

17 Comments »
Crowdsourcing vs. Traditional Design: The Results

A long time ago we set out to get two sets of textbook covers designed, one for Physical Science Gr 10-12 and one for Mathematics Gr 10-12. We used the opportunity to test crowdsourcing against traditional design. Here are the results of the two processes for you to compare.

3 Comments »
FHSST site upgrade update

First part of the site upgrade finished, the FHSST site now uses Drupal 6.

No Comments »
Crowdsourced covers are in.

We had many submissions and there were some great ones but these were the most popular amongst members of the FHSST and OpenPress teams. I’ll write up a more detailed follow-up post when we’ve got the maths ones in.

1 Comment »
Drupal Module for FHSST Feedback – quotes wanted

If you’re a Drupal person and would like to have a crack at developing a feedback module for FHSST please read on for the specification details and contact me with any clarifying questions or a quote for the work. I intend to make a decision by the middle of next week (18th November) so you’ve got a week to get the information to me.

FHSST Feedback Module

The FHSST site allows authors to build books in LaTeX. The original goal was to have many LaTeX-competent authors working on many sections. We have learnt that very few people are comfortable with LaTeX and PSTricks. To better accommodate people who still want to make contributions but not get their hands dirty we must provide a simple way to give the necessary input.

We would like a feedback module to be written for Drupal to help with this. This module should allow three types of feedback:

  1. errata

  2. suggested contributions

  3. testimonials

Errata

Each erratum needs to contain:

  • erratum title (mandatory)

  • detailed erratum information (mandatory)

  • book for which it is submitted (mandatory)

  • book version for which erratum is applicable (mandatory)

  • book section in which error occurs (mandatory)

  • book page number (optional)

  • submitter’s:

    • name and surname (mandatory)

    • email address (mandatory)

    • role, one of:

      • learner

      • educator

      • parent

      • other

  • timestamp of submission (recorded automatically)

  • status (only changeable by coordinator – starts in pending):

    • pending

    • corrected

    • disputed

  • timestamp of resolution (i.e. corrected or disputed state change – recorded automatically)

  • person changing state (recorded automatically)

When submitted, an erratum must go into a queue and the coordinators of the relevant book should receive an email notification that it has been submitted. They can then login and review the erratum. Once they have processed it they must be able to set it to either corrected or disputed in the case where the erratum is actually incorrect.

A page should be provided where users can see all errata submitted, the submitters’ name, the relevant book and version, and the status of the errata. The title should link to the full erratum view.

A block should be provided where users can see the 5 most recent errata submitted (title, book and status).

Suggested Contributions

This is to allow general users to submit a contribution to be included in the book by a LaTeX-enabled author. Each contribution should have:

  • contribution title (mandatory)

  • detailed contribution (mandatory)

  • attached files (optional)

  • book for which it is submitted (mandatory)

  • book section (optional)

  • submitter’s:

    • name and surname (mandatory)

    • email address (mandatory)

    • role, one of:

      • learner

      • educator

      • parent

      • other

  • timestamp of submission (recorded automatically)

  • status (only changeable by coordinator – starts in pending):

    • pending

    • incorporated

    • discarded

  • timestamp of resolution (i.e. incorporated or discarded state change to be recorded automatically)

  • person changing state (recorded automatically)

When submitted a contribution must go into a queue and the coordinators of the relevant book should receive an email notification that it has been submitted. They can then login and review the contribution. Once they have processed it they set it to either incorporated or discarded state in the case where the contribution cannot be used.

A page should be provided where users can see all contributions submitted, the submitters’ name, the relevant book and version, and the status of the contribution. The title should link to the full contribution view.

A block should be provided where users can see the 5 most recent contributions submitted (title, book and status).

Testimonials

This is simply to collect information about how the content has been used.

  • testimonial title (mandatory)

  • detailed testimonial (mandatory)

  • book for which it is submitted (optional)

  • book section (optional)

  • submitter’s:

    • name and surname (mandatory)

    • email address (mandatory)

    • role, one of: (mandatory)

      • learner

      • educator

      • parent

      • other

  • timestamp of submission (recorded automatically)

Administration

For the feedback module the books for which feedback is being received need to be configured. This should happen from the module administration page and not depend on the book module of Drupal. The administrator will add the books for the module and then add, on a book-by-book basis:

  • versions

  • chapters and sections

  • coordinators

When a book is added at least one version number is required. For each version number provided, a list of chapters and sections is required. A book will have multiple versions, each with their own unique chapter and section listing. This listing can be a simple textarea where each line is a chapter or section heading.

Each book must also have a list of coordinators who are users on the system. Coordinators should be able to access a list of all errata and contributions for their books. They should be able to view them and change the status if necessary. The time when the status is changed should be recorded.

Special Remarks

All the feedback types should be node types and should integrate into the Drupal CMS properly so that they can be integrated with other modules designed to manipulate nodes. The theming information should also be separated so that they can be re-themed.

A special page should be provided that can be used as the homepage. This page should have a customisable body of full html and then have forms for all three feedback types. This will be presented to non-authenticated users as the homepage allowing them to provide the feedback directly from the front page. We would like jQuery/jQuery UI integration in this page so that a button can be shown for each type of feedback and if clicked the form must render as a modal window. Submission using these forms should be via AJAX and should trigger an update on the blocks for the content types if they are shown.

To simplify the forms when a user selects a book the relevant versions should be loaded. Once the version is selected only the relevant sections should be loaded. Validation for all form fields should be implemented.

The module should be written in such a way to conform to the Drupal 6.X API and should only have dependencies on well established modules (modules that are actively maintained and have demonstrable support and traction within the Drupal community).

We would release all the code under the Gnu General Public Licence.

--> 1 Comment »
Crowdsourcing versus Traditional Design

We’ve decided to run our own internal competition. The prize will be bragging rights as the optimal process for future covers for OpenPress / FHSST texts. We are going to allocate the same budget sourcing sets of covers for the Maths and Physical Science books, but we are going to have the Maths set commissioned by a regular design firm and we’ll get the Physical Science ones created on 99Designs.

2 Comments »