ideas


The need for rapid development of a PLE prototype have loads us to the decision of running the PLE on top of Google Apps infrastructure because it provides at no cost most of the common features needed to build the PLE: iGoogle, gadgets and Google App Engine.

iGoogle is the front-end of the corporative PLE. It provides access to a wide variety of widgets within a Locally Controlled Environment (LCE) represented by Google Apps. The LCE allows the institution to preconfigure a set of fixed widgets with institutional tools, services and information channels customized according to the profile of the user, but also allows users to add their own preferred widgets.

Besides, iGoogle offers some features that seem to be very suitable for PLEs: open social, canvas view, widget sharing and automatic topic-based tab creation. Open Social defines a common API for accessing a social network’s users and resources. Canvas view enables the visualization of powerful full-page widgets that can be very useful on browser-based interfaces. Widget sharing refers to the ability for sharing a widget and the data within it. With automatic topic-based tab creation you can ask iGoogle about a topic (e.g.: “learn english”) and it will automatically add a tab with widgets based on the topic keywords.

Own-programmed gadgets constitute our widget platform for the integration of an increasingly number of back-ends (institutional and external services) into iGoogle. In order to do that, gadgets make use of XML, JavaScript, open APIs and REST paradigm. The open nature of these technologies allows the placement of widgets not only at iGoogle, but also at a wide range of platforms.

Google App Engine is our cloud-computing platform for the generation of server-side applications that extract and analyze the collective intelligence that emerges from the data and the interaction of many uses. These applications will implement the algorithms for building new services that detect similar elements (users or resources), recommend resources, discover groups, customize search engines, etc.

Authoring tool support is not provided by Google Apps infrastructure. Therefore, we plan to integrate eXe e-learning XHML editor into the framework. eXe is an IMS and SCORM compliant authoring tool configured as an standalone application based on a client-server architecture. We plan to be split the server-side from the client-side. A content manager will be added to the server-side in order to distribute learning resources among the institutional and external services integrated within the framework. The client-side will be embebed as a widget and placed at iGoogle.

Thanks to Ramón Ovelar ( again ;-) ) I found an interesting presentation of Malinka Ivanova about the use of start pages as Personal Learning Environments (PLE). These are the slides:

—–

Posted in Gabinete de Informática on 2008/04/24

A personal learning environment framework (PLEF) needs to fulfil the following requirements:

  • Personalisation: PLEF should provide the learner with ability to incorporate myriad of tools and services; and ability to determine and use the tools and services the way she deems fit to create her own PLE, adapted to her own situation and needs.
  • Social features: PLEF should offer means to connect with other personal spaces, so that learnres can engage in knowledge sharing and collaborative knowledge creation. Social features such as tagging, commenting, and sharing have to be supported.
  • Social filtering: The problem with a knowledge-pull approach is information overload. Therefore, there is a need for “filters” (e.g. recommendation, rating, ranking, review, votes, attention metadata) to help learners find quality in the Long Tail.
  • Incorporate various Web 2.0 concepts and technologies. The web as platform, mashup of services, widely use of widgets, content aggregation, opened identity, small pieces loosely joined Web and rich user experience are the concepts which should build up PLEF. Web 2.0 technologies, such as, RSS, openID and social tagging have to be adopted as the basis to develop PLEF.
  • Flexibility and extensibility, such that new services/modules can easily be plugged into the basic framework. PLEF should be based on a Web Oriented Architecture (WOA) that makes it possible to extend the framework with new Web modules. It should also provide a public API that can be used by third party applications.
  • Web browser platform: With web browser as the platform, the independence of operation system can be assured. This also enables PLEF to aggregate and integrate third-party services.
  • Aggregation/Mashups: PLEF should allow a learner to aggregate and remix different learning artefacts (e.g. feeds, widgets and media).
  • Ease of use: PLEF should provide rich experience with e.g. AJAX support. A learner should be able to copy&paste and drag&drop elements to personalize and manage her PLE with minimum effort.

