April 3, 2008 -- Initial Authoring Call
Date: April 3, 2008
Time: 12pm EDT
- IP Address: 156.56.240.9
- Telephone: 812-856-7060
- Conference Code: 348
- PIN: 72524
Expected Attendees (actual attendees bulleted)
- Mark Breuker <mbreuker@loi.nl>
- Mark Norton <markjnorton@earthlink.net>
Aaron Zeckoski <aaronz@vt.edu>
John Norman <john@caret.cam.ac.uk> - Damian Sobieralski <dsobiera@indiana.edu>
Hannah Reeves <hreeves@rsmart.com>
Daphne Ogle <daphne@media.berkeley.edu>
Colin Clark <colin.clark@utoronto.ca> - Sean Keesler <smkeesle@syr.edu>
- John Hall <hall@udel.edu>
- Karen Tsao <ktsao@stanford.edu>
- Lydia Li <lydial@stanford.edu>
- Michael Korcuska <mkorcuska@sakaifoundation.org>
- Megan May <mmmay@indiana.edu>
Janet de Vry <janet@udel.edu> - Becky Kinney <bkinney@udel.edu>
Karen Kral <karenk@udel.edu> - Mathieu Plourde <mathieu@udel.edu>
- Nancy O'Laughlin <nolaug@udel.edu>
Susan Hollar <shollar@umich.edu>
Joseph Hardin <hardin@umich.edu> - Erica Ackerman <ericaack@umich.edu>
- Noah Botimer <botimer@umich.edu>
- John Leasia <jleasia@umich.edu>
- Sean DeMonner <demonner@umich.edu>
- Beth Kirschner <bkirschn@umich.edu>
- Jim Eng <jimeng@umich.edu>
- Peter Knoop <knoop@umich.edu>
- Angela Rabuck <adehart@rice.edu>
- Omer Piperdi <omer@rice.edu>
Agenda
Our intended purpose in convening this meeting includes the following:
- encourage sharing of information about current work on authoring in sakai
- encourage cross-project collaboration in support of authoring
- begin (or resume?) the conversation about how to improve support for authoring in sakai
- actually improve support for authoring in sakai.
Proposed agenda for today's meeting (not necessarily in this order):
- Review of current work on authoring in Sakai subprojects
- State of the art for authoring outside of Sakai (MSWord? Google docs?)
- Pedagogical issues
- Design of UI features to support web-based authoring
- Possibility of sharing new capabilities across projects
- Admin: Next meeting? JA-SIG? Paris?
Notes from meeting
- Michael encouraged folks to post requirements to wiki page
Review of work - OSP (Noah Botimer)
There are a number of ways to author content in OSP, including structured Forms (Meta-Obj) and Portfolios (varying in degrees of structure/freedom). There is strong interest at the middle, as well as the ends of the spectrum for varied pedagogies in use – all need more "user delight". U-M concentrating on expressive WYSIWYG portfolios with extensive FCKeditor integration. - Sakaibrary
The subject research guides touch on authoring in 2 ways. There is a WSYWIG view of these guides and you can click on individual components to edit them (like Google Docs, Google Notebook). Developing a prototype of this. Second, they would like people to pull the results from using the subject research guides (e.g. a citation or some content) back into the document the user is creating. - Rice--IBM grant
Pulling content from DSpace and Connexions, sequence the content and add descriptions, etc. Also looking at an image repository system. - Rice--Internal materials
Working on a tool to publish 10 years worth of materials for professors to select to show to students. They will then make these materials available to the community. - LOI
Want to see a universal tool for content authoring across Sakai context - Sean (Syracuse)
Ability to pull meta-objs into documents and mark up that document/object. The use case is important for accreditation (ability to search). - Mark Norton – Sousa
Idea is to have a toolkit that allows you to combine content into a page, organize those pages into a presentation order and then bundle those pages into modules and move them around, etc.
Other tools like Melete, OSP, Sakaibrary have a particular structure in mind. Sousa is trying to be general tool without a particular pedagogical end point in mind. Sousa is highly integrated with the Content Hosting/Resources. - Melete
Nobody here from Melete, but is probably the style of content authoring that is most commonly found/used by faculty. - HEC Montreal
ZoneCourse, a tool that does structured syllabus authoring. - ASU
FCK Editor plug-in for browsing entities (e.g. assignments and tests) and adding them to the FCK content. - SCORM
SCORM is a way to get authored content into Sakai. There are a variety of Sakai tools for SCORM. (HKUST, UC Davis and CRIM-Montreal). - LAMS
Other comments
- The whole idea of being able to address activities is crucial, especially in assignments.
- John Norman points out (via Jim Eng) that not all authoring should be inside Sakai.
- Mark Norton
- Common UX elements would help
- Entity support (and other infrastructure items like tagging) are crucial to address.
- LOI – the big challenge is making content in volume and still have a manageable repository of learning objects.
- The FCK editor is not doing the trick. We need a different tool or improvements
Next steps
- Document of current efforts, requirements & dependencies (or link to them at least)
- Delineation of UX, Pedagogy and Technical needs
- Another call in approximately 2 weeks.
- Session in Paris, pre or post conference: Yes!
- Maybe some informal conversation at JA-Sig, not that many people attending