Factors to Consider When Choosing Accounts Payable Services Providers.pptx
Get CloudEngine IET coffee morning July 2011
1. Get CloudEngine Cloudworks open-sourced Comments? cloudworks.ac.uk/cloud/view/5100 Nick Freear – CloudEngine lead developer - @nfreear IET Technology Coffee Morning, The Open University, July 2011 #ouTCM
Comments? http://cloudworks.ac.uk/cloud/view/5100 License: Creative Commons Attribution-ShareAlike License, except where noted, http://creativecommons.org/licenses/by-sa/3.0/ This presentation will review the development of the open source CloudEngine software and provide an update on the prototype site Cloudworks CloudEngine: http://getcloudengine.org CloudEngine Demo: http://dev.getcloudengine.org CloudEngine blog: http://cloudengineblog.wordpress.com OULDI blog: http://www.open.ac.uk/blogs/OULDI Project mailbox: cloudworks@open.ac.uk Who else? Juliette Culver – Lead/ original developer (on maternity leave) Gráinne Culver – OULDI project lead Rebecca Galley – Open University Learning Design Initiative (Project Officer) Richard Lovelock – Cloudworks/ CloudEngine developer
A number of the slides, including this one, are by Rebecca Galley! 1. Low barrier to entry – imperfect is OK! 2. Folksonomies not taxonomies 3. Tool-agnostic 4. People-orientated 5. Open 6. Link with communities, rather than replace 7. Recognise role of learning technologists and other mediators 8. Encourage discussion of learning design problems 9. Recognise ownership issues 10. Release early, release often
(Slide by Rebecca!) Jyri Engström http://www.zengestrom.com/blog/2005/04/why-some-social-network-services-work-and-others-dont-or-the-case-for-object-centered-sociality.html http://annlytical.com/phd/2011/6/23/engstrom-2005.html Cloudworks has been developed in order to support these social, collaborative and dialogic design processes - throughout development we have drawn considerably on the work of Engestrom, Dron and Anderson, and Bouman. Firstly, the site is essentially object-centred rather than ego-centred in nature. Engestrom focuses on the notion of social objects, saying that: The term 'social networking' makes little sense if we leave out the objects that mediate the ties between people. Think about the object as the reason why people affiliate with each specific other and not just anyone... And goes on to argue: “ The fallacy is to think that social networks are just made up of people. They're not; social networks consist of people who are connected by a shared object.”
Secondly, the design framework is one based on sociality. Core to this approach are a number of assumptions which come from Bouman et al. Firstly, that the system needs to accommodate both the evolution of practices and the inclusion of newcomers. Secondly, that individual identity is important so there needs to be a mechanism to enable the development of identities. Thirdly they argue that people are more inclined to use software systems that resemble their daily routines, language and practices than to adopt whole new concepts, interfaces and methods. And that metaphors and structures that mimic real life practices are likely to be more successful
(Slide by Rebecca.) DBR - An iterative cycle of rapid prototyping, user testing and adaptation Many of you will already be familiar with the prototype site – Cloudworks...( next slide)
(Slide by Rebecca) A place for sharing and discussions learning and teaching ideas Application of the best of Web 2.0 practices Launched July 2009 Over 4000 registered users Over 95,000 unique visitors (on average over 1000 unique visitors a week) – as of mid-June 2011. Cloudworks is a social network specifically aimed at supporting sharing and dialogue between educators, technologists, strategists and policy makers. New pedagogies and innovative use of technologies seem to offer so much in terms of providing new, exciting educational experiences for learners. However taken as a whole, the majority of educational offerings are still based on fairly traditional approaches, with a primary focus on content and assessment of outcomes, delivered via traditional didactic approaches. Educational innovations in both pedagogical approaches and innovative use of technologies remain the remit of educational innovators or early adopters It is important not to underestimate the barriers which are not just technical, but also pedagogical and organisational in nature. As part of the OULDI project we have conducted many interviews with teachers working in HE and they tell us for example: [there is a] “problem of doing something new (for example, oral assessment). Innovation is encouraged in the university but systems are quite set in their ways.” They often mention a lack of time or lack of skills or that they receive not support or rewards for using technologies. There is an inherent tension between the pressures of excelling in research versus promoting innovative approaches to learning and teaching. Teachers lack the necessary new forms of digital literacies needed to make effective use of new technologies, and some have concerns as to whether or not these new technologies are indeed any better than existing approaches They tell us that what they want are case studies, other practitioners to talk to and discuss ideas with - and it is this need that Cloudworks hopes to address.
Screen shot of a CloudEngine home page. Demo site, http://dev.getcloudengine.org Aurora theme, by Stephen Turvey / Yep Design, http://stephenturvey.co.uk/ Stable: CloudEngine 1.1.2 Tip/ development: CloudEngine 1.1.3-dev Clone with Mercurial $ hg clone https://bitbucket.org/cloudengine/cloudengine
A formal 'mission' would be: Develop software to make creating social web sites easier Keep the essence of Cloudworks Keep it small and lightweight Make it flexible, extensible, usable, accessible. What CloudEngine is not: Not a 'Swiss army knife', eg. a general purpose Content Management System/ CMS. Not a desktop tool!
Defining key terms Clouds - one person starts, others collaborate with extra content, comments, embeds, links... Cloudscapes - group Clouds around a theme or event. Technical Uses PHP 5 and MySQL Built on CodeIgniter MVC framework - lightweight, easy to learn Prefer Apache and mod_rewrite Clean URLs Uses jQuery, Tiny MCE editor, Mollom anti-spam oEmbed for embedding GNU Gettext for localization Configurable REST API, internationalization, moderation… Built with accessibility & standards in mind
Screen-shot from blog-post by Richard Lovelock, http://cloudengineblog.wordpress.com/2011/05/27/search-usability-enhancements/ Search – before… BUG - some searches failed – eg. “Events” All results were listed – the screen-shot above has the annotation “Very large page to scroll through”! No indication of relevance/ score, how results were ordered etc. Usability testing showed that people didn’t concentrate on the top few results – influence of adverts/ Google sponsored links??
Search enhancements – after… Performance fixes – fixed the bug for searches like “events”, Usability enhancements – shorter lists, tabs, Uses SimplePager, http://www.geckonewmedia.com/blog/2009/8/20/simplepager---jquery-paging-plugin--updated Browser plug-in By Richard Lovelock (and Nick Freear) Screen-shot, http://cloudworks.ac.uk/search/result?q=JISC
Screen-shot from, http://cloudworks.ac.uk/cloud/view/5426 OU embeds, http://freear.org.uk/content/ou-embed-proposal OU player, http://freear.org.uk/content/ou-media-player-project Also new Embeds for Timetoast (timelines), Cacoo (collaborative diagrams), Github Gists… Embed Javascript, http://embed.open.ac.uk/scripts/jquery.oembed.js Builds on “MALT Wiki” prototype - http://maltwiki.org/ TODO Embeds for CompendiumLD / SVG – with OULDI/ Andrew Brasher Embeds for Mathtran, Cohere, Google Docs/ Spreadsheets, MIT Scratch ...
HTML5 – form usability, http://cloudworks.ac.uk/auth/register Benefits: Browser performs error-handling, without Javascript, Simple new attributes, type=email|url|date …, required, pattern, placeholder … Consistent error handling, eg. type=email Consistent error reporting – accessibility/ usability, Consistent Javascript/DOM API. … In supporting browsers/ with HTML5 emulation. Examples: <input type=&quot;email&quot; required placeholder=&quot;you@example.org&quot; ../> <input type=&quot;password&quot; name=&quot;confirm&quot; oninput=&quot; setCustomValidity( value!=password.value ? 'Error, the passwords should match' : '' )&quot; ../> Works best in: Opera 9.6+ Firefox 4+ Half a job - Webkit: Safari Chrome TODO: Form coverage Date/ time fields HTML5 form emulation – for older browsers, MSIE 9, Webkit etc.
Here are some examples - a bit technical!
Messaging Private, direct To multiple participants By Richard Lovelock
Roadmap – code development Roadmap – community/ sustainability Potential internal uses: Curriculum Business Model site Knowledge Network “replacement”
ROADMAP Search enhancements – Done. Messaging – Done. HTML5, forms – Started. More embeds – LAMS, Prezi, Google Spreadsheets, OU player (OU embed/ oEmbed). Improved project site. * Pluggable authentication? * Extensions, integrations, API, RDFa… You help decide! Ideas for integration - consume feeds, data etc. Eg. integrate with Moodle....?
(Slide by Rebecca) A rigorous programme of user testing and feedback, and usability and accessibility audits, have informed the development of support and guidance materials which happened in parallel with the technical development - and include videos, presentations and documents aimed at supporting activity and collaboration on the site. Most of this support and guidance is underpinned by research and has been empirically tested. We believe many of our findings are transferable to other open network platforms and the Cloudworks guidance and support has been designed so that it can be easily repurposed to support activity on any CloudEngine community.
Our interest is in supporting the process of development of weak ties between groups to the stronger more cohesive ties that can be seen to emerge from repeated and iterative collaborative activity that happens within, across and between more established communities. Our framework focuses on supporting 4 aspects: Firstly Participation – Encouragement and support for a core group of participants, who contribute regularly and in encourage the engagement and activity of others. Strategies to engage or ‘nudge’ participants to make repeated contributions. Ways of prompting people to contribute into the wider Cloudworks space and draw others back to the designs. Identification of the special roles participants can take on and understanding of the hierarchical structures which we can see are effective in promoting and supporting collaborative activity. Secondly Cohesion – Providing a space that fosters professional and friendly discussion which encourages new, and perhaps inexperienced, visitors to participate. A space where people show a willingness to listen and learn from others. Thirdly Identity – Support for communities in establishing a shared vocabulary and phraseology. A place where participants can start to feel a sense of belonging, or sense of ‘us’. And finally, Creative capability – Ensuring that visitors to the site understand the purpose of what they are doing. Are helped to develop the skills they need to participate in the space. Feel drawn to participate and get involved. A framework so that they feel able to share experiences from a variety of different contexts, contradict and challenge assumptions and establish and articulate links between concepts and ideas?