[DG: Teaching & Learning] Sakai-11 - proposal ideas

Wed Feb 26 12:43:03 PST 2014

Hi Alan,

What do you recommend as the best way for community members to keep up 
to date with the Apereo Analytics Initiative?

I know you guys are working on a Confluence page. Can you please 
announce when that is ready for public eyes?

For those going to the Open Apereo Conference, I believe you will be 
having one or more sessions there as well, correct?

Thanks,
Neal

> Berg, Alan <mailto:A.M.Berg at uva.nl>
> February 26, 2014 at 3:05 PM
> Yes, I agree that is why the Apereo Analytics initiative is an 
> interesting influence. Join in :)
>
> Regards,
> Alan
>
>
> Alan Berg
>
> Innovation working group
> On the use of ICT in Education & Research
> University of Amsterdam
> Postbus 1025 / 1000 BA Amsterdam
> Weesperzijde 190 / 1097 DZ Amsterdam
>
> ________________________________________
> From: pedagogy-bounces at collab.sakaiproject.org 
> [pedagogy-bounces at collab.sakaiproject.org] on behalf of Gregory 
> Guthrie [guthrie at mum.edu]
> Sent: 26 February 2014 21:00
> To: pedagogy at collab.sakaiproject.org
> Subject: [DG: Teaching & Learning] Sakai-11 - proposal ideas
>
> I wasn't sure if this was the best place to post ideas and suggestions 
> for future Sakai versions - but here goes...
>
> I would like to see more analysis tools in next versions of Sakai.
>
> 1) One might include some analysis of faculty and course interactions 
> in the forums - and although defining the metrics would be the most 
> important part of this, perhaps things like (thread depth, average 
> response time, size of responses (to eliminate "me too! and chatter 
> responses), faculty response time, number of 'like's to posts (per 
> student, per faculty), ...).
>
> This would allow one to oversee a group of courses to see how 
> interactive faculty are in their support of a course, and also how 
> engaged in participation students are in a course(s).
>
> 2) A second area would be institutional reporting and accountability. 
> This would include items perhaps like: (student forum submissions (pre 
> student, per course), responses, assignments submitted (%age), date of 
> last interaction, ...). This is important both for QC of course 
> quality per these measures, but also a legal requirement for Federal 
> Financial aid support.
>
> 3) One implementation feature to support this would be more automated 
> ways to extract reporting data from Sakai. The sitestats reports are 
> useful, but very limited in their range and format.
> We have setup one approach to this, where any internal report in sakai 
> can be automatically extracted (csv, xml, json) so that external 
> presentation and analysis tools can be used to better present, 
> integrate, and aggregate it. From that we can then correlate data from 
> various reports and give evaluation and performance tracking tables 
> for each (and all...) courses.
>
> (I think that the Canvas LMS has some nice examples of such data 
> access and reporting tools.)
>
> 4) A system of hierarchical reporting tools for : ( courses, faculty, 
> departments, school, ...) so that administrators could easily QC and 
> track the overall quality of courses using Sakai, perhaps most 
> importantly for DE courses.
>
> If other Schools have already discovered or setup good ways to do 
> this, we would love to hear of it.
> -------------------------------------------
> _______________________________________________
> pedagogy mailing list
> pedagogy at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/pedagogy
>
> TO UNSUBSCRIBE: send email to 
> pedagogy-unsubscribe at collab.sakaiproject.org with a subject of 
> "unsubscribe"
> _______________________________________________
> pedagogy mailing list
> pedagogy at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/pedagogy
>
> TO UNSUBSCRIBE: send email to 
> pedagogy-unsubscribe at collab.sakaiproject.org with a subject of 
> "unsubscribe"
> Gregory Guthrie <mailto:guthrie at mum.edu>
> February 26, 2014 at 3:00 PM
> I wasn't sure if this was the best place to post ideas and suggestions 
> for future Sakai versions - but here goes...
>
> I would like to see more analysis tools in next versions of Sakai.
>
> 1) One might include some analysis of faculty and course interactions 
> in the forums - and although defining the metrics would be the most 
> important part of this, perhaps things like (thread depth, average 
> response time, size of responses (to eliminate "me too! and chatter 
> responses), faculty response time, number of 'like's to posts (per 
> student, per faculty), ...).
>
> This would allow one to oversee a group of courses to see how 
> interactive faculty are in their support of a course, and also how 
> engaged in participation students are in a course(s).
>
> 2) A second area would be institutional reporting and accountability. 
> This would include items perhaps like: (student forum submissions (pre 
> student, per course), responses, assignments submitted (%age), date of 
> last interaction, ...). This is important both for QC of course 
> quality per these measures, but also a legal requirement for Federal 
> Financial aid support.
>
> 3) One implementation feature to support this would be more automated 
> ways to extract reporting data from Sakai. The sitestats reports are 
> useful, but very limited in their range and format.
> We have setup one approach to this, where any internal report in sakai 
> can be automatically extracted (csv, xml, json) so that external 
> presentation and analysis tools can be used to better present, 
> integrate, and aggregate it. From that we can then correlate data from 
> various reports and give evaluation and performance tracking tables 
> for each (and all...) courses.
>
> (I think that the Canvas LMS has some nice examples of such data 
> access and reporting tools.)
>
> 4) A system of hierarchical reporting tools for : ( courses, faculty, 
> departments, school, ...) so that administrators could easily QC and 
> track the overall quality of courses using Sakai, perhaps most 
> importantly for DE courses.
>
> If other Schools have already discovered or setup good ways to do 
> this, we would love to hear of it.
> -------------------------------------------
> _______________________________________________
> pedagogy mailing list
> pedagogy at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/pedagogy
>
> TO UNSUBSCRIBE: send email to 
> pedagogy-unsubscribe at collab.sakaiproject.org with a subject of 
> "unsubscribe"

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/pedagogy/attachments/20140226/be7b47f4/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/pedagogy/attachments/20140226/be7b47f4/attachment-0002.jpg 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1184 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/pedagogy/attachments/20140226/be7b47f4/attachment-0003.jpg 