—–

Posted in Mohamed Amine Chatti’s ongoing research on Technology Enhanced Learning on 2008/02/18

Por muy diferente que sea el trabajo diario de un empleado de una empresa privada del de un empleado de universidad, ambos tienen necesidades comunes por las que el uso de una red social o de un PLE puede resultar igualmente provechoso.

Desde mi punto de vista, el empleo de un PLE podría facilitar, agilizar y aumentar la eficiencia de mi trabajo por poder distoner de un entorno donde mantener concentrada información que en la mayoría de los casos se encuentra dispersa y que es de naturaleza diversa. En mi caso particular, el PLE podría estar compuesto de la siguientes recursos, widgets y eventos:

  • Calendario/Agenda Lotus Notes y/o Google Calendar.
  • Alerta de eventos marcados en el calendario según el periodo de antelación de alerta preestablecido en el calendario para cada evento.
  • To do: lista de tareas. Deben registrarse automáticamente y de manera transparente, los eventos marcados en el calendario una vez que haya saltado la alerta.
  • Correo Lotus Notes. Debe permitir leer el correo entrante, responder, y escribir nuevo correo saliente desde el propio widget.
  • Base de Datos Documental Lotus Notes. Debe permitir conocer cualquier modificación que alguien realice sobre las carpetas de la gestión documental en las que nos demos de alta. Debe además mostrar los documentos que tenga pendientes de aprobar.
  • Notas. Deben poder almacenarse anotaciones que puedan ser después adjuntadas directamente a un correo o posteadas en un blog.
  • Editor de texto y excel. Debe permitir compartir los documentos, almacenarlos en local, almacenarlos en servidor o unidad de red, colgarlos en la base de datos documental Lotus Notes, postearlos en un blog …
  • Foro SDN SAP. Debe permitir ver el foro SDN SAP de las categorías deseadas, y ver como bandeja de entrada los mensajes de respuesta que hayamos recibido. Debe disponerse de una gestión de alertas para los mensajes sin leer de la bandeja de entrada.
  • Notas OSS SAP. Debe poder gestionarse la bandeja de entrada y de salida de las notas oss enviadas a SAP para poder revisar las incidencias reportadas a SAP así como su status en la bandeja de salida y las respuestas en la bandeja de entrada. Debe disponerse de una gestión de alertas para los mensajes sin leer de la bandeja de entrada.
  • Gestor de incidencias. Debe disponerse de alertas de primer nivel en el momento de la recepción de una incidencia en la que se me haya establecido como responsable y de alertas de segundo nivel en el momento de la recepción de incidencias en las que se me haya establecido como partícipe pero no responsable. Debe poder establecerse la periodicidad del recordatorio de incidencia pendiente en forma de evento/alerta. Debe permitir responder a las incidencias, así como actualizar su status directamente desde el PLE.
  • Gestor del grafo social. Debe poder consultarse el listado de los empleados, el organigrama de la empresa, los perfiles de cada empleado (datos profesionales como el puesto o cargo ocupado en la organización, consulta y descarga de su curriculum vitae, y si se han indicado, también los datos personales), así como el listado de teléfonos.
  • e-Portfolio y curriculum vitae. Debe permitir consultar o descargar mi curriculum vitae, realizar modificaciones al mismo desde el PLE y que según la configuración del e-portfolio se realicen actualizaciones de manera automática y transparente. Este curriculum vitae deberá estar disponible en los distintos formatos que se establezcan y según distintos niveles de detalle preestablecidos.
  • Diccionario y pequeño traductor en distintos idiomas.
