Having almost completed a draft version of the first POCKET material to be transformed to open content on the OU OpenLearn platform I feel this is a good point to reflect on the project process so far. The first unit I worked on for POCKET, taken from section 1 ‘What is Customer Service?’ from the Customer Skills module, as part of the Foundation Degree in Hairdressing and Salon Management ran at The University of Derby Buxton.
I found that downloading various OU XML content packages from the OpenLearn LabSpace and exploring the XML file in an XML editor was very helpful. It helped me to see the structure of the XML files already on OpenLearn and how the OU schema worked to achieve this structure.
Within the files that I downloaded from OpenLearn there were two OU schemas: OUGeneric_v1.2.xsd and OUGenericFull.xsd. As the Generic_v1.2 is the most recent schema and the one that offers most flexibility I decided to work to this schema only. Downloading a folder from OpenLearn also provided me with the other files I needed to include when I uploaded my unit (for example the XML file list and the metatdata file).
In the unit folders that can be downloaded from OpenLearn there are instructions for previewing an XML file before you upload it to the LabSpace. I did try and follow these instructions but found it to be a very time consuming and complicated process and personally I preferred to upload my file onto the PlaySpace to preview it.
XML editor
As the project promotes open content and open access the project team and I were very keen to use an open source XML editor. I downloaded and tried out a few different XML editors on the PC (including Jaxe and XML Copy Editor), but ran into problems when trying to get one of these editors to run on a mac. As I was working across both Mac and PC platforms I wanted an editor that I could use on both. That was the reason I decided to purchase oXygen XML editor as this works across both platforms.
Adding film and interactions
The OpenLearn site does not seem to have clear guidelines on what the ideal file size is to create and export film and animation files to the platform. From the schema and from downloading other OpenLearn units (which included film files) I was able to understand which file formats to use (for film this was mp4 and flv) and a kind of idea of the file size to export them to.
Uploading content to OpenLearn
I had a few initial problems uploading my files to the OpenLearn platform and I feel I would have benefitted from clearer instructions and guidelines available on the site. The ‘How to’ unit named Re-using, remixing and creating content, which I found quite useful. The problems I had uploading content to OpenLearn (to the PlaySpace) were:
I zipped up the actual folder of files instead of just the files.
I associated the CSS file to my XML file.
I didn’t label my main XML file ‘content.xml’
I got advice in the Help and Support forum, which is a very useful feature.
Original material
The original material was quite easily broken down into separate units. Written originally for use on Blackboard, it also contained a lot of self-assessment and reflective exercises which provided a lot of scope and opportunity for developing into flash and video interactions.
A re-occurring problem with the material was that it quoted a lot from secondary sources. Due to copyright issues this could not be included in the material and the academic needed to either re-write or remove large quotes from the material. Another option was to direct readers of the content to the relevant websites.
Content author (Louise Buxton, University of Derby, Buxton)
Louise and I built up a strong working relationship by meeting regularly and this also helped to keep the project on track, give both of us clear goals to achieve by each meeting and kept us both informed of progress made. Also any problems that arose could be readily addressed and managed as soon as possible.
Flash animations and interaction (Estimated time taken:15 hours)
The material contained regular self-assessment activities which translated well into interactive activities. The Flash interactions were straightforward to plan from the existing activities in the material, but were fairly time consuming to create as this involved planning the scenes, doing illustrations, creating animation and adding actionscript where necessary. I found the Technology unit in the LabSpace helpful to see what kind of animations were on OpenLearn already (and to get an idea of style) but could not find any guidance on what kind of size to create the animations. It would have been helpful if the original Flash files were included in the OU XML package download.
Films (Estimated time taken: 21 hours)
Creating the films for this unit took a fair bit of planning, which included: recruiting the students to act in the films; writing ‘all rights release’ forms for the actors to sign; writing a script and prop list for each film; arranging the filming location. We were able to use the salon and the reception to film in and planned filming for two Wednesday afternoons, as there were no clients due in at this time.
Movie was used to edit the films and I also used Visual Hub to convert the files into mp4 and flv format. Similarly to the animations there was no guidance on the OpenLearn site on what size to export the video files to, so I downloaded a few OU XML package files from the LabSpace from units which used video and then saw from the video files included in these packages the average file size (about 3mb). Transcripts also had to be written for each film and saved as a pdf to be uploaded onto the OpenLearn site.
Study hours
These still need to be decided with the content author and are a factor which I think should be considered from the very start of the transformation. The content author has struggled with knowing how many hours to allocate, so a guide for calculating this would be a good outcome for the project.