Tom posts about weblogging / eportfolioing in schools from a “progressive comprehensive school reform” angle and looking towards “a progressive, authentic approach to standards-based assessment”. Good stuff!
Personally I reckon that what he asks for, namely as system which allows him to:
“* View entries for a given course, e.g., English 11, across different sections and teachers.
* View entries related to a specific unit, e.g., quatratic equations.
* View entries related to units which address a common standard, e.g., all units which address the bill of rights.
* View entries by 9th grade students.
* View entries by all students in my advisory.”
Isn’t far off the kind of system that CMSs, Blogs, Aggregation, ePortfolios and Digital Objects Management Systems are going to blend into in the not too distant future… hopefully.
In the meantime though here’s a theoretical hack solution using WPMU and a yet to be released web-based, independently hosted aggregation / email service.
-Using LDAP independent Blog/CMSs are created for each learner
-Using LDAP as well OPML files are generated for class(es) / year / ‘house’ (posh school hangover ;o) etc. These pre-populate the aggregators which are also assigned to individual students (School library also has set of subject specific OPML packages but that’s another area)
-These OPML files are also easily extractable to independent aggregators
-For each course a ‘category’ is automatically created in each individuals students blog… tags are available for each category covering specific units / standards
-These categories and blogs are automatically registered by year, class, advisory, student / musical interest / sporting stuff etc. etc. for easily viewable access.
Naturally these blogs have all the functionality of a sleek CMS, wonderful editing tools, wiki-esque potential for collaboration, simple authentication processes etc. etc. etc. and they’re all hosted behind a school firewall but with the RSS able to ‘get out’.
But I don’t reckon it’s that far off or that hard… where I do think it’ll fall down though is if one systems tries to do it all. The idea above is kind of a WordPress / Plone / Any dbase / Bloglines-esque aggregator type solution, any ‘all-encompassing’ would surely fall over standards / interoperability-wise as well as provide insufficient tools for the job? Perhaps?