Las actividades realizadas a través de mi PLE deben ser empleadas para una actualización automática de mi e-portfolio. Para ello, habrá sido necesario configurar o parametrizar los criterios de actualización del mismo, para establecer qué es lo que deseo que sea automáticamente recogido en el e-portfolio. También podría interesar que pudiera establecer qué es lo que deseo que sea propuesto para incluir en el e-portfolio y que requiera mi autorización antes de hacerse efectiva la actualización pública del e-portfolio. Algunas de las posibles actualizaciones automáticas del e-portfolio aunque requieran de mi autorización para su inclusión en una u otra versión pública del e-portfolio y como consecuencia en los distintos formatos de curriculum vitae generados a partir del e-portfolio, son las siguientes:
  • Participación y aportaciones en el foro SDN SAP. Puede recoger tanto la temática de las aportaciones realizadas como los puntos conseguidos según las gratificaciones obtenidas.
  • Documentos compartidos generados cuando el índice de impacto de estos sea suficiente. Este índice de impacto puede establecerse según un criterio tan sencillo como el número de lecturas del documento, o según un criterio más complejo perp más exhaustivo como el número de veces que ese documento ha sido a su vez compartido con otros por sus lectores, o enviado por correo o posteado en blogs, wikis y foros, o almacenados en bases de datos documentales o unidades de red por parte de sus lectores.
  • Incidencias resueltas según el gestor de incidencias cuando éstas sean consideradas de un grado de complejidad o importancia suficiente como para ser incluidas en el e-portfolio.
  • El perfil actualizado a través del gestor del grafo social deberá actualizar automáticamente el perfil incluido en e-portolio.

This is the PLE version review of a previous post.

Below I’ve rewritten Will’s tale using the terminology of some of my design wireframes:

The wireframes draw quite heavily on several application designs, notably Shrook and Colloquia as well as my earlier more web-oriented E-Learning Aggregator design. Note that this design is part of my thoughts for the JISC PLE Reference Model project, so I’m not actually building it, its just part of a specification for what a PLE might be.

Note that the examples in the figures aren’t the same as the story, as I created these wireframes before reading Will’s post, but hopefully most people reading this can figure out what on earth is meant to be going on.

English teacher Tom McHale sets down his cup of coffee and boots up the computer at his classroom desk. It’s 6:50 a.m., and he’s got about 45 minutes before his sleepy Journalism students will begin filing into his classroom.

He opens his iBook and launches the PLE program. In the Resources view, he does a quick scan of the New York Times headlines that are displayed in the list and clicks on one of the links to read a story about war reporting that he thinks his student journalists might be interested in. Tom right-clicks the item and selects “Share…”, then adds a bit of annotation in the dialog box that comes up, and finally selects the “journalism resources” conduit to post it to his Journalism Resources link blog on the school server. With this step, he archives the page for future reference and automatically has the link and his note appear in the “Journalism Resources” feed his journalism students subscribed to at the beginning of the course, when they joined the “Journalism” activity that Tom created and shared.

Next, he switches to the Activities view and selects the “Journalism” activity, and in the Resources group he scans summaries that link to all the work his students submitted to their Weblogs the night before. Seeing one particularly well done response, he right-clicks the item, selects “Share…”, and posts a positive comment about her submission in his Journalism class blog. (He notices, scanning through the items, that a couple of his students have already left some positive feedback to the author on their blogs as well.) He selects “Share…” again, this time first publishing it to his “Best Practices” conduit (the target of which is also one of the sources in the Journalism activity, for students to read and discuss), and then using a separate conduit he has created for a place he uses to keep track of all of the best examples of student work. It’s 7:00.

After taking a sip of his coffee, Tom flips back to the Resources view, and takes a look at his research feeds (handily grouped under “Research”). He’s been asked to keep abreast of the latest news about technology and teaching writing, and this morning he sees his Google search feed has turned up a new version of “Write Outloud.” He clicks the link, reads about the new version on the site, and then decides to “Share…” it using a link blog set up for all of his department colleagues to share. In the “Share Resource” dialog box, he writes a couple of lines of description about how it might benefit the department, and then tags it “Technology” before posting it (this means the server hosting the department blogs automatically archives it to the tech page of the English Department Weblog). Later that day, all the members of his department will see his link as well as any others his colleagues may have added as a part of their daily scan of their PLEs, aggregators, or however they get their news. He also decides he wants to create another group for the words “journalism” and “weblogs.” From the “Resources” menu he chooses “New > Smart Group”, and enters the criteria. The new Smart Group will select items from the sources in the “Research” group containing those words.

