Hi Everybody,
 
I really appreciate Philipp bringing Collaboration topic up. I believe School's health ( including, but not limited to, financial health ) and growth potential depend on Collaboration Capability. Parents are not satisfied to see the schedule of the classes. They request to know methodology and content of what is taught. The same applies to Enrollment and Donation process.
 
I believe Collaboration is the most essential element of School Software. It essentially exposes School Administration data ( including calendar, class schedule ),  School Programs ( including syllabus ), Student Grades, etc., etc. to all Collaboration Categories of Users involved in a School Process ( School Administrators, Teachers, Students, Parents, Educational Community, potential donors, including school's Alumni and more ).
 
I think "integration with a scheduling program (perhaps organized by class)" is not sufficient. There should be many integration points:
 
1. To Instructors
2. To School Departments ( Math, English, etc. )
3. To School Administrators ( Principal, Director )
4. To Grade System ( to be able to see trends to make forecasts )
5. To Class ( to be able to see Curriculum/Outline, Syllabus )
6. To Governing Body ( Department of Education )
7. To Other Schools, which deployed the same tool ( and other tools if the share common
    metadata )
 
I am sure that's not all.
 
Thanks,
Arkady


Philipp Schröder <[EMAIL PROTECTED]> wrote:
Hi Schooltoolers and CanDoers,

There is an interesting thread on the Edubuntu mailing list. I forward
it here, because I think it is relevant to SchoolTool & CanDo.

The most relevant parts are the last 5 paragraphs (I kept the others to
give some context).

Greetings, Philipp

-------- Original Message --------
Subject: Re: collaborative content submission
Date: Fri, 30 Sep 2005 00:04:08 -0500
From: Ryan Michael <[EMAIL PROTECTED]>
Reply-To: Ryan Michael <[EMAIL PROTECTED]>
To: Miles Berry <[EMAIL PROTECTED]>
CC: [email protected]

Ryan Michael wrote:
> (comments inline)
>
> Miles Berry wrote:
>
> Moodleforge, which is a schoolforge.org.uk
> project, is about using
>
> Moodle to provide communication and collaboration tools for groups of
> educators, in much the same way as Edna groups do down in Oz (see
> http://www.groups.edna.edu.au/course/view.php?id=40), but with the
> expectation that at least some of these groups will use it as a platform
> to work collectively at creating moodle courses, with, it is hoped,
> creative commons licences.
>
>
> this is an interesting site, but it's a little sparse on content.
>
> I for
> one would prefer to polish things a bit before they make it out into a
> shared repository. More interesting would be to leaverage the
> collaborative principals underpinning wiki, or good old cvs, for
> e-learning materials - this is kinda what we hope to achieve with
> moodleforge in part, but moodle doesn't yet have any real version
> control.
>
>
> of course nobody wants to publish things that are thrown together (not
> in a bad way of course), but if they're good enough for your students
> they might also be good enough for someone else's students - you've got
> to start somewhere when creating a body of community maintained
> materials, right?
>
>
> John Ingleby wrote:
> > If not, then Wikibooks - http://wilkibooks.org
> - has much to offer, and
> > is another collaborative venture.
>
>
> thanks for this link - i saw this a year or so ago but never really
> looked at it. it seems to be well maintained and quite diverse. i'm
> not sure if it would be suitable as a primary course text in some areas,
> but it look like it would provide good support materials.
>
> it seems like collaborative projects fail for one of two reasons: either
> there are too many versions of the same resource, or contributing takes
> too much work. wikibooks (and wikipedia) do a good job of alleviating
> both problems because they are essentially the only resources of their
> type and contributing is immediate and doesn't require you to sign up
> for an account.
>
> i guess what's less obvious about the success of wikis is that they
> tightly integrate the processes of using and contributing to them. i
> think this is the primary attribute lacking from the examples of shared
> teaching resources i've been able to find (and the ones you've been kind
> enough to link to) - they are too divorced from the everyday process of
> developing lesson plans, hand-outs, tests, etc.
>
> the moodle resources are clearly the most successful because they allow
> teachers to develop presentation materials, making contributing a simple
> matter of submitting the file.
>
> here's what i would think could be improved:
> -robust tagging and metadata for indexing/searching
> -revisioning and forking
> -integration with a scheduling program (perhaps organized by class)
> -semester/year-long course timelines linking to any materials used
> (syllabus, handouts, wikibooks, quizzes/tests, homework, etc)
> -some type of discussion forum, either topical (typical BBS) or
> organized by material (wikipedia)
> -even more transparency to the user
>
> perhaps a solution would be to write a wrapper program for most of the
> administration tools included in the distro which would 'contextualize'
> any work you did by inserting metadata regarding the class, date, your
> name and the name of your school, etc. it could serve as a launcher and
> intercept file i/o while providing a consistent metadata schema.



--


:::::::::::::::::::::::::::::::::::::::::::.

Philipp Schroeder
DIN15 / Information Architecture & Interaction Design
www.din15.org, [EMAIL PROTECTED]
_______________________________________________
Schooltool mailing list
[EMAIL PROTECTED]
http://lists.schooltool.org/mailman/listinfo/schooltool


Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort.
_______________________________________________
Schooltool mailing list
[EMAIL PROTECTED]
http://lists.schooltool.org/mailman/listinfo/schooltool

Reply via email to