At around 7:05, back in the Activities view, Tom goes to the “American Literature” activity and creates a post about an assignment on symbolism for his major American literature class, attaching the assignment document to the post. He right-clicks the completed post and selects “Publish > American Lit Best Practices”, which publishes the post using the conduit (account settings) for his American Literature Best Practices blog. The rest of the American Lit teachers will be able to see his published artifact so that they can use in their own classes. He selects “Publish > American Lit Class – Homework” from the context menu, which posts the assignment, with a “Homework” tag added to it, to the blog account he uses to communicate with students in the class . The school has a special aggregator service set up that scans all its teacher’s class blogs for entries tagged “Homework”, and automatically sends an email to relevant parents who have requested it, saying that their son or daughter has homework to do that evening. E-mails also get sent to a couple of counselors who are tracking at risk students.

About 7:15 Tom decides to scan the latest feeds from the school Weblogs he is subscribed to, which he can see from the Resources view (he previously put them all in a group called “School – Misc”). He sees that the basketball team won the county tournament, the new edition of the school paper is online, and that the superintendent has posted important information about an upcoming safety drill. He clicks through to read the entire post, and then leaves a comment suggesting a way to alleviate crowding in the hallways during the drill. (He sees a parent also has a suggestion about the timing.) He decides that he doesn’t want to scan the soccer team news any longer, so he selects the “Soccer” feed in the sources list and presses backspace. He does notice, however, the “New Feeds” feed from the school lists a new “Tech Deals” feed that the tech supervisor has created. Since he’s looking for a new home computer, he clicks to subscribe to it.

At 25 after, he notices that two of his students have posted the interview they did with the principal. He clicks the “download and sync” button on the post to add it to his iPod. He lifts it out of his cradle and puts it in his briefcase so he can play it on his car stereo during his ride home after school. If it’s good, he’ll upload it to the school podcast page where the 135-odd subscribers (mostly parents) will automatically receive it so they can hear it and hopefully get most of their questions about the new building project answered.

With just a few minutes left before his first class, Tom goes back to the “American Literature” activity, selects “New > Document” and types in a few notes about an idea he had for the lit project his students are completing next week. Now that his volume of e-mail has been drastically reduced, he scans the few messages in his in box, takes a last gulp of coffee, and opens his classroom door to the sound of happy students.

—–

Posted in Scott Wilson’s Worklog on 2005/08/31

A PLE is not an application, but a comprised of all the different tools and services we use in our everyday life for learning. If we are to use these different tools and services, then open internet standards and lightweight propietary APIs are critical for allowing one application to talk to another. So, rather than monolithic design driven VLE, PLE is based on the idea of “small pieces, loosely connected”.

Scott Leslie  mentioned that one option for the PLE is to enhance the browser into a complete personal learning toolkit using plugins and other technologies such as Mozilla’s XUL. Something we’ve seen recently with Flock.

—–

Posted in the personal learning environments blog on 2006/04/11

Cappuccino U, available from Spotted Cow Press is short CC-licenced book e-book by Jerome Martin. It is a pleasant flow of a read that discusses personal learning and the role of third-spaces. It’s a great introduction to learning for the 21st century.

Cito a continuación algunas de las ideas del libro:

“This e-book is about a new style of learning in which innovative people have combined new information technology with traditional ways of learning to develop a new personally-driven approach to learning. I happens predominantly in “the third place”, a location that is neither home nor office. [...] People gather in their favourite third places to work [...] independently or in groups; some of them use computers which may or may not be linked to the web; some are taking courses online and others are writing books like this one. The third place is usually a coffe house, on which is designed to serve this particular audience. [...] This is Cappuccino U.

[...]

Cappuccino U is a metaphor for a new approach to learning based on community, networking, self-study, distance education and technology. [...] Capuccino U is your university, your learning facility; you ar in control of it and your learning. [...] Capuccino U offers mentorship, small group learning and seminar, solitary learning, distance education, e-books, the possibility of formal degrees and the opportunity for asynchronous learning. [...] There are three possibilities for this approach to education: informal group learning, informal individual learning and directed individual learning administered by an institution.

[...]

Information technology has provided us with new opportunities for learning through the electronic media and the Internet but most of us and most of our learning institutions have been slow to take full advantage of it. [...] The traditional education system cannot be expected to provide learning for everyone, everywhere, all of the time. Knowledge is growing so quickly in so many fields that educators cannot remain current in their fields. [...] We need just-in-time learning to meet our needs.

[...]

Cappucino U provides a virtual office. Simply find a Third Place with wireless or other connections and you can check your e-mail, download files and send documents to others in your organization. [...] You can sit in an internet café (Cappucino U) and learng by accessing a course on your wireless-equipped laptop. Carry your books on your hard drive. Use podcasting for information, knowledge and courses.”

—–

Posted in Harold Harche’s blog on 2006/11/26

Seguimos con dibujando entornos de aprendizaje utilizando el blog y RSS como marco. En este caso, recopilo una idea aplicable a la coordinación/evaluación de asignaturas, departamentos, centros, etc.

[...] At this school, as in many, teachers are required to submit lesson plans to the administration each week. Lesson plans are frequently scanned, because the school leadership feels a need to know the day-to-day instructional culture of the school: what students are learning, and how they are learning it. The plans are then filed.

But how might this process be automated in a way that is flexible, locally manageable (at the teacher level), and value added? We might:

  1. Require all teachers to stop submitting lesson plans in paper, and instead, keep a daily Weblog, where they would post a succinct description of what they taught and how they did it. In addition, teachers would be required to post some reflection on the lesson’s success, and what they might have done differently. The key here is succinctness, not only for the say of writing, but also for reading.

  2. With a selected aggregator, the school leadership would capture all of the teachers’ lesson reflections and scan them appropriately for the above stated reason. They would also comment periodically with praise, suggestions, insights, and other statements, understanding that comments will be public to the rest of the schools teachers.

  3. Teachers would also be using aggregators. They would probably subscribe to, and compile the lesson blogs from all of the educators in their department. But I suspect that certain teachers are going to emerge as especially skilled at innovative/effective lessons, or at least as entertaining bloggers. The teachers would likely be subscribed to, from outside their departments.

  4. Software would also be employed that could generate dynamic RSS feeds. For instance, if a teacher is looking for insights on using spreadsheets in instruction, they might define a feed that aggregates all lessons that include the keyword, “spreadsheet”. Technorati and other blog wayports can actually do this now, but a more local and customizable solution may be advisable.

  5. With aggregators in use now, the school leadership would start using them for blog-based announcements, meeting notes, policy information, calendars, and other important information. Other special departments such as sports, theatre, music, art departments, and other school culture entities would use blogging to communicate.

  6. Some how, school leadership (and other participants) would be able to look at subscriptionship. Who’s being subscribed to? Who are school employs paying attention to? This is not specifically for professional evaluation. Instead, it would give leadership an interesting and useful picture of the school’s culture, and reveal potential pivot points among the faculty, for improving the culture in useful ways.

Now this all sounds a bit complicated, and it isn’t simple. Managing its assembly, introduction, implementation, and support would require some expertise and vision on someone’s part.

* PROTIC: the instructional technology facilitator also collects from each teacher three lesson plans a month that the teacher has identified as a potent example of technology integration. These lesson plans are combined into the school’s intranet site for reference by all teachers.

—–

Posted in 2¢ Worth on 2005/08/19

Next